How to redesign a SaaS website for a new ICP

Your site was built for a different buyer. Here is how to reposition it without losing the search equity and pipeline you already have.

Ziyan Abbas

To redesign a SaaS website for a new ICP, lock the new buyer and claim first, audit every page by which buyer it serves, keep the URLs and content that still rank, then redesign the homepage and the pages that carry the new story. Do it as one fixed-scope sprint rather than a slow page-by-page edit, so the site stops speaking to two buyers at once.

Signs your website is still speaking to the old ICP

A website lags the business by about two quarters. These signals mean it is describing a buyer you no longer sell to.

  • Sales rewrites the pitch on every call because the site does not match what buyers say.
  • The hero claim, logos, and case studies point at a segment you are moving away from.
  • Paid or outbound traffic from the new segment lands on a page that fails the stranger test.
  • Feature pages use the old buyer's vocabulary, so the new buyer cannot find the problem you solve.
  • Marketing cannot ship new-ICP pages quickly because there is no component system to build them from.

Step 1: Lock the new buyer and the claim

Do not open design until the new claim is specific enough to design against. Write the new ICP in one sentence, then run two checks. The stranger test: hide the logo, and ask whether a cold visitor from the new segment can state your claim in ten seconds. The team test: ask three people to write the ICP independently and compare. If the answers differ, fix positioning first, because design cannot repair a story the team disagrees about. Read the redesign prerequisites and positioning before website redesign before briefing any agency.

Step 2: Audit every page by which buyer it serves

List every indexed page and tag it with the buyer it speaks to: old ICP, new ICP, or both. Pages that serve both can usually stay with light edits. Pages that serve only the old ICP need a decision: rewrite, redirect, or retire. This audit is also the content map for the redesign, because it shows which page types the new story needs and which ones you already have. A company that needs a dozen new-ICP pages in the next two quarters needs a component system, not a one-off homepage, and that should drive the scope you choose.

Step 3: Protect what already ranks

Repositioning does not mean throwing away search equity. Before anything is redesigned, export your top pages by impressions and clicks from Search Console and mark the URLs that earn traffic. Keep those URLs, keep their core headings where they still fit, and redirect anything you retire to its closest replacement. Preserve schema, internal links, and canonical tags through the migration. The most common repositioning mistake is a launch that wipes out rankings the company spent years earning while it tries to look new.

Step 4: Redesign the homepage and the pages that carry the new story

Redesign in one fixed-scope sprint so the site changes voice all at once instead of drifting between two buyers for months. If the new story only needs a stronger front door, the Signature Homepage at $9,783 ships in nine days. If the new segment needs a set of supporting pages and your team will keep adding more, the Scalable Website System at $22,981 covers a homepage plus five pages and an AI-ready design system in 3.5 weeks. Both include custom development. Weroast builds live and records the behind-the-scenes of its case studies, so you can see how the new identity takes shape before you commit.

Step 5: Migrate, measure, and hand over

Launch with redirects in place, resubmit the sitemap in Search Console, and watch impressions and positions on your protected URLs for the first four weeks. Track pipeline from the new segment, not just traffic. Then hand the system to your team so new-ICP pages ship without a design ticket. A Weroast engagement ends with a plan for your team to take over, including a guide and video showing how to build new pages through Claude, so repositioning becomes an ongoing capability instead of a one-time project.

Best for and not best for

This approach fits post-PMF B2B SaaS and AI companies that have already decided on the new buyer and want the website to catch up quickly. It does not fit teams still debating which segment to serve, because a redesign built on an unstable claim has to be redone. In that case, fix positioning first and return to design after.

What clients say

FAQ

Can’t find your answer?

Book a call and let’s talk

Book a Call

Lock the new buyer and claim, audit every page by the buyer it serves, protect the URLs that already rank, redesign the homepage and the pages that carry the new story in one sprint, then migrate with redirects and hand the system to your team.

Not always. If the new story needs a stronger front door, a homepage sprint may be enough. If the new segment needs many supporting pages and your team will keep adding more, a website system with a modular design library is the better scope.

It does not have to. Keep the URLs that earn traffic, redirect retired pages to their closest replacements, and preserve schema and internal links through the migration. Monitor impressions and positions on protected URLs for the first four weeks.

The Signature Homepage takes nine days and the Scalable Website System takes 3.5 weeks. Timelines hold when the new claim is locked and approvals move quickly.

Fix positioning before design. A redesign built on an unstable claim has to be redone. We will tell you on the first call if you need positioning work first and introduce trusted partners who specialize in it.

Need help deciding what to build first?

Book a sprint call and we will map the right scope for your launch stage.

Book a Sprint

Join our newsletter