SaaS MVP Build Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A web application built with Next.js and a Node.js API on PostgreSQL, implementing the 38 user stories in Appendix A (total budget 210 story points).
2. 2.2Three user roles: account owner, member and read-only viewer, with the permissions matrix in Appendix B.
3. 2.3Stripe Billing integration for 2 subscription plans with monthly and annual prices, a 14-day trial and a customer portal.
4. 2.4Transactional email for the 7 events listed in Appendix C using the client's Postmark or SendGrid account.
5. 2.5An internal admin view for searching accounts, impersonating users and issuing plan credits.
6. 2.6CI/CD to the client's Vercel and AWS accounts with preview environments per pull request.
7. 2.7Two-week sprints with a sprint review, a live staging URL and a written sprint report.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Native mobile apps, browser extensions and desktop clients.
2. 3.2Usage-based or seat-based metering, invoicing in multiple currencies and tax calculation beyond Stripe Tax configuration.
3. 3.3Single sign-on (SAML, SCIM), audit logs and enterprise data residency.
4. 3.4Public API, webhooks for customers and third-party integrations not listed in Appendix A.
5. 3.5Marketing website, product analytics instrumentation beyond page and event tracking for 10 named events.
6. 3.6SOC 2 readiness, penetration testing and load testing beyond 200 concurrent users.

Story acceptance criteria may be refined during sprint planning at no charge. The client may swap a not-started story for a new one of equal or smaller point value once per sprint. Changes to a story after it is accepted are new stories.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1Each story meets its acceptance criteria in Appendix A on staging and passes automated tests in CI.
2. 5.2The client reviews each sprint's stories within five business days of the sprint review. Unreviewed stories are accepted.
3. 5.3MVP release is accepted when all committed stories are accepted and no severity 1 defects remain open.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1The founder or product owner attends sprint planning and sprint review, and answers blocking questions within one business day.
2. 6.2Third-party accounts (Stripe, email provider, hosting) are opened in the client's name.
3. 6.3Designs for each story are approved before the sprint that builds it.
4. 6.4The client accepts the agency's estimation in story points as the unit for swaps and changes.

Adding stories beyond the 210-point budget, adding a role, plan or integration, or changing an accepted story is a change. The agency estimates the change in points and hours, converts it to cost at the Schedule 1 rate, and shows the effect on the release date. The client may approve the change order or swap out stories of equal value instead.