The short answer
For a properly built custom site, typical market timelines look like this: a focused site (1–3 pages) runs about 2–4 weeks, a standard business site (4–8 pages) about 4–8 weeks, and an online store or branding-plus-website project about 8–12 weeks. Those numbers assume two things: your content is ready, and decisions get made quickly. When either slips, timelines can double.
What sets the pace
People assume the build itself is the slow part. It usually isn’t. Four things decide how fast a project moves, roughly in this order: content readiness (are the words and photos ready, or does “we’ll send the text next week” become month three?), decision speed (one person who can say yes beats a committee every time), scope stability (each “while you’re in there…” adds days), and the feedback loop (48-hour replies keep a project moving; a two-week silence stops it). All four sit on the client’s side of the table, so they’re yours to control.
How a JMD build runs, week by week
Every project starts the same way: a free 20-minute call, then one fixed, itemized quote. Once you approve it, the build starts, and you get a live preview link in the first week: your site, taking shape at a real URL you can open on your phone. From there, the middle weeks are build-and-refine: you look at real pages, tell me what’s off, and the fixes happen against the live link, usually within days. The final week is polish (speed checks, phone testing, search-engine setup) and then launch. There’s no “big reveal” at the end, because you’ve been looking at the site since week one.
The thing that doubles timelines: content
If a project is going to stall, it stalls on words and pictures. It happens often enough that I plan for it in step one: either your existing content gets edited for the web, or writing is included in the scope, agreed up front in the quote. If you want a faster build, this does more than anything else: have your content ready before the build starts, or hand the writing to the person building the site.
Timeline red flags
Both extremes should worry you. “Live in 3 days” means a template with your logo dropped in, so you’re paying for data entry. No timeline at all means no plan; “it’s done when it’s done” is how six-week projects become six-month projects. And a studio that won’t show you the site until the end has removed your only early-warning system. A good answer sounds like a realistic range up front, a live link early, and a clear statement of what could move the date, most of which will be on your side of the table.
Can it go faster?
Yes, without cutting corners. A focused scope, content in hand, and a single decision-maker can bring a small site in near the bottom of its range. What I won’t do is compress a build by skipping the parts you can’t see: phone testing, speed work, and search-engine basics are why the site performs after launch, and they stay in every build at every speed.
How ready are you? A 20-second check
The three things that decide whether a build lands at the fast or slow end of its range all sit on your side of the table. Check yours:
- 1. Your content: the words and photos. Where are they? (Ready, or close / Mostly in my head)
- 2. Decisions: can one person say yes? (One decision-maker / A few of us weigh in)
- 3. Scope: do you know what the site needs to do? (Settled / Still taking shape)
All three ready — fast lane. Everything that stalls a build is already handled. A project like yours lands at the bottom of its range. For a focused site, that can mean live in about two weeks.
Two of three — nearly fast. One gap between you and the fast lane. Close it before the build starts, or fold it into step one of the process, and you’re at the quick end of the range.
One of three — typical start. This is where most projects begin, and it’s fine: expect the standard range. The free call and the fixed quote are there to close these gaps before the clock starts.
None yet — early days, and that’s okay. Nothing here has to stretch your timeline if it’s handled up front: content planned into the scope, one named decision-maker, and the brief settled on the first call. That’s what the first call is for.
Put the other guides to work
Timeline is one of four questions to settle before you hire anyone. The should-I-even-rebuild question is covered in the seven signs your site is costing you customers, and the vetting side in the ten questions to ask before hiring a web designer (question four covers previews during the build). If you’re still deciding whether to hire anyone at all, start with the website builder vs web designer comparison.