When a competitor changes the picture

An announcement arrives, an executive asks what we are doing about it, and three different questions land on your desk glued together.

The idea

A press release is not a change. Somebody sent an email; nothing has moved on a customer's screen yet. Before you can say what you will do, you have to say what actually changed for a buyer, and what that change threatens.

Three questions arrive as one. Is this real? What does it threaten? What do we do? Answer them in that order and most competitive fire drills shrink to a paragraph and a date. Answer them out of order and you spend a quarter building parity with a slide.

There are two clocks, and they are not the same clock. The first is what you say this week, to customers and to your own field. The second is what you build over the next two quarters. Most of the damage in the first four weeks is done on the first clock.

The two-clock response board

the card on your desk

—

1 · what could it threaten 2 · what would settle it 3 · the two clocks 4 · four weeks

live caption Deal is on the table. Sort each consequence into the bucket it really belongs to.

pick a consequence, then pick a bucket

you can run one thing properly this week — commission it

this week · what we say

this quarter · what we build (13 engineering weeks, one team)

How it works

The method is four moves, and the order is the whole trick.

Write the sentence a customer would say. Not "they announced an EU region" but "my security reviewer now asks where the data sits, and I cannot answer". If you cannot write that sentence, the change is in a press release, not in the market.
Name what it could threaten, in four buckets. Differentiator, price, distribution, narrative. Most events touch three of them. Only the differentiator bucket is answered by building product. Price is answered by packaging and discount policy, distribution by channel, motion and procurement, narrative by what you say and who says it.
Pick the one fact that would settle it inside a week. Cost and days matter more than elegance. Evidence that lands in week five cannot justify a decision made in week two.
Answer on two clocks. This week: the sentence the field says in every account. This quarter: at most one structural bet, sized against the capacity you actually have.

The internal half: a point of view, not a plan

An anxious executive messaging at ten at night does not want a Gantt chart. They want to know that somebody has a view. A point of view is three things, and it fits in a message:

point of view = claim + reason + revisit date

claim:   "we are not matching it — this is a list-price move,
          not a street-price move"
reason:  "in our last 20 competitive deals their quote landed
          within 4 points of ours; 1 of 12 renewals has raised it"
date:    "I re-run the renewal check on 14 March and tell you
          if it has moved"

The date is the part that makes an early claim safe. It converts a guess into a commitment to look again, which is what a nervous room is actually asking for.

The disciplined refusal, and what to say instead

Feature-for-feature matching is always available and it always costs the same: everything.

quarter capacity            = 13 engineering weeks (one team)

match them feature for feature = 13 weeks  ->  0 weeks left
deepen the differentiator      =  7 weeks  ->  6 weeks left
remove the buying friction     =  5 weeks  ->  8 weeks left
change the fence, not the number =  3 weeks -> 10 weeks left
instrument it and revisit        =  1 week  -> 12 weeks left

The sentence that replaces the match is not "we're better". It is four lines a salesperson can say without you in the room:

"We are not matching it. Here is what we are doing:
   what changed      — their list price, not their street price
   what it means     — your renewal number does not move
   what we are doing — a smaller tier in March that starts
                       below their new list price
   what would change my mind — three of our twelve renewals
                       raising it. I check on 14 March."

When to use it

situation	the move	the trade-off
Announcement with no change a customer can see	Point of view this week, instrument, revisit on a named date	You look slow to people who wanted a press release of your own
A price cut that survives contact with your renewals	Change the fence, not the number: a new tier or a repackage	A tier is real work and it fragments the line-up
A rule change that blocks a market	Unblock the buying path first — artefacts, dates, an addendum	You carry compliance debt until the real build lands
Open source or a rival reaching parity on your customers' data	Deepen the differentiator the evidence found, and name what stays proprietary	Seven of thirteen weeks committed to a single bet
A genuine gap two named customers refused to buy without	Build it, timeboxed, and say so plainly	The one case where matching is the answer — verify with names, not anecdotes

Limit: this frame covers the first four weeks. A rival with a structurally cheaper cost base or a distribution channel you cannot reach is a strategy problem, not a response problem, and it deserves a different meeting.

Watch out for

Answering the press release instead of the change. Their status page, their trial, their pricing page and your own CRM settle more in an afternoon than a war room settles in a day. Ask for the availability date, not the announcement.
Everything landing in the differentiator bucket — because that is the bucket with the satisfying remedy, and engineering is the muscle you know how to flex. Test it: what would a buyer have to do differently? If the answer is "nothing yet", it is narrative.
Matching the number without moving the fence. A discount is permanent, symmetrical and invisible in your roadmap; a new tier is a decision you can price, explain and withdraw. Cutting price to answer a story is the most expensive sentence in the quarter.
A point of view with no revisit date. It hardens into a position you defend long after the facts moved, and the person who wrote it stops being credible. Every claim gets a date and a number that would change it.
Replying to the ten o'clock message with "we're working on a plan". A plan takes a week and arrives after the anxiety has already produced a decision someone else made. Send three sentences tonight and the one-pager to the field by Wednesday; twelve different answers in twelve accounts is worse than one imperfect answer, and it is your fault, not theirs.

Worked example

You own a payments risk product. At 22:10 your CRO writes: "Fintechly just cut list price thirty percent and emailed our top forty accounts. What are we doing about it?"

You do not open the roadmap. You reply with a point of view: "My read is that this is a list move, not a street move — we've been within a few points of them on every competitive deal this year. I'm checking two things: the quoted price in our last twenty win/loss notes, and whether any of the twelve renewals closing this quarter has raised it. You'll have both by Thursday, and a one-pager for the field on Wednesday either way." That is a claim, a reason and a date, sent in ninety seconds.

Thursday the analyst comes back: in twenty competitive deals their quote landed within four points of yours, and one of twelve renewals mentioned the cut. So the threat is price as an anchor and narrative, not a new floor. The remedy is not a thirteen-week parity build and not a matching discount. It is three weeks of packaging — a smaller entry tier that starts below their new list number — plus a field one-pager with the street-price fact in it. You tell the CRO what would change your mind, and you check again on the fourteenth.

In an interview, the listener is not scoring your remedy. They are listening for whether you separated the three questions, whether you named evidence with a cost and a deadline, and whether you gave the executive a view instead of a plan.

Check yourself

It is 22:40. Your CRO asks what you are doing about a rival open-sourcing their engine. What do you send tonight?

Not quite — a plan takes a week to write and arrives after the room has already invented an answer. The plan can follow; tonight the useful artefact is a view with a date on it.

Yes. Claim, reason, revisit date. It costs ninety seconds, it stops twelve people improvising, and the date is what makes an early claim safe to state.

Not quite — reassurance without a reason reads as defensiveness, and it is unfalsifiable. Give the fact you are going to check, and when.

Your sort says a rival's price cut threatens price and narrative. Which of these remedies is a product change?

Yes. Only the differentiator bucket is answered by building product. Price is answered by the fence and the discount policy, narrative by what you say and who says it. Keep the thirteen weeks for something a customer asked for.

Not quite — that is a differentiator remedy applied to a price problem, and it spends the whole quarter answering a question no buyer asked. If features were the issue, the sort would have put a consequence in that bucket.

Not quite — a discount is a real price action, but it is not a product change, and it is permanent. Move the fence first: a tier you can price, explain and withdraw.