Competitive Displacement

Reach for Competitive Displacement when you know what the account uses today and want outbound aimed at replacing it.

• The account runs a named tool or a manual process. The sequence can name the job the tool does, not guess at the account.
• A renewal date is known, or can be found. The difficulty rating turns on the contract, so the timing is settled before the first email.
• A BDR is about to write to an account that may already have an AE. The BDR guard stops the sequence before anyone drafts it.
• Account Snapshot has confirmed the incumbent. Run this skill once the incumbent is known, not before.

The skill drafts. The rep reads every email, and the rep decides what goes out.

Displacement outbound fails in two ways. It names a problem the buyer does not have, so it gets ignored. Or it states a figure with no source, so the first buyer who asks where it came from finds nothing behind it. This skill plans the outbound against both failures, by checking the source of every claim and the ownership of the account before the first email is drafted.

Difficulty Tests And The Template

The profile's Displacement section holds one template row per incumbent type. Each row has a positioning line with its tag, a one-sentence wedge, three discovery questions and a primary and secondary persona. A template keeps the team's tested wedge in front of the rep, so nobody has to invent one in the moment.

Difficulty has three levels, and each has one directional test. Low means no contract term to exit, as with a manual process. Medium means a renewal inside 180 days. High means a term running more than 180 days past today with an exit fee. The rating is the highest test met. When the contract term is unknown, the rating is High, because an unknown term is not a favorable one. A renewal month on record fixes the end of the term, so the three tests decide the rating instead.

Four Emails And Their Rules

Each persona gets four emails, and each email uses a different angle. Email 1 gives an industry trend, or a benchmark dated within 90 days of the run date, without attacking anyone. Email 2 asks a question the incumbent cannot answer well. Email 3 cites a customer result, and only when its Status is Verified, otherwise it is held. Email 4 acknowledges the current vendor and asks about timing, or confirms the renewal month when that month is on record.

Every email has a subject line that never names the competitor, a body of 120 words or fewer, and a first line that refers to something specific about the prospect. Every number needs a named, dated source, or it comes out, and the email asks the question instead.

Confidence And The BDR Guard

Confidence applies to the incumbent. HIGH means a CRM note that names the incumbent, a discovery call or a prospect statement confirms it, and full sequences follow. MEDIUM means it is suspected, so the sequence proceeds with the assumption noted, and discovery question 1 tests it. LOW means it is a guess, so displacement does not run until Account Snapshot finds the incumbent.

The BDR guard is a hard rule. A BDR never gets sequences on an account that is ACTIVE with an AE owner, unless that AE has said yes. The analysis goes to the AE instead. An account pending AE assignment is not ACTIVE, so it is worked, and the output says it is pending.

Core Workflow

Confirm whether the user is a BDR or an AE, and read the account status and owner first, because the guard decides whether any sequence is written. Identify the incumbent, rate readiness and set the confidence. Run the three difficulty tests. Load the template row and build the gap matrix with a tag on every gap. If the guard does not apply, draft four emails for each persona, checking every number and claim before drafting. An ENGAGED account gets a reply plan in place of the four emails, and an INBOUND account gets a reply to its request first. Finish with the summary, the hand-off block and one next action with an owner and a date. The report comes back inline, and a file is written only when you ask.

What It Reads

This skill reads the Company, Buyer Personas, Competitive Landscape, Value Propositions, Proof Points and Displacement sections of the client profile. The Proof Points section supplies the Displaced vendor and Status columns, which decide whether a result can be cited. From the Context OS knowledge base it opens the account's folder under accounts, the competitors under gtm and the personas under people. The CRM read is offered, asked for and read only, and it is never written back. Pasted notes work the same way.

Where It Fits

Competitive Displacement sits in the Beat The Incumbent chain, after Competitive Strategy and before Account Snapshot or Meeting Prep. When Competitive Strategy has run on the account, this skill starts from its gap matrix. Its incumbent type, difficulty rating, target personas and sequences pass to Account Snapshot and Meeting Prep by name, so the outbound and the meeting prep use the same facts.