Find your first useful release.
Choose your product, essential capabilities and delivery capacity. Explore an indicative timeline and use the result to start a clearer scoping conversation.
How the numbers work.
- Starting effort includes discovery, core implementation and launch preparation: website 8–14; web app 25–45; mobile 30–55; SaaS 40–70; desktop 30–55 person-days. These are editable-scope planning assumptions, not measured industry averages.
- Add selected capability allowances, 4–8 person-days per documented integration, and design effort: ready 0–3, partial 4–7, new 8–12. Apply a 20–35% delivery and testing allowance, then round up.
- Calendar weeks = person-days ÷ (effective full-time capacity × 5), plus your extra review allowance, rounded up. Discovery is included in the range. More people do not remove dependencies; enter effective available capacity, not headcount.
All money values are GBP. Keep VAT treatment consistent across inputs. Outputs are indicative, not a quote or a guarantee. Model reviewed October 2026.
Explore discovery & technical consultingBefore you decide.
Is this a promised delivery date?
No. Discovery may change scope and reveal dependencies. Procurement, migration, app-store review, regulated workflows and complex integrations need a separate assessment.
How should I choose MVP features?
Pick one user group and one complete journey. Include the security, accessibility and recovery needed to make that journey useful. Defer features that do not help test its core value.
Does this include a price?
This tool focuses on scope and timing. Use the separate project cost calculator for an indicative GBP range and discuss both outputs with a development partner.