01 /
How long should the business plan be?
Long enough to support the decision. A short investor deck and a detailed operating plan can use the same structure at different depth.
Business-plan template
Write a plan,
built on evidence
and real operating choices.
Connect market scope, service design, driver supply, demand, compliance, technology, and finance in one plan your team can test.
8 sections
A complete operating-plan structure
Evidence first
Source market and financial assumptions
One app
Model the real unified mobile product
Scenario based
Use ranges instead of invented certainty
By Waslni Editorial TeamPublished · Last updated · 9 min readBusiness plan
A useful business plan connects a specific customer problem to an operating model and a financial model. It should not copy market-size, driver-cost, conversion, or revenue figures from a generic article.
Document the product accurately. Waslni uses one role-aware mobile app for rider and driver experiences, quick administration inside the app, and a full web dashboard. App Experience can show rides only, delivery or shops only, or both.
Every important assumption should name its source, date, owner, downside case, and validation method. Replace assumptions with real pilot data as soon as the operation starts.
Copyable working template
Fill one row
before writing each section
The prompts below are designed to be copied into your planning document or spreadsheet. Do not leave “TBD” without an owner and due date.
Ride-hailing plan evidence register
Create one row per material decision. Add the source URL or interview reference, source date, assumption owner, validation deadline, and the action taken if the downside case occurs.
| Plan section | Decision to write | Evidence to attach | Downside case | Accountable owner |
|---|---|---|---|---|
| Customer and city | First service area, primary trip problem, target user, operating hours, and current alternative. | Interview notes, observed journeys, regulator boundary, and service-area map. | Demand is concentrated elsewhere or the selected hours cannot be supplied. | Founder / market lead |
| Supply and service | Eligible vehicle classes, initial driver cohort, onboarding standard, availability, dispatch, and support process. | Driver interviews, document requirements, supply-by-hour table, and pilot roster. | Pickup time or completion remains unstable at planned demand. | Operations lead |
| Legal and risk | Legal operator, licences, insurance, privacy roles, payment responsibility, incidents, and customer terms. | Current authority links plus dated advice from qualified local specialists. | Approval is delayed, a service is restricted, or insurance terms change. | Legal / compliance owner |
| Product and vendors | Enabled services, roles, fares, payments, integrations, data boundaries, support, and exit plan. | Demo acceptance record, written scope, security review, contract, and tested export. | A critical workflow or integration misses the pilot date. | Product / technology owner |
| Unit economics | Revenue and every variable cost for one completed trip, segmented by zone, service, payment, and time. | Local quotes, contracts, payment terms, incentive rules, and pilot ledger. | Lower completion, higher incentives, refunds, or payment cost. | Finance lead |
| Go-to-market and gates | Acquisition experiment, referral rule, partner plan, weekly scorecard, runway, pause rule, and expansion gate. | Campaign budget, experiment design, cohort results, cash forecast, and signed gate review. | Acquisition, retention, service quality, or cash falls outside the approved range. | Growth lead + executive sponsor |
Minimum contribution formula
Contribution per completed trip = collected trip revenue − driver fulfilment − payment cost − incentives − refunds/credits − variable support − other variable trip costsKeep taxes and pass-through amounts explicit. Run conservative, expected, and favourable cases, then replace each assumption with actual pilot ledger data.
Eight plan sections
A plan your team,
can test and update
Use the structure for internal planning, fundraising, or lender review, then adapt the detail to the audience.
01 /
Section 01
Customer problem and positioning
Define the city, customer segment, current alternative, unmet need, and why your service can solve it. Use interviews and observed trips rather than slogans.
02 /
Section 02
Market scope with sources
Build a bottom-up estimate from service area, reachable customers, trip frequency, and realistic adoption. Cite every external figure and show a range.
03 /
Section 03
Product and App Experience
State whether the launch is rides only, delivery or shops only, or combined. Describe one rider-and-driver app, in-app operational administration, and the full web dashboard.
04 /
Section 04
Driver and operations plan
Explain recruitment, registration, document review, training, support, availability, quality control, and ownership of daily decisions.
05 /
Section 05
Customer acquisition and retention
Describe channels, message, budget rules, referral assumptions, partnerships, support, and the experiments that will measure repeat use.
06 /
Section 06
Legal, risk, and security plan
Cover local transport licences, insurance, tax, privacy, data handling, payment responsibilities, incidents, fraud, and dependency risks with qualified advice.
07 /
Section 07
Unit economics and cash plan
Model fare revenue, commissions, incentives, payment costs, support, taxes, refunds, platform costs, and cash timing. Use base, downside, and upside scenarios.
08 /
Section 08
Milestones and decision gates
Tie spending and expansion to evidence: configuration complete, pilot accepted, service quality stable, unit economics understood, and local approvals current.
Planning questions
Clear answers
for founders and operators
02 /
Where should market numbers come from?
Use current primary sources where possible: regulators, statistical agencies, payment providers, store data, surveys, and your own pilot. Record the date and limitations.
03 /
Can I use generic MENA unit-economics benchmarks?
Only as clearly labelled context. Local fares, commission, incentives, payment costs, taxes, and driver behaviour vary too much for a generic benchmark to run the model.
04 /
How should technology appear in the plan?
Describe the real product scope and commercial model. For Waslni, model one mobile app, two administration surfaces, enabled modules, integration costs, platform fees, and operator-owned launch work.
05 /
Does Waslni provide legal or investment advice?
No. WASLNI LTD provides software. Use qualified local advisers for licensing, tax, financial modelling, securities, and investment decisions.
Test the product assumptions
Open a demo,
and update the plan
Review the unified app, App Experience, registration, service types, permissions, and administration before finalising costs and milestones.