SaaS website redesign process: a step-by-step plan for startups

Quick answer: A SaaS website redesign runs best in six steps: define the one business problem the redesign solves, audit what the current site already does well, fix the message before the visuals, design the key pages first, build with SEO and analytics protected, then launch and measure for 30 days. Skipping the first two steps is where most redesigns go wrong.

Why so many redesigns disappoint

Founders rarely regret redesigning. They regret redesigning without a reason they can measure. A common story goes like this: the site feels dated, a competitor launched something sharper, a new round closed, and the team decides it is time for "a new website." Months later the new site looks different, but demo requests, signups, and search traffic look the same or worse.

The problem is usually not the designer. It is that nobody wrote down what the old site was failing to do, so nobody could judge whether the new one fixed it. A redesign is a product decision, not a style refresh. Treat it the way you would treat a new feature: start with the problem, agree on what success looks like, and only then open Figma.

If you are still deciding whether you need a redesign at all, start with how often a startup should redesign its website. This article assumes you have already decided, and focuses on how to run the process so the result is worth the money.

Step 1: define the problem in one sentence

Before any design work, write one sentence that describes what the current site is failing at. Good examples:

• "Visitors from paid campaigns land on the homepage and leave without understanding what we sell."
• "Enterprise buyers ask for security details on every call because the site does not answer them."
• "We moved upmarket and the site still speaks to solo developers."

Bad examples are aesthetic only: "it looks old" or "we want it to feel more premium." Those can be true, but they are symptoms. Push one level deeper and ask what looking old costs you. Lost trust on a sales call? Weak conversion on pricing? That is your problem statement.

Then pick two or three numbers you will compare before and after launch. Demo or call bookings, signup rate from the pricing page, and organic traffic to your top pages are the usual ones. If you do not have analytics in place, set it up now, before anything changes, so you have a baseline.

Step 2: audit what already works

Every live site has parts that are quietly doing their job. A redesign that throws them away can lose more than it gains. Spend a few hours on an audit before you brief anyone.

Pages and traffic

List every page that gets meaningful traffic or ranks in search. Note the URL, what it ranks for if you know, and how it converts. Those pages and their URLs need a plan, not an accident.

Messages that land

Look at sales call notes, support tickets, and reviews. Which phrases do customers use to describe your product? Which headline do prospects repeat back to you? Keep those words. A new site that sounds clever but drops the language your buyers already use is a step backward.

Proof you have collected

Customer logos, testimonials, case studies, security pages, and integration lists take time to earn. Inventory them so they get a home in the new structure instead of getting lost in the move.

Step 3: fix the message before the visuals

Most "the website is not working" problems are really "the message is not clear" problems. If the hero cannot say who the product is for and what changes for them, no amount of visual polish will fix it.

Work on the copy for your homepage hero, your core value sections, and your pricing page before visual design starts. It does not need to be final, but the structure and the main claims should be agreed. We cover the order of operations in more depth in website copy or design first.

This is also the moment to decide who the site is for now. Many SaaS companies redesign because they moved from self-serve to sales-led, or from startups to larger teams. The new audience changes what the homepage needs to prove, and that should shape the sitemap as much as the visuals.

Step 4: design the pages that matter most first

You do not need to design forty pages at once. Start with the pages that carry most of the traffic and most of the buying decisions. For most SaaS companies that is:

1. Homepage
2. Pricing
3. One or two core product or feature pages
4. A case study or customer page template

Once these are approved, the rest of the site follows the same system and moves much faster. Designing in this order also means you see the new direction on real content early, instead of on a mood board.

Build the system as you go

As the key pages take shape, capture the components: headings, buttons, cards, testimonial blocks, logo rows, pricing tables. A small, reusable set keeps later pages consistent and makes future updates cheap. It also means marketing can ship new landing pages without waiting on a designer for every one.

Review on real devices

Review every key page on a phone, not only in a desktop browser. Plenty of first visits to B2B sites happen on a phone, often from a link in a message or an email. A hero that works at 1440 pixels wide and breaks at 390 is a common, avoidable miss.

If you want a second opinion on your plan before you commit budget, book a call with our team and we can walk through your current site and what we would change first.

Step 5: build with SEO and analytics protected

The build is where redesigns quietly lose search traffic. Visual changes rarely hurt rankings. Structural changes, done carelessly, often do.

Keep or redirect every URL

Use the page list from your audit. If a URL stays the same, great. If it changes, set up a permanent redirect from the old URL to the closest new page. Do not send everything to the homepage. Do this before launch, not after you notice traffic dropping.

Carry over the basics

Page titles, meta descriptions, heading structure, image alt text, and internal links should all survive the move. Check that the new site has a sitemap, that pages load quickly, and that nothing important is hidden behind scripts that search engines struggle to read.

Reconnect tracking

Make sure analytics, conversion events, and any form or booking integrations fire on the new site exactly as they did before. If the numbers you chose in step 1 stop being tracked on launch day, you will not be able to tell whether the redesign worked.

Step 6: launch, measure, and iterate

Launch is the start of the redesign, not the end. Plan for it.

Run a pre-launch check

Click every link, submit every form, test on mobile and desktop, and confirm redirects work. Our pre-launch design QA checklist covers what to check so the first week is not spent fixing broken buttons.

Give it 30 days of real traffic

Do not judge the new site in the first 48 hours, positively or negatively. Compare your chosen numbers over a few weeks of normal traffic against the baseline from step 1. If a key page underperforms, you now have a specific, fixable question instead of a vague feeling.

Keep shipping small improvements

The best SaaS sites are never finished. A new case study, a sharper pricing table, a landing page for a new segment. Small, regular updates usually beat another full redesign two years from now.

How long a SaaS website redesign takes

Timelines depend on scope more than anything else. A focused redesign of a homepage and a few key pages moves much faster than a full site with dozens of pages, new copy, and new illustrations. The biggest delays are rarely design or development. They are slow decisions: unclear ownership of copy, feedback from too many people, and late changes to positioning.

You can shorten the process by doing steps 1 to 3 well. When the problem, the audit, and the message are clear, design and build mostly move in a straight line.

What we have seen work

We redesigned the website for Entangle, and the redesigned site went on to help the team win clients including FixBIOME, KX Pilates, Dr Siegal's Cookie Diet, and EO. You can read the full story in the Entangle case study.

The lesson we take from projects like that is consistent: a redesign earns its cost when it is tied to a business outcome from the first conversation. Our team works as a product partner on these projects, which means we push on the problem statement and the message before we push pixels. Design and build happen in one team, so the site that gets approved in Figma is the site that ships. You can see more of this work in our web design projects.

A simple redesign checklist

• Write the one-sentence problem the redesign solves.
• Pick two or three numbers and record a baseline.
• List every page with traffic or rankings, and its URL.
• Inventory testimonials, logos, case studies, and security content.
• Agree on the hero message and page structure before visual design.
• Design homepage, pricing, and core product pages first.
• Build a small component system as you go.
• Map redirects for every changed URL.
• Reconnect analytics and conversion tracking.
• Run a full pre-launch check on mobile and desktop.
• Measure for 30 days, then iterate.

Plan your redesign with us

If your site no longer matches your product, your audience, or your stage, we can help you scope the redesign around the result you need, then design and build it in one team. Get in touch with our team and tell us what your current site is failing to do.