Competitive Strategy

Reach for Competitive Strategy when an open deal has a named incumbent or rival, and the battlecard on file is generic.

• The buyer has named a current tool or a rival in the deal. The battlecard should describe this buyer, not the category.
• An incumbent is entrenched and the rep is losing the room. The threat level shows how hard the switch will be, and the win plan shows where to push.
• A rival was evaluated and no preference has been stated. The skill records the rival beside the incumbent without scoring it, claims no advantage over it, and the AE gets the buyer's criteria in writing before any demo.
• A renewal date sits inside the deal's window. The plan starts from the renewal, so the decision finishes before it.

The skill builds the plan. It never sends a message, never writes to the CRM and never trashes a competitor.

A competitive battlecard is only useful when it describes the buyer in front of you. Reps lose active deals to incumbents they never characterized, or they pitch gaps that the buyer can disprove with one question. This skill fixes both problems by filing the incumbent under a shared type, scoring the threat, and building the gap matrix from what this buyer has actually said.

Seven Incumbent Types

Every competitor or incumbent is filed under one of seven types: direct software, a single-function tool, a service bureau, a manual process, no program at all, outside professionals, or an adjacent tool. The type decides which failure patterns, proof points and objections apply, so it comes first. A rival that fits two types is filed under the one that describes the buyer's current spend, and the battlecard says why.

The threat level scores five factors: prospect satisfaction, contract status, switching barriers, internal champion for the incumbent, and the incumbent's product advantage. LOW counts 1, MEDIUM counts 2 and HIGH counts 3. A factor the record does not show scores MEDIUM, because silence is not a no. The five scores are averaged, and the battlecard shows the sum and the average. Below 1.5 is LOW, 1.5 to 2.5 is MEDIUM, and 2.5 or above is HIGH. The calibration can raise the level one band, but only on a recorded fact that a HIGH clause names and no factor already scored. A rival never changes the level, and the battlecard names each clause it checked.

Proof Points, Status And Five Cases

Every proof point carries one Status. Verified means the customer confirmed the number and agreed to be named, and only a Verified row can be quoted in a talk track, a battlecard line the rep reads aloud or an email. Benchmark is a published figure with its source and date, used as context and labelled as one. Illustrative is invented for an example, marked do not cite, and never shown to a prospect.

A failure pattern needs five cases with a named source before it is called a pattern. Fewer than five is an observation, and the battlecard says so in the same sentence. Any jurisdiction deadline cites its rule and the date the rule was checked.

Gap Matrix And Win Plan

The gap matrix covers only the capabilities this buyer named, or a failure pattern predicts, with the incumbent's status, our status and why it matters to this buyer. A row qualifies only on a pain or criterion the buyer stated on a dated call. A row whose claim is Unknown is a discovery question, not a gap. Positioning landmines are listed with a mitigation for each, because an AE who is surprised by a competitor's strength loses credibility fast. The win plan is a checklist by stage, from pre-meeting to post-meeting, with an owner and a date where one is known.

Core Workflow

Read the account's folder and the competitor notes first, then offer the CRM read and ask before it runs. Name the incumbent, how it was identified and its contract status, marking gaps Unknown. Profile the incumbent, file its type and score the threat. Build the positioning, the zone ranking, the gap matrix and the landmines. Write the discovery questions, objection responses and talk tracks, and match only the proof points whose Status allows them. Finish with the win plan and one next action with an owner and a date. The battlecard comes back inline, and a file is written only when you ask.

What It Reads

This skill reads the Company, Buyer Personas, Competitive Landscape, Competitive Patterns and Trends, Value Propositions, Proof Points, Qualification Criteria, Qualification Zones and Sales Methodology sections of the client profile. From the Context OS knowledge base it opens the account's folder for its notes, calls and decisions, and the competitors under gtm for the incumbent's row and its failure patterns. The CRM read is offered, asked for and read only, and nothing is written back. Pasted deal notes work the same way.

Where It Fits

Competitive Strategy sits in the Beat The Incumbent chain, after MEDDPICC Analysis and before Competitive Displacement, Account Snapshot or Meeting Prep. It reads the Competition element and the stage call from MEDDPICC Analysis. Its incumbent type, threat level, rival record, gap matrix, battlecard and win plan pass to Meeting Prep by name, and its incumbent type, threat level and rival record pass to Competitive Displacement, so both skills file the same incumbent and agree.