Competitive heat changes timing. When a qualified buyer shows observable competitive behavior, the question is no longer "should we be in this account?" It becomes "how should we show up right now?"

With Deal Intelligence, fit and recency are already handled. Signals are filtered to your ICP and tied to real buyer personas. They are time-bound. You are not reacting to vague intent or anonymous surges. You are looking at qualified competitive motion from identified decision-makers.

That simplifies the decision tree. The remaining work is strategic, not technical.

Two decisions matter:

1. What motion are we running?
2. How should the message be structured?

Step 1: Decide the Motion

Competitive heat does not dictate a single play. The situation determines the motion.

There are three common scenarios, each requiring a different approach.

Motion A: Closed-Lost Re-Engagement

The setup:
The account evaluated you before. It stalled, went with a competitor, or chose to defer. Now competitive activity resurfaces—either with the same competitor or a different one.

What this means:
This is not a cold start. It is a re-entry. Something changed: budget released, the prior solution underperformed, a new leader arrived, the business context shifted.

The approach:
The tone should reflect familiarity and evolution. You are not interrupting. You are reconnecting at a new moment in the cycle.

Acknowledge the history without dwelling on it. Focus on what has changed—on your side, on their side, or in the market. Position the conversation as an update, not a retry.

Example email:

Subject: Revisiting [initiative] at [Company]?

Hi [Name],

Last time we connected, timing wasn't right around [use case].

I've seen several teams in [industry] re-evaluate this space recently as priorities shift—especially around [specific pressure point, e.g., "pipeline predictability" or "faster rep ramp"].

If this is back on your radar, I'm happy to share what's changed on our side and how teams like [peer company] are approaching it now.

Open to a short reconnect?

Best,
[Rep]

Why this works:

• Respects history without apologizing for it
• Acknowledges shifting context (validates their re-evaluation)
• Does not mention competitors or ask why they're looking again
• Keeps the ask proportional to the relationship stage
• References a peer company (social proof without pitch)

What to avoid:

• "Saw you're looking again"—too direct, implies tracking
• "Did the other vendor not work out?"—puts them on defense
• Leading with product changes—features are not why they're re-evaluating
• Overselling the re-engagement opportunity—stay measured

Follow-up (if no response after 3 days):

[Name],

Following up on the note about [use case].

One thing that's shifted since we last talked: [specific capability or market change]. For teams dealing with [their likely challenge], that usually changes the evaluation criteria.

Worth a 15-minute conversation if you're taking another look at this space.

[Rep]

Motion B: Net-New Competitive Intercept

The setup:
The account fits your ICP. There is no existing pipeline. Competitive heat appears—a buyer persona connected with a competitor's AE, engaged with competitor content, or showed up in G2 comparison activity.

What this means:
This is not generic outbound. It is timing-aware introduction. They are actively evaluating the category. You do not know if they are aware of you, but you know they are in-market.

The approach:
The tone should reflect relevance and peer context. You do not reference the signal directly. You let it inform your confidence and positioning.

Position as if you assume they are evaluating solutions (because they are). Frame around the outcome they are trying to achieve, not the vendors they are comparing. Use language that normalizes the evaluation process without naming it explicitly.

Example email:

Subject: Quick note on [problem area]

Hi [Name],

Many [role peers, e.g., "VPs of Sales at Series B companies"] are actively tightening how they manage [specific challenge, e.g., "outbound signal prioritization"], especially as evaluation cycles compress and teams need faster time-to-value.

If improving [metric or outcome, e.g., "pipeline from cold outbound"] is a focus this quarter, I can share how teams similar to yours are approaching it without adding operational drag.

Would it make sense to compare notes briefly?

Best,
[Rep]

Why this works:

• Assumes relevance without stating how you know
• Frames around outcome, not vendor comparison
• Positions you as timely, not reactive
• Uses peer framing ("teams similar to yours") to establish credibility
• Keeps the ask collaborative ("compare notes") rather than transactional ("schedule a demo")

Alternative approach (problem-first framing):

Subject: [Specific challenge] at [Company]

Hi [Name],

Most [role] leaders I talk to are trying to solve for [specific problem, e.g., "signal overload—too many alerts, not enough context"].

The teams that solve this well tend to focus on [specific approach or framework]. The ones that don't end up with tools that create noise instead of reducing it.

If you're evaluating options in this space, happy to share what separates the approaches that work from the ones that don't.

15 minutes, no pitch.

Best,
[Rep]

Why this also works:

• Leads with the problem, not the solution
• Demonstrates understanding of the category (builds credibility)
• Positions you as an advisor, not a vendor
• Self-qualifies (if they're not evaluating, they won't respond)

What to avoid:

• "I noticed you're looking at sales intelligence tools"—too direct
• Mentioning specific competitors—unnecessary and risky
• Generic value props—they've already heard them from others
• Asking for 30+ minutes—disrespects their time in active eval mode

Follow-up sequence:

Touch 2 (Day 3): LinkedIn message

Hey [Name]—sent a note earlier this week about [problem area].

One thing most teams don't think about until mid-evaluation: [specific technical or workflow consideration, e.g., "how signals route to territories" or "whether data backfills historically or starts from scratch"].

That usually determines whether the tool works for your workflow or creates more manual work.

Worth asking in your demos.

Touch 3 (Day 6): Email with proof

Subject: How [Similar Company] approached this

[Name],

Following up on the note about [problem area].

[Similar Company Name] was in a similar spot last quarter—[their situation]. They ended up focusing their eval on [specific decision criteria] because that's what actually impacted [outcome].

Wrote up a short breakdown: [link to case study or comparison doc]

Might not apply to your situation, but the use case felt close.

Best,
[Rep]

Touch 4 (Day 9): Final educational value

Subject: Three eval questions worth asking

[Name],

Last note on this.

If you're still comparing options, here are three questions that usually surface the biggest differences:

1. [Question about technical architecture or data freshness]
2. [Question about workflow integration or territory routing]
3. [Question about a common limitation in the category]

The answers will tell you whether the tool matches your workflow or not.

Good luck with the eval.

[Rep]

Motion C: Multi-Thread Acceleration

The setup:
You already have an open opportunity or partial coverage in the account. Competitive heat appears from a different persona or function—someone outside your current thread.

What this means:
The evaluation is expanding. This is not about increasing pressure on your existing champion. It is about increasing coverage across the buying committee.

The approach:
The motion shifts from single-thread follow-up to buying-group expansion. The goal is to support internal alignment, not bypass your champion.

The tone should reflect collaboration. You are helping them build consensus, not going around them.

Example email (to the new persona):

Subject: Looping in the right stakeholders

Hi [Name],

I've been working with [Champion Name] on [initiative]. As teams move deeper into evaluating [category], I often see additional stakeholders weigh in around [security / integration / ROI / vendor management].

If helpful, I can provide a short overview tailored to that perspective so the broader team has what they need to make a confident decision.

Would it make sense to include you (or anyone else) at this stage?

Best,
[Rep]

Why this works:

• Normalizes the expanded evaluation (not surprising or threatening)
• Positions you as supportive of their internal process
• Asks permission rather than assuming inclusion
• Keeps the champion in the loop (references them by name)

Example email (to your existing champion, when you see new personas emerge):

Subject: Evaluation expanding?

Hi [Champion],

Noticed a few additional stakeholders at [Company] may be weighing in on the [category] decision.

In similar evals, we typically brief [security / finance / ops] separately on [specific concerns relevant to their function] so they have what they need without sitting through a full demo.

Does it make sense to loop anyone else in at this point? Happy to tailor the conversation to their priorities.

Best,
[Rep]

Why this works:

• Acknowledges expanded committee without making it adversarial
• Offers to reduce friction (separate briefings = efficiency)
• Keeps champion in control of the process
• Demonstrates understanding of enterprise buying dynamics

What to avoid:

• Going around your champion to the new persona without coordination
• Treating multi-threading as an escalation (stay collaborative)
• Assuming the new persona is a blocker (they might be an accelerator)
• Sending identical content to multiple people (tailor by function)

Expanded example (when the new persona is a known blocker function):

Subject: Quick context for [security / procurement / finance]

Hi [Name],

[Champion Name] mentioned you're involved in the [category] evaluation from the [security / procurement / finance] side.

Most [your function] teams I work with care about three things when evaluating tools like ours:

1. [Specific concern relevant to their function]
2. [Compliance or risk consideration]
3. [Integration or operational impact]

I put together a short doc that addresses these directly: [link]

If you have additional questions or need anything formatted differently for internal review, let me know.

Happy to jump on a call if it's easier to walk through.

Best,
[Rep]

Why this works:

• Respects their function-specific concerns
• Provides immediate value (doc addresses their questions upfront)
• Offers flexibility (async or sync)
• Does not force a meeting

Step 2: Structure the Message

Competitive heat should influence how you write. It should not be disclosed.

Effective messages share a few characteristics:

They acknowledge timing without claiming knowledge.
You write as if you assume they are evaluating (because they are), but you do not state how you know. The signal lives inside your system, not inside your email.

Bad: "I saw you connected with [Competitor] on LinkedIn."
Good: "Many teams in your space are evaluating this category right now."

They focus on buyer priorities, not competitor behavior.
Your message should center on what they care about—outcomes, timelines, decision criteria—not on what your competitor is doing.

Bad: "We're better than [Competitor] at [feature]."
Good: "The main difference teams care about is [specific capability tied to their workflow]."

They use proof points aligned to likely evaluation criteria.
Competitive evaluations are comparative by nature. Your examples should reflect that. Reference peer companies, specific use cases, or decision frameworks that help them evaluate better.

Bad: "We have great customer success stories."
Good: "Teams like [Similar Company] prioritized [specific capability] when they evaluated this space because [reason tied to outcome]."

They offer a clear but proportional next step.
Do not ask for 60 minutes when 15 will do. Do not ask for a demo when a doc answers the question. Match the ask to the relationship stage and the information density they need.

Bad: "Let's schedule a full demo to show you everything we do."
Good: "Happy to walk through [specific topic] in 15 minutes if it's helpful."

Additional Structural Principles

Lead with outcomes, not features.
Competitive evaluations happen because buyers have a problem to solve. Your message should frame around that problem, not your solution's capabilities.

Structure: Problem → Outcome → Proof → Ask

Use specificity to build credibility.
Vague claims sound like marketing. Specific claims sound like experience.

Weak: "We help sales teams be more efficient."
Strong: "Teams using us see 5-10 additional qualified at-bats per rep per week because signals surface in real-time instead of 24-48 hours later."

Normalize the evaluation process.
Do not treat their vendor comparison as unusual or urgent. Treat it as a rational business decision. This reduces pressure and increases trust.

"As teams evaluate options in this space..." (normalizing)
"You need to make a decision fast..." (pressuring)

Avoid negative competitive positioning.
Do not bash the competitor. It makes you look insecure and unprofessional. Acknowledge their strengths, then differentiate on specifics.

Bad: "[Competitor] is slow and outdated."
Good: "[Competitor] focuses on [their strength]. The trade-off is [specific limitation]. For teams prioritizing [your strength], that gap usually matters."

A Note on Tone

Competitive heat increases probability. It does not guarantee urgency.

Your message should reflect quiet confidence, not escalation. You are not reacting to a crisis. You are responding to a signal that suggests timing alignment.

The buyer is in control. You are providing context to help them make a better decision. That framing should come through in how you write.

Confident, not aggressive:
"If improving [outcome] is a priority, happy to share how teams like yours approach it."

Helpful, not pushy:
"Here are three questions worth asking in your demos. The answers will tell you what actually matters."

Timely, not urgent:
"Many teams are re-evaluating this space as priorities shift."

Collaborative, not competitive:
"Would it make sense to loop in additional stakeholders at this stage?"

Competitive heat gives you permission to act. The structure and tone of your message determine whether that action creates pipeline or resistance.

What to Measure

Competitive heat outreach should outperform cold outbound. If it does not, something in your execution is broken.

Baseline metrics:

• Response rate: 2-3x higher than cold (if not, your messaging is off)
• Meeting conversion: 40-60% of responders (vs 20-30% for cold)
• Time to response: Faster when you reach out within 24 hours
• Win rate: Equal to or higher than inbound (if lower, you are entering too late or positioning poorly)

Diagnostic metrics:

• Response rate by motion (which scenario is working best?)
• Response rate by message structure (problem-first vs peer-framing vs outcome-focused?)
• Objection patterns (are you hearing the same pushback repeatedly?)
• Follow-up effectiveness (which touch in the sequence drives the most engagement?)

If your competitive heat outreach is not materially outperforming other channels, the signal is fine. The execution needs work.

Common Mistakes

Disclosing the signal.
"I saw you connected with [Competitor]" makes the conversation about your tracking, not their evaluation. Let the signal inform your timing and positioning. Do not make it the subject line.

Treating all competitive heat the same.
Motion A (closed-lost) requires different messaging than Motion B (net-new) or Motion C (multi-thread). Match the message to the situation.

Leading with a meeting request.
They are already in demos. They do not need another one. They need information that helps them evaluate better. Provide value first. The meeting will follow if it makes sense.

Waiting too long.
Competitive signals decay. Reach out within 24 hours or accept that you are entering late.

Overpitching in the first touch.
Your goal is to start a conversation, not close a deal. Keep the first message focused on one clear point of value. Save the full story for when they engage.

What Good Execution Looks Like

You reach out within 24 hours of the signal. Your message reflects the motion (closed-lost, net-new, or multi-thread). You offer specific value tied to their likely evaluation criteria. You follow up persistently but not desperately. You stop after four touches if they do not respond.

The result: response rates that are meaningfully higher than cold outbound, meetings that convert at 40-60%, and deals that close because you entered early enough to shape the evaluation.

Deal Intelligence gives you qualified competitive motion. Your execution determines whether that motion becomes pipeline.