SaaS MVP Development Proposal Template
In SendScope under Development, as SaaS MVP Development
Every MVP quote is a negotiation about the word minimum. A founder means the smallest thing that proves the idea. By the time the features are listed it has become the smallest thing they would be proud to show an investor, which is a different and far larger product.
These three packages name that difference explicitly. A prototype has the core feature and authentication. A launch-ready build adds billing, roles and an admin panel, which is where most of the unglamorous work actually lives. The top tier is a product rather than an experiment.
Support windows are written into all three, and they are the clause that matters most in this trade. A founder who ships will find bugs, and whether the first sixty days of those are included or billed is a conversation to have while everyone is still optimistic.
What the client reads
The scope
This is the wording the template arrives with. Yours replaces it.
The packages
3 to choose from
The client picks one, and the one they pick is the one they approve and pay on.
Prototype
Functional prototype
A$5,000
4-6 weeks
- Core feature build
- User authentication
- Basic dashboard
- Responsive UI
- Deployment
- 2-week support
Launch-Ready
Production MVP
A$15,000
10-14 weeks
- Full feature set
- User auth & roles
- Billing integration
- Admin panel
- Email notifications
- Analytics
- CI/CD pipeline
- 60-day support
Scale-Ready
Enterprise-grade
A$30,000
16-24 weeks
- Complete platform
- Multi-tenancy
- API access
- Webhooks
- Advanced analytics
- Performance optimization
- Security audit
- 90-day support
- Documentation
The whole thing, live
The page your client opens
Not a screenshot. This is the real client page running on an invented deal. Pick a package and press approve to see what your client would see; nothing is sent or charged.
How it gets paid
Deposit, then balance
40% is due when the client approves, and the balance when you mark the work delivered. Both payments happen on the same link the proposal is on.
Card or bank transfer, and you choose which per deal. If you want a package to bill every month instead of once, you set that on the package itself when you build the deal, and the client can cancel it from their own link.
Prices are a starting point in Australian dollars. Change the figures, the inclusions and the number of packages to suit what you sell.
The starting terms
What approving the page records
These sit above the approve button. The client reads them, and approving records that they accepted them.
These terms cover the build you approve on this page.
- Scope. The build is the package described above. Anything not listed is a change request, quoted and approved on its own before it is built.
- Payment. The deposit shown on this page is paid on approval and the balance when the work is delivered and accepted.
- Acceptance. The work is delivered for you to review. Please raise anything that does not match the scope within seven days, and it is fixed at no charge.
- Fixes and new features. A defect is behaviour that does not match the scope and is fixed under this price for 30 days after delivery. A new requirement is a change request.
- Hosting, domains and services. Hosting, domains, licences and third party services are yours, held in your name and billed to you, unless the package above says otherwise.
- Your part. Content, access, credentials and decisions come from you. Time lost waiting moves the delivery date.
- Ownership. The code written for you is yours once the balance is paid. Open source and third party components keep their own licences.
- Cancellation. If you cancel, you are charged for the work completed and handed what has been built to that point.
Approving this page records that you accepted this scope, this price and these terms.
Starting terms, not legal advice. Read them, change what does not match how you work, and have a lawyer look at them if the work is large enough to warrant it. Your own default terms in Settings replace these automatically.
Before you send it
What to change first
The parts of this template most likely to be wrong for you.
- What minimum means for this particular client, which is the whole negotiation
- Whether infrastructure costs are yours or theirs, since they begin on day one
- Who owns the code, and the point at which that ownership transfers
- What happens after the support window, which every founder will ask about
Related
Ready to close deals faster?
Create your first deal page in minutes. No credit card required.
Get started free