An MVP in two weeks: scope, dependencies and testing
An MVP timeline needs a defined main workflow and known dependencies. A promise to build an application in two weeks says little without them. Payment setup or missing content can take longer than the coding itself.
Choose the question the first release must answer
Suppose you want to find out whether people will pay for a curated selection of materials. You need a clear offer, an order process, payment and delivery. An advanced recommendation engine may be unnecessary for that test.
Define what you will observe: whether visitors place an order, understand the result and return. A few early purchases do not establish lasting demand, but they can inform the next release.
Write down the customer journey
List the actions from first visit to delivery. Mark what the application does and what you will handle manually. Manual delivery can work if customers know the terms and you can fulfill orders on time.
Keep login, paid-order storage, access permissions and support reliable. Reducing the feature list does not remove the need to test these parts.
Include a portal, referral program or detailed reports only when they are necessary to test the main workflow.
Check dependencies before agreeing on a date
The developer may need copy, images, domain access and test data. A payment provider may require documents. An integration depends on API availability and your service plan.
Agree when each dependency will be ready and what can be demonstrated without it. An order form on its own does not establish that you can accept payments.
The estimate should allow for testing, corrections and handover as well as implementation.
What a 14-day plan could look like
Consider a hypothetical service that takes orders for curated materials, records verified payments and delivers results prepared by a person. The offer, content, account access and approved payment connection are ready before day one. Waiting for external services is outside this example.
Recommendations based on past activity, referrals and advanced reporting are excluded. Revisit the plan if a required dependency is not ready. This illustrates a scope discussion; it is not a delivery promise for every project.
| Days | Result to inspect |
|---|---|
| 1–2 | Order flow and delivery terms agreed |
| 3–6 | Orders are saved and staff can see the work to fulfill |
| 7–9 | Payment is verified and the result reaches the correct customer |
| 10–12 | Declines, duplicate notifications and unauthorized access tested |
| 13–14 | Corrections, instructions and a decision on the first launch |
Decide what happens after launch
Assign someone to review the first inquiries and failures. Record why people decline and what they ask, alongside page views. Choose the next improvement from a recurring problem.
At DevNomad, we agree on the first release’s scope before estimating it. Start with the user, the task and the action they will pay for. A specific date depends on that scope and its dependencies.