"Four to six weeks" is the industry's favourite answer because it is unfalsifiable. It covers a five-page brochure site and a booking platform, which are not the same object and should not carry the same estimate.
Here are the windows we actually quote, and the things that move them.
What we quote
| Build | Window |
|---|---|
| Custom marketing website | 3–5 days |
| Site plus admin dashboard | 1–3 weeks |
| Internal business system | 2–4 weeks |
| Mobile app, iOS and Android | 1–3 weeks |
| AI agents and automation | 5–7 days |
Those are real, and they are on our services pages because we are willing to be held to them.
Why they are shorter than you expected
Three reasons, none of them "we rush".
Fewer meetings. Most agency timelines are mostly waiting. A two-person studio skips the internal review layer entirely.
Discovery happens once, properly. Deciding what the thing does before building it is the single biggest saving available. Reversing a decision after the work is done is what makes projects take months.
We do not build what you did not ask for. Scope creep is usually generosity that nobody scheduled.
What actually makes a project slip
Almost never the code.
Content. Text, photography, product data. This is the number one cause of delay in every project we have run. If you have not written the words, the site cannot be finished, and no developer can fix that for you.
Access. Domain registrar login, existing hosting, the analytics account somebody set up four years ago and left. Chasing these can add a week to a five-day build.
Approval. One person deciding is fast. Three people deciding is slow. Four is a month. Name the decision-maker before the project starts.
Changing the target. A new requirement mid-build is fine and normal — but it is new work, and it moves the date. A studio that absorbs it silently is either padding the estimate or cutting something you have not been told about.
How to make it faster, genuinely
- Write the content first, or pay someone to. Before the build starts, not during.
- Gather every login into one document on day one.
- Name one decision-maker and give them the authority.
- Say yes to the smaller first version. You can add to something that exists.
Do those four and a five-day build takes five days. Skip them and the same build takes a month, and it will look like the developer was slow.
The question to ask a quote
Not "how long will it take?" — everyone says the same thing. Ask:
"What do you need from me, and by when, for that date to hold?"
A studio that answers precisely has run projects before. A studio that says "just the content whenever you're ready" is telling you the date is decorative.