How to Plan a New Website or Redesign Without Wasting the Budget

Most website projects do not fail in the code.

They fail in the planning: unclear goals, a growing page list, content nobody owns, and a “quick redesign” that turns into a platform rebuild halfway through.

If you are launching a new website or planning a website redesign, this guide is the decision sequence we use before custom website development starts — so budget and timeline stay intact.

---

1. Decide the job of the website

Write one sentence:

In 12 months, this site should primarily help us ____.

Examples:

• Book more qualified service leads
• Explain a complex offer so sales cycles shorten
• Support a brand relaunch with a flagship presence
• Separate marketing storytelling from a commerce storefront

If the team cannot agree on the job, you will argue about homepage hero copy for weeks. Get the job right first.

---

2. Choose: new site, redesign, or rebuild

Path	Use when	Avoid when
New website	You are launching, consolidating, or starting fresh	You only need a content refresh on a healthy site
Redesign	Platform is sound; UX, visuals, or IA are the problem	The CMS/theme cannot support the structure you need
Rebuild	Technical debt, plugins, or architecture block growth	You mainly need better photography and copy

Still unsure? Use our framework in Rebuild vs Optimize, then validate with a free site audit.

---

3. Freeze the sitemap before design

List every URL you need at launch — not every URL you might want someday.

For most company and service sites:

• Home
• About / team
• Core service or product pages
• Proof (work, reviews, case studies — even if light)
• Contact / book / start a project
• Legal (privacy, terms)

Optional but high-value: location or service-area pages, resources/blog, careers.

Rule: If a page does not have an owner who will supply content, it does not make the v1 sitemap.

---

4. Assign content ownership early

Website projects stall when design is done and nobody has written the About page.

For each sitemap item, name:

• Owner (who drafts)
• Approver (who signs off)
• Source (existing PDF, deck, SME interview)

Content can run in parallel with design. It should not start the week before launch.

---

5. List integrations before you pick a stack

Write down what the site must talk to:

• Forms → email / CRM / inbox
• Booking or scheduling
• Analytics and ads pixels
• Newsletter
• Commerce, donations, or payments (if any)
• Single sign-on or member areas (if any)

Integrations change architecture. Discovering “we need HubSpot + Calendly + a dealer locator” in week six is how timelines slip.

Stack guidance for custom builds lives on our Custom Web Development page — Craft CMS, Next.js headless, or Shopify when commerce is primary.

---

6. Define success metrics (simple ones)

Pick 3–5 measures you will look at 30–90 days after launch:

• Form submits or calls from the site
• Key landing page conversion rate
• Organic traffic to money pages
• Core Web Vitals / mobile speed
• Time for your team to publish a new page

If success is only “it looks modern,” you will not know whether the investment worked.

---

7. Plan SEO carryover and redirects

For redesigns and rebuilds:

• Export current top URLs by traffic and conversions
• Map old → new URLs before launch
• Keep titles/H1s intentional on money pages
• Preserve (or improve) internal links to services and contact

Skipping redirects is the fastest way to donate organic traffic to competitors.

---

8. Set a realistic timeline

A typical custom marketing site:

1. Discovery & scope — 1–2 weeks
2. IA / UX / design system — 2–4 weeks
3. Build & CMS — 4–8 weeks
4. Content, QA, launch — 2–3 weeks

Total: often 8–16 weeks, assuming content keeps pace. Parallel work compresses the calendar; missing content expands it.

---

9. Know what “custom” actually buys you

A template is fine for experiments.

Custom website development is for when you need:

• Brand-distinctive UI that is not obviously a theme
• A CMS your team can run without breaking layout
• Performance as a requirement, not a plugin
• Structure that search engines and AI assistants can understand
• Room to add commerce, booking, or integrations later without a second rebuild

That is the work we do in Custom Web Development — new sites and redesigns for companies past templates, including service and hospitality brands that do not need a storefront on day one.

---

Planning checklist (copy this)

• One-sentence job of the website
• Path chosen: new / redesign / rebuild
• v1 sitemap frozen with owners
• Integrations listed
• 3–5 success metrics defined
• Redirect / SEO plan (if replacing a live site)
• Launch window and content freeze date
• Budget range aligned to scope

When that list is solid, you are ready to build — not before.

---

Next step

If you want a technical and content baseline on your current site, run a free site audit. If you already know you need a custom build or redesign, start a project and we will map the right engagement.