Most failed website projects don't fail in development. They fail before development even starts — because the client showed up unprepared, the agency had to guess, and what got built didn't match what was actually needed.
If you're about to start a redesign, the prep work below will save you weeks of revisions, thousands of dollars in scope changes, and a lot of frustration. None of it is hard. Most business owners just skip it because nobody told them they should do it.
1. Define the actual goal of the redesign
Not "we want a new website." That's not a goal. Real goals look like:
- "We want to double our online lead volume in 6 months."
- "We want to look as premium as our competitors when prospects compare us."
- "We want to stop losing mobile visitors to our broken responsive layout."
- "We want to be able to update our own content without calling a developer."
Write down 1–3 actual goals. Every design decision should be measured against them. If a feature doesn't serve any of the goals, it doesn't belong in the project.
2. Audit your current site
Spend an hour on your existing site as if you were a brand new customer. Write down:
- Every page that exists
- Which pages get traffic (from Google Analytics)
- Which pages convert (from your contact form data)
- Which pages are outdated, broken, or embarrassing
- What information is missing that customers ask about
This single hour will save you a week of "wait, did we forget the FAQ page?" later.
3. Collect your brand assets
Before development starts, gather everything in one folder:
- Logo files — original vector format if possible (SVG, AI, EPS)
- Brand colors — actual hex codes, not "the blue from our truck"
- Fonts (or font preferences)
- Existing photography — your real photos, not stock
- Any brand guidelines if you have them
If you don't have a logo file and just have a JPG of one, this is the time to find out. Discovering it during week 3 of the project is expensive.
4. Decide who has approval authority
This is the silent killer of website projects: too many cooks. The agency designs the homepage, sends it to you, you love it, you forward it to your business partner, your business partner forwards it to their spouse, the spouse forwards it to a graphic designer friend, and three weeks later you're back to the drawing board.
Pick one decision-maker on your side. Tell the agency that's the only person whose feedback is final. Get input from others if you want, but route it all through one person.
5. Write your sitemap
List every page your new site needs. A simple text outline works:
Home About - Our Story - Team Services - Service A - Service B - Service C Portfolio Pricing Contact Blog
This becomes the foundation of the proposal, the design phase, and the build. If you skip this step, the agency has to guess — and guesses always miss.
6. Gather example sites you like
Spend an hour saving 5–10 websites you like. Don't just pick competitors. Pick anything — outside your industry is often better. For each one, jot down what you actually like:
- "The hero section is super clean"
- "I like how the testimonials look"
- "The way they handle pricing is great"
This gives the designer real reference points instead of trying to interpret "make it modern but classic, bold but elegant."
7. Write your copy (or hire someone to)
This is the #1 thing that delays website projects. The design is done. The development is done. The launch is scheduled. The agency is waiting on... your copy. Which you haven't written. Which you don't want to write. Which now becomes a 6-week delay.
Write your copy before design starts, or hire a copywriter to do it as part of the project. Your homepage, your services pages, your about page. If you wait, the project will wait with you.
8. Decide what content moves over from the old site
Some old pages should die. Some should be kept exactly as-is. Some should be rewritten. Go through your existing site and label each page:
- Keep — stays as is
- Rewrite — same idea, fresh copy
- Kill — outdated, no traffic, or just bad
- New — pages you wish you had
Decide this before the project starts so you're not making content decisions in real time during design reviews.
9. Set realistic feedback timelines
Your agency will send drafts. You'll need to review them. If you take 10 days to respond to each round, your 6-week project becomes a 4-month project. Decide upfront: "I will respond to feedback rounds within 48 hours." Then actually do that.
10. Plan for migration
If you're moving to a new host, switching domains, or changing platforms, talk about how it will happen before the project starts. Will the new site go live on the same domain? How will you handle DNS? What's the rollback plan if something breaks? These are 30-minute conversations that save 30-hour fire drills.
The realistic timeline expectation
For a typical small business site, with the prep above done well:
- Week 1: Discovery, sitemap finalization, brand review
- Weeks 2–3: Design
- Weeks 3–5: Development
- Week 5: Content population, QA, revisions
- Week 6: Launch
At Frost Web Studio we run on a 7-day timeline for most projects — but that only works because we've front-loaded all the prep above before development starts. If you skip the prep, no agency can hit a tight timeline.
The bottom line
Most website redesigns fail at the kickoff, not at the launch. Spend 4–6 hours on the prep above and you'll save weeks of churn, get a better result, and probably pay less than clients who showed up with a vague idea and a logo JPG.
The agencies that deliver fast aren't magic. They're working with clients who came prepared.