> ## 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

> Qualify competitor-related account evidence before proposing a displacement action.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/signal-competitive-intel.md)

> [!NOTE]
>
> Create a factual competitive review from dated, attributable evidence.

Use this page after [competitive and ad
intelligence](https://deepline.com/docs/plays/play-ad-intelligence.md) has collected competitor evidence.
It owns the narrower decision: whether a dated competitor event or public
discussion is relevant to a particular account. It does not own competitor
research, battlecards, or broad positioning analysis.

## Required evidence

* A dated source URL for the competitor event, complaint, or public discussion.
* Evidence that the target account is affected or is plausibly evaluating the
  competitor. do not assume every account is affected.
* A relevant product or operational issue you can substantiate.
* Account fit, current owner, active-opportunity state, and suppression state.
* One proposed action with the evidence attached.

## Choose the response

| Evidence result | Decision |
| - | - |
| Dated event and account-specific impact are both supported | Draft a factual, reviewed response angle. |
| Competitor event without account-level relevance | Keep it in a market or battlecard brief, not an account campaign. |
| Account is an existing customer or active opportunity | Route the evidence to the account or deal owner. |
| Weak source, outdated event, or unsupported impact claim | Take no outreach action. |

## Prepare the review file

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Review target-accounts.csv for [competitor] evidence. For each
candidate, return the dated source URL, account-level relevance, supported
problem, owner or suppression check, and one proposed action. Keep market-only
evidence separate.
```

## Keep the message factual

Lead with a supported strength or a useful question about the account's
observed problem. Do not state that a competitor event affected the account
unless the evidence supports it, and do not use a competitor failure as a
reason to pressure a buyer. Keep market research and account actions separate.

***

**Related:** [Champion Tracking](https://deepline.com/docs/plays/signal-champion-tracking.md) | [Company News & Social](https://deepline.com/docs/plays/signal-company-news.md) | [Deal Risk & Signal Combos](https://deepline.com/docs/plays/signal-deal-risk.md) | [Lead scoring and signal discovery](https://deepline.com/docs/plays/play-qualify-lead-fit.md)

## Verify this task

Preserve the source and account match. Separate observed competitor activity from inferred strategy or performance.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.