SaaS MVP Builder
Go from idea to a working SaaS MVP: auth, core feature, billing readiness, and a landing page that converts.
The route
6 steps to Done
- 01
Define the MVP in one sentence
Force clarity: one user, one problem, one core action.
Preview prompt + verify gate ▾ Hide ▴
Define this SaaS MVP with brutal focus. Produce: a one-sentence value proposition ('X helps Y do Z'); the single core action a user performs to get value; the minimum data model behind that action; the 3 pages the MVP needs (landing, auth, dashboard/feature); and an explicit NOT-list of features we will not build yet. Keep the core action count to exactly one.
- ✓ Value proposition fits in one sentence
- ✓ Exactly one core action is defined
- ✓ The NOT-list has real cuts in it
- 02
Build the landing page
The front door: a visitor must get it in 10 seconds and know what to click.
Preview prompt + verify gate ▾ Hide ▴
Build the landing page. Requirements: a headline stating the value proposition (no buzzwords); a subheadline explaining how it works in one sentence; a primary CTA button to signup; a 3-item 'how it works' or benefits section; social-proof placeholder section; responsive layout; real copy everywhere (no lorem ipsum). The CTA must actually route to signup.
- ✓ Headline states the value in plain words
- ✓ CTA routes to signup
- ✓ No placeholder/lorem text anywhere
- ✓ Layout holds at 375px width
- 03
Add working auth
Users need accounts before the core feature can be theirs.
Preview prompt + verify gate ▾ Hide ▴
Implement real signup and login for this SaaS. Requirements: email/password signup with validation and duplicate handling; login with credential verification; session persistence across refresh; logout; protected dashboard routes redirecting logged-out users; visible loading and error states on both forms. This must be real auth with persisted users - not visual forms.
- ✓ Signup creates a persisted user
- ✓ Refresh keeps the session
- ✓ Dashboard is blocked when logged out
- ✓ Errors show in the UI
- 04
Build the core feature end to end
This is the product. It must actually work and persist real user data.
Preview prompt + verify gate ▾ Hide ▴
Implement the single core feature end to end. Requirements: the user performs the core action from the dashboard; the result is stored in the database linked to the user id; the dashboard lists the user's own items with loading and empty states; items can be edited and deleted with persistence; every query filters by the logged-in user so no data leaks between accounts. Prove it with two different accounts seeing only their own data.
- ✓ Core action creates a persisted record
- ✓ Refresh shows the same data
- ✓ Second account sees none of the first account's data
- ✓ Edit and delete persist
- 05
Add the plan/upgrade surface
Make the business model visible and ready for billing integration.
Preview prompt + verify gate ▾ Hide ▴
Add a pricing/upgrade surface. Requirements: a pricing section or page with 2-3 plans, real feature differences, and prices; the user's current plan shown in settings or dashboard; an Upgrade button that opens a 'billing coming soon' dialog OR the real checkout if payments are configured; free-plan limits enforced in the core feature (e.g. max N items) with a clear upgrade nudge when the limit is hit.
- ✓ Plans render with concrete differences
- ✓ Current plan is shown for the user
- ✓ Free limit actually blocks and nudges at N items
- 06
Full MVP QA pass
Walk the entire funnel like a new user and fix everything that breaks.
Preview prompt + verify gate ▾ Hide ▴
QA the complete funnel as a brand-new user and report PASS/FAIL with evidence: landing loads and CTA works; signup creates an account; core action delivers value and persists; refresh keeps session and data; second account is isolated; free limit triggers; logout works; the whole path works at 375px. Fix every failure and re-run the table.
- ✓ Full funnel executed as a new user
- ✓ Data isolation verified with two accounts
- ✓ Mobile pass completed
- ✓ All failures fixed and re-verified