The short answer, and the honest one
If you want a single number: most small business websites take 3 to 6 weeks to build once the project starts. That's a fair range for a roofer near Roanoke, a plumber outside Wytheville, or a law office in Richmond that wants a clean, conversion-first site.
But "how long to build a website" is really two questions wearing one coat. There's build time — the actual design and development work — and there's calendar time, which includes every day spent waiting on decisions, content, and approvals. Build time might be two focused weeks. Calendar time is where a project balloons to two months because the photos never showed up.
Here's the part most agencies won't put in writing: the developer is rarely the bottleneck. The bottleneck is the stuff only you can provide — your service list, your pricing philosophy, photos of your actual work, and a decision on which phone number rings. The build can move fast. A project can only move as fast as its slowest input.
So treat the ranges below as planning tools, not promises. A five-page site for a solo trade business and a thirty-page site for a multi-location contractor are different animals, and pretending they take the same amount of time helps no one. Every web design project should come with a written scope and a real range up front, not a vague "a few weeks." That's the difference between a timeline you can plan around and one that keeps slipping.
A realistic week-by-week timeline
Here's how a typical small business build unfolds, assuming you respond to questions within a day or two. The weeks below describe a mid-sized site — call it eight to twelve pages. Smaller and larger builds bend this shape, but the order of operations holds.
- Week 1 — Discovery and planning. We nail down your services, your service area, your goals, and what a lead is actually worth to you. The sitemap and page structure get locked. This week is short on visible progress and long on decisions that prevent expensive changes later. Skipping it is how projects end up rebuilt halfway through.
- Week 2 — Copy and design direction. Real writing gets drafted for your key pages, and the visual direction — layout, colors, typography — takes shape. This is where a site stops looking like a template and starts sounding like your business. You approve a direction here so the build isn't guessing.
- Weeks 3 to 4 — Build and assembly. Pages get built out, your photos and content get placed, forms get wired to actually deliver leads to your inbox and phone, and the whole thing is made fast and readable on a phone. Most of the "website" you picture happens here.
- Week 5 — Review and revisions. You walk the site, we fix what's off, and we tighten the copy and calls to action. One or two rounds is normal and healthy. This is not the week to discover you wanted a fourth service page — that's a Week 1 conversation.
- Week 6 — Launch and technical setup. Domain, SSL, analytics, Google Business Profile connection, and the basic on-page SEO get finalized before the site goes live. Then it's watched for the first few days to catch anything real traffic surfaces.
Simple sites compress this to 2 to 3 weeks, mostly by collapsing discovery and shrinking the build. Bigger builds stretch weeks 3 through 5 as page count and custom work grow. The shape of the process stays the same — the middle just gets longer.
What makes a website take longer
Almost every delay traces back to one of a handful of things. Knowing them in advance is how you keep "how long to build a website" from turning into an open-ended answer.
- Page count. A 5-page site and a 25-page site are not close. Every service page, city page, and blog section adds design, copy, and a review pass. If you want ten service pages, expect the calendar to reflect ten service pages.
- Custom design vs. template. A layout built specifically for your trade takes longer than dropping your logo into a stock theme. For a business trying to stand out in a crowded local market, that extra time is usually where the results come from.
- Who writes the copy. If you're writing it, the timeline runs on your schedule and your available evenings. If it's written for you, drafting and your approval become the pacing item. Either way, words are frequently the slowest part of a site — not code.
- Photography. Waiting on real job-site photos, or scheduling a shoot, is one of the most common silent delays for trade businesses. Stock images are faster but read as generic, and customers notice.
- Integrations. Online booking, payments, quote calculators, or a CRM connection each add setup and testing time. "Just add a booking button" is rarely just a button.
- Approvals. A site where three partners each need to sign off moves slower than one where a single decision-maker can say yes. Every extra approver adds a round trip.
None of these are problems. They're choices with a time cost attached. The trick is deciding them up front instead of mid-build, when changes are most expensive. A clear scope on day one prevents the slow, quiet stretch of a project that never quite finishes.
Why the wait is almost always about content
If you could fix one thing to cut most website timelines, it wouldn't be code. It'd be content readiness. The pattern is consistent: the build races ahead, then parks for two weeks because the site needs your before-and-after photos, your list of towns you serve, and confirmation of your hours.
Think about what only you can answer. What services do you actually want to promote? Which are the money-makers versus the ones you'll take if asked? What makes a customer choose you over the other guy across the county? What's the one thing you want every visitor to do — call, book, or fill out a form? A builder can guess, but guessing costs revision rounds, and revision rounds cost weeks.
The fastest projects tend to have one thing in common, and it isn't the biggest budget. It's an owner who spent one focused afternoon before kickoff: pulling twenty good photos into a folder, writing three plain sentences about each core service, and listing every town they'll drive to. That single afternoon can pull a launch date closer than any amount of chasing on the build side.
So when you're comparing timelines, ask yourself honestly how ready your content is. If the answer is "not very," build that into your expectations — or start gathering it now, before the meter's running. Content you can hand over on day one is the cheapest speed you'll ever buy.
A website can only move as fast as its slowest input, and the slowest input is almost always the words and photos only you can provide.
Rush jobs, phased launches, and when speed backfires
Sometimes you genuinely need to move fast — a competitor just launched, a busy season is coming, or your old site went down and took your leads with it. There are legitimate ways to speed things up without buying a site you'll regret.
The best one is a phased launch. Instead of waiting for all thirty pages, you go live with a sharp core — home, main services, contact, and your service area — in two to three weeks, then add depth over the following weeks. Your business stays visible and taking calls while the rest gets built. For a seasonal Virginia trade, being live and imperfect in March beats being flawless and invisible in May.
What's worth steering away from is the true rush job — the "live by Friday" template with placeholder copy and forms nobody tested. Speed there comes straight out of the parts that make a site work: real writing, a design fit to your trade, and lead capture that actually delivers. The most expensive version of a website is the one you pay to rush and then pay again to rebuild.
A form that silently fails is worse than no form at all, because you'll spend weeks assuming the phone is quiet when the truth is the leads never arrived. Rushed builds are where those failures hide.
If your timeline is tight, say so at kickoff. An honest builder will tell you what's realistic and where a phased approach protects both the date and the quality — instead of nodding along and shipping something broken to hit a Friday.
How to plan your own timeline (and hit it)
You have more control over your launch date than you think. Most of it comes down to being ready and being decisive — two things no builder can do for you.
- Gather content before you start. Photos, service descriptions, service-area towns, hours, and any reviews you're proud of. This is the single highest-leverage thing you can do, and you can start today.
- Name one decision-maker. Feedback from a committee is where timelines go to die. Pick the person who can give a final yes and let the rest weigh in through them.
- Batch your feedback. Send all your revision notes at once, not a trickle over ten days. One clear round beats five scattered emails that each restart the clock.
- Decide integrations early. Know up front whether you need online booking, payments, or a quote form, so nothing gets bolted on at the end and re-tested under deadline.
- Set a real launch date and work backward. A date on the calendar keeps everyone — including you — honest about when photos and approvals are actually due.
Do those five things and a 6-week project routinely lands closer to 4. Skip them and a 4-week project drifts toward 8. The build is only half the equation; readiness is the other half, and that half is yours.
If you'd rather have someone run the whole thing — scope, copy, design, and launch — on a clear schedule with a written proposal instead of a vague quote, that's exactly what a Webb Flow web design project is built to do for Virginia small businesses. You bring the content and the decisions; we handle the timeline. When you're ready to put a real date on it, get started here.