How to write a comparison page that converts

A feature matrix is not a comparison page. Buyers need jobs, tradeoffs, and who it is for.

Most "Us vs Them" pages are spreadsheets in HTML. Fifty rows. Green checks. A red X on the competitor for something nobody asked about. That page does not convert. It performs certainty theater. The buyer still cannot grunt what they get if they pick you.

Why do feature matrices fail?

Because buyers do not buy features. They buy a job done with less risk.

A matrix trains the eye to scan for checkmarks. It does not answer: what breaks for me on Monday if I choose wrong? Who is this actually for? When should I pick the other tool and stop wasting both of our time? If your page cannot say that out loud, you fail the grunt test before the demo is booked.

I have seen teams ship longer matrices every quarter and wonder why demo no-shows climb. Length was not the problem. Clarity was.

What should a converting comparison page include?

Four blocks, in this order.

1. The job. One sentence on the buyer job you both claim to solve. Not your category slogan. The job in their words.
2. Who it is for / who it is not. Two short lists. Be willing to lose bad-fit traffic. That is Convert, not ego.
3. Honest tradeoffs. Where they are stronger. Where you are stronger. If you cannot name one place they win, the buyer will not trust the places you claim to win.
4. The path. What happens after they pick you: trial, demo, or proof asset. One primary CTA.

Wrap those blocks in who / why / how. Who is the role. Why is the desire under the purchase label. How is the mechanism, not the feature dump.

How do I structure the middle without a giant table?

Use three to five buyer jobs as H2s, not twenty features.

Example shape:

• When you need X job done. You: how you do it in plain steps. Them: where they are fine, and where they stall.
• When your team looks like Y. Fit / not fit.
• When budget and risk look like Z. Tradeoffs without drama.

A small table is fine for three proof points. A fifty-row matrix is a hiding place for weak positioning. If early category design is still fuzzy, fix the category sentence before you build the page. A comparison page cannot save a muddy category.

What language should I avoid?

Anything that needs a decoder ring. "Pipeline velocity synergy." "End-to-end AI-native stack." If a stranger cannot grunt the outcome in one breath, rewrite. Also avoid pretending the competitor has no customers. They do. Buyers know. Lying with omission kills the rest of the page.

What are common mistakes on comparison pages?

Three show up over and over.

Competitor strawmen. You list strengths they do not claim and then "win." Buyers who use both tools notice. You lose the ones who were about to trust you.

Category mush. You compare on twenty features that describe the whole market. Nothing is distinctive. If swapping logos still works, rewrite the who-it-is-for block.

CTA confusion. Two primary buttons, a webinar, a white paper, and a chat widget. Pick one Convert action. Demo or trial. Everything else is a distraction on a high-intent page.

How do I know the page is converting?

Not bounce rate alone. Watch demo requests, trial starts, and sales notes that say "they found us on the vs page and already knew the tradeoff." If inbound still asks "so how are you different?" after reading the page, the page failed. Fix the who-it-is-for block first.

What should I do this week?

1. Pick your top competitor by lost deals, not by Twitter drama.
2. Interview two wins and two losses for the language they used when they compared you. Their words beat your matrix.
3. Draft who-it-is-for and who-it-is-not in ten bullets total.
4. Write three job-based sections. Cut every feature that does not serve those jobs.
5. Add one honest "choose them if…" section. Ship it. Measure Convert events for two weeks.

Adapt or fail. Checks in a grid are not a decision.

Start Signals, Convert, Grow

FAQ

What is a comparison page in B2B SaaS?

A page that helps a buyer choose between you and a named alternative by mapping jobs, fit, and tradeoffs. It is not a feature checklist with your logo on top.

Should I build a page for every competitor?

Start with the two or three that show up most in late-stage losses. A thin page for a rival nobody asks about is SEO sludge.

Is it okay to say when the competitor is better?

Yes. Buyers trust pages that admit a tradeoff. You want the right customers, not every visitor.

Where should the comparison page sit in the funnel?

High-intent. Link it from pricing, sales decks, and mid-funnel content. Do not hide it. If you are afraid of the comparison, fix the product or the positioning, not the URL.

How is this different from an objections page?

An objections page answers pushback after interest. A comparison page structures the choice against a named alternative. Related jobs. Different page. Do not mash them into one mushy URL.