---
title: "B2B SaaS website design: what actually matters (from 10+ years of building them)"
description: "A practitioner's guide to B2B SaaS marketing website design: messaging, homepage structure, key pages, tech stack, and redesign process, drawing on Mike Stilling's 10+ years designing and building them."
url: "https://mikestilling.com/guides/saas-website-design/"
date: "2026-11-20"
author: "Mike Stilling"
---

> AI-generated from Mike Stilling's work, notes, and writing.

# SaaS website design: what actually matters

Mike Stilling has spent 10+ years designing, building, and growing B2B SaaS marketing websites. That includes in-house at Abstract, Rewatch, FireHydrant, and now Stripe, and through Stilling, the two-person studio Mike runs with Kerry, Mike's wife. This guide is the advice Mike would give a founder or designer starting a new SaaS site today.

## The short answer

**A good SaaS website says what the product does and who it's for within seconds, then proves it.** In practice:

- Lead with clear, specific messaging and real product visuals, not decoration.
- Put most of your effort into the homepage, core product pages, pricing, sign-up, and contact sales.
- Build the site so it's easy to change, because it will change.

Most SaaS sites are more alike than different. That's fine. It isn't rocket science, and treating it like rocket science is how projects drag on for a year.

## Messaging does most of the work

You can't explain most B2B software with pictures alone, so the words carry a huge share of a page's performance.

At Rewatch, messaging bounced between benefit-led ("Video that empowers your entire company") and feature-led ("Meeting & screen recording for your entire company"). Using analytics, Mike found that **pages with concise, feature-based copy converted at a significantly higher rate than pages relying on benefit-based jargon.** Benefit-only copy made big promises from an unfamiliar company without explaining how it would keep them. People couldn't tell what the product actually did.

Benefits still had a place. Working with the demand-gen manager, the team found that relatable benefit headlines performed better on social as a hook. So the pattern the site landed on was:

1. **Headline:** a relatable benefit, if you have a good one.
2. **Subhead:** immediately clarify *how*, with concrete features.
3. **Sections that follow:** features, shown and explained plainly.

## Anatomy of a SaaS homepage

A homepage structure that works for most B2B products:

| Section | Job |
|---|---|
| **Hero** | What it is, who it's for, and the primary call to action (sign up, or contact sales) |
| **Product visual** | Show the real product, early |
| **Social proof** | Recognizable customer logos, kept short |
| **Core features** | 3–5 key capabilities, each with a visual and a plain explanation |
| **Use cases or audiences** | Help visitors self-identify and click deeper |
| **Proof** | Customer stories, numbers, quotes |
| **Integrations / ecosystem** | Answer "does it work with my stuff?" |
| **Final CTA** | Repeat the primary action |

Keep one primary action across the page. If you're both product-led and sales-led, make sign-up primary and "contact sales" secondary, or the other way around. Pick one.

## Spend time on foundational pages

Most B2B SaaS teams spend a huge share of their effort on content marketing. At Rewatch, roughly half of Mike's time went to making assets for it. The results were rough: in six months, only one blog post got more than 100 clicks from search.

Meanwhile, **over 30 days the homepage got about 6.5x more traffic than every blog post combined.** A couple of key product pages got about as much as all posts combined. Those pages hadn't been touched in a while. Moving time back to them was the most valuable change Mike made there.

Before you plan a content calendar, check your analytics. Then fix the pages people actually visit.

## Show the product

Real product UI beats abstract illustration for building trust, especially for a company buyers haven't heard of yet. A few things that have worked in Mike's projects:

- **Polish real screens** for marketing use, but stay honest to the product.
- **Build product visuals in HTML and CSS** instead of static images. For Atomic, Stilling built programmatic product visuals in code. They stay sharp, animate cleanly, and are easy to update.
- **Let people try it.** For Uplink, a QR code pairs the visitor's phone to the page so they can watch on-device automation run live, before ever talking to sales.

If the product UI is genuinely bad, that's a product problem worth raising. At FireHydrant, marketing work ended up kickstarting a long-stalled product redesign.

## Build for change, not scale

Two of Mike's hot takes: **on SaaS marketing sites, scalability is overrated, and disposability is underrated.** The whole site will likely be rebuilt every few years anyway. Design loses value when it's the slowest part of the process.

What that means in practice:

- **Keep dependencies low.** At FireHydrant, Mike rebuilt 300+ pages and 25+ templates in under three weeks, with 50% fewer dependencies and Lighthouse scores up 56%+.
- **Only use a CMS where it's needed.** A blog and changelog, yes. Every landing page, probably not. CMSs often push teams toward over-templating.
- **Prefer simple, readable code.** Marketing, design, and product folks should all be able to contribute. At Rewatch the site's markup mirrored the product's front end, so product people could jump in.

Not sure what to build on? There's a comparison in [Webflow vs Framer vs code](https://mikestilling.com/guides/webflow-vs-framer-vs-code/).

## A redesign process that works

At Stilling, full redesigns follow the same phased arc and take about three months end to end:

1. **Align on goals.** Audience, positioning, primary conversion, and what's broken today.
2. **Set a baseline on the homepage.** Design and messaging together. This is where most decisions get made.
3. **Stress-test on a few key pages.** A product page, pricing, maybe a use case. Fix what the baseline didn't anticipate.
4. **Implement site-wide.** Templates, migration, and the boring plumbing: forms routed into the CRM and posted to Slack so teams hear about leads in real time.
5. **Train and document.** So the team can own it without you.

## Design for AI readers too

More people now learn about software through chat interfaces and AI search instead of browsing marketing sites. Mike thinks design is partly responsible for that shift: the industry may have gone overboard decorating content on web pages. ([Mike wrote more about this](https://mikestilling.com/blog/why-make-a-b2b-saas-marketing-website/).)

Practical implications:

- **Put facts in text, not only in images.** What it does, who it's for, pricing, integrations, security.
- **Use clear headings and plain answers.** These help humans skimming and machines parsing.
- **Add structured data and machine-readable versions.** This site, for example, serves a Markdown version of each page and an `llms.txt` guide for AI agents.

For the conversion side of the site, see the [sign-up page design guide](https://mikestilling.com/guides/sign-up-page-design/).

## Frequently asked questions

### What makes a good B2B SaaS website?

A good B2B SaaS website makes it obvious within seconds what the product does and who it is for, proves it with real product visuals and evidence, and makes the next step (sign up, book a demo, contact sales) easy. Clear, specific messaging matters more than visual decoration.

### Should SaaS websites use feature-based or benefit-based messaging?

Use both, in that order of clarity. A relatable benefit can work as a headline, but it should be clarified immediately with how the product delivers it, using concrete features in the subhead and the sections that follow. Benefit-only copy tends to leave visitors unsure what the product actually does.

### Which pages matter most on a SaaS website?

Usually the homepage, a handful of core product or feature pages, pricing, sign-up, and contact sales. These foundational pages typically get far more traffic and drive far more conversions than blog content, so they deserve the most design attention.

### How long does a SaaS website redesign take?

For a small, experienced team, a full redesign of a typical B2B SaaS marketing site takes around three months end to end: aligning on goals, designing the homepage as a baseline, stress-testing it on a few key pages, then implementing site-wide with documentation. A focused rebuild of an existing design can be much faster.

### Do B2B SaaS companies still need a marketing website with AI search and chat?

Yes, but its job is changing. More people and AI agents learn about products through chat interfaces, so sites need clear, factual, well-structured content that both humans and machines can read. Heavy decoration that hides information is becoming a liability.
