How long does it take to build a web app? Phases and timeline
A clearly scoped MVP is usually live in 6 to 10 weeks, a customer portal in roughly 8 to 14 weeks, and a platform with payments, several user roles and integrations in a few months. Unlike a website, the timeline of a web app depends less on copy and images than on decisions: how early is it settled what the first version has to do? Below you will find the phases, the typical time sinks and how the platform YachtBrokerBid went live after 12 weeks instead of the agreed 20.
- Published
- Last updated:
- Reading time
- 6 min read
- Author
- By Maurice de Felice, web developer in Augsburg, Germany
How long does each kind of web app take?
These figures apply from the moment scope and fixed price have been agreed. How long a plain website takes is covered in the guide How long does a website take?.
| Project | Typical scope | Duration |
|---|---|---|
| Web app / MVP | Login, database, one core feature | 6–10 weeks |
| Customer portal | Roles, documents, status, notifications | 8–14 weeks |
| Platform with payments | Several user groups, payments, admin area | several months |
| A website, for comparison | One-page site or 5–10 pages | 2–3 or 4–6 weeks respectively |
Prices and timelines per project type: web app €5,990–15,000, customer portal €8,000–15,000 – as of October 2026
What are the phases of web app development?
| Phase | What happens | Share of the time |
|---|---|---|
| Scoping and data model | Features of the first version, roles, data structure | short, but before the first screen |
| Core feature | The part that delivers the actual value | largest block |
| Accounts, roles, notifications | Sign-in, permissions, emails | medium |
| Payments and integrations | Only where needed – with their own test cases | depends on how many |
| Testing, polishing, launch | Automated tests, sign-off, go-live | at the end, including your sign-off |
Based on experience; the specific milestones are set out in the fixed-price offer
What delays a web app most often?
- Growing scope: every new idea during the build pushes the launch back. Good ideas go on the list for version 2.
- Integrations: third-party systems have their own access procedures, test environments and contacts. If you only request access in week six, you will be waiting.
- Decisions without a decision-maker: when approvals pass through several people, each milestone loses days.
- Legal matters: the privacy policy, terms and conditions and data processing agreements have to be in place before launch.
- Real content: web apps need copy too – email templates and help texts are easily forgotten until the very end.
How did YachtBrokerBid go live sooner than planned?
The auction platform YachtBrokerBid was online after 12 weeks; 20 had been agreed. The client confirms that the tight schedule was beaten.
The biggest difference came from deciding not to build things in-house: payments run through Stripe Hosted Checkout with server-side verification instead of a self-built webhook infrastructure, and translations are maintained through an interface, so changing copy does not need a new release. Both save not only development time but also rounds of back-and-forth once the platform is running.
What did take time was what has to take time: the credit system with transaction-safe bookings and a complete history. Where a mistake costs money or trust, care is the faster route.
How much time per week do I set aside for your project?
I freelance alongside my main job. That is why I plan every project with a fixed weekly allocation – the cost calculator currently works with 15 hours per week – and only take on as many projects as fit within it. That may sound slower, but it is more reliable than a start date that keeps slipping because another project gets in the way.
We fix the specific schedule with milestones in the initial call. How much additional features extend the timeline is shown directly by the cost calculator.
What happens after the launch?
Going live marks the start of the phase in which you learn the most. The first real users find workflows nobody thought of during testing and ask for features that were never on anyone’s list. So plan for a few weeks after launch in which bugs are fixed quickly and small improvements are made – for web apps, six months of support are included in the fixed price.
Only after that is it worth planning the next major version. The order then follows real data rather than assumptions: which feature is used most, where do users drop out, which requests keep coming up? That keeps the timeline for version 2 realistic as well.
How can you speed up development?
- Strictly limit the scope of the first version – more on that in the guide MVP development.
- Provide access to integrations, the payment provider and hosting before the project starts.
- Name one decision-maker who approves milestones within two days.
- Use proven services instead of building everything yourself: payments, email delivery, hosting.
- Prepare copy, email templates and legal texts in parallel with development.
What do clients often ask?
Planning a project?
In a free initial call you get an honest assessment of scope, timeline and a fixed price – by video, or in person in Augsburg and Munich. I usually reply within 24 hours.
About the author
Freelance web developer in Augsburg, Germany. By day a backend developer at one of Germany’s largest comparison portals; as a freelancer I build websites, web apps and SaaS platforms with Laravel and React – for example the SaaS platform YachtBrokerBid. More about me
Read next
More guides: How much does a website cost in 2026? Prices, examples and cost drivers · Getting a website built: freelancer, agency or website builder? · How long does it take to have a website built?