A few months before a B2B SaaS launch, three decisions are usually close to locked: what the product does on day one, what the headline says, and what it costs. The team makes all three from what it can see of its rivals, which mostly means their websites. A sales-led rival keeps its product behind a demo form and makes its pitch only on sales calls.
The best way to research competitors before launch is to take those sales demos as a buyer, and Mystery Demo does that for you. It books your competitors’ demos as the kind of buyer your launch is aimed at, asks the questions the launch depends on, and records every call.
You get back a board with what each rival showed working, what its rep said, and what it quoted. Each competitor costs a flat €499 and takes one to two weeks, about the length of one sprint. Many teams come to us at exactly this point, with the product nearly built and the launch date set, and the calls catch mistakes that are cheap to fix before a launch and expensive after it:
You can research competitors from your desk too, and five methods are worth your time. They sharpen the questions. None of them gets you into a sales-led rival’s demo, where the product is shown and the pitch is made.
In B2B, a Rival’s Product Only Comes Out on a Sales Call
Three things make the sales call the place to look, and a mystery demo the way to get there.
The Product Is Behind the Demo Form
A rep shows sales-led B2B software on a call, to a buyer who qualifies. Everyone else gets the screenshots marketing picked for the website.
A product manager put the problem plainly on r/ProductManagement, while researching a field that was new to them. How do you learn about a competitor’s features, they asked, “if the feature is stuck behind a paywall, or doesn’t have enough information on their public website?” Every team launching into a new market starts with that question.
You know the rivals’ names. You have never seen their products working.
The Demo Follows the Buyer
Gong’s data team analyzed 67,149 recorded sales demos and found that winning demos mirror the topics discussed in discovery. The rep opens on whatever the buyer spent the most time on, then works down the buyer’s list.
So the demo a rival gives depends on who is asking. To see what your buyers will see, the buyer on the call has to look like the one you are launching to: the same size, the same problem, the same deadline.
You Can’t Take the Call as Yourself
A rep who spots your company’s email domain gives you the generic tour, or no tour at all. Weeks before a launch there is a second cost, because a demo request in your own name tells the rival you are coming.
Mystery Demo arrives as a believable buyer, so each rep runs the call it runs for buyers like yours. Nobody at the rival is told who asked us to look, and you see its product before your buyers start comparing the two.
The Launch Mistakes a Rival’s Sales Call Catches
Seeing it first matters, because every launch plan is a set of bets about the competition, each one placed from a rival’s website. Here is each bet, as the website shows it and as a buyer on the call sees it.
| Before launch, you decide | What the rival’s website shows | What its sales call shows |
|---|---|---|
| What to build before day one | A feature grid with a tick in every row | Which ticks the rep can show working, which work with limits, and which are “on the roadmap” |
| What your headline says | The line at the top of its homepage | The claim its rep opens the demo with, and how hard the rep leans on it |
| What to charge | A starting price, or a Contact Sales button | The number quoted to a buyer your size, the tier it is in, and what brings it down |
| How fast customers go live | “Up and running in days” | Who does the setup, how long the rep says it takes, and whether a services fee comes with it |
| Who you sell to first | Customer logos and a list of industries | The qualifying questions the rep asks, and the buyers it steers somewhere else |
| How you answer their pitch | Nothing about you yet | What its rep already says about newer tools, before you exist |
The first row is where the months go. Say a rival’s feature grid shows a tick for an integration your launch doesn’t have yet. The usual answer is to build it before launch, and that can take a quarter.
On the call, a buyer can ask to see that integration working on data like theirs. If the rep shows it working, buyers who have seen it may expect it from you too. If the rep shows a slide, or says it lands next quarter, it is a promise, and you don’t have to match a promise before you ship; your launch may even beat it by showing the real thing.
Product managers argue about this in public, and both sides have a point. In the same r/ProductManagement thread:
Which of the two applies to the feature in front of you depends on what rivals can show working and what your buyers expect. The call answers the first half, and your own buyers answer the second.
The other rows matter as much, and the last three change the launch more than the roadmap does:
All of this matters most when the launch takes you into a market you don’t know yet. The incumbents there have a pitch their reps have worked on for those buyers, and you have never heard it once.
Little of it is on a public page. So the question is how to get it before your launch date, without telling anyone at the rival it was you.
How a Pre-Launch Mystery Demo Project Runs
Start From What You Are Launching
At kickoff you show us the product, the launch plan and the price you have in mind. The buyer we send can then ask each rival for the same capabilities you are about to ship.
Below is the client’s own page from our public example board, where the client and every competitor are invented. On a real project, this page holds what you are launching and the question the project has to answer before launch day.

Turn Each Launch Decision Into a Question
We agree the questions with you, one for each decision the launch plan is waiting on. On a pre-launch project, the buyer carries questions like these into every call:
| Launch decision | What the buyer asks on the call | What the rival’s answer shows |
|---|---|---|
| What to build before day one | Can we see the capability running on data like ours, today? | Whether it is shown working, shown in part, or only promised |
| What to charge | Which plan is it in, what does it cost at our size, and what would bring the number down? | The number quoted to a buyer your size, and how far it moves |
| How fast customers go live | Who sets it up, how long until our team uses it, and is there a setup fee? | The setup time the rep gives, and any services fee |
| How long a gap stays open | What is on the roadmap for this area, and when? | The rep’s claim about the roadmap, which is all a call can hear |
| How your reps answer their pitch | Who do you usually come up against, and why would we pick you over a newer tool? | The line its rep uses against newer tools |
Choose the Rivals Your Buyers Will Weigh
We choose them with you, usually three to nine, each for a reason you can name. On the example board, the Research Companies page keeps that reasoning: why each company is in, what it focuses on, and how many meetings it took.

Build the Buyer to Match Yours
Before any call is booked, we write the buyer. It is a believable company with a real reason to evaluate software, shaped like the buyer you are launching to and close enough to each rival’s ideal customer to get the full demo.
Its industry, size, funding stage, current tools and deadline are chosen so the rep takes it seriously. The evaluation itself is genuine, because we are evaluating that software on your behalf. The only invented part is which company is asking, and nobody real is impersonated.
Run the Calls Like Any Serious Evaluation
We book through each rival’s normal front door, then go through discovery, the demo, a technical deep dive, the pricing conversation and the follow-up. The people asking the questions have sold B2B software themselves, so they know which question pulls a rep off the script.
Every call is recorded, and every email and piece of collateral is kept. Then every claim a rep made, from customer names to launch dates, is checked against the rival’s website, LinkedIn and public news, so the board marks what holds up, what does not, and what nothing public confirms.
One call shows what one rep showed one buyer on one day. When a second rep shows the same thing, or dodges the same request, you are starting to see the company’s answer, not one rep’s afternoon.
.png)

Read the Rivals on One Board
Each rival gets its own page, with its recordings, transcripts, emails, collateral and our analysis. The Findings & Analysis page then sets the rivals side by side.
For a launch, the part that matters most is the feature matrix: what each rival claims, what its demo proved, and whether each capability was shown working, shown in part, or only promised. Here is one comparison from the same invented board. Each vendor’s headline performance claim stands next to the range its demos verified, and how the demo showed it.

On a real board, every finding traces to a recording, a transcript line or an email. That is the work of SaaS competitor product comparison: what each rival really ships, feature by feature, with the proof attached.
What It Costs, and How Long It Takes
Mystery Demo charges a flat €499 per competitor, everything included. One competitor takes one to two weeks.
A full landscape, about six to fifteen rivals, takes four to eight weeks rather than months, because the calls run in parallel. A launch a quarter away has room for all of it.
If your launch date is set and one rival’s product is still a feature grid to you, send us its name and your launch date. We will go through its demo as your buyer and bring back what it could show.
Five Ways to Research Competitors From Your Desk
The calls cover what only a buyer can see. Your own research still earns its place: it tells you which rivals belong on the list and what to ask them. Each method stops somewhere, and it helps to know where.
| Desk method | How to run it | What it gives you | Where it stops |
|---|---|---|---|
| Ask buyers what else they are weighing | Ask design partners and early prospects what they would use if you did not exist, and who else they are looking at | Your real competitor list, which can include a spreadsheet, a suite the buyer already pays for, or doing nothing | Nothing on what those rivals show or say |
| Read the docs, not the website | Read every help-center page, the API reference and the changelog on your launch capability, and watch its YouTube walkthroughs; note the limits, the plan each page says it needs, and ship dates | How the product works for customers who already bought | The pitch and the price a new buyer hears |
| Trial whatever you can | Run your launch’s main job through a free trial or plan, from signup to result, and time it | The most honest look at a product you can get from a desk | The top tier, the setup service and the pitch, all on the other side of the sales call |
| Read the complaints | Sort G2 and Capterra reviews by newest and read the middling ones first; search Reddit for its name next to “alternative” or “switching” | Where buyers feel let down, which is where a new product wins its first deals | The product as it was when the reviewer bought it, told by someone who already chose it |
| Read the job posts and the announcements | Note what the rival hires for and announces | Signals worth checking: implementation consultants hint that setup is sold as a service, a new product line hints where it goes next | What it ships today |
On a Mystery Demo board, a rival that sells with no call at all gets a trial log where the recordings would be. And when a rep talks about the roadmap on a call, that is a claim too: a call hears what the rep promises, never the roadmap itself.
Make the Launch Calls From What Rivals Showed
Put your desk notes and the board together, and write every line of the launch plan down the left of one sheet: each capability, the headline, the price and the setup promise. Beside each capability, mark what each rival did with it on the calls: showed it live, showed part of it, promised it, or never raised it; beside the headline, the price and the setup promise, write what each rival’s rep said instead. Then give the line one decision.
The same notes feed the enablement team’s first battlecard: what each rival’s rep quoted becomes the pricing answer, and its line on newer tools becomes an objection reps practice before launch day. Here is the launch sheet filled in for an invented launch, with three lettered rivals. Every line on it is made up to show the shape.

Start while the roadmap can still move, because a board that lands after the launch only tells you which mistakes you made. After launch, run it again: once rivals have had time to answer you, the move to watch is how each changed its pitch. Clients come back one to three years later to see how each rival moved.
Your team can start the desk work tomorrow. The demo is the step only a buyer can take, and it is the one we take for you. Tell us which rivals your launch will meet, and each rival’s page lands as its calls finish, while the plan can still change.
.png)