What must the first release prove?
Start with one business question: can a user complete an order, pay for a booking, or can staff operate the service through a simple panel? Trying to prove everything turns an MVP into a full product under a smaller label.
Minimum does not mean unsafe
Even a small release may need secure sign-in, roles, data protection, a basic admin view, and understandable failures. Defer complex automation when manual operations can test demand, but not essentials required for a real user journey.
- Deliver one complete journey rather than many disconnected features.
- Use temporary manual staff work only when acceptable and documented.
- Separate what can be measured now from later improvements.
What changes the estimate
Target platforms, bespoke design, backend, payments, maps, content, analytics, and device testing all change cost. Request a first-release quote and a separate backlog with criteria for adding later features.
Measure learning, not vanity
Agree on an observable event such as order completion, repeat use of a core function, or staff processing without developer help. Do not invent a conversion target without a baseline; record friction and user feedback.