T-Ride Taxi Hailing Platform Discovery Form

Alphatech Developers — Help us understand your ride-hailing platform vision, operational goals, target users, and technical requirements so we can prepare an accurate project proposal and development roadmap. Required fields are marked *.

← Back

Thank you for your response. ✨

Section 1 — Client Information

We start with who you are and how to reach you. This information is used for proposals, clarification calls, and project updates throughout development.

Primary contact for this ride-hailing project.

Enter your company / startup name.

Business email for proposals and project updates.

Include country code if outside Kenya.

Include country code if outside Kenya.

Enter your country.

Enter your city / primary operational area.

Preferred Communication Method

Select all channels you actively use.

Do you already own a business or startup?

Helps us understand your current operational stage.

Do you already have branding?

Select all assets you already have.

Section 2 — Project Overview

Tell us about your ride-hailing vision, target market, and what makes your platform different from existing players in Kenya and Africa.

Enter your platform / app name.

Provide details for: Describe your business idea in detail.

Provide details for: What problem does your platform solve?.

Provide details for: Who is your target audience?.

Provide details for: Countries / cities you intend to operate in.

Platform type

Select all options that apply.

Enter your other platform type (if selected above).

Competitors that inspire your platform

Select all options that apply.

Enter your other competitors (if selected above).

Provide details for: What makes your platform unique?.

Section 3 — Business Model

Your revenue model and driver structure shape commissions, wallets, fleet tools, and admin workflows.

How will your platform generate revenue?

Select all options that apply.

Enter your other revenue model (if selected above).

Driver type

Select all options that apply.

Will you support

Select all options that apply.

Commission type

Select all options that apply.

Promotions / referrals planned?

Choose one option.

Section 4 — User Types & Roles

Different apps and dashboards may be needed for riders, drivers, fleet managers, dispatchers, and admins.

User roles needed

Select all options that apply.

Different permissions per role?

Choose one option.

Provide details for: Custom user roles (if any).

Section 5 — Passenger App Features

Select features for the rider/passenger mobile app. We can phase features for MVP vs later releases.

Passenger app features

Select all options that apply.

Provide details for: Custom passenger features.

Section 6 — Driver App Features

Driver app capabilities including KYC, earnings, and safety tools.

Driver app features

Select all options that apply.

Manual driver approval?

Choose one option.

Drivers upload documents through the app?

Choose one option.

Fleet owners manage multiple drivers?

Choose one option.

Section 7 — Ride Management & Operations

How rides are requested, assigned, priced, and cancelled.

Ride timing

Select all options that apply.

Ride categories

Select all options that apply.

Enter your other ride categories (if selected above).

Users choose drivers manually?

Choose one option.

System auto-assigns drivers?

Choose one option.

Bidding / inDriver-style fare negotiation?

Choose one option.

Surge pricing?

Choose one option.

Fare types

Select all options that apply.

Provide details for: Cancellation policy requirements.

Enter your driver timeout duration.

Enter your ride radius logic.

Peak-hour pricing support?

Choose one option.

Section 8 — Payments & Financial Systems

Payment methods and financial flows — especially M-Pesa for the Kenyan market.

Preferred payment methods

Select all options that apply.

Platform financial features

Select all options that apply.

M-Pesa integration type

Select all options that apply.

Auto-deduct commissions?

Choose one option.

Track driver balances / debts?

Choose one option.

Section 9 — Real-time & Map Features

Maps, live tracking, and routing power the core ride experience.

Preferred map provider

Choose one option.

Map / real-time features

Select all options that apply.

Live trip sharing with contacts?

Choose one option.

Section 10 — Safety & Security

Safety features for riders, drivers, and platform trust.

Safety features

Select all options that apply.

Provide details for: Market-specific safety concerns.

Section 11 — Admin Dashboard & Operations

Back-office tools for your team to manage rides, users, revenue, and support.

Admin dashboard features

Select all options that apply.

Multiple admin / staff roles?

Choose one option.

Section 12 — Notifications & Communication

How the platform notifies users and enables rider–driver communication.

Notification channels

Select all options that apply.

Communication features

Select all options that apply.

Section 13 — Design & Branding

Visual direction for passenger, driver, and admin experiences.

Preferred design style

Select all options that apply.

Enter your preferred color palette.

Provide details for: Inspiration apps / websites (URLs).

Do you already have UI/UX designs?

Choose one option.

Screenshots, Figma exports, or PDFs — always available in this step.

Section 14 — Technical & Platform Requirements

Platforms, scale, and integrations we should plan for.

Platforms needed

Select all options that apply.

System should support

Select all options that apply.

Expected user scale

Choose one option.

Provide details for: API integrations needed.

Provide details for: Existing systems to integrate with.

Section 15 — Hosting, Maintenance & Scalability

Ongoing infrastructure and support expectations after launch.

Hosting setup needed?

Choose one option.

App deployment support needed?

Choose one option.

Ongoing maintenance required?

Choose one option.

Cloud infrastructure management needed?

Choose one option.

Analytics / monitoring systems needed?

Choose one option.

Architect for future scaling?

Choose one option.

Section 16 — Project Timeline & Budget

Timeline, budget, and how you want to engage Alphatech.

Desired launch timeline

Choose one option.

Project stage

Choose one option.

Enter your approximate budget in KES (e.g. Ksh 500k – 1M, Ksh 1M – 5M).

You are seeking

Select all options that apply.

Section 17 — Final Notes

Anything else we should know before preparing your proposal.

Provide details for: Additional comments or requirements.

Provide details for: Biggest concern about this project.

Briefs, competitor screenshots, or technical documents (optional).

Select one option.

Confidentiality: Information you share is treated as confidential and used only to prepare your project proposal. We are happy to sign an NDA before deeper technical discussions.

Section 1 of 17