The standard quote is eight to twelve weeks. The standard build is under a week. The gap between those two numbers is worth understanding before you sign anything.
I built a product called Crisp and its entire marketing site in two days. Not a landing page — the app and the site.
I mention that not to brag but because of what happens when I say it out loud to people quoting websites: the immediate assumption is that something must have been skipped. That reaction is worth taking apart, because it reveals how strange our expectations about this work have become.
A typical local service site is a home page, a services page or a few, an about page, a contact page, and a form that emails you. Underneath: responsive layout, a bit of schema markup, meta tags, a sitemap, analytics, and a host.
Every one of those is a solved problem. None of it is novel engineering. Someone who has built a hundred of these is not discovering anything on the hundred-and-first.
Honest accounting of the production work:
| Task | Actual working time |
|---|---|
| Structure and page layout | 3–5 hours |
| Writing the pages (from existing material) | 3–4 hours |
| Responsive and mobile pass | 2 hours |
| Forms, analytics, schema, meta | 2 hours |
| Domain, hosting, SSL, launch | 1 hour |
| Review and revisions | 3–4 hours |
| Total | Roughly 2–3 focused days |
Add a buffer for a real client with real opinions and you land at four or five days. Not eight weeks.
Three places, and only one of them is about your project.
An agency with six active clients is not working on yours continuously. Your two days of work are distributed across six weeks of their calendar. Nothing dishonest is happening — you are buying a slot in a schedule, and the quote reflects the schedule rather than the labor.
This is the big one, and it is usually the client's side of the ledger. A content request goes out, it lands on a business owner who is already busy, and the project stops for weeks. I have written about this at length because it is the single most common reason a project that should take a week takes a season.
Anyone who has built sites for a living has been burned by a project that dragged for months through no fault of their own. Quoting twelve weeks is partly a hedge. It is easier to deliver early than to explain a slip.
Most long timelines are not estimates of work. They are estimates of calendar — yours, theirs, and the gap in between.
I am not faster because I skip things. I am faster for three structural reasons, and they are worth naming because they should be reproducible by anyone.
I draft your content first. Rather than sending a questionnaire and waiting, I write every page from your existing site, listings and reviews, then you correct it. The single longest delay in the industry standard process is removed by inverting who writes first.
I use AI for the mechanical parts. Boilerplate, responsive edge cases, schema markup, alt text, meta descriptions — the parts that are careful rather than creative. That is a real multiplier on the hours, and pretending otherwise would be strange coming from someone who builds AI products.
I take few clients at once. No queue means your two days are two days.
"Of those eight weeks, how many are you working on my site?"
Good answers are honest ones — "about a week of work, the rest is my schedule and waiting on your content." That is fine and you now know what you are buying. A vague answer about process and discovery phases usually means the number is small and nobody wants to say it.
I would be arguing dishonestly if I implied every website is a two-day job. Some are not, and the difference is worth knowing so you do not push a project that deserves eight weeks into two.
A brochure site for a roofer, dentist, landscaper or restaurant is on none of those lists.
There is a hidden line item in a twelve-week timeline: twelve weeks of not having a website.
A new domain accumulates search history by existing. It has to be crawled, indexed, and gradually associated with your business name and your city. None of that starts until the site is live. Three months of delay is three months where you do not appear for your own business name, three months of ad traffic you cannot send anywhere good, and three months of prospects who looked you up and found nothing.
That cost is invisible because it never shows up as an invoice. It is usually larger than the difference between a cheap builder and an expensive one.
For a straightforward local service business, here is what I think is fair to expect:
| Milestone | Reasonable |
|---|---|
| Draft content back to you | 2–3 days from kickoff |
| First working preview | Within 1 week |
| Live site | 2 weeks, assuming you reply |
| Photos swapped in later | Whenever they're ready |
If a quote is much longer than that for a simple site, it is not necessarily wrong — but you are entitled to know which part is work and which part is waiting.
The build itself is usually two to five working days for a standard five to seven page service site. Most quoted timelines of eight to twelve weeks are mostly scheduling and waiting rather than production, because the project is queued behind other work and paused while the client assembles content.
Speed and quality are mostly independent. What determines quality is whether the site loads fast, works on a phone, is structured for search, and gets someone to contact you. A build can be slow because it is careful, or slow because it sat in a queue, and from the outside those look identical to the client.
Partly to absorb their own scheduling across several concurrent clients, and partly to protect against the client-side delays that genuinely do happen, especially content collection. A long quote is often a realistic estimate of calendar time rather than an estimate of work.
Original photography, custom e-commerce with real inventory logic, complex integrations into booking or payment systems, migrating a large existing site without breaking its search rankings, and any regulated industry review. A brochure site for a local service business is not on that list.
Send me your current site or your Google listing. I'll tell you what I'd build, how many days it takes, and what it costs — in writing, before you commit to anything.
If your current site is fine, that's a valid answer and I'll give it.