One valuable journey can be enough to launch
A two-week MVP should let one identifiable customer complete one valuable journey from start to finish. That might be submitting and approving a timesheet, generating a client-ready audit, onboarding a contractor, or moving a service job through defined stages.
It should not attempt to satisfy every future segment, automate every edge case, or imitate every feature of an established competitor.
A credible focused release can include
Production foundations still matter when delivery is fast. The exact combination is scoped before the clock starts.
- Authentication and account recovery
- A limited role and permission model
- One core workflow with validation and status history
- A focused administration view
- One payment or external integration
- Responsive web interface
- Production deployment and ownership handover
These requirements usually exceed the promise
Complexity comes from uncertainty and interaction between systems—not merely the number of screens.
- Native iOS and Android applications
- Regulated or highly sensitive data without prior controls
- Large or poorly understood data migration
- Several third-party integrations with uncertain APIs
- Real-time collaborative editing
- Broad marketplace logistics and financial settlement
- Many customer segments with different workflows
The client controls part of the timeline
One decision-maker must provide same-day answers, approved content, brand assets, test credentials, and access to required services. New feature ideas move into the next-release backlog.
The two-week promise begins only after scope, acceptance criteria, access, content, and commercial terms are approved. That boundary protects both launch speed and engineering quality.