// COMPETITIVE OPS · HEADS OF GROWTH

Competitor Agents Need Battlecard Locks Before They Start Price Wars

Operator thesis: the fastest way to cheapen your category is to let AI answer competitor mentions with unapproved claims, instant concessions, and panic-routing.

Lock the claim before the reply
01 TriggerBuyer names a competitor, asks for comparison, or hints at price pressure.
02 RiskThe agent improvises proof, discount, or legal language to win the thread.
03 ControlBattlecard locks decide which claim, proof, price move, and escalation are allowed.
04 OutcomeSpeed stays high without teaching the market that AI can be bargained down.
If the machine can mention a rival, it needs a locked source of truth before the first sentence.
// THE FAILURE PATTERN

Competitor pressure turns useful automation into margin damage.

Without locks

The agent sees a competitor name and treats it like a sales objection to defeat immediately. It cites stale feature claims, offers an aggressive concession, or routes the deal as urgent because the word "competitor" appeared.

Growth sees activity. Sales sees noise. Legal sees a claim it never approved.

With locks

The agent can only use approved comparison lines, customer proof, price boundaries, and escalation paths. It can move fast, but it cannot invent positioning under pressure.

Competitive motion becomes a governed workflow, not a live improvisation.

// VISUAL FRAMEWORK

The battlecard lock matrix

Give the machine four hard gates before it replies to a competitor mention.

Signal
Agent can do
Agent cannot do
Feature comparison
Buyer asks who does what.
Use approved claim and link proof.
Invent roadmap, trash rival, or promise parity.
Price pressure
Buyer says the other option is cheaper.
Explain value boundary and route discount request.
Offer concession outside threshold.
Switching risk
Customer names churn or renewal threat.
Open retention path with account owner.
Rewrite contract terms in chat.
Legal claim
Security, compliance, benchmark, or guarantee.
Use approved snippet only.
Summarize policy from memory.
// CONTROL PLANE FLOW

Route competitor work through proof, not vibes.

Detect

Competitor named, category compared, or price challenged.

Classify

Feature, price, legal, switching, or procurement pressure.

Lock

Attach approved claim, proof asset, and price boundary.

Reply

Send only inside the allowed lane.

Escalate

Human owns anything outside the lock.

Competitor automation is not a copywriting problem. It is a claims-control problem.
// OPERATOR CHECKLIST

Install these locks before the agent sees live deals.

1
Claim lock. Every feature comparison points to an approved proof source.
2
Price lock. The machine can explain value but cannot offer concessions beyond threshold.
3
Proof lock. Case studies, benchmarks, and compliance answers come from dated assets only.
4
Escalation lock. Legal, procurement, churn, and discount edge cases route to named owners.
5
Receipt lock. Every competitor reply stores signal, claim, proof link, and owner in CRM.

Decision rule: if the agent cannot cite the exact approved battlecard row, it can acknowledge the question and route it. It cannot answer.

What A Head Of Growth Should Do Next

Take the issue in this piece and turn it into one operating rule. If a machine worker in this lane can touch pipeline, routing, pricing, forecasting, CRM truth, or customer communication, define the permission boundary, evidence requirement, and escalation path before you scale it.

The win is not more activity. The win is more trusted action with less cleanup debt.