Your monitoring system fires on Tuesday afternoon: a competitor quietly dropped their entry-tier price by 30%. By next Tuesday, three deals are gone and you still haven't decided whether to respond — or how.
Detection is not response. Catching the alert is the easy part. What you do in the next 14 days is what determines whether you keep the deals that matter.
days is the typical window between detecting a competitor price move and the first lost deals you can attribute to it
Beyond that, the lost-deal field in your CRM gets noisy and you lose the causal link. The response clock starts at the alert, not at your strategy meeting.
Most founders treat this as a "should we respond?" question. It's actually four: triage (how serious?), response (what's the right move?), alignment (who agrees?), measurement (did it work?). Drift in any of them is where deals slip.
1. Alert Triage: Classifying the Move in 72 Hours
The first 72 hours after an alert are the most important window. The change is fresh enough that AEs can address it prospect-by-prospect before it hardens into a competitor position. The job is to classify the move — and assign a severity score — before doing anything else.
Price Drop (> 20%)
A direct cut on an existing tier. The most common competitive pricing move. The headline number is the story sales reps will hear on calls within two weeks.
Packaging Change
Features moved between tiers, feature limits raised, or seat minimums dropped. The headline price often looks unchanged — but the effective price just fell.
Grandfather Trap
Existing customers get a cheaper renewal rate; new customers pay the new price. Targets your upgrade pipeline without touching the public pricing page headline.
New Tier Introduction
A new entry-level or mid-tier added to target a segment you serve. Expansion rather than repricing — but the new tier is still a pricing signal worth responding to.
Severity comes from two factors: the percentage gap at the deal level (a 15% gap on a $50/mo plan doesn't matter; the same gap on a $50K/year enterprise contract is a board-level issue), and whether the change targets your most-fought segment.
For the upstream detection mechanics, see how to track competitor pricing changes. This playbook assumes the alerts are already flowing.
2. Response Options: Match, Undercut, or Anchor on Value
Most founders think there are two pricing responses: match the competitor or undercut them. There are actually three, and the third is usually the right one.
Match means cutting your entry tier to the competitor's headline. It removes the objection but compresses margin on your most price-sensitive, least loyal segment. Undercut goes lower, usually via a short-term promotion. It wins the next quarter and creates a renewal-price anchor you can't escape. Anchor on value means holding price and repositioning around what they don't offer — implementation speed, integration depth, support quality, switching costs.
| Response | Best When | Risk | Time to Implement |
|---|---|---|---|
| Match | You fight on price constantly and your segment is highly price-sensitive | Margin compression; trains the market to expect a price war | 1–3 weeks |
| Undercut | The competitor cut to capture a price-sensitive segment you can't afford to lose | Invites a counter-cut; creates a cheap-renewal expectation among new wins | 1–2 weeks |
| Anchor on value | Your differentiation is real and provable; your segment is not purely price-driven | Requires immediate battlecard + sales enablement to defend the position | 3–7 days |
If you can't articulate your differentiator in one sentence a buyer will repeat back, anchoring on value is a bluff — it just loses deals slower. That's where most "hold the line" decisions go wrong.
Need a structured way to capture these moves? The free competitor analysis template at /resources includes a pricing-signal log with the Type A/B/C/D classification built in.
The founder who matched when they should have anchored — and lost margin on every customer they kept
A mid-market analytics SaaS saw a competitor cut their growth tier from $149 to $99/month. The founder panicked, called an all-hands, and matched within five days. Win rate ticked up; the quarter looked strong.
Six months later, three problems landed at once: gross margin compressed 14 points, every existing customer expected the new lower price at renewal, and the competitor — VC-subsidized with room to cut — held $99 for nine months while the SaaS founder's price ceiling was permanently anchored. The founder had won the quarter and lost the next 24 months.
Anchor-on-value is almost always right if the move is pricing-only — pure price cuts without packaging or positioning changes. When pricing and positioning move together, you're facing a strategic pivot and the response math is different. For how those combine, see how to track positioning shifts. For the signal framework that classifies the move before you respond, see the competitor pricing intelligence guide.
3. Internal Alignment: Who Signs Off, Who Signals
Most pricing changes ship broken because the RACI is implicit. The founder decides alone, three people argue in Slack, or sales hears about the change the same morning prospects do. None of these work.
The cleanest alignment is a four-role RACI that runs once per response:
- Founder / CEO — Accountable. Owns the final go/no-go decision; has the authority to trade margin for position.
- Head of Product + VP Sales — Responsible. Bring the data: win/loss at the affected tier, churn risk by segment, the differentiators that justify the response.
- RevOps + Marketing — Consulted. Verify the change can be implemented (billing, contracts) and signaled (website, sales emails, case studies).
- Sales reps + CSMs — Informed. Get the briefing before the change goes live, not in the message that announces it. They're the ones defending the decision on calls.
The most common failure mode isn't disagreement on the response — it's shipping a price change without updating the battlecard and sales enablement in the same 24 hours. The pricing page moves; sales hears it from a prospect; no one has a rehearsed answer to the new objection. That gap is where deals get lost in the first 30 days.
For the format of a battlecard reps actually use mid-call (and the weekly loop that keeps it current), see the competitive battlecard framework. A pricing response without a battlecard update is half a response.
4. The Monitoring Loop: Proving It Worked in 30/60/90 Days
The response itself is a signal. After you ship a pricing change, the next question is whether it worked and whether it triggered a competitor counter-move. The standard cadence is a 30/60/90 review.
| Window | Primary Metrics | Why This Window |
|---|---|---|
| First 30 Days | Win rate at the affected tier · Deal velocity · New logo volume | Direct impact on the segment you responded for. The most decision-relevant signal. |
| Days 31–60 | Churn-cohort overlap (did pre-response customers churn at higher rate?) · ASP per new deal | Margin health. Whether you traded short-term win-rate for long-term margin compression. |
| Days 61–90 | NPS by tier · Buyer sentiment in reviews · Competitor counter-moves | Whether the response itself triggered a competitor escalation — and whether customers see your change as positive or as a sign of weakness. |
The most overlooked signal at the 60-day mark: your response triggered a competitor counter-move. If you cut price and they cut deeper, you didn't run a response — you started a price war. If you anchored on value and they introduced a feature that matches yours, they pivoted instead of cutting. Both outcomes are detectable in your own deal data — and both require a different follow-up response.
5. Response Anti-Patterns: The Five Mistakes That Lose Margin on Every Move
recurring anti-patterns that convert a pricing response from a margin win into a slow margin leak
Each is survivable alone. Stacked together — the typical failure mode — they cost more than the original price war.
The other half of running this playbook is the patterns that quietly undo every step above. They're the default behavior under time pressure — which is exactly when most pricing responses get shipped.
- Matching without anchoring on value first. Cutting price before proving the differentiator is a confession, not a tactic. Correct: run section 1's triage and section 2's one-sentence differentiator test before the pricing page moves.
- Undercutting with a promo that becomes the renewal anchor. Time-limited discounts compound into a renewal-price memory that survives the campaign. Correct: structure undercutting as a tier-internal trial so renewal defaults to list.
- Shipping the price change without updating the battlecard same day. Pricing page moves at 9am; sales hears it from a prospect by 4pm. Correct: section 3 must place battlecard delivery inside the same 24-hour window.
- Skipping the 60-day post-response review. The 30-day metric is new-logo volume, which tells you nothing about the trade you made. Correct: hold section 4's cadence — the 60-day churn-cohort overlap exposes whether you traded wins for margin.
- Treating the response as one-time instead of building the playbook to reuse. Every pricing response is a future template. Correct: after each 90-day review, update this playbook and file the row in the pricing-signal log at /resources — the same template that classifies the move from section 1.
Teams that consistently beat competitor pricing moves aren't the ones that respond faster — they're the ones that avoid the patterns that turn a one-quarter win into a multi-year margin problem.
For deal-level pattern detection, see how to read your last 20 deals as competitive intelligence. For the customer-voice signal that confirms whether the response landed, see how to turn customer feedback into competitive intelligence.
A pricing move is the most visible competitor signal. Treat the response as structured — triage, options, alignment, measurement — and protect it from the anti-patterns in section 5.