Most SaaS website redesigns fail not because the new site looks worse, but because the team redesigned the wrong layer. New visuals on top of the old positioning is repaint, not redesign. Conversion stays flat and the team blames the buyer.
A SaaS website redesign that actually lifts qualified pipeline starts with positioning, then structure, then visuals, then performance. In that order. This is the order every Altair Studio project follows.
1. Pick one buyer before you pick anything else
If your homepage tries to talk to founders, marketers, and engineers at once, it talks to none of them. The first decision is which buyer the homepage is for. Everyone else gets a section, a page, or a separate funnel.
We run a one-hour positioning session with the founder. The output is a single sentence that names the buyer, the pain, and the outcome. Everything downstream defends that sentence.
2. Audit before you redesign
Pull six weeks of analytics. Find the three pages that bring qualified traffic and the two that bleed it. Most teams skip this and end up rebuilding pages that were already converting.
- Top organic landing pages: keep their URLs, improve the content
- Bounce-heavy pages with paid traffic: rebuild from scratch
- Pages with zero traffic: delete unless they exist for sales reasons
3. Information architecture is the redesign
The biggest conversion lever in any B2B website redesign is structure. A homepage that compresses one buyer's full journey into six well-ordered sections beats a beautiful page that meanders. Decide what is a page, what is a section, and what is a sentence.
Pricing gets its own page. Case studies get their own template. The homepage is not a portfolio of intents.
4. Pick a stack that does not slow marketing
If your marketing team needs a developer to publish a blog post, the redesign is already failing. Next.js with a headless CMS is the default for a reason: marketing ships copy, developers ship features, performance is a build-time guarantee.
Webflow and Framer are fine for a v1. They become a tax once SEO and structured data matter.
5. Performance is a feature, not a polish step
Largest Contentful Paint under one second on mid-range Android. Cumulative Layout Shift effectively zero. Total payload under 250kb on the homepage. These are not nice-to-haves; they decide whether Google rewards the redesign with rankings.
6. Write copy before you design
Designers can make weak copy look strong, but only for the length of the screenshot. Real visitors read. Lock the copy first, then design around the words. Hero copy, social proof copy, pricing copy, and CTA microcopy come before any wireframe.
7. Treat the homepage as a single funnel
One CTA. Two if you must. Above-the-fold gives the buyer the outcome and the proof. Mid-page closes the trust gap. Bottom of the page gives the easy yes. Anything else is decoration.
8. Ship in three to four weeks, not four months
A SaaS website redesign that drags past six weeks is no longer a redesign; it is a hostage situation. Tighten scope until the timeline holds. Cut features, not quality.
What changes after launch
Most teams treat launch as the finish line. The first 30 days post-launch are when most of the conversion lift gets unlocked. Watch session recordings, ship copy fixes weekly, kill any section that does not earn its scroll.
This is the order behind how we design SaaS websites. For the execution side, phase by phase, see the B2B website redesign checklist, and for a product built this way, the Orba case study.
If you are weighing a SaaS website redesign, start with a 15-minute call. I will tell you whether a redesign is the right move before proposing one, and if it is, the work starts with a one-week positioning sprint, credited in full against the build.