# How do you evaluate whether a competitor’s new feature is a real threat or just noise?
> A way to test a rival’s new feature against evidence in your own funnel, with a spoken example, readings to avoid, and the likely follow-ups.

Source: https://mokk.ai/pmm-questions/market-research/competitor-feature-threat-or-noise (updated 2026-09-22)
Markdown: https://mokk.ai/pmm-questions/market-research/competitor-feature-threat-or-noise.md

Test the feature against your own evidence. Try it yourself, then count how often buyers raise it in deals, support tickets, and churn reasons, and check whether it changes outcomes. Judge how quickly the competitor can improve it and what matching it would cost you. Make a call, noise for now or a threat, and write down the specific trigger that would change it.

## What the threat-or-noise question rewards

Every competitor launch arrives with a post, a demo video, and at least one person inside the company who is sure it changes everything. Reacting to all of them wears a team out. Ignoring all of them eventually costs you a segment. This question asks for the method in between, which is how you decide where attention goes.

Market expertise is the main competency, with analytical rigor close behind. The rubric’s Exceptional level describes someone who looks for the data that would disprove their own view. Here that means saying what evidence would change your call, before anyone asks.

## Questions that sort a rival’s feature

Questions that separate a threatening feature from a noisy one
| Question | Evidence to check | Leans toward threat when |
| --- | --- | --- |
| Does it solve a problem your buyers rank highly? | Discovery notes, support tickets, community forums, feature requests | Buyers raised the problem before the rival shipped anything |
| Does it change outcomes? | Lost and stalled deals, churn reasons, trial conversion where the rival competes | Deals or users you lose name it as a reason, beyond a passing mention |
| Can they improve it faster than you can respond? | Release pace, the depth of their first version, what it would take you to build or partner | Their version is early but sits on an architecture you would need a year to match |
| What does matching it cost you? | An engineering estimate, what gets delayed, and whether a partner or workaround exists | Matching is cheap relative to the deals at stake |

Try the feature yourself as well. Launch posts describe the best case, and ten minutes in a free trial usually shows where the edges are.

## The reasoning, out loud, for a database company

**Strong answer (invented example)** "I’d start by using it. We run a managed Postgres service, and a rival just launched database branching, so every pull request gets its own copy of the database. I’d spin up a trial and test it on a realistic dataset, since demos use tiny ones. Then I’d ask three questions. Do our users want this, do we lose because of it, and can they pull ahead? For the first, I’d search support tickets, our community forum, and feature requests from the last six months. For the second, most of our revenue is self-serve, so I’d look past sales calls to churn survey answers and to signups from teams that use preview environments. If branching shows up in two of about a hundred churn reasons, I’d call it noise for now. If it shows up in a fifth of them, or we lose two larger accounts on it in a month, I’d bring product a brief with the tickets and deals attached. Either way I’d write down the trigger and check it monthly, so the call doesn’t depend on who’s loudest in the room."

Notice the move from mentions to outcomes. A launch spikes mentions for a few weeks, and mentions alone say nothing about losses. The answer also adapts its evidence to a self-serve business, where users leave without ever telling a sales rep why.

## Readings the evidence won’t support

- **Mentions went up, so it is a threat.** Launches raise mentions across the board. Look at mentions inside lost deals and churn reasons, and compare them with the weeks before launch.
- **Nobody mentions it, so it is noise.** In a self-serve product, users often churn without saying why. Check the cohorts that would care most, such as teams already using the workflow the feature serves.
- **Our engineers say it is easy to build, so we should.** Cheap to build answers a different question. If buyers don’t rank the problem, a quick copy adds clutter and a message you have to explain.
- **Their launch numbers are big.** Launch posts count signups, waitlists, and stars. None of those measure whether your buyers switch.

**A tidy matrix with nothing behind it (invented example)** "I’d score it on a simple matrix, customer impact, strategic fit, and effort to match, each from one to five. Anything above twelve goes to product as a priority. It keeps the process consistent and takes emotion out of the decision."

The structure is sensible, and interviewers will like the consistency for about ten seconds. Then they ask where the scores come from. Without a source for customer impact, the matrix turns a guess into a number. Keep the frame if you like it, but name the evidence behind each score and the threshold that would change your call.

## Follow-ups on a competitor’s feature launch

Pushback to expect on a rival’s new feature
| When they press | What they are weighing | What to say |
| --- | --- | --- |
| Sales insists it is a threat. What do you do? | Whether you can hold a position with evidence | Ask for the specific deals, add them to the count, and agree on the trigger together |
| What if the data is thin? | Comfort with ambiguity | Say so, make a provisional call, and name what you will collect over the next month to firm it up |
| How do you find mentions in call recordings? | Practical research habits | Search transcripts for the feature name and for the problem it solves, since buyers often describe the problem without naming the feature |
| What would make you escalate to product? | Whether your trigger is specific | A threshold in outcomes, such as losses citing it across several deals in one month |

## More questions in this category

- [Competitive updates for sales](https://mokk.ai/pmm-questions/market-research/competitive-updates-for-sales)
- [Competitor targets your core](https://mokk.ai/pmm-questions/market-research/competitor-targets-your-strongest-use-case)
- [Adjacent and direct threats](https://mokk.ai/pmm-questions/market-research/adjacent-vs-direct-competitors)
- [Competitive analysis for execs](https://mokk.ai/pmm-questions/market-research/present-competitive-analysis-to-execs)
- [All market research questions](https://mokk.ai/pmm-questions/market-research)

## Frequently asked questions

**What if I don’t have win-loss data?** Describe a light version. Tag the next ten lost deals, add one question to the cancellation flow, or ask reps two questions after each loss. Start small and say what you expect to learn.

**How often should the threat call be revisited?** Monthly suits most teams, with an earlier check if a deal stalls on the feature or the rival ships a second version. The date matters less than having the trigger written down, so each review is a check against a standard.

## Practice

**Answer it out loud.** A Mokk session asks this question, follows up on your answer, and scores it on five competencies.