Skip to content

Competitor Comparison Pages: Answer “Why Not You?” First

Turn buyer objections into an honest SaaS comparison page, with evidence, approval owners and a plan to keep claims current.

On this page
  1. Who Answers “Why Not You?” on Google and in AI Answers Today
  2. Where To Find the Reasons Buyers Choose Someone Else
  3. How Six SaaS Companies Admit Their Limits
  4. What Goes on the Answer Page
  5. Keeping the Page True After Launch
  6. Frequently Asked Questions

Empact Newsletter

One email a month on what is working in AI search and SaaS go-to-market.

Check your email for a link to confirm your subscription.

You are already subscribed.

Check your email address and try again.

We could not save your subscription just now; please try again.

Ask ChatGPT or Perplexity why a buyer shouldn’t use a well-known SaaS product, and the answer usually comes back as a handful of short downsides. You read that the price climbs with seats, that reporting needs a workaround, or that support slows after onboarding. The sources underneath are competitor comparison pages, review sites and the vendor’s own pricing or help pages, quoted without the context the vendor would have given.

We tested that question on six of the best-known SaaS brands. Perplexity cited the brand being asked about zero times in 120 citations, so a buyer who reads only the answer never sees a page the brand wrote.

Positioning and messaging should say who your product is for and who should look elsewhere, and Empact Partners writes both for SaaS companies. Leave the second part out and an AI answer fills it in from your help pages and rivals’ comparisons.

Who Answers “Why Not You?” on Google and in AI Answers Today

We ran the test on October 2, 2026, with HubSpot, Asana, Mailchimp, Mixpanel, Zendesk and Notion 1. For each brand, we searched Google for its name plus “alternatives” and asked ChatGPT and Perplexity why a buyer shouldn’t use it. Three counts show who owned what a buyer would read.

0 of 60top-ten Google results for “alternatives” were the brand’s own pages
31 of 60were other software companies’ pages
0 of 120Perplexity citations went to the brand being asked about
Source: Empact Partners, why-not search and AI answer audit: Google US desktop top ten for six SaaS brands’

For all six brands, Google’s top ten for the alternatives search held no page the brand owned. More than half of those results came from other software companies, and community threads made up most of the rest, as the first chart shows.

Who Owns The Top Ten When Buyers Search Your Alternatives

60 Google results for six SaaS brands' alternatives searches, US desktop, October 2, 2026

View the data
LabelValue
Other software companies51.7%
Communities28.3%
Review or comparison sites11.7%
Publishers and independents8.3%
The brand itself0%
None of the 60 results belonged to the brand being searched, so rivals and communities answer the alternatives question for it.Source: Empact Partners, why-not search and AI answer audit: Google US desktop top ten for six SaaS brands’

The AI answers drew on a wider mix. Other software companies and review sites supplied nearly two-thirds of the 179 citations, as the second chart shows.

Who AI Answers Cite When Asked Why Not To Buy

179 citations in 24 ChatGPT and Perplexity answers about six SaaS brands, October 2, 2026

View the data
LabelValue
Other software companies34.6%
Review sites30.2%
The brand’s own pages20.7%
Publishers and independents10.1%
Communities4.5%
Rivals and review sites supply most of what answers cite about a brand’s downsides, and Perplexity cited no brand page at all.Source: Empact Partners, why-not search and AI answer audit: Google US desktop top ten for six SaaS brands’

Of those 179 citations, 37 were the brands’ own pages, and every one of them came from ChatGPT 1. None of those pages made the brand’s case. They were pricing pages, help-center articles, legal pages and feature pages, and one answer about Zendesk’s downsides cited Zendesk’s own support article, “Understanding real-time dashboard limitations.”

None of the brand pages the engines cited made the brand’s case.

We then asked the same two questions about six smaller brands that publish an honest page, one that tells buyers who should choose something else 1. Plausible’s “not the right fit” page was cited in all four of its answers. Close’s and Tuple’s honest pages were cited once each, and Help Scout’s, PostHog’s and Supabase’s weren’t cited at all. These are different brands from the six incumbents, so the check shows only what happened that day.

That check cannot tell you whether an honest page causes citations. It does show that the engines sometimes quoted one when it existed, while the incumbents’ answers cited their pricing, help and legal pages and their rivals’ comparisons instead, as the Zendesk answer showed.

A page of your own would still be one source among many. We see that in our own Empact Panel, built and run for more than a dozen of the SaaS companies we work with (we call them partners). Each week it puts their buyers’ questions to three AI engines (Claude, ChatGPT and Google AI Mode) and logs which pages each answer cites. One partner’s card shows how small a share of those citations a brand’s own site gets.

Empact Panel competitors ranking by citation ownership over 30 days, with Partner third at 2.9% and 344 cited pages, behind two rivals at 4.7% and 4.2%
Empact Panel example: the partner ranks third of 49 brands by citation ownership, and no brand’s own site draws even 5% of the citations.Empact Panel

In that card, the partner’s own pages drew 2.9% of the engines’ citations over 30 days, third among the brands tracked, while the leader’s drew 4.7% 2. We don’t name the partner, so “Partner” stands in for its name. The page most often quoted in our check, Plausible’s, answers one question directly: who should use something else. Yours should do the same for the objections your buyers raise, and finding those comes first.

Where To Find the Reasons Buyers Choose Someone Else

Start by writing down why buyers pick someone else, in their own words, and ranking the reasons. We call that an objection inventory, and you already own most of what goes into it. Each source tells you something the others don’t.

Scroll horizontally to see all columns when the table is wider than this page.

Where the reasons buyers choose someone else already live, and what to record from each
SourceWhat to recordWhat it tells you that the others don’t
Sales call recordingsThe objection in the buyer’s exact words, the call stage, the deal sizeWhich objection kills deals late, after the demo went well
Lost-deal notesThe stated reason, then the rep’s free-text note under itThe real reason hiding under “price” or “no decision”
Review-site complaints (G2, Capterra, TrustRadius)The complaint, the reviewer’s role and company size, the dateWhat a buyer reads before they ever reach you
Reddit and community threadsThe phrasing, the community, the month, whether the poster is a vendorThe words buyers use when no vendor is listening
Competitors’ pages about youEvery limit they name, and whether it’s still trueThe objections your rival is betting on
Support ticketsRepeated “can it do X” questions from new customersGaps buyers discover after they’ve signed
AI answers to “why not” questions about your brandThe bullets and every cited source, across two enginesWhich of the above an engine already treats as the answer

Samantha Spiro, this post’s author and a Senior GTM Consultant at Empact Partners, ranks one of those sources above the rest.

The most underrated source in that table is your competitor’s page about you. It ranks the objections they’re betting their pipeline on, by what they think hurts you most. Read it like a brief, check every line against your current product, and answer the true ones before their buyers ask you.

Samantha SpiroSenior GTM Consultant @ Empact PartnersSamantha Spiro on LinkedIn

If the page about you comes from a much bigger rival, our four-page playbook on positioning against one can help. It shows how to read the rival’s pages for a limit it cannot fix without upsetting its own customers, and which buyers that limit leaves open to you.

With the objections collected, rank them on counts your sales team can check for itself.

Turn the raw objections into the few you will answer

  1. Merge duplicates.

    One objection each, in the buyer’s words rather than the preset lost-deal reasons in your sales system.

  2. Count mentions.

    How often it comes up across sources over the last two quarters.

  3. Count affected deals.

    Lost or stalled deals where the notes show the objection mattered, each counted once. Add up what those deals were worth. That is the pipeline at stake, though you won’t win all of it back.

  4. Mark the truth.

    True, partly true or false today, before anyone picks what to publish.

  5. Pick a few.

    The objections that come up often, touch real deals and show up where buyers read.

A false objection gets a correction with current proof. A true one gets an admission with its reason and the buyer it suits. The partly true ones take the most work, because they need a sentence your product team will sign.

Agreeing on the objections takes longer than collecting them. Product has to accept the exact wording of each weakness. Sales has to accept every row that names a competitor, and legal checks the source behind each claim about a rival. The drawing shows where that sign-off falls between the first objection and the published page.

Objections from sales notes, reviews and competitor pages are marked true, partly true or false, answered, then reviewed by product, sales and legal.
Grade each objection true, partly true or false first, because that grade decides what the page admits and what it corrects.

How Six SaaS Companies Admit Their Limits

Before you write your own answers, it helps to see how other companies word an admission. An honest page pairs each one with its answer. It says what you’re worse at, why you chose that, and who should pick someone else because of it. These six pages are built that way, and each admits a different kind of limit.

Plausible Names the Jobs It Turns Away

Plausible, the privacy-focused web analytics tool, publishes “When Plausible is not the right fit” 3. Each section names the tool to use instead, and one ends: “Mixpanel, Amplitude and PostHog are built for those workflows. Plausible is not.”

Plausible’s “When Plausible is not the right fit” page, showing the passage that ends “Mixpanel, Amplitude and PostHog are built for those workflows. Plausible is not.”
This page was cited in all four of Plausible’s answers, the best record among the six honest pages we checked.Screenshot by Empact Partners

Help Scout Wrote Its Own Alternatives Post

Help Scout publishes its own alternatives post 4, opening on the admission that “in some cases we won’t be the best choice.” It tells a team of one it’s fine to stay on Gmail or Outlook, and names Zendesk for big teams that need the bells and whistles.

Help Scout’s alternatives post opening on the line that in some cases Help Scout won’t be the best choice, with a table of contents that includes reasons it might not be the best fit.
Despite its frank opening, this post was cited in none of Help Scout’s answers on the day we checked.Screenshot by Empact Partners

Close Gives Five Reasons Not To Buy

Close published “5 Reasons Why You Shouldn’t Buy Close CRM” 5, with a table of who it is and isn’t for. It rules out teams that want a free CRM, large enterprises and anyone who wants an all-in-one platform.

Close’s post “5 Reasons Why You Shouldn’t Buy Close CRM,” showing its table of contents and the first reason, that Close is not a free CRM.
The reasons not to buy are the headline here, and the page drew one citation across Close’s answers that day.Screenshot by Empact Partners

Tuple Answers the Person Who Approves the Purchase

Tuple’s buyer guide 6 answers “Who shouldn’t purchase Tuple?” for the budget holder, starting with “Teams that pair only rarely.” It names the missing Linux app outright and answers the “Can’t we use Zoom?” question instead of dodging it.

Tuple’s buyer guide answering “Who shouldn’t purchase Tuple?” with four kinds of team, starting with teams that pair only rarely.
The approver sees plainly which teams should not buy, and this guide drew one citation in Tuple’s answers that day.Screenshot by Empact Partners

PostHog and Supabase Give Rows to Their Rivals

PostHog’s comparison with Amplitude 7 calls the enterprise row a tie and says which way it breaks: “marketing-heavy teams will prefer Amplitude.” Supabase opens the conclusion of its Firebase page 8 by crediting the rival’s “excellent developer experience for prototypes and simple applications,” then says which teams Supabase suits better.

PostHog’s comparison with Amplitude, showing the enterprise row marked as a tie and the line that marketing-heavy teams will prefer Amplitude.
The tie in the enterprise row is the honest part, and it still went uncited in PostHog’s answers that day.Screenshot by Empact Partners
The conclusion of Supabase’s Firebase comparison, which opens by praising Firebase’s developer experience for prototypes and simple applications.
Like PostHog’s, this comparison went uncited that day, so candor about a rival is no shortcut to a citation.Screenshot by Empact Partners

None of these pages makes its company look weak. Each one tells the reader plainly which buyer the product is for. The buyers such pages are written for are wary, judging by what marketers say on Reddit. They read vendor pages defensively, doubt affiliate reviews and often arrive having compared you already.

Tips from Reddit

What marketers say about comparison pages

Product pages exist to persuade, so buyers read them defensively.

r/b2bmarketing, u/SatisfactionThis993, December 2025

Affiliate blogs can be helpful but now I’m always skeptical they’re reviewing in favor of whichever product has the highest affiliate payout.

r/b2bmarketing, u/heyimkrista, December 2025

We realized our best demo calls came from people who’d already compared us to the big names.

r/SaaS, u/Most_Acanthaceae8624, February 2026

What Goes on the Answer Page

Before you draft your own page, see where your site and your closest rival’s already disagree. Our free Competitor Messaging Teardown sets up to eight of your pages beside one rival’s. It compares your claims, proof and tone, including what each of you avoids saying.

Then write the page with its sections in this order, so a buyer learns whether the product fits before reading where it falls short.

The answer page, top to bottom

  1. Who it’s for.

    The buyer, the team size and the job, in one sentence the buyer would say.

  2. Who it’s not for.

    Two to four specific teams, each with the reason.

  3. What we’re worse at.

    The true objections from the inventory, each written as a choice you made, with the reason for it and the buyer it affects.

  4. What to choose instead.

    An alternative for each buyer you just turned away, named where you can.

  5. How to switch.

    What moves over, what doesn’t, and how long it takes.

  6. Proof.

    Dated evidence for every claim about you and every claim about a rival.

Here is how those sections read for Brindlepay, a fictional invoicing tool that exists only on this page:

Scroll horizontally to see all columns when the table is wider than this page.

The answer page’s sections, written for a fictional invoicing tool
SectionBrindlepay’s line
Who it’s forFinance teams of 3 to 30 people who send under 2,000 invoices a month and want them out the door in an afternoon.
Who it’s not forIf you bill in more than a dozen currencies or need approval chains with five levels, you’ll outgrow us inside a year.
What we’re worse atOur reporting is basic. We kept it that way so the first invoice goes out on day one, and teams who live in their reports should pick a tool built for them.
What to choose insteadIf you bill several legal entities in many currencies, choose a subscription billing platform with a ledger per entity and automatic currency conversion. It will serve you better than we will.
How to switchCustomers, items and open invoices import from a CSV in under an hour. Payment history stays in your old tool.
ProofImports of up to 50,000 rows and billing in 12 currencies, both last confirmed by our product team on October 1, 2026.

Before your draft goes to sign-off, read it once more for the ways an honest page can still work against you.

Stop the page before it ships if it has any of these

  • Punching down: a “why not them” page dressed as candor
  • Unverifiable rows: a claim about a rival you can’t source today
  • The fatal flaw: an admission worded so broadly that every buyer reads it as a reason to leave, when it only rules out one kind of buyer
  • The confession dump: every weakness you can think of, unranked and unanswered
  • The token concession: a win-every-row page that gives ground once, on something nobody cares about

Keeping the Page True After Launch

Give the page its own address, so a buyer can be sent to it and an engine can cite it. From launch on, it needs someone to keep it accurate, links that lead buyers to it, and a regular check on whether the engines cite it.

Three habits after launch

  • An owner: someone in product marketing, with a review date tied to your release calendar and to every change in your messaging framework
  • Links in: from pricing and from every comparison page you own, so a buyer and an engine both reach it
  • The re-test: the same two questions in two engines once a month, logged with whether your page is among the sources

If your team wants help with all of this, we would start with your closest rival’s page about you. We would set it against your lost-deal notes, because it shows which objections that rival already sells against you.

From there, our Brand Marketing consultants would work out the messaging with your team and carry it through your site, the answer page included, and your sales story. A buyer then hears the same answer from your page, your site and your sales team.

Frequently Asked Questions

Should we name a competitor on the page?

Name one where it helps the buyer decide, and only with dated evidence for every claim about them. A named alternative for each buyer you turn away is the most useful line on the page, because it tells the reader you understand their situation.

Avoid naming rivals just to criticize them. That reads as an attack and invites the same treatment on their page. When a rival is the right choice for a buyer, saying so plainly is what makes the rest of the page believable.

What if an objection is false?

Correct it with current proof, such as a release note, a screenshot or a customer quote with a date. Keep the buyer’s wording of the concern recognizable, so a buyer who has heard it knows this is the answer.

If the objection was true a year ago, say when it changed, because buyers trust a dated fix more than a denial. Then ask the review sites and roundups that still repeat the old objection to update it, because they will keep feeding it to AI answers otherwise.

Who approves the page, and how long does sign-off take?

Run the sign-off in one shared document with a column per approver. Product signs each admission, sales signs each competitor row, and legal signs the sources.

Product marketing owns the document and publishes only when every row has its three signatures. Plan two to four weeks of sign-off for the first page, most of it spent agreeing on the partly true objections. Later updates take days. Agree in advance who breaks a tie, usually the head of product marketing, so one disputed row doesn’t hold the whole page.

Will an honest page get us cited by AI engines?

There is no guarantee. In our October check, honest pages were sometimes cited and sometimes not, and the brands differed from the incumbents, so it proves nothing about cause. In the incumbents’ answers we sampled, the engines built the case against each brand from its fine print, review sites and its competitors’ pages. A clear page at its own address gives them your version to quote. The monthly re-test tells you whether they use it.

Won’t admitting a weakness lose us deals?

It can. Some buyers will rule you out on the page who might have stayed after a good demo. The trade is that buyers who were never a fit leave earlier, before the demo, the trial and the security review, and your sales team gets that time back.

The admissions that cost real deals are the ones worded as if they apply to every buyer. Before the page ships, product marketing should rewrite any admission that reads that way so it names the buyers it really affects.

Where should the page live on our site?

At its own address, linked from your pricing page, your comparison pages and your navigation where buyers compare options.

Inside a help-center article or a PDF, it is harder for a buyer to find. It is also easier for an engine to quote one line without the rest. Give it a plain title a buyer would search, such as “Who [product] is not for” or “[Product] alternatives, honestly”. Keep the address stable when you update the content, so links and citations keep working.

How many objections should one page answer?

Three to six. Fewer looks like a token gesture, and more starts to read as a string of reasons to leave. Pick the objections that come up most, touch real deals and appear in the AI answers about you, and leave the rest to the FAQ or to sales conversations. Revisit the selection each quarter, because the objections change as your product and your rivals do.

How do we know whether the page works?

Watch three signals for a quarter. The target objections should come up less often in sales calls and lost-deal notes. Buyers who read the page should move on to a demo or trial, and the AI engines should start citing it for the “why not” questions. None of the three proves revenue impact alone, but together they show whether the page is doing its job. Note the starting numbers before launch, or there is nothing to compare against.

When should we update the page?

At every release that changes a capability the page mentions, whenever a competitor changes a claim you answer, and at a fixed review date every quarter even if nothing obvious changed. An admission that is no longer true is a false claim on your own site, so the owner checks every line against the current product.

Can an AI agent write the page for us?

An agent can collect and group the objections, check which are still true against your product documentation and draft answers with their evidence. It shouldn’t decide what you admit in public. That choice needs product, sales and legal, and the wording should sound like your team. An agent-drafted admission is a starting point for that conversation, never the version that ships.

Sources (8)
  1. Empact Partners, why-not search and AI answer audit: Google US desktop top ten for six SaaS brands’, "alternatives" (2026)Empact Partners' own data↩1↩2↩3↩4↩5↩6searches; ChatGPT through DataForSEO’s ChatGPT scraper and Perplexity’s sonar model, two why-not questions per brand with web search on, 24 answers and 179 citations; the same questions for six brands with honest pages, October 2, 2026.
  2. Empact Partners, "Empact Panel" (2026)Empact Partners' own data↩1citation ownership for an anonymized B2B software partner, 30 days to November 14, 2026.
  3. Plausible Analytics, "When Plausible is not the right fit" (2026)↩1
  4. Help Scout, "alternatives" (2026)↩1
  5. Close, "5 Reasons Why You Shouldn’t Buy Close CRM" (2026)↩1
  6. Tuple, "Should we buy this Tuple thing?" (2026)↩1
  7. PostHog, "vs Amplitude" (2026)↩1
  8. Supabase, "vs Firebase" (2026)↩1

Ready
To Connect?

Let's Partner