Two days is enough for a real website. It is not enough for every website, and the difference is worth being honest about.
What makes 48 hours possible
The scope is fixed before the clock starts. We agree exactly what pages exist and what each says. Adding a page halfway is what turns two days into two weeks — not the building.
The content exists. This is the real constraint. Design and code are fast; waiting for someone to write their own About page is not. We can write it from a conversation, but that conversation has to happen at the start.
One team, no handoffs. Nobody is waiting for a designer in another city to send a file to a developer who has not read the brief.
The infrastructure is solved already. Hosting, deployment, SSL, analytics, forms, performance budgets — we are not deciding those per project. That is weeks of decisions that simply do not recur.
What actually happens
Hours 0–4 — brief and structure. What the business does, who it is for, what a visitor should do. Then the page list and what each page has to achieve. This is the only part where being slow is worth it; everything downstream inherits the mistakes made here.
Hours 4–16 — design and copy. Real pages with real words, not a mood board. You see the actual thing, on a staging link, from the first day.
Hours 16–36 — build. Structure, responsive behaviour, motion, forms. Built for speed and search from the start, because retrofitting either is expensive.
Hours 36–44 — the unglamorous half. Metadata, Open Graph, structured data, sitemap, analytics, form testing on real devices, keyboard and screen reader checks, Core Web Vitals. This is what separates a site that ranks from a site that merely exists.
Hours 44–48 — review and launch. Your round of changes, domain pointed, SSL live, handover.
When 48 hours is the wrong promise
We say so rather than take the work:
- Web applications. Logins, dashboards, payments, user data. These are scoped and time-locked separately, and the timeline is honest.
- Ecommerce with real catalogue depth. A few products, fine. Hundreds of SKUs with variants and inventory, no.
- Content that does not exist yet. Fifty pages of legal or medical copy cannot be written responsibly in two days.
- Multi-stakeholder approval. If four people must agree on the headline, the constraint is the meetings, not us.
What you get either way
A site you own outright. Fast, indexable, accurate on a phone, and built so the next change is cheap. Then we stay on it — a site that launches and rots is a failed project regardless of how quickly it shipped.
See what we have shipped, or tell us what you need and we will tell you honestly whether it is a 48-hour job.