How long a custom website takes (and why it no longer needs to be three months)

“When will it be ready?” is the second question after price. For years the honest market answer was “a few months”: long discovery, slow design rounds, page-by-page build, and content arriving at the end. That does not have to be the default anymore.

What still stretches the calendar

Even when build is fast, timelines slip when:

• Scope is not written down and every week brings another “can we also…?”.
• Copy and photography are missing or change on every review.
• Too many decision-makers and nobody signs off within 48–72 hours.
• Integrations (CRM, booking, payments) are requested without access or docs on time.

Watch out: a fast agency cannot offset a client who takes three weeks to approve a homepage. The clock runs on both sides.

What changed: AI with judgment, not cheap templates

AI genuinely shortens the phases that used to eat the calendar: information architecture, design variants, layout, components, basic technical SEO, copy drafts. A team that uses it well produces in days what used to take weeks.

That does not mean shipping “whatever the model spat out.” The site still has to sound like your brand, respect typography and visual rhythm, and pass human review. If a website looks generic or reads like a chatbot, customers notice — and trust drops. We accelerate the process; we do not lower the bar for quality or originality.

How we run it at Bitora (about four weeks max)

For a custom corporate site with a closed scope, we work to a realistic ceiling of about four weeks to a publishable site — provided content and approvals are not blocked on the client side.

Typical order (compressed, in parallel where it helps):

1. Short discovery — goals, pages, integrations, success criteria.
2. Design and art direction — a clear proposal, few rounds, fast decisions.
3. Build — owned code, a CMS your team can use, agreed forms and integrations.
4. Content and polish — copy and images in parallel; final review, technical SEO, go-live.

If the project is larger (complex catalog, client portal, many integrations), we split scope: a useful first version in that window, then expansions. We do not treat “three months of silence” as the normal path.

What we need from you to hit the date

• Scope agreed in writing before work starts.
• One contact who can approve on behalf of the team.
• Copy and images (even drafts) early, not on the last day.
• Access to domains, analytics or CRM when something must connect.

How we do it at Bitora

We use AI where it speeds work without leaving a “generic product” fingerprint, and human review where brand matters. The goal is not to ship for the sake of shipping: it is an owned, fast, editable site on a calendar an SME can live with.

For a realistic estimate on your case, see custom web development or our corporate website solution.