Guide
Business plan for seed funding
At seed stage, a plan is not a forecast of revenue. It is an argument that the next twelve months will produce evidence the company does not have today.
A seed plan must prove five things: a problem worth solving, a product that addresses it, a market reachable from a specific entry point, unit economics that can work, and a team able to execute the next stage. The ask follows from those, not the other way round.
What "seed" changes
| Element | Seed-stage emphasis |
|---|---|
| Market | Entry wedge more than total size |
| Product | What exists now, and what the money builds next |
| Traction | Any evidence, described precisely |
| Team | Why these founders, and what is missing |
| Financials | Runway and milestones more than five-year revenue |
| Risks | The ones that could end the company |
Use of funds, tied to milestones
A seed plan should show what each tranche buys:
| Allocation | Amount | What it achieves |
|---|---|---|
| Engineering | Ship version 2 with the core workflow | |
| Sales | First ten paying customers | |
| Operations | Delivery capacity for the pilot cohort | |
| Marketing | Channel test with measured acquisition cost | |
| Contingency | Two months of additional runway |
The milestone is the point. "Hire three engineers" is an activity; "ship the workflow that unlocks paid conversion" is a milestone.
The model at seed stage
Monthly for 24 months:
- headcount by role, with salary burden;
- infrastructure and tooling;
- marketing spend by channel;
- revenue by customer cohort;
- gross margin after hosting and support;
- cash balance and runway.
Then show two cases: plan and slow. The slow case is what an investor will actually test in the meeting.
Traction, described honestly
Weak: "strong early traction". Strong: "14 paying customers, average contract SAR 18,000 annual, two signed in the last 30 days, monthly churn zero to date across a three-month cohort."
The second invites questions; the first invites doubt.
Risk section
Include the risks a founder would rather not write:
- concentration in one customer or channel;
- dependence on a platform or API;
- a regulatory dependency;
- key-person risk;
- a competitor with distribution.
Each with a mitigation that is within your control.
Related documents
Investor business plan for the full narrative, pitch deck support for the meeting, and startup plans for the service.
The investor meeting versus the plan
The plan is what survives after the meeting. The meeting is where the founder is tested. They should not contradict each other.
Practical alignment checks:
- the raise amount is identical in both;
- the use of funds matches the model;
- the traction numbers are the same, with the same definitions;
- the milestones in the deck appear in the plan's financial section;
- the team slide and the management section name the same roles.
Mismatches are common and damaging. An investor who spots a different revenue figure in the deck and the plan will assume one of them was constructed for the occasion.
What seed investors tend to ask next
- What have you learned from the first customers that changed the product?
- Which assumption would you most like to test with this money?
- What happens if the next round is harder to raise?
- Who is the second hire, and why?
- What is the smallest version of this business that is still interesting?
A plan that anticipates those questions reads as a document written by someone who has thought about the business, not just about fundraising.
A note on valuation
Including a valuation is optional at seed stage. If it is included, it needs a basis: comparable rounds, a revenue multiple, or a dilution target. A number with no reasoning invites negotiation from a weak position.
Where the founder has no basis, the better approach is to state the raise amount and the dilution range considered acceptable, and leave the valuation to the term sheet discussion.