How Long Does It Take to Build a Business Website? (Real Timelines, Not Agency BS)

"How long will this take?" is the question every client asks in the first 10 minutes of a Discovery Call.

The agency answer is "6-12 weeks." The honest answer is: it depends almost entirely on how fast you can get me the content.

I'm going to walk through the real timelines for business websites in 2026, broken down by scope, and explain which phase actually takes the longest (spoiler: it's not the one you think).

The four scopes, with real timelines

Landing page (1 page, marketing campaign)

Build time: 3-5 business days. End to end, including copy, design, dev, and launch.

A landing page is genuinely fast. You need:

• One hero, one value prop, maybe 3-4 sections
• One form or CTA
• A clean thank-you flow
• Tracking set up (GA4, a conversion event)

If you've already got brand assets, logos, and rough copy, a competent dev can ship this in a week without breaking a sweat. If you don't have any of that, budget another week for the content pass.

What actually takes the time: waiting for Chase-or-whoever to approve the copy. The coding is a day.

Small business website (4-7 pages)

Build time: 2-4 weeks.

Standard small business site — Home, About, Services, Contact, maybe a couple service detail pages. No CMS needed for content, no blog (or a basic one), no login.

Week 1: structure, design decisions, content intake. Week 2: build the pages. Week 3: content refinement, SEO setup, QA. Week 4 (if needed): revisions and launch.

What actually takes the time: content. You'd be stunned how long it takes a busy small business owner to write (or approve) 2,000 words of copy across 5 pages.

Full business website (10-20 pages, blog, structured content)

Build time: 4-8 weeks.

Now we're talking about a "real" site — services detail pages, portfolio / case studies, a proper blog with categories, maybe gated downloads, SEO-optimized page structure, multiple CTAs per page.

Week 1: discovery, sitemap, content outline approval. Week 2-3: design pass on key templates (home, services, blog post, case study, contact). Week 4-5: build + content entry. Week 6: SEO setup, schema markup, analytics, form integrations. Week 7: QA across devices, performance optimization. Week 8: launch + post-launch fixes.

What actually takes the time: case studies. If your portfolio includes 3 case studies, each one requires a conversation with the client, screenshots or redacted mockups, before/after data, and careful legal review. Plan 1 week per case study just for content collection.

Custom web application (not a website — an app with logins, roles, data)

Build time: 6-16 weeks.

Different beast. Not included in "website" timelines, but worth mentioning because people blur these together. Budget 2-3x a comparable website for the same visual complexity, because you're also building:

• Authentication (Clerk / Supabase / Auth0)
• Role-based access control
• Database schema and API
• Multi-user collaboration patterns
• Error states, loading states, edge cases
• Admin panels

Don't confuse this timeline with a website timeline when you're scoping.

The phases, and which ones drag

Any web project, regardless of scope, has roughly the same phases. Where they drag is predictable.

Phase 1: Discovery & content planning (usually 20% of timeline)

Drags because: the client hasn't made decisions yet. Every question in discovery — "who's your audience," "what do you want visitors to do," "what's your brand tone" — reveals ambiguity that needs resolution before building starts.

How to not drag: show up to the discovery call with answers written down, not thought-about. The difference between a 30-minute kickoff and a 3-week pre-kickoff is whether you've committed your decisions to paper.

Phase 2: Design (20-25%)

Drags because: subjective feedback loops. "Can we make the button pop more?" "I'm not sure about this color." "My wife thought the header felt weird."

How to not drag: pick one decision-maker. One. If three people need to approve every design choice, the project will drift.

“

The design phase expands to fill the number of people with opinions about it.

Phase 3: Build (30-40%)

Drags because: content isn't ready when the dev finishes the template. Developers can only stub in lorem ipsum for so long before work stalls waiting for real copy, real images, real case study details.

How to not drag: have the final content written BEFORE build starts, not during. I know this sounds obvious. Nobody does it.

Phase 4: QA & launch (15-20%)

Drags because: finding edge cases ("the contact form doesn't show the success message on iPhone 13 Safari") and doing the boring pre-launch checklist (redirects, analytics, sitemaps, meta tags, broken link audit, performance tweaks).

How to not drag: budget this phase explicitly. A launch week is real. Rushing it gets you an analytics dashboard that's silently broken for three weeks.

The math on "fast-tracked"

When a client says "we need this in 3 weeks," I do the mental arithmetic:

• 3 weeks = 15 business days
• Subtract 3 days for QA / launch
• Subtract 2 days for design decisions (realistically 2-3)
• That leaves 10 days for build + content

10 days of build time can produce a very nice site. 10 days of build time cannot produce a nice site plus custom copy for 12 pages plus 3 case studies written from scratch plus photography plus video editing.

What actually happens on "3-week timelines":

• Content is half-baked, leading to "we'll update it later"
• Design skips exploration and goes straight to the safe option
• SEO basics get skipped
• "We'll add [feature] in v2" shows up a lot

If you actually need something in 3 weeks, that's fine — just be honest with yourself about what you're giving up.

What I build and how fast

My ranges, in calendar weeks, assuming the client is responsive:

I can do this because I don't have a 6-person team that needs to hold status meetings about my work. I don't write a brief, then hand it to a designer, then hand that to a dev. I design and build in the same session. That's the whole trick.

Common timeline killers (avoid these)

A few specific things that push projects from "on time" to "who knows."

1. "Just one more round of design changes"

Every round after round 2 slows the project by a full week, minimum. Not because the changes take a week — because they break momentum. I'm now context-switching between design and code, and so are you.

Fix: agree to 2 design rounds max, in writing, at kickoff.

2. "Can you also integrate it with…"

Scope creep usually shows up in week 3, when someone realizes "wouldn't it be nice if…" Every mid-project integration adds 3-7 days.

Fix: list integrations in the contract. Anything new becomes a v2 item.

3. "Let me have my marketing person review this"

A new reviewer joining in week 4 isn't reviewing the site — they're reviewing the decisions you already made. Expect another full design round.

Fix: marketing person should be on the kickoff call. Not week 4.

4. "We're going to rewrite the content"

Usually the content doesn't get rewritten — it gets blocked by someone's uncertainty about it. The site sits at 95% done for a month.

Fix: write content first, approve it, then build. Don't treat content as a "we'll tighten it up at the end" task.

The honest answer to "how long will this take?"

If you hire me, here's what happens:

• Week 0 (before contract): you answer my scoping questions in writing. We agree on scope. I send a fixed-price quote.
• Week 1: contract signed, deposit paid. I design the homepage and one inner template. You approve direction.
• Weeks 2-4 (small) / 2-6 (full): I build. You see progress via a staging link every Friday.
• Final week: QA pass, content tweaks, performance audit, SEO audit, launch.

Total: 3-8 weeks depending on scope, assuming you're responsive. If you're not responsive, we add a week per week of lag. That's not a threat — it's just math.

---

If you've got a website project in mind and want a real timeline (and price) for it, that's what my Discovery Call is for. 15 minutes, no pitch.