A SaaS website redesign usually starts as a design request and turns into a platform question within the first call. The marketing team wants new pages. Then it turns out the current site is a React single page app that scores poorly on mobile, or a WordPress install with a dozen plugins nobody dares update, or a Webflow project that has outgrown its CMS limits. We handle the B2B SaaS website design and the replatform as one project, because doing them separately means building the same pages twice.
Signs the platform is the problem
Three things tell us a redesign alone will not help. Pages that should be static load several hundred kilobytes of JavaScript before anything appears. Every new landing page needs a developer. And the site has drifted from the product so far that a prospect who signs up feels they have landed somewhere else. If you see only the last one, a redesign on the existing stack is cheaper. If you see the first two, moving platforms usually pays for itself.
Two SaaS replatforms we have shipped
A US Series-B B2B SaaS ran its marketing site as a React single page app. A heavy bundle, an analytics script and an embedded demo widget pushed LCP past four seconds on mid-range phones, and marketing waited days for layout changes. We rebuilt it in Astro over ten weeks. LCP fell from 4.2s to 1.4s, Lighthouse performance reached 98 and every existing URL kept working. Details are in the Astro marketing site case study.
A European mid-market B2B SaaS had its marketing site on WordPress. We moved it to Payload CMS with page blocks the marketing team could combine on their own. Time to publish dropped by about 65%, LCP on the main landing page went from 4.2s to 1.7s, mobile Lighthouse performance reached 96, and engineering spent about 40% fewer hours a month on content tasks. See the Payload CMS build case study.
How the move is planned
We start with an export of every URL Google has indexed, plus the pages that bring signups and demo requests. Each one gets a destination on the new site. Titles, meta descriptions and structured data move across unless we have agreed to change them. Content is migrated with scripts we can run again, so a late edit on the old site does not get lost.
The new site runs on a preview URL for weeks before cutover. Your team edits real content in the new CMS while the old site is still live. On launch day we switch DNS, run the redirect tests again and watch Search Console and analytics for the weeks after. Our website migration page covers the same process for sites outside SaaS.
Choosing the new stack
For most SaaS marketing sites we pick Next.js or Astro on the front end and a headless CMS behind it. Astro suits sites that are mostly content and need to be fast with very little JavaScript. Next.js suits sites with logged in areas, heavy personalization or a docs section rendered on the server. On the CMS side, Payload keeps content in your own database and repository, while hosted options such as Sanity, Contentful and Storyblok suit teams that prefer not to run anything. Our headless CMS agency page compares them in more depth.
The redesign is part of our SaaS website design work. If the app needs work as well as the site, our software development for SaaS companies covers the product side.