Service
Startup business plans for Jeddah founders
Early-stage plans are judged less on certainty than on clarity: what is known, what is assumed, and what the next round of money is meant to prove.
- Built around assumptions and milestones, not confident prose
- Runway and use of funds modelled month by month
- Honest about what has not been proven yet
- Works alongside a seed or pre-seed deck
What is different at the start
An operating business can be described. A startup has to be argued. The document therefore spends more space on the problem, the customer and the evidence — and less on organisational detail that does not yet exist.
The three questions a seed-stage reader is really asking:
- Is this a real problem that enough people will pay to solve?
- Why is this team the one that gets to solve it?
- What does this money prove, and what happens after it is spent?
Structure for an early-stage plan
| Section | Emphasis at seed stage |
|---|---|
| Executive summary | The problem, the solution, the ask, what it buys |
| Problem and customer | Specific evidence, not a category description |
| Product | What exists today, what is next, what is deliberately out of scope |
| Market | Bottom-up sizing and a credible entry wedge |
| Business model | Price, cost to serve, margin logic and path to repeatability |
| Traction | Pilots, LOIs, waitlists, revenue — precisely described |
| Competition | Real alternatives, including "do nothing" |
| Team | Why these people; which gaps the raise fills |
| Financial plan | Runway, burn, milestones, scenarios |
| Risks | The risks that could end the company |
Milestones instead of forecasts
Pre-revenue projections are usually fiction dressed as planning. A more useful approach is to model what each funding tranche is meant to achieve, and what the numbers look like if it does.
For example, the model may show three states:
- Base case: pilot converts to paid usage at the assumed rate, hiring follows the plan.
- Slow case: conversion takes twice as long, runway shortens, hiring pauses.
- Strong case: conversion is faster, the next raise can be delayed.
Each state has a trigger and a consequence. That is more useful to a founder than a five-year revenue line, and more credible to an investor.
Runway and use of funds
The model must answer: how many months does this money buy, at what burn, and what has to be true to reach the next milestone before it runs out.
That requires:
- monthly cash flow for at least 24 months;
- hiring plan with salary burden, not just headcount;
- cost of product development and infrastructure;
- working capital assumptions if the business invoices rather than charges upfront;
- a stated contingency.
A plan that shows 18 months of runway with no contingency is not conservative, it is unexamined.
What I need from you
- The deck or a written description of the product.
- Any evidence of demand, however early.
- The intended raise and instrument.
- Hiring and cost assumptions.
- A view of the next 12–18 months of milestones.
If those do not exist yet, the first engagement may be a shorter strategy document rather than a full plan. I will say so rather than write 30 pages around an empty middle.
Related work
Investor business plan for a more detailed funding narrative, pitch deck support for the meeting itself, and financial modelling if only the numbers need building.
What belongs in the appendix
Early-stage plans benefit from a short appendix, because it lets the main document stay readable while keeping the evidence available:
- detailed assumptions behind the model;
- cohort or usage data, even if small;
- product screenshots or a link to a demo;
- letters of intent or pilot agreements;
- hiring plan by role and month;
- a one-page competitive comparison.
The appendix is also where a founder can be honest without derailing the narrative. A short note on what has not been proven is more credible than a confident claim that everything is on track.
The milestone table
A simple table forces clarity:
| Milestone | Date | What it proves | Spend to reach |
|---|---|---|---|
| Pilot with three merchants | Month 3 | Demand exists at the proposed price | |
| First ten paying customers | Month 6 | The sales motion works | |
| Repeat purchase above a stated rate | Month 9 | Retention, not just acquisition | |
| Break-even contribution per customer | Month 12 | The unit economics work |
If a milestone cannot be described in terms of evidence, it is an activity rather than a milestone. "Hire a sales team" is an activity. "Ten paying customers acquired through a repeatable channel" is a milestone.
What to leave out
- Five-year product roadmaps.
- Total addressable market calculations that do not connect to the entry segment.
- Org charts for roles that do not exist.
- Adviser lists assembled for the document.
Each of those makes the plan longer and less believable.