A website rebuild rarely fails in design or development. It fails earlier, when nobody decided what the site is for, who signs off on content and what happens to the pages that already rank. Settle these before the first workshop:
- Write down the one job the site has to do better than today.
- Name a single owner for every decision on this list.
- Inventory and grade existing content before planning new pages.
- Protect the URLs and pages that already bring traffic.
- Choose the platform last, once you know who edits what.
Why website rebuilds go over budget
Scope creep on a website is almost never about extra features. It comes from decisions made late: a sitemap reopened after design, copy that arrives three weeks after the templates, a stakeholder who sees the site for the first time at launch review.
Every one of those late decisions forces rework on something that was already finished. The fix isn't a longer discovery phase — it's a shorter list of decisions made early, each with a named owner.
Strategy: decisions 1–4
1. The one job of the site
“Look more modern” is not a job. “Turn enterprise visitors into booked demos” is. Pick the single outcome the new site must improve and write it at the top of the brief — every later trade-off gets checked against it.
2. Primary audience and their question
List the two or three visitor types that matter and the question each one arrives with. A procurement lead asks “is this vendor safe?”; an engineer asks “will this integrate?”. The pages you plan should answer those questions in order.
3. How success will be measured
Agree on two or three metrics and capture a baseline now: conversion rate on key pages, qualified leads per month, organic sessions. Without a baseline, nobody can prove the rebuild worked.
4. Who signs off
One person approves direction, one approves content. Committees are fine for feedback, not for decisions. If the final approver only sees the site at the end, budget for a second round.
Takeaway
If a decision has no owner, it will be made at launch review — by whoever is in the room.
Content: decisions 5–8
5. Content inventory
Export every URL and grade it keep, merge, rewrite or delete. It's tedious for a day and saves weeks later, because design finally works with real content instead of lorem ipsum.
6. Who writes the new copy
Copy is the most common reason launches slip. Decide now whether it's written in-house, by the agency or by a freelancer — and schedule it to land before high-fidelity design, not after.
7. SEO pages to protect
Pull the pages with organic traffic and backlinks. They keep their URLs where possible; everything else gets a 301 redirect mapped before launch. Read more in our notes on legacy migrations.
8. Proof you can publish
Case studies, logos and numbers take the longest to get approved by clients. Start those conversations in week one so the proof is ready when the templates are.
| Decision | Usually owned by |
|---|---|
| The one job of the site | Founder or head of marketing |
| Success metrics and baseline | Marketing, with analytics access |
| Content inventory | Content lead, agency supports |
| Copywriting | In-house team or dedicated writer |
| Redirect map | Agency, checked by SEO |
| Platform choice | Marketing and engineering together |
Build: decisions 9–12
9. Who edits the site after launch
A marketing team that publishes weekly needs a visual CMS and reusable sections. A site that changes twice a year doesn't. This decides the platform more than any feature list does.
10. Platform
Only now compare platforms — Webflow, a headless CMS with Next.js, or something else. We wrote up how we choose between Next.js and Webflow.
11. Integrations
List every form, CRM field, analytics event and third-party script the site must support. Integrations discovered in QA are the most expensive kind.
12. Launch plan
Pick a launch date with a buffer, a freeze window for content, and who is on call the day DNS switches. A calm launch is planned; a lucky one is not repeatable.
Takeaway
Choose the platform last. Who edits the site, and how often, narrows the options faster than any feature comparison.
Turn the checklist into a one-page brief
Answer the twelve decisions in one document, one line each, with a name next to every line. That page becomes the brief the whole project is checked against — and the fastest way to see what's still undecided.
If you'd like a second pair of eyes on it, send it to us — we'll tell you where we see risk before you commit a budget.