SaaS MVP proposal with a first-release scope, launch targets, an eight-week timeline and three one-time options.
Start free. No card required.
A starting point for the scope, pricing and next steps you want to share
Keep useful pages and replace the content with your client details
Choose the colors, fonts and imagery that fit your business
A SaaS MVP proposal turns a founder’s waitlist and customer interviews into a first release they can launch and learn from. This template separates what goes in the first release from what waits, sets targets for the first weeks after launch, and offers three one-time options from a tested prototype to an MVP with support after launch.
Product studios, MVP agencies and freelance development teams working with founders who have evidence of demand but no product yet. It suits a fixed-fee build where the founder needs to know what they will get, when, and what is left for later.
Fixed-fee options by stage work well for founders with a set budget: a clickable prototype tested with users, a launch-ready MVP, and an MVP with a period of support after launch. Each option should end with something the founder can use, even if they stop there.
Tie payments to milestones the founder can see, such as acceptance, prototype approval and launch. Keep hosting, third-party services, app store fees and new features after launch outside the fee, and quote extra features as change requests.
Time to customise: about 20–30 minutes.
11 parts, in the order your client reads them. Every part is editable: keep what fits the job, rewrite the rest and add your own.
We propose an eight-week build of the smallest product a firm would pay for: a link the client opens to upload what is missing, automatic reminders and a dashboard of who still owes what.
Signed up in eight weeks with no advertising
Covers: What the accountants told you
Everything else waits until firms are paying and asking for it.
Targets for the first 60 days, agreed before we build.
Everything the fixed fee covers, and what it does not.
One workshop to agree the release, the price plans and the launch targets.
The same four people from the workshop to launch.
A reporting tool for agencies, and its first month.
Covers: The client, The result
Three options. We recommend Launch-ready MVP.
You do. The code, hosting, Stripe and email accounts are all in your name from the first week.
Pick an option and any extras, then accept on this page.
Only what is needed to test the riskiest assumption with real users: the core workflow, sign-up and, if you are testing willingness to pay, payments. Everything else waits until launch data shows it is needed.
Fixed-price stages suit most founders, as long as the scope is written down feature by feature. Changes after that are quoted separately, so the budget stays predictable.
Set a few targets before launch, such as sign-ups that activate, weekly active users or first paying customers, and review them after the first weeks.
Normally the founder, once it is paid for. Say so in the proposal, and make sure the code, accounts and infrastructure are in the founder’s name at handover.
11 editable parts, in this order: Introduction, Your situation, Our recommendation, What launch should prove, What is included, Timeline, Your team, Results for a similar client, Options and fees, Questions and Next steps. Keep the parts that fit the job, rewrite the rest and add your own.
As three one-time options the client can choose between: Prototype and test ($9,500), Launch-ready MVP ($34,000, recommended) and MVP and three months ($46,000). Payment terms: 40% on acceptance, 30% when the prototype is approved, 30% at launch. The prices are examples; replace them with your own before you send it.
Plan on about 20–30 minutes to replace the sample client, scope, dates and prices with your own, then preview it as your client will see it.
Share it as one link your client can read on any device, comment on, accept and e-sign, or export a PDF for your records.
Add your scope, pricing and brand. Preview the client experience before sharing.