SaaS startup business plan example
An illustrative SaaS startup example: model, go-to-market assumptions, evidence gaps, financial assumptions to validate and the questions investors ask.
Quick answer
This illustrative SaaS example sells a subscription tool to operations teams at small companies. Its credibility rests on retention evidence, a defensible acquisition cost, and a pricing model that matches the forecast — none of which are proven at the stage described.
Important note
Illustrative fictional example. This is not a real CEO? customer, and every figure below is a labelled working assumption for illustration — not an observed result, benchmark or projection you should rely on.
Business summary
A fictional two-person startup selling a subscription tool that helps operations teams at 10–50 person companies track supplier commitments. The product is live with a small number of unpaid pilot users. The founders' goal is a first paid cohort and a defensible retention signal before raising.
The problem
Operations leads at small companies track supplier obligations across spreadsheets, email threads and calendar reminders. Missed renewal dates and forgotten service commitments produce cost and disputes, but the problem sits below the threshold where dedicated procurement software is justified.
Target customer
Operations or finance leads at UK companies with 10–50 staff, typically managing between 20 and 200 active supplier relationships, with no dedicated procurement function. The buyer and the user are usually the same person, which shortens the sales cycle but caps the price.
Business model
Per-seat monthly subscription with an annual option, sold self-serve with an assisted onboarding call for larger accounts. Revenue depends on seat count per account, expansion within the account and monthly retention. Cost to serve is dominated by hosting and support time per account.
Go-to-market assumptions
These are the routes to market this fictional business would test first. Each is an assumption until it produces measurable results.
- Content aimed at the specific failure mode: missed supplier renewals
- Partnerships with bookkeeping and outsourced finance practices
- Direct outreach to operations leads in a narrow vertical first
- Free tier limited by number of tracked suppliers, not by time
Key evidence still needed
The gaps that would stop this plan being credible to an investor, a lender or the founder's own decision-making.
- Whether pilot users would pay, and at what price
- Month-three retention for at least one paying cohort
- Acquisition cost from at least one repeatable channel
- Whether seat expansion happens without prompting
- Evidence that spreadsheets are the real alternative, not an incumbent tool
Financial assumptions to validate
Working assumptions used for illustration only. Each would need to be replaced with observed data before it belongs in a real forecast.
- Assumed average of 3 seats per account at launch
- Assumed monthly price point per seat, untested against willingness to pay
- Assumed 5% monthly churn in year one, with no data behind it
- Assumed support load of under one hour per account per month
- Assumed no discounting, which rarely survives a first sales cycle
Questions an investor would ask
The questions this business should be able to answer without hesitation before a first meeting.
- What is your evidence that this is a paid problem rather than an annoyance?
- How do the pilot users behave when you stop prompting them?
- What is your realistic ceiling on price given who the buyer is?
- Which channel do you believe scales, and what have you measured?
- What happens if a general workflow tool adds this feature?
Common contradictions and risk areas
Where documents in a business like this typically fall out of step with each other, and where the underlying risk sits.
- Pricing changed in the model but unchanged in the plan narrative
- Deck describing paying customers while the plan describes unpaid pilots
- Different churn assumptions between the forecast and the growth story
- Target segment narrowed after customer calls but still wide in the market sizing
- Support cost assumption incompatible with the described onboarding call
Home · Features · How it works · Pricing · Compare · For founders · Try free