Competitive Intelligence for RevOps Teams
Know what each competitor costs you in deals, discounts and forecast misses, with CRM data your leaders can trust. The complete guide for revenue operations, sales operations and deal desk teams.
14-day free trial · 30-second setup · or read the guide
Definition
What is competitive intelligence for RevOps?
Competitive intelligence for RevOps is the data side of competition: the CRM fields, definitions and reports that show where you win, lose and discount against each competitor. RevOps designs that system, keeps it clean and puts the numbers in front of the people who decide.
Call it competitive revenue analytics. Competition barely appears in RevOps job descriptions, yet it sits inside the numbers you already own. It is in the win rate you report, the discounts your deal desk approves and the deals that slip as the quarter closes.
The competitive part of each number only shows up if the CRM records who you were up against. Few CRMs do that out of the box. Someone has to design the field, define each value and make sure reps fill it in. In most companies, that someone is you.
Use cases
How RevOps teams use competitive intelligence
Product marketing writes the battlecards. You own the numbers that show whether they work, in six parts of the job you already run.
CRM fields and definitions
Whether you run Salesforce or HubSpot, add a competitor picklist kept apart from the loss reason. Write one definition for each value, so every team reads it the same way.
Win rate by competitor
Split your win rate by named competitor, with the deal count beside each rate. A blended rate can rise while you lose more often to every competitor.
Discount and pricing
Compare the average discount in deals against each competitor with deals where none was named. That difference is what you pay for meeting them.
Forecast and pipeline reviews
Compare the sales cycle length of deals against each competitor with uncontested ones. Flag commit deals that run past it, or where a competitor showed up late.
Deal desk approvals
Ask for the competitor's name and their written quote before you approve a discount above your usual limit. "They're cheaper" becomes a fact you can check.
QBR and board reporting
Report the same competitive numbers every quarter, with coverage stated. The QBR competitive update puts win rate, deal volume and deal size by competitor on one slide.
In practice
Competitive revenue examples: what RevOps does next
In RevOps, a competitor rarely arrives as news. It arrives as a number that moved, and a leader asking you why.
Illustrative examples · CompetitorX is a fictional competitor
What the data shows
Your win rate against CompetitorX drops from 41% to 28% over two quarters, on 36 closed deals.
Your move
Check the field before you build the slide. Did coverage fall, or did CompetitorX start showing up in a new segment? Split the rate by segment and by the stage where they entered. Then give product marketing the pattern, with the deals named.
Before the QBR deck locks.
What the data shows
The average discount in deals against CompetitorX is 11 points deeper than in deals with no competitor named.
Your move
Pull the approved discounts and the reasons attached. If most cite CompetitorX's price, ask the deal desk for the written quotes. Bring the gap to the next pricing review, with the deals won and lost at each discount level.
At the next pricing review.
What the data shows
Three commit deals name CompetitorX for the first time in week 10 of the quarter.
Your move
Late entry is a risk signal, not a detail. In the forecast call, ask each rep what the buyer said and what changed. Keep a deal in commit only if it has a dated next step before quarter end.
This week's forecast call.
What the data shows
"Price" is the loss reason on 60% of this quarter's lost deals, and "Other" on 15%.
Your move
Price is the fastest reason to pick, and it blames nobody. Check a sample against call recordings or buyer interviews. Split "price" from "no budget", and review every "Other" with the rep who chose it.
At the quarterly field audit.
What the data shows
CompetitorX raises its list prices by 15% and removes its entry plan.
Your move
List every open deal and upcoming renewal that names CompetitorX. Where your team was discounting to match their old price, tell the deal desk to hold back. Ask product marketing for a pricing teardown of the new plans before the pricing review.
Within a week of the change.
What to know
The competitive questions your revenue data should answer
Each question needs a field, a report and a date range behind it. When one is missing, that is your next field request.
Where we meet them
- Which competitors appear in how many deals, by segment and region?
- At which stage does each competitor usually enter?
- Where are they the incumbent, and where are they new?
How we do against them
- What is our win rate against each one, with the deal count?
- How long do those deals take, next to uncontested ones?
- How many deals end with no decision at all?
What they cost us
- How much deeper do we discount against each competitor?
- Which approved exceptions cite a competitor's price?
- How much ARR did we lose to each one this year?
Whether we can trust it
- What share of closed deals name a competitor?
- How many deals say "Other", or nothing at all?
- How often do reps' loss reasons match what buyers say?
Sources
Where RevOps finds competitive intelligence
Your own systems hold most of the answer. Fill the gaps with a few public sources, and date everything you add.
What you already hear
- Opportunity records
- Each deal should record the competitor, the incumbent, the stage each competitor entered and the loss reason. Good CRM data starts with fields you designed, not free text.
- Call recordings
- Trackers in Gong or Modjo catch competitor names that reps never enter in the CRM. Compare the two lists every month.
- Quotes and approvals
- Your quoting tool and deal desk approvals show every discount, and the reason given for it. Tag the ones that cite a competitor.
- Cancellations
- Customer success logs why accounts leave or cut back. When a competitor took the work, the record should name them.
- Buyer interviews
- Reps pick a loss reason in seconds. Win/loss interviews give you the buyer's own reason, so you can check the one in the CRM.
- Forecast calls
- Reps say more about competitors in a forecast call than they ever type. Add what you hear to the deal record the same day.
What competitors publish
- Pricing pages
- Published competitor pricing gives you list prices. What buyers actually pay is usually lower, so never quote list price as the street price.
- Hiring
- A competitor adding account executives in one region is a warning for your territory plan. Competitor hiring shows where they will push next.
- Earnings calls
- Listed competitors talk about deal sizes, retention and price pressure on their earnings calls. Read them before you set next year's targets.
- Deal size benchmarks
- A competitor's average deal size tells you which segment they really sell to. Compare it with the deals where you meet them.
Stay on the right side of the line
Each source here is your own data or open to anyone. A new hire's old price lists, discount rules and pipeline reports stay with their former employer. And nobody on your team should pretend to be a prospect to obtain a competitor's quote.
Signal vs noise
Which competitive data belongs in your reports
A number earns a place in a report when it could change a forecast, a price or a plan. Everything else can stay in the raw data.
Track
Act within a week
- The competitor on each closed deal
- Win rate by competitor, with deal counts
- The discount gap against each competitor
- Competitors entering commit deals late
- Competitor price changes
Skim
Monthly roll-up
- Competitor mentions on calls
- Win rate by rep
- Competitor hiring
- Deal size against each competitor
- Competitors named in one deal
Ignore
Unless it repeats
- Rates on a handful of deals
- One month's win rate on its own
- Tags added after a deal closed
- Competitors no buyer mentions
- Industry win rate benchmarks
Small samples need the most care. Below about 30 closed deals against one competitor, show the counts instead of a rate. Pool quarters until the number can carry a decision.
More data is not always better. In the 500 G2 reviews behind our G2 review study, one complaint came back across all four tools: alerts nobody needed. A dashboard with twenty competitor charts has the same problem: nobody reads it.
Know the day a competitor changes its pricing
Flares watches competitors' pricing pages and plans, and alerts you to the changes that could move your deals and your forecast.
14-day free trial · 30-second setup
Distribution
How competitive data moves between RevOps and the teams it serves
RevOps sits between the people who enter the data and the people who act on it. Reps fill in the fields. Leaders, finance and product marketing read the reports. When either side stops trusting the other, the numbers stop meaning anything.
What comes in
Sales reps
The competitor on each deal, and the reason it was won or lost.
Customer success
The competitor on each cancellation and cutback.
Product marketing
The competitor list, and what each loss reason means.
Deal desk
Discount requests, with the competitor's quote attached.
What goes out
Sales leadersForecast call
Commit deals where a competitor entered late.
Product marketingQuarterly report
Win rate and loss reasons by competitor, with deal counts.
FinancePricing review
The discount gap against each competitor, and its trend.
Sales enablementMonthly note
The segments and teams where one competitor wins most.
LeadershipQBR
Win rate, discount and ARR lost per competitor.
Settle the division of work with product marketing: you own the fields, the definitions and the numbers, and they own the explanation. Send sales enablement the segments where losses cluster, so training goes where it pays.
Ask customer success to name the competitor on every cancellation, or lost revenue won't add up. And show sales teams the report their entries built. Reps fill in a field more carefully once they see it used.
The deliverable
What goes on a competitive revenue dashboard
One dashboard, read the same way every quarter, beats a new deck each time a leader asks. Build the layout once, then let only the numbers change.
01Coverage
The share of closed deals with a competitor named, shown first.
02Where we meet them
Deals per competitor, by segment, region and entry stage.
03Win rate
Per competitor, with the deal count beside each rate.
04Discount gap
Average discount per competitor, next to uncontested deals.
05Cycle and deal size
Median days to close and deal value against each competitor.
06Loss reasons
What reps chose, next to what buyers said in interviews.
07ARR lost
Revenue lost to each named competitor, over the last 12 months.
08Owners and decisions
Who acts on each number, and what they decided last quarter.
The loss reasons block is only as good as the check behind it. A win/loss report sets the reasons reps chose next to what buyers said, deal by deal.
The quarter
Competitive checks across the revenue quarter
Your quarter already has a shape: pipeline build, forecast calls, close, then the business review. Each stage has one competitive check, and most take minutes, not days.
- 1
Quarter start
Weeks 1 to 2- Publish last quarter's numbers per competitor.
- Update the competitor picklist with product marketing.
- Confirm discount limits with the deal desk.
- 2
Pipeline build
Weeks 3 to 6- Check that new opportunities name a competitor, or "None known".
- Check call trackers for competitors missing from the CRM.
- Note where each competitor shows up most.
- 3
Forecast
Weeks 7 to 11- Flag commit deals where a competitor entered late.
- Review discount requests that cite a competitor.
- Log any competitor price change for the pricing review.
- 4
Close
Weeks 12 to 13- Require a competitor and a loss reason on every closed deal.
- Chase blanks while the deals are fresh.
- Record the ARR lost on each cancellation.
- 5
Business review
After the quarter- Report win rate, discount gap and ARR lost per competitor.
- Audit "Other" and blank loss reasons.
- Name an owner for each decision.
Routine
A competitive routine for RevOps
You don't need another meeting for any of this. Each check rides on a report you already send, or a call you already join.
Weekly
20 minutes- Scan new opportunities with no competitor named.
- List commit deals where a competitor appeared after the demo.
- Check discount approvals for a competitor's written quote.
Monthly
1 hour- Compare call tracker mentions with the CRM field.
- Check coverage by team and segment.
- Refresh win rate by competitor on a rolling 12 months.
Quarterly
Half a day- Refresh the competitive revenue dashboard.
- Review every "Other" loss reason with its rep.
- Add or retire competitors on the picklist.
When a competitor changes its pricing
30 minutes- List the open deals and renewals that name them.
- Tell the deal desk what changed.
- Add it to the next pricing review.
For the quarterly audit, a win/loss synthesis prompt can code interview notes against your loss reasons. Give it your own list of reasons. A model that invents its own categories gives you a new chart every quarter.
Freshness
How to keep competitive revenue data clean
Revenue data doesn't go stale the way a battlecard does. It drifts: a new competitor typed into "Other", a reason nobody defined, a quarter of blank fields.
| What you track | Goes stale in | Update it when |
|---|---|---|
| Competitor picklist | A quarter | The same name in "Other" twice |
| Loss reason definitions | A year | Two teams reading a reason differently |
| Competitor coverage | A month | Any team below half |
| Win rate by competitor | A month | The monthly refresh |
| Discount gap | A quarter | A competitor price change |
| Competitor list prices | A quarter | A change on their pricing page |
| Call tracker keywords | A quarter | A competitor renaming a product |
| Incumbent on each account | A year | A contract renewal |
| ARR lost per competitor | A quarter | Each cancellation or cutback |
| Discount limits | A quarter | A gap that keeps widening |
Date the competitor field, so you can see when each competitor entered a deal. When the picklist changes, don't rename a value in the middle of the year. Add the new one, retire the old one, and keep both in your reports until the year ends.
Metrics
How to measure competitive revenue performance
One win rate for the whole business hides the competitor that is hurting you. Jeff Ignacio, who writes about RevOps, explains why the split matters. "If you're winning 60% of deals when you're aware of a competitive situation and 38% when a specific competitor is involved, that's actionable product and enablement input."
Competitive win rate
won deals against a competitor ÷ deals won or lost against that competitor
Refresh it monthly over a rolling 12 months, and decide on it quarterly. Show the deal count beside every rate.
Discount rate
(list price − sold price) ÷ list price, averaged across competitive deals
Read it next to the same rate on uncontested deals. The gap is the price each competitor takes from you.
ARR lost to competitors
ARR lost to cancellations and cutbacks where a named competitor took the work, per period
Customer success names the competitor on each loss. You total it, so the figure agrees with finance.
Competitive displacement rate
wins where the buyer left a named incumbent ÷ closed deals against that incumbent
It needs an incumbent field beside the competitor field. Measure it in both directions.
For the pricing review, add a competitive pricing index at list price and at the price customers actually pay. Report "no decision" as its own line, because deals lost to inaction teach you as much as deals lost to a competitor.
Pitfalls
Competitive data mistakes RevOps teams make
Most of them make the data look complete while making it less true. In Validity's 2025 survey of 602 CRM users, 37% said staff regularly fabricate data to tell leaders what they want to hear.
Requiring every field too early
A field required at the first meeting gets filled with the top value in the list. Offer "None known" early, and make the competitor required at close.
Letting "price" explain every loss
Reps pick price because it is quick and blames no one. Check a sample against call recordings or interviews before price reaches a slide.
One field for who won and why
A loss reason called "lost to competitor" hides the reason. Keep the competitor and the loss reason in two fields, and report them side by side.
Percentages on tiny samples
On eight deals, one result moves a win rate by 12 points. Show counts until you pass about 30 closed deals against that competitor.
Tagging deals after they close
Adding competitors to closed deals to fill a report makes the counts meaningless. Date every entry, and backfill once, with the rule written down first.
Reading one month's win rate alone
At competitor level, one month holds too few deals, so its rate is mostly noise. Refresh monthly on a rolling 12 months, and say so on the slide.
Automation
How to automate competitive intelligence for RevOps
Your CRM tells you who you met and how each deal ended. It can't tell you what a competitor changed last week: a new price, a new plan, a new claim. By the time that change reaches your loss reasons, it has already cost you a quarter.
A competitive intelligence platform covers that outside view. Flares tracks your competitors' pricing, plans, website, messaging and reviews, and tells you what each change means for your deals. Your reports then show what happened in deals next to what changed in the market. Flares won't clean your CRM data, though. The fields and definitions stay with you.
Automated competitor monitoring
New prices, plans and claims, caught the day they appear, not a quarter later in your loss reasons.
Weekly competitive digest
A Monday summary of competitor changes that could touch this week's forecast and deals.
Competitive intelligence via MCP
Your AI assistant can tell you what a competitor charges now, while you build the report.
Put the market next to your pipeline
With Flares, each competitor change reaches you the week it happens, long before it shows up in your loss reasons.
14-day free trial · 30-second setup
FAQ
RevOps competitive intelligence FAQ
What is competitive intelligence for RevOps?
It is the revenue side of competitive intelligence: recording which competitor is in each deal, then reporting win rate, discount and lost revenue per competitor. RevOps designs the CRM fields, keeps them clean and brings the numbers into forecasts, pricing reviews and QBRs.
What is the difference between revenue intelligence and competitive intelligence?
Revenue intelligence reads your own activity: calls, emails and pipeline, to predict which deals will close. Competitive intelligence looks outward, at what competitors charge, ship and claim. The two meet in the CRM. A call tracker can spot a competitor's name, but only competitive intelligence tells you what that competitor changed last week.
What does a RevOps analyst do with competitive data?
They keep the competitor fields clean, build the reports and answer the questions leaders ask. Where do we lose, and to whom? Are we discounting more against one competitor? Did a late competitor put the forecast at risk? The analyst also audits the data every quarter, so the answers hold up in the QBR.
What problems does competitive intelligence solve for RevOps?
It explains numbers that otherwise move for no clear reason. A falling win rate, deeper discounts or a missed forecast often trace back to one competitor in one segment. With the competitor recorded on each deal, you can show where the problem is instead of guessing, and send it to the team that can fix it.
What's the difference between sales ops and RevOps in competitive analysis?
Sales ops usually sees the sales pipeline only. RevOps spans marketing, sales and customer success. So it can follow one competitor through the whole revenue cycle: the deals marketing sourced, the deals sales won or lost, and the customers who later left for them. That full view is what makes competitive reporting useful.
Who owns competitive intelligence: RevOps or product marketing?
Usually both, for different parts. RevOps owns the data: the fields, the definitions and the reports. Product marketing owns the analysis and the story reps tell. Bigger companies add a competitive intelligence team to lead the program, with RevOps supplying the numbers. Write the split down, or the work falls between the teams.
How do you track competitors in Salesforce?
Add a competitor picklist on the opportunity, separate from the loss reason, with one value per named competitor plus "None known" and "Other". Make it required at close, and add a field for the incumbent. Then build three reports: deals by competitor, win rate by competitor and loss reasons by competitor. HubSpot has no competitor property, so add a custom deal property there.
Should the competitor field be required in the CRM?
Yes, at close, with "None known" as a valid answer. Earlier than that, a required field gets filled with whatever is quickest. Ask reps to add a competitor as soon as one appears, and date each entry. Then check coverage every month by team, so gaps get fixed before the quarter ends.
How do you calculate win rate by competitor?
Divide the deals you won against a competitor by the deals you won or lost against them, over the same period. Leave out deals that ended with no decision, and show them beside it as their own rate. Below about 30 closed deals against one competitor, show the counts rather than a percentage, and pool quarters until the rate is stable.
Why are closed-lost reasons in the CRM unreliable?
Reps choose them quickly, usually at quarter end, and some reasons are more comfortable than others. "Price" blames no one, so it is chosen far more often than buyers give it. Treat CRM reasons as what your team believes, and check them with win/loss analysis that asks buyers directly.
How do you include competition in a sales forecast?
Flag it rather than build it into a formula. In each forecast call, list the commit deals where a competitor entered late or where no competitor is named. Ask the rep what changed. Then compare those deals with your historical win rate against that competitor before you accept the commit.
What are examples of competitive intelligence in RevOps?
Say your win rate against one competitor falls from 41% to 28% in one segment. That points to a product or training gap there. Discounts that run 11 points deeper when a certain competitor appears show what they cost you in price. And a competitor's price rise tells your deal desk it can stop discounting to match.
Is competitive intelligence legal for RevOps teams?
Yes, when the data is your own or public. Your CRM, call recordings, quotes and published price lists are fair to use. Using price lists or pipeline data a new hire brought from a former employer is not. Neither is pretending to be a prospect to get a quote. When in doubt, ask your legal team.
What tools do RevOps teams use for competitive intelligence?
The CRM comes first, with a call recording tool and a BI tool for dashboards. Those show what happened in your deals. To follow what competitors change outside your deals, teams add competitive intelligence software that tracks pricing, plans and messaging and reports each change.
Can AI be used for competitive analysis in RevOps?
Yes, for the reading and coding work. AI can tag loss notes against your reason codes, pull competitor names out of call transcripts or compare two price lists. Asked from memory, it often gives last year's prices, so feed it your own data and dated pages. That is how competitive intelligence with AI stays accurate.
Ready? Your competitors won't wait for you.
Get your first competitive digest next Monday.
14-day free trial · 30-second setup