How long does a custom web app take to build?
A simple custom web application takes 6 to 12 weeks from signed specification to production launch. A typical custom SaaS or business platform takes 4 to 9 months. An enterprise-grade multitenant platform takes 9 to 24 months. Specification work adds 2 to 12 weeks on top depending on scope. Most schedule slippage is buyer-decision-velocity-driven, not engineering-driven; approvals that take 2 to 3 weeks each turn a 12-week project into a 20-week project.
The longer answer
Custom web application timelines split into the same three categories as the pricing, and the schedule drivers are well-understood once the scope is clear. The factor buyers underestimate most often is their own decision velocity on the design, integration choices, and content side of the project.
Simple (6-12 weeks)
Specification: 2-3 weeks. Build: 4-8 weeks of two-week sprints with working demos on staging. Launch and handoff: 1-2 weeks. The schedule risk is integration uncertainty — surprises in a third-party API, data-quality issues in the buyer's existing system, or unexpected complexity in the business logic.
Mid (4-9 months)
Specification: 4-6 weeks produced collaboratively with the buyer's stakeholders. Build: 3-7 months in two-week sprints. Beta testing with internal users: 2-4 weeks. Launch and handoff: 3-4 weeks. The schedule risk shifts to feature-scope discipline — the most common cause of slippage is feature accretion mid-build.
Enterprise (9-24 months)
Specification: 6-12 weeks produced collaboratively with the buyer's product and engineering teams. Build: 6-18 months in two-week sprints with substantive staging environments. Beta testing with selected buyer pools: 4-8 weeks. Compliance audit and certification (SOC 2 Type I, HIPAA, NAIC): 2-6 months running in parallel with later build phases. Launch and handoff: 4-8 weeks with staged rollout.
What slows projects down
Four predictable causes. Buyer decision velocity. If approvals on design, integration, or scope decisions take 2-3 weeks each, a 12-week build becomes a 20-week build. Integration discovery. Third-party API surprises, data-quality issues in existing systems, or unexpected complexity in the business logic. Scope changes. The right fix is a written change order quantifying the schedule impact, not silent absorption. Design iteration. Bespoke design adds calendar time; templated design ships faster.
What speeds projects up
A written specification that already exists; a design system that already exists; backend APIs or data sources that are already stable; clear acceptance criteria with named decision-makers on the buyer side. Engagements with all four ship at the fast end of their band; engagements with none of them ship at the slow end.
The honest schedule conversation
Most schedule slippage in web-application engagements is not engineering-driven. The build itself runs on schedule in the typical engagement; the slippage comes from decision-velocity gaps, scope creep, or content / design iteration. The mitigation is a written specification with explicit acceptance criteria and a named decision-maker on the buyer side, not adding more engineers.
Common follow-up questions
Can a custom web app launch in three weeks?
A prototype or template configuration, yes. A production-grade custom web app with tests, authentication, integrations, deployment infrastructure, and a written runbook — no. Three-week launches are useful for validating an idea, not for shipping production software.
Why does the specification take 2-12 weeks?
Because the specification is the load-bearing artifact. A good spec defines the data model, acceptance criteria, non-goals, integration contracts, and a phased delivery plan. Skipping it produces builds that cost more and ship later than the spec would have.
Can the build start before the specification is done?
For self-contained early features that do not depend on later spec decisions, yes — with explicit acknowledgement that those features may require rework. For anything load-bearing on the domain model, no.
If this answer is useful and you have a real engagement in mind, the contact form routes directly to the principal — James Henderson is the single engineer who scopes, writes, and supports every engagement end-to-end.