Define what the first version must prove
Identify the user, the problem, the essential action and the evidence that would justify further investment. Separate essential workflows from later features. Agree how feedback, usage and exceptions will be assessed; an MVP is not a promise of market success.
Prototype, build and test
A prototype may test screens or workflow before production development. A working MVP adds the agreed data handling, permissions and core functions. Testing covers normal use, validation failures and important exceptions. Live customer data and production deployment require an agreed operating and privacy plan.
Move from MVP to final implementation
Review what the first version demonstrates, then prioritize the next phase. Migration, integrations, monitoring, role design, documentation, training and support must be planned for operational use. The technology and architecture should fit the intended scale and the business constraints.
What should founders bring?
Bring your target users, current alternatives, sample workflow, required integrations, data sensitivity and budget constraints. We can turn an early concept into a practical scope; funding, commercial traction and a fixed launch date are not guaranteed.