"72-hour website" sounds like marketing. Sometimes it is. Sometimes it is a real thing — but only when the scope, the assets and the platform line up before the clock starts.

This is the honest version of what 72-hour delivery actually looks like, written by someone who ships them.

What 72 hours means in practice

Three working days. Roughly 20–24 hours of actual build time. That is enough time to:

Write or edit copy for 5–8 pages
Design and build a clean, mobile-first layout
Wire up forms, analytics and basic SEO metadata
Test across major browsers and devices
Deploy to production with a custom domain and SSL

It is not enough time to:

Run a brand discovery
Photograph a business
Run a multi-stakeholder approval process
Build complex integrations (custom APIs, multi-step checkouts, gated portals)
Reverse-engineer a strategy from scratch

The 72-hour format works because every one of those constraints is dealt with before the clock starts, not during.

What has to be in place before day one

Studio 72 only confirms a 72-hour slot when these are sorted:

**Decision-maker available.** One person who can approve the build without committee. If three stakeholders need to sign off, the format does not fit.
**Brand assets ready.** Logo (vector or high-res), colour palette, font preferences. If these need to be created from scratch, add a week.
**Photography.** Either existing usable photos or a willingness to use stock + AI-generated imagery. A photoshoot is its own project.
**Content direction.** Not finished copy — a clear sense of services, prices, audience and the action you want visitors to take. Studio 72 writes the copy, but needs the inputs.
**Domain and email already configured.** DNS access on day one, not "I'll find that login during the build."

When all five are in place, 72 hours is achievable. When any one is missing, the project becomes a normal 2–3 week build.

What the day-by-day looks like

A typical 72-hour Studio 72 build:

Day	Hours	What happens
Day 1 morning	4	Kickoff call (60 min), copy drafted for all pages
Day 1 afternoon	4	Design system set up, hero + about pages built
Day 2 morning	4	Services / products pages built, contact form wired
Day 2 afternoon	4	SEO metadata, analytics, schema, mobile QA
Day 3 morning	3	Client review call, revisions applied
Day 3 afternoon	3	Final QA, deploy to production, DNS cutover

Not glamorous. Just consecutive focus.

What 72 hours can't do well

Three categories of project that should not be forced into the format:

**E-commerce with more than 30 products** — product photography, descriptions, variant configuration and tax setup eat the timeline
**Membership or gated content** — auth, billing, member dashboards need testing time the format does not allow
**Multi-language sites** — translation QA is a separate workstream, not a "we'll add it" task
**Complex CRM integrations** — a Salesforce-connected lead form needs more than 24 hours of testing alone

For these, Studio 72 uses a longer 2–4 week format. The 72-hour option is reserved for projects where the constraint is realistic.

Why the format exists at all

Most web projects fail not because the work is hard but because the timeline is loose. Eight weeks becomes twelve. Twelve becomes "let's revisit in the new year." Decisions made in week three get re-litigated in week seven.

A hard 72-hour timeline forces:

Early scope-locking (because there is no time to renegotiate mid-build)
Decisive client review (one round of revisions, not five)
Clean technical choices (no time for half-implemented features)

The result is a small business website that is live, useful and doing its job — built in three days instead of three months.

What it costs

The 72-hour format does not carry a rush premium. Pricing matches the standard packages:

Package	Price	72-hour eligible
Starter	£497	Yes (most cases)
Pro	£1,497	Yes (with assets ready)
Signature	£2,997	Sometimes (depends on scope of integrations)

The format is built into the production process. It is not a separate product.

Who should book one

Use the 72-hour format when:

The current site is actively losing leads or embarrassing
You have a launch event, campaign or grant deadline forcing a date
You have already wasted 3+ months waiting on another agency

Skip the format and use a normal timeline when:

You are still figuring out what the business does
The site is part of a wider brand refresh
You need significant custom functionality

Next steps

Run /audit to see whether your current site needs the rebuild, or check eligibility for a 72-hour slot at /get-started.

*Garth Adams runs Studio 72 and ships small business websites in 72 hours from Cardiff when the scope fits the format.*

The 72-Hour Website: What's Actually Possible (And What Isn't)