> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Competitive Intelligence Signals
> How do I build a competitive intelligence workflow and run displacement plays when competitors stumble? Use it to pilot, verify output, and scale safely.
Competitive intelligence is a monthly operating rhythm, not a one-time report. It tells you who you are winning and losing against, and gives you displacement plays to run when competitors stumble. Signal-based outreach gets **18% response rates** vs 3.4% for generic cold email ([Autobound](https://www.autobound.ai/blog/signal-based-selling-complete-guide)). Displacement plays convert even higher because the prospect already has a defined problem and budget.
## How do I build a competitive intelligence workflow with Claude Code?
The workflow analyzes your CRM deal data to identify competitive patterns and monitors external signals for displacement opportunities.
In Claude Code, type:
```
/deepline-gtm Analyze my closed deals in HubSpot from the last 6 months. Show me competitor frequency, win rate by competitor, which stage I tend to lose at, and flag any new competitors appearing for the first time.
```
**With Codex:**
```
codex "Pull all closed-won and closed-lost deals from HubSpot with competitor fields populated. Break down win rate by competitor, loss stage, and rep. Flag any competitor appearing for the first time."
```
## What should I analyze in my monthly competitive review?
**Priority:** P1-P2 | Quarterly review cycle | Monthly data pull
Run this analysis monthly. The trends matter more than any single data point.
| Analysis | What to look for | Action |
| -------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Competitor frequency** | Who is showing up more or less on deals? | Rising competitors need new battlecards. Declining ones may indicate market shifts. |
| **Win rate by competitor** | Getting better or worse against each one? | Declining win rates need immediate attention. Talk to reps who won recently. |
| **Loss stage** | Where do you lose? Discovery = positioning problem. Proposal = pricing problem. | Adjust sales process at the failing stage. |
| **Rep performance** | Who is strong/weak against which competitor? | Pair weak reps with strong ones for coaching. Route competitive deals to your best closer. |
| **New competitors** | Anyone appearing for the first time? | Research immediately. Get a demo. Build a preliminary battlecard within 2 weeks. |
## How do I detect displacement opportunities?
When a competitor stumbles, their customers are briefly open to alternatives. Act within the window or lose it.
In Claude Code, type:
```
/deepline-gtm Search for news about [competitor] layoffs, outages, data breaches, or pricing changes in the last 30 days. Cross-reference against my target accounts that use [competitor]. Find the right contact and get their email.
```
**With Codex:**
```
codex "Find companies using [competitor] that are showing dissatisfaction signals — search for social posts mentioning [competitor] problems, check for recent [competitor] outages, and find decision maker emails at affected companies."
```
## What are the key displacement triggers?
| Trigger | Window | Play |
| -------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Competitor layoffs** | 2-4 weeks | Layoffs mean reduced support, slower roadmap, and worried customers. Any customer showing a signal is a displacement target. |
| **Competitor outage or breach** | 48 hours | Act fast. Reference reliability and security without being predatory. "We built \[specific architecture] to prevent this" works better than "Did you see their outage?" |
| **Competitor pricing increase** | 2-6 weeks | Customers talking about price hikes on social media or in industry forums are actively signaling. Lead with total cost of ownership, not just lower price. |
| **Competitor acquisition** | 4-8 weeks | Acquisitions create product uncertainty and roadmap changes. Customers worry about being deprioritized. |
| **Customer hiring while using a competitor** | 2-4 weeks | They are either switching or building in-house. Either way, they are evaluating alternatives. |
## What does a displacement outreach sequence look like?
Set up keyword monitoring for competitor name + negative terms (outage,
breach, pricing, layoffs, acquisition). Use Exa search, social monitoring,
and news scraping.
Match affected companies against your target account list and any accounts
known to use the competitor. CRM competitor fields and technographic data
help here.
For competitor-related signals, target the person most affected: the primary
user (for outages), the budget owner (for pricing), or the executive sponsor
(for strategic concerns).
Resolve verified work email via multi-provider waterfall.
Use competitor-specific battlecard messaging. Lead with your specific
advantage that addresses the competitor's weakness, not generic displacement
language.
> Subject: \[Function] reliability — how we built differently
>
> \[First Name],
>
> I know this week has been rough for teams running on \[Competitor].
>
> We built \[Product] with \[specific architecture decision] specifically to avoid single points of failure in \[function]. Our uptime over the last 12 months is \[stat]. Not because we are lucky — because of \[specific technical choice].
>
> If reliability is becoming a priority for your team, I can walk you through the architecture in 15 minutes.
> Subject: \[Function] costs going up?
>
> \[First Name],
>
> Been hearing from a few \[Competitor] customers about the pricing changes.
>
> We price \[differently — usage-based / flat-rate / per-seat with no overages]. For a team your size, the math usually works out to \[X]% less than what teams were paying on \[Competitor]'s new pricing.
>
> Happy to run the numbers if it would be useful.
## Frequently Asked Questions
### How do I know which accounts use a specific competitor?
Three sources: (1) CRM competitor fields from past deals, (2) technographic data from providers like Crustdata or BuiltWith, (3) social signals where employees mention the competitor's product. Combine all three for better coverage.
### How aggressive should displacement outreach be?
Don't be predatory. Reference your strengths, not their failures. "We built X to prevent Y" works. "Did you see their outage?" does not. Prospects who feel you are exploiting their vendor's problems will distrust you.
### How often should I run the competitive review?
Monthly data pull, quarterly deep review. The monthly pull catches trends early. The quarterly review is where you adjust battlecards, re-train reps, and update competitive positioning.
### What if a new competitor appears that I have never seen before?
Get a demo within 2 weeks. Build a preliminary battlecard with positioning, pricing (if public), and differentiators. Talk to any reps who encountered them. By the time a competitor shows up on 3+ deals, they are established, so treat first appearances seriously.
### Should I track competitor job postings too?
Yes. Competitor hiring patterns reveal strategic direction. If they are hiring heavily in a market you serve, expect more competition. If they are cutting in a segment, that is a displacement opportunity. Cross-reference with [Hiring Signals](/docs/plays/signal-hiring) for the full workflow.
***
**Related:** [Champion Tracking](/docs/plays/signal-champion-tracking) | [Company News & Social](/docs/plays/signal-company-news) | [Deal Risk & Signal Combos](/docs/plays/signal-deal-risk) | [Lead scoring and signal discovery](/docs/plays/play-qualify-lead-fit)