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
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
Last updated · July 20269 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.
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.