How to Research Competitors Before Launch

Before a SaaS launch, find out what rivals really ship and what their reps tell buyers. Here is how Mystery Demo does it, and what to check yourself.

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:

A quarter spent building a feature to match a rival that only promises it.
A headline two rivals already open their demos with.
A price set against a rival’s opening bid instead of the number its rep quotes.
Reps sent into their first month with no answer to the line rivals already use against newer tools.

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 decideWhat the rival’s website showsWhat its sales call shows
What to build before day oneA feature grid with a tick in every rowWhich ticks the rep can show working, which work with limits, and which are “on the roadmap”
What your headline saysThe line at the top of its homepageThe claim its rep opens the demo with, and how hard the rep leans on it
What to chargeA starting price, or a Contact Sales buttonThe 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 firstCustomer logos and a list of industriesThe qualifying questions the rep asks, and the buyers it steers somewhere else
How you answer their pitchNothing about you yetWhat 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:

One reply says that once enough competitors have a capability, it stops being a difference and becomes something buyers expect, so a product without it gets left off the list.
Another person has watched people “get fixated on matching the feature set of another product,” which is “generally not a way to win.”

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:

The headline. This is a positioning problem you can find before launch instead of after it. If the line you are saving for launch day is already slide three of a rival’s demo, buyers will hear yours as an echo. A rebrand runs the same check for lines that are already taken.
The price. A rival’s published starting price is only its opening bid. The number its rep quotes a buyer your size is the price you will compete with, and finding a competitor’s real price takes the same call.
The setup. If a rival’s rep says setup needs its services team for a quarter, your one-week setup is a headline, as long as you can show it live.
The first customers. The qualifying questions tell you which buyers a rival wants, and a new product can win its first customers among the buyers it turns away.
The answer to their pitch. The rival’s line on newer tools is the objection your own reps will meet in their first month, and you can write the answer before launch day.

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.

The client’s own page on a Mystery Demo example board, with a summary of what the invented client sells and why the project was commissioned, above a company overview table.
The client’s page on our invented example board. On a pre-launch project it holds your product and the decisions the calls have to inform.

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 decisionWhat the buyer asks on the callWhat the rival’s answer shows
What to build before day oneCan we see the capability running on data like ours, today?Whether it is shown working, shown in part, or only promised
What to chargeWhich 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 liveWho 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 openWhat 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 pitchWho 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.

The Research Companies page of a Mystery Demo example board, with a callout explaining why five vendors were chosen and a table listing each company, why it was chosen, its focus, meetings, founding year and funding.
The Research Companies page on the invented example board. Every rival on a real project is there for a reason you agreed at kickoff.

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.

Chief Mystery Officer
Mystery Demo
“It’s coming next quarter” is the most useful sentence a rep can say to a team about to launch. Write the quarter down, then ask what a buyer would use until then. A workaround tells you the gap is real and the rival knows it. A services quote tells you the rival plans to close the gap with people, at a price. A change of subject tells you nobody is going to show it, and a feature nobody shows is the easiest thing for a new product to beat on a live screen.

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.

A comparison table from a Mystery Demo example board’s Findings and Analysis page, setting each vendor’s headline performance claim beside the verified range, the demo method and the gap to the client.
One comparison from the invented example board: what each vendor claims, and what its demo proved.

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 methodHow to run itWhat it gives youWhere it stops
Ask buyers what else they are weighingAsk design partners and early prospects what they would use if you did not exist, and who else they are looking atYour real competitor list, which can include a spreadsheet, a suite the buyer already pays for, or doing nothingNothing on what those rivals show or say
Read the docs, not the websiteRead 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 datesHow the product works for customers who already boughtThe pitch and the price a new buyer hears
Trial whatever you canRun your launch’s main job through a free trial or plan, from signup to result, and time itThe most honest look at a product you can get from a deskThe top tier, the setup service and the pitch, all on the other side of the sales call
Read the complaintsSort 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 dealsThe product as it was when the reviewer bought it, told by someone who already chose it
Read the job posts and the announcementsNote what the rival hires for and announcesSignals worth checking: implementation consultants hint that setup is sold as a service, a new product line hints where it goes nextWhat 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.

Build it before launch when rivals show it working and buyers expect it.
Lead with it when no rival could show it working and your buyers asked for it.
Narrow it when a rival shows something close, for a different buyer or in a higher tier.
Cut it from day one when rivals only promise it, none of them made it part of the pitch, and your buyers never raised it.

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.

An invented example launch check for school admissions software: each line of the launch plan, marked for three lettered rivals as shown live, partial, described only, promise only, roadmap or never said, with the decision it leads to. Every line is invented.
An example launch check. The launch, the rivals and every mark on it are invented.

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.

Ready
To Connect?

Let's Connect