1. Realistic Delivery Windows by Product Archetype
Unrealistic deadlines are the #1 cause of software failure. Quality engineering requires deliberate discovery, UI system definition, and rigorous automated regression verification.
Marketing & Brand Flagships: 3 to 6 Weeks. Complete custom design system, zero layout shift, 100 Lighthouse performance, CMS integration, and internationalization.
Minimum Viable Products (MVPs): 4 to 8 Weeks. User authentication, core loop logic, database schemas, Stripe billing, and production deployment.
Commercial SaaS Platforms: 8 to 16 Weeks. Multi-tenancy, workspace team invitations, webhook dispatchers, reporting telemetry, and load testing.
Complex Enterprise Systems: 16 to 24+ Weeks. Legacy database migrations, microservice extraction, compliance audits, and multi-region failover testing.
2. The Critical Path: What Actually Takes Time?
Contrary to popular belief, writing code is rarely the primary bottleneck. The phases that determine delivery velocity are:
1. Technical Discovery & Scope Freezing (Weeks 1–2): Eliminating speculative ambiguity and locking architectural schemas.
2. Interactive Prototyping (Weeks 2–3): User testing clickable flows in Figma to prevent expensive code refactors.
3. Quality Engineering & Penetration Testing (Final 2 Weeks): Cross-browser verification, load testing under 10k RPS, and security audits.
- Insist on bi-weekly production staging URLs rather than waiting for a single end-of-project reveal.
- Scope cuts during discovery save 3x more calendar time than adding additional developers mid-flight.
- Strict TypeScript schemas and automated CI tests compress the stabilization phase by 60%.