MVP or full platform? How to choose your starting point

Start with the question you're actually answering

Before choosing a scope, get clear on what you need to learn. If you're validating demand or a new workflow with real users, a lean MVP — the smallest version that delivers real value — gets you there fastest and cheapest.

If you already know the product works and you're replacing a fragile internal process or scaling a proven idea, a fuller platform build from day one can save you a costly rebuild later.

Signs you should start lean

• You haven't validated the core assumption with real users yet
• Budget or timeline is tight and you need to learn fast
• The market or workflow might change based on what you learn

Signs a fuller build makes sense

• You're replacing a system that already has real usage and can't afford instability
• Compliance, security or integration requirements are non-negotiable from day one
• You already have validated demand and are optimizing for scale

Either way, keep the architecture honest

A lean MVP doesn't mean sloppy code — it means a smaller scope, built on an architecture that can grow. That's the difference between an MVP you can extend and one you have to throw away.