How Long Does It Take to Build a Website or a Web App?
Most timelines you get quoted are guesses wearing a suit. Here are the numbers I actually give, what stretches them, and how to land your project on the short end.
Most timelines you get quoted are guesses wearing a suit. Here are the numbers I actually give, what stretches them, and how to land your project on the short end. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
Almost every first call I take contains some version of the same question: how long will this take?
Most answers out there are guesses said with confidence. So here are the numbers I actually quote, and the things that move them.
The numbers I quote
These are real ranges from my own workflow, which is Next.js, React and Firebase, built by one person who has done it many times.
- Five-page marketing site, copy and images ready: 2 to 3 weeks.
- Marketing site with a blog, forms, analytics and a sheet or CRM connection: 4 to 6 weeks.
- Custom web app with logins, user roles, a dashboard and payments: 8 to 14 weeks.
- Startup MVP, one core flow, one user type, nothing else: 3 to 5 weeks.
Those are working weeks of real progress, not calendar weeks with two weeks of silence in the middle. That distinction is the whole article.
Where the time actually goes
Here is the part that surprises clients. Writing code is fast. Waiting is slow.
On a typical three-week site, I spend maybe eight to ten days building and the rest waiting for things to arrive: copy, images, a logo in a usable format, a decision about which page goes in the menu.
Three things eat the calendar:
Decisions nobody has made yet. The build stops the moment the next step depends on a choice only the client can make. Which plan do we show first? Do we list prices? Is the contact form going to sales or to the founder? Each one is a day lost if it is discovered at 5pm.
Access and approvals on other people's systems. DNS records, the domain registrar, Google Workspace, a payment gateway doing KYC, an API key from a partner. None of this is hard. All of it is somebody else's queue, and some of it takes a week on its own.
Feedback latency. A project moves at the speed of the slowest approver. If design sign-off sits in a founder's inbox for four days, the build sits for four days. This is the single largest cause of a three-week project becoming a three-month project, and it has nothing to do with technology.
What is faster than people expect
- Writing a page from content that already exists in someone's head.
- Building that page.
- Deploying it.
The building is genuinely the fast part. I have shipped a working page in an afternoon. I have also waited eleven days for a bank to approve a merchant account so that page could take a payment.
If you are planning a project, do not budget your thinking around the build. Budget it around the queue.
How to make yours land on the short end
Every one of these has shortened a real project by a week or more:
- Name one decision maker. One person who can say yes, with no committee behind them.
- Have content ready before the build starts. Even rough. Real sentences beat lorem ipsum, because layout decisions depend on what the text says.
- Give access on day one. Domain, hosting, analytics, email. Not when we ask, but upfront.
- Answer within 24 hours. Not because it is polite, but because it doubles the speed of the whole project.
- Freeze the scope. Additions are fine. Additions in week two are an estimate reset.
Do those five things and the honest answer to how long a site takes is closer to the bottom of the range than the top.
Scope is the real multiplier
Technology choice barely moves a timeline. Scope moves it enormously.
"This is just a small web app" usually means a login screen plus a dashboard, which sounds like two screens. Underneath there is authentication, password resets, roles, permissions, data modelling, error handling, email delivery and an admin view for every list. That is why a "small" app costs more and takes longer than a marketing site, and why I cover that gap in detail in my post on building a custom web app for a startup.
Every extra user role, integration or dashboard is a branch in the work. Three of them turn a four-week project into a ten-week one, without anyone feeling like they changed much.
What is not included in the number
A timeline is not a full picture. None of the ranges above include:
- Ongoing maintenance, hosting oversight, or content updates after launch.
- Search visibility. A new site does not rank because it exists, and launching is the start of that work rather than the end.
- Ongoing marketing, ads or social.
Plan for the launch as the start of a second, quieter phase of work. Anyone who quotes you a build price and stops there is quoting you half a project.
How to get an honest estimate
Ask for a range plus the assumptions behind it. A single number with no caveats is either padded by 40 percent or pulled out of the air to win the work.
Then ask what would move it. Any developer who has done this more than a few times will immediately tell you: content readiness, one approver, access on day one. If the answer is only about technology, the quote is probably going to move later anyway, and the increase will arrive when you have the least room to walk away.
If you already know what you want to build, message me on WhatsApp with one sentence about the project. I will tell you honestly whether it is a two-week job or a two-month one, before you commit to anything.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.