Competitive Intel

What it does

Goes beyond a feature-comparison table to model why a competitor would or wouldn't respond to a given move: what they're capable of doing (resources, capabilities, speed), what they're incentivized to do (their strategic priorities, what they'd sacrifice by responding), and what constrains them (org structure, channel conflict, balance-sheet limits). Produces a ranked set of likely competitor moves and a pre-committed response for the top ones, instead of reacting in real time.

When to use

Before a major move (pricing change, new product launch, market entry) that a competitor is likely to react to, or when the current competitive read is just a feature table with no view on likely next moves. Also use when the team keeps getting surprised by competitor actions.

Method

1. Build a capability profile per competitor: balance sheet strength, R&D/engineering velocity, distribution/channel reach, brand permission (what moves fit their brand and what would damage it). Capability, not intent, is the ceiling on what they can actually do.
2. Build an incentive profile per competitor: what is this competitor's stated strategic priority this year, what internal metric are their leaders being measured on, and what would they have to sacrifice (margin, focus, another business line) to respond to your move.
3. Identify structural constraints: channel conflict (would responding cannibalize a partner relationship?), organizational speed (how long does their planning cycle actually take?), and prior public commitments that limit their options.
4. Generate the actual move set: for each competitor, list the 3-4 plausible responses to your move, not just "they might cut price" — include capability-consistent and incentive-consistent alternatives (bundling, channel deals, talent poaching, category redefinition).
5. Score each move on likelihood × impact on you, using the capability/incentive/constraint profile as the evidence, not a gut guess.
6. Pre-commit a response to the top 2-3 likely moves before they happen. Write the actual trigger condition ("if competitor X drops price by more than 15% within 60 days of our launch, we will...") so the team isn't improvising under pressure.
7. Set a monitoring cadence: name the specific signals (job postings, pricing page changes, partner announcements, earnings call language) that would show a modeled move is starting, and who is watching for them.