Apps & Software
How Long Does It Take to Build a Web Application? Stages and Time Estimates
For a mid-sized system, building a web application generally takes 3 to 6 months. Here is the time per stage, the factors that most often extend it, and what you can do to keep it on schedule.
SEO and Content Specialist
4 min read
Short answer: a mid-sized web application usually takes 3 to 6 months, split into five stages: requirements mapping (1-2 weeks), workflow and interface design (2-3 weeks), phased development (most of the time, with results tried every 2-3 weeks), testing and a limited pilot (2-4 weeks), and launch and handover (1-2 weeks). The factors that most often extend the timeline are not development itself, but delayed decisions and requirements that change midway.
“How long will it take?” is almost always the second question after “how much will it cost?”. The answer depends on the size of the system, but the pattern of stages is fairly consistent. Understanding those stages helps you build a realistic schedule, including setting aside time for your own team, which is often the biggest deciding factor.
Time breakdown per stage
| Stage | What is done | What you need to provide | Estimated time |
|---|---|---|---|
| Requirements mapping | Walking through the workflow with the people who run it | Interview time and sample documents | 1-2 weeks |
| Workflow and interface design | User flows and a clickable prototype | Prototype approval | 2-3 weeks |
| Phased development | Building part by part and handing each part over to try | Time to try it and give feedback | The largest part, with results every 2-3 weeks |
| Testing and limited pilot | Testing the system and supporting part of the team as they use it | A team to try it first | 2-4 weeks |
| Launch and handover | Moving data, training the team, handing over code and access | Data to be moved, training schedule | 1-2 weeks |
What makes a project take longer
From experience across many projects, the most common causes of delay lie outside the code:
- Delayed decisions. The prototype waits weeks for approval because the decision maker is busy, or several divisions have not yet agreed.
- Requirements that change after development has started. Every change has to be reassessed for impact, and a large change can repeat part of the work.
- Number of roles and exceptions. A system with many user roles and layered approval rules needs more design and testing.
- Integration with other systems. Connecting the application to existing systems, such as accounting or company login, depends on documentation and access from other parties.
- Messy legacy data. Moving data from spreadsheets or an old system needs cleanup time that is often underestimated.
How to avoid delays
- Prepare a requirements document before starting. The clearer the problem, users, and workflow, the shorter the mapping and the fewer the changes midway. A guide is in the article How to Write a Requirements Document Before Building an Application.
- Appoint one decision maker. One person with the authority to approve the prototype and answer questions within days, not weeks.
- Separate must-have features from those that can follow. A smaller first version can be used sooner, and feedback from real use makes the next version more accurate.
- Try every part that is handed over. Feedback in week three is far easier to handle than feedback in month five.
- Start cleaning legacy data early, in parallel with development.
Example schedule for a mid-sized system
As an illustration, a procurement approval system with three user roles (requester, approver, and finance), one integration with an accounting application, and a monthly report could be laid out like this:
| Month | Main activities |
|---|---|
| Month 1 | Requirements mapping, then workflow design and prototype until approved |
| Month 2 | Building the request and approval modules, tried in stages by your team |
| Month 3 | Building reports and the accounting integration, cleaning legacy data |
| Month 4 | Testing, limited pilot in one division, fixes, training, and launch |
This example is an illustration, not a client project. The actual schedule is set after requirements mapping, and shifts if there are additional roles, integrations, or approval rules.
Can it be faster than 3 months?
Yes, for a small system: one workflow, few user roles, no integrations. For a larger system, the safest way to speed things up is to shrink the first version, not to cut the testing stage. An application launched without a limited pilot usually spends the same amount of time on fixes after it goes into use, with greater risk because the data is already real.
If the need is common and must be in use soon, ready-made software can be a faster answer. The considerations are in the article Custom Application, Ready-Made Software, or Spreadsheet.
How Legia does it
In the Web Application Development service, the five stages above are used for every project, and the estimated time for a mid-sized system is 3 to 6 months. Development results are handed over to try on a regular basis, not all at once at the end. If requirements change midway, the change is recorded as a separate request, assessed for its impact on time and cost, and agreed before the work is done.
Frequently asked questions
When can a firm time estimate be given?
After requirements mapping. Before that, the estimate is only a range, because the number of workflows, roles, and integrations is not yet known.
Can the application be used in part before everything is finished?
Yes, if the system is split into parts that stand on their own. For example, the request module is used first, and the report module follows.
How long does a mobile app take compared with a web application?
Generally a similar range for the same scale, plus a testing stage on real devices and publishing to the Apple and Google app stores, which have their own review processes.


