Two page types do more for a SaaS site than almost anything else you could publish, and most companies have neither. Use case pages, which show a buyer their own situation. Comparison pages, which help a buyer choose between you and someone else.
Both are unglamorous. Neither gets shared on social media. They sit quietly, catch people who are nearly ready to buy, and give your sales team something to send. Here's how to write them properly.
Why these two pages pull so much weight
A blog post catches somebody with a question. These pages catch somebody with a decision in front of them. That's a different reader, and the numbers show it. The people searching "your product vs their product" have already narrowed the field to two options. The people searching "software for onboarding contractors" have already decided they need a tool and are describing the job they need done.
Competition for those searches is also thin, because almost nobody writes them. Your homepage is too general to rank for a specific job. Your features page lists capabilities instead of situations. So a reader with a specific need finds nothing, and either guesses or goes elsewhere. That gap is the opportunity, and it's why I put both page types at the front of any funnel plan.
Use case pages: one page per job
A use case page covers one specific thing customers hire your product to do. Not one feature. One job, described the way a customer would describe it. "Onboarding seasonal staff" is a job. "Bulk import" is a feature that helps with it.
The test is whether a buyer could read the page title and think "that's literally my situation." If the title describes your software instead of their day, it's a features page wearing a different hat.
What goes on the page
- 1The situation, in the reader's words. Describe the mess they're living in specifically enough that they recognise it. This paragraph decides whether they keep reading.
- 2What it costs them now. Time, errors, money, the thing that keeps going wrong. Be concrete.
- 3How your product handles it, step by step. Not a feature list. The actual sequence of what happens.
- 4What changes afterwards. Say it in terms a buyer can check, not in adjectives.
- 5Who this is not for. A sentence here saves everyone a wasted demo and makes the rest of the page more believable.
- 6One clear next step. A demo, a trial, or a specific page, and nothing competing with it.
Three to five of these will usually cover most of what your product gets bought for. Resist writing fifteen. A thin use case page is worse than none, because it reads as filler and drags the good ones down.
Where use case pages go wrong
- They're the same page with one noun swapped out. Readers and search engines both spot it, and it does more harm than publishing nothing.
- They describe the feature rather than the situation, so the reader never sees themselves.
- They're written for a job nobody actually buys the product for, usually because somebody in marketing liked the keyword.
- They have no next step, so the reader who was finally convinced has nowhere to go.
- They sit in the blog instead of the main navigation, where buyers can't find them.
Comparison pages: the ones everybody is scared of
Writing about your competitors feels risky. It isn't, and here's the logic. People search "you vs them" whether or not you publish anything. Right now, the page they find is either your competitor's version, which is unlikely to be kind to you, or a review site that gets the details wrong. Staying silent doesn't keep you out of the conversation. It just means you have no say in it.
The rule that makes these pages work is simple. Be fair enough that a reader trusts you, including where the competitor is genuinely better. You lose a few buyers who were always going to suit the other tool, and you gain credibility with everyone else, which is a trade worth making every time.
| Element | Page that works | Page that gets closed |
|---|---|---|
| Tone | Fair, specific, dated | Every row happens to favour you |
| The competitor's strengths | Named plainly | Missing, or faint praise |
| Who should pick them | Stated in a sentence | Never mentioned |
| Facts | Checkable, with a last-updated date | Vague, or quietly out of date |
| Pricing | Real numbers, with what drives them | "Contact us for a quote" |
| Next step | One, clear | Three competing buttons |
How to keep a comparison page honest and current
Two practical habits. First, only state things about a competitor you can point to on their own public pages, and link to them. If you can't source it, leave it out. Second, put a visible last-updated date on the page and actually revisit it when either product changes. An out of date comparison is a liability, because the first thing a competitor's sales team will do is screenshot the row you got wrong.
Keep the writing calm as well. The temptation is to get a dig in. Resist it. A reader comparing two tools reads snark as insecurity, and the competitor's page right next to yours will seem more adult by comparison.
Alternatives pages are the quiet cousin
Worth mentioning because it's cheap to add. People search "[competitor] alternatives" when they're already unhappy, which makes it one of the warmest searches in B2B software. An alternatives page lists the real options, including ones that aren't you, and explains which situation each suits.
Yes, you're sending some readers elsewhere. You're also the site that helped them decide, which is a good position to be in when the tool they picked disappoints them too. These pages are easier to rank for than almost anything else and they age well.
Where these pages should live
Not buried in the blog. Use case and comparison pages are sales pages, so they belong in your main navigation or at least one click from the homepage. Put them under a clear path like /use-cases/ and /compare/, link to them from your features page, and link between them where it makes sense.
Internal links matter more here than on a blog post. A reader on a comparison page is close to deciding, so give them the use case page that matches their job, the pricing page, and the integration page for the tool they already use. Each of those is a reason to stay instead of going back to the search results.
The page that wins a buyer is rarely the clever one. It is usually the one that described their situation accurately and told them who it is not for.
A realistic first month
Pick the two competitors your sales team hears about most and write those comparison pages. Pick the three jobs customers most often hire the product for and write those use case pages. That's five pages, and it's a month of focused work rather than a quarter.
Then check the simplest thing available: does your sales team send them? If a page gets forwarded to prospects in week two, you wrote the right page. If nobody uses it, ask them why, because the answer tells you what the next page should be. That feedback loop beats any keyword tool I know of, and it's part of how I pick topics in SaaS keyword research.
Use case pages and comparison pages are quiet, specific, and slightly uncomfortable to write. That's exactly why so few companies have them, and why the ones who do tend to win the searches that matter most.
If you'd like help working out which five to write first, send me your site and your competitor list. I'll come back with the order I'd do them in, free. Writing these pages is the part of my SaaS content work that moves pipeline fastest.
Frequently asked questions
A page about one specific job customers hire your product to do, described the way they would describe it rather than as a feature. A good one makes a reader think the page is about their exact situation, then shows the sequence of how the product handles it.