Why your SaaS homepage isn't converting (and why design won't fix it)

Your homepage is doing too much explaining. That's why it isn't converting.

Read your headline and ask one question. Does it describe what your product does, or what your buyer gets?

If it's the first one, you've found the problem. Design won't fix it. Neither will more traffic.

The address gap

We build products from the inside out. We know every integration and every edge case the thing quietly handles. That intimacy is how good products get built, and it's exactly why good products get described badly.

When we know a product deeply, we describe what it is. "AI-powered customer support platform." "Unified data observability suite." "End-to-end workflow automation."

Every one of those is accurate. None of them answers the question the visitor arrived with, which is whether this matters for the situation they're in this week.

So the visitor does the translating themselves. They turn "unified support platform" into "fewer tickets from big accounts sitting unanswered overnight." That's the address gap. It's the work a visitor does to turn a claim about the region into a fact about their own house. Translation tax, and we charge it on every line of capability copy we ship.

Most visitors won't pay it. They click away instead.

Georgiana Laudi, co-author of Forget the Funnel, says feature-centric messaging drops conversion because it makes the prospect translate what a product does into why they should care. April Dunford calls feature-list positioning the most common mistake she sees.

The forecast said a 40 percent chance of rain. It was right, and you still didn't know whether to move the party inside.

Accurate for the region. Useless at the address where somebody has to decide.

Category copy is that forecast.

Fourteen hours to two

Two versions of the same product.

The capability version. "AI-powered customer support platform."

The outcome version. "Cut your support team's first-reply time from 14 hours to 2."

A support ops lead reads the second one and thinks, that's my queue. Nothing to translate.

Two things are doing that work. The number gives the reader something to check against their own backlog, where "faster replies" gives them nothing to check at all.

The other is "first-reply time," a pain that already has a name inside support orgs. The right visitor knows they're the right visitor without the copy ever saying "for support teams."

The number is also carrying credibility. A specific claim says somebody measured something for someone like you. Vague claims say the opposite, that we don't have the receipts and are hoping nobody asks.

"14 hours to 2" stops the scroll. "Faster support workflows" never will.

The for-everyone trap

If outcome copy converts better, why do we keep shipping the other kind?

Proximity, first. The closer we sit to our own product, the harder it gets to read the page as a stranger.

Of course a unified support platform means faster replies and fewer dropped escalations. Obvious to us. Invisible to them.

Then fear. If we say we cut first-reply time from 14 hours to 2, what happens to the buyer whose problem is something else?

So we hedge. We write copy wide enough to cover every use case, and it converts nobody.

Dunford calls this the "for everyone" trap. Position for everyone who might benefit and you're relevant to no one in particular.

Sharp positioning does two jobs at once. It pulls the right buyer in with a jolt of recognition, and it lets the wrong buyer leave early. Fewer leads is fine when the leads are right.

The before is the product

The homepages that convert best don't describe the product. They describe the situation the buyer was in before they found it.

Your visitor is still living in that before. They're months away from being a customer and they're in the middle of the thing that keeps going wrong.

Name it with precision and they feel seen. Once they feel seen, they'll believe you understand the problem well enough to have solved it.

Finding that language takes one question, asked of your best-fit customers. What would have happened to this business if you'd never found us?

The answers come back concrete and slightly alarming. The escalation backlog would have taken the renewal. The two people who quit would have been four.

Nobody names a missing capability when you ask it that way, because a missing capability was never what kept them up.

That answer is your positioning. It's the pain the product prevents, in the words of someone who lived it.

"We were drowning in escalations bouncing between three queues for days." That's the sentence a customer says out loud in month eleven.

A homepage that opens with it proves you were in the room when the problem was real. A feature list can't prove anything.

Counting the tax

Read your headline, your subheadline, and the paragraph above the fold. For each phrase, ask whether it names a capability or a situation the buyer can feel.

Capabilities read like this:

• "AI-powered automation"
• "Real-time visibility"
• "Unified platform"
• "Frictionless integration"

Four phrases with no texture. Not one of them says compared to what, or for whom.

Situations read like this:

• "Your support team stops losing customers to tickets nobody saw"
• "Know within an hour when a key account goes quiet, while the renewal can still be saved"

Each one carries a before and an after. Each implies a specific person with a specific frustration.

Count both columns. If capabilities outnumber situations by more than two to one, you have your diagnosis.

Then run the translation on the worst offender. Take a capability claim, say "automated ticket routing," and ask what the buyer does without it. They track escalations by hand in a spreadsheet and find out on Thursday that a ticket from a key account sat for a week because nobody flagged it.

Now name what they get. "Know within an hour when any ticket goes silent, before it costs you the customer."

Same capability underneath. No tax on top.

Working through every claim on the page takes an afternoon. The lift will outlast whatever design refresh is queued behind it.

Stop forecasting the region. Say what's happening at their house.

---

For the wider picture of B2B SaaS positioning strategy, including frameworks, common failure patterns, and how positioning connects to messaging, ICP, and GTM, see the B2B SaaS positioning guide.

What to do next

If your homepage reads back as a list of capabilities and you can't say which buyer it was written for, that's a positioning problem and a fast one to diagnose.

A positioning audit finds the address gap line by line and rewrites the first hundred words around the buyer's before. If that's where you are, start here. The first conversation is free.