INTRO
“Build me an MVP” often means two opposite things. Sometimes it is a conversion site with a waitlist. Sometimes it is auth, tenancy, roles, and a workflow that real operators use. Pricing, timeline, and stack choices only make sense after you name which one you mean.
Marketing / brochure scope
Primary job: explain the offer, capture leads, look trustworthy. Stack can stay lean: App Router pages, forms, analytics, CMS optional.
Success looks like: clear story, fast LCP, working contact path, and deploy you can update without a full engineering team.
Multi-tenant product MVP scope
Primary job: one tenant can complete a core workflow end-to-end. That forces auth, data isolation, roles, and admin surfaces — the QuikPOS class of work.
Success looks like: staging users finishing the path weekly, not a homepage that “looks like a product.”
How to brief without confusion
Write one sentence: “In eight weeks a {role} can {action} and we will measure {event}.” If you cannot write that sentence, you are still in discovery — not build.
If you need both a site and a product, sequence them. Lead-gen first is fine when fundraising. Product spine first is better when you already have paying operators waiting.
KEY TAKEAWAYS
“Brochure and multi-tenant MVP are different products.”
- 02
One success event beats a feature wishlist.
- 03
Sequence site and product instead of pretending they are the same quote.
CONCLUSION
Closing thought
Share which scope you need on Contact — I will push back if the brief mixes brochure timelines with SaaS depth.
CONTINUE
Related pages
UP NEXT
SaaS MVP Feature Checklist (Next.js) — Cut Scope Without Cutting Quality
A ruthless SaaS MVP checklist for Next.js products: auth, one workflow, admin, observability, and what to postpone without lying to yourself.
Read next article