Most of what you want to know about a B2B SaaS competitor sits on the far side of a button that says Request a Demo. The form is a remarkably effective perimeter.
The price a rep ends up quoting, the product as it demos rather than as the roadmap describes it, the questions they ask before showing anything, and what they say when your name comes up are all back there. None of it appears on a page anywhere, because none of it ever has to.
That gated stretch of the funnel is where we work: we book the demos, sit the calls as a genuine buyer on a partner’s behalf, and record what gets said.
Mystery shopping for B2B SaaS is legal, and the reason is short.
Real SaaS operators run a real software evaluation, so nobody is impersonated. We never sign an NDA and we never pay for the product, so no contract is broken and nothing is obtained by fraud.
That is the entire legal case. The rest of this is about what comes back.
Public Research Stops at the Demo Gate
Competitive intelligence software is good at the thing it was built for, which is watching what becomes public. Websites, news, review grids, job boards, filings: useful traces, and mostly ones a rival has had time to prepare for.
B2B software is unusual in how much it holds back. A product manager in a gated category described it on a public forum without much drama: no competitor offers a free demo or a walkthrough, and even the knowledge base carries no screenshots or videos.
Pricing behaves the same way. Buyers describe leaning on their own sales team to chase competitor numbers, then finding the answers unreliable.
Mystery shopping is not a technique somebody invented for software. It has measured business performance at the point of customer contact for decades across retail, hospitality, and financial services.
The research codes describe it the same way each time: a prospective customer, a set of predetermined tasks, an assessment against stated criteria.
What changes in B2B SaaS is where the useful evidence lives. The shop floor is a sales conversation, and the conversation is gated.
| Intelligence layer | What it observes | What it cannot directly observe |
|---|---|---|
| Public monitoring | Site changes, launches, reviews, hiring, filings | The live product, the quoted price, the pitch |
| Your own deal data | What your prospects and reps say inside your pipeline | What the rival says when you are not in the room |
| Win-loss interviews | How a buyer remembers and explains a decision | What was demonstrated, in what order, with what caveats |
| Mystery demos | Qualification, demonstration, pricing, objections, follow-up | Anything internal: their win rate, retention, or pipeline |
A Real Operator Asking Real Questions Is the Whole Method
The evaluation has to be genuine or it is worth nothing, and that is a practical constraint before it is an ethical one.
A call that stops feeling like a live opportunity turns into something else, and it records that something else perfectly well. It just stops recording the sales process you came for.
So the operator on the call is a real SaaS professional who evaluates software for a living. The context is a fábula: an invented but truthful narrative with a coherent company profile, a believable use case, a buyer persona, and commercial details that fit together.
Nobody pretends to be another person. The only thing the vendor does not know is who asked us to look.
That distinction does more work than it looks like it does. Providers in this category are blunt about the failure mode: the evaluation collapses when the enquirer cannot hold a technical B2B sales conversation.
We have run these evaluations for some of the best-known names in B2B SaaS, across hundreds of live competitor demos. The questions that open a call up are almost never clever. They are the ones a person who has bought and run this category already knows to ask.
What Comes Back Is a Working Notion Board
The demos get run and recorded, and what the partner opens afterwards is a workspace organized around the decision, with the calls sitting underneath it as evidence.
A folder of recordings is storage. A summary deck is the calls compressed until the useful parts fall out. The board keeps the evidence and the read in the same place.
It arrives in layers, and each layer answers a different question:
The evidence grades matter more than they sound like they should.
A workflow demonstrated live on screen and a workflow described confidently in an answer are different facts, and a feature grid flattens them into the same tick. Keeping them apart is most of what stops a comparison from turning marketing claims into product truth.
Comparison Is Where Five Sales Stories Become a Market
A single vendor page is a record of one company. Put five beside each other and the shape of that five starts to show: where they converge, where one stands alone, and which question earns a different answer from every one of them.
The matrices do the lining up. The Executive Summary compresses it for the people who will not read the matrices.
The Findings and Analysis page connects that evidence to what a leadership team changes: a pricing rule, a demo path, a battlecard field, a position on a roadmap.
.png)
What the recording keeps is the pause before the answer, and the follow-up that arrives with a deck instead of a link. A founder reading that back does not conclude the feature is missing. They conclude it was not demonstrated in that session, which is a narrower thing to know and enough to change a sentence on a battlecard.
None of this predicts what a competitor earns. Direct observation gets you what they said, showed, quoted, and sent, and it is honest about stopping there.
Everything downstream is your own read, which is the point. A product comparison built from recordings argues from evidence rather than from a brochure.
Your CI Software and Your Mystery Demos Answer Different Questions
Monitoring tools tell you what changed this week. Your pipeline tells you what your own buyers said. Win-loss tells you how a decision felt afterwards, once the story has settled into something tellable.
A mystery demo captures how a competitor qualifies, demonstrates, prices, deflects, and follows up inside a sales process running as a live opportunity.
Those are four different jobs. Treating one as a substitute for the others is how a team ends up confidently wrong.
Competitive intelligence draws on both primary and secondary research. For a lot of B2B software teams, the primary half is the one missing from the routine.
The failures that follow are predictable enough that we wrote them down separately, and whether the primary layer earns its cost is its own question with its own answer.
If the answer you need lives behind a form you cannot fill in as yourself, that is the job. We run the evaluations, record them, and hand back the vendor pages, the matrices, and the read. Hand over the competitor list and we will tell you what a project would look like.
.png)
