> ## Documentation Index
> Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Competitive Intelligence From Your Own Data

Most competitive intelligence is third-party research or anecdote — analyst reports, a slide someone made last quarter, a hallway conversation about why you lost a deal. The most accurate signal you have is sitting untouched: what your customers and prospects actually say about competitors, in call transcripts nobody has time to read. Competitive Intelligence From Your Own Data surfaces every competitive mention across your conversations — which competitors come up in which deals, what objections they raise, and how your team responds — in one question.

## Data Sources

| Category  | Required | Recommended |
| :-------- | :------- | :---------- |
| Calls     | ✓        |             |
| CRM       |          | ✓           |
| Email     |          | ✓           |
| Messaging |          | ✓           |

**Starter** (required only): every competitor mention pulled from call transcripts, tied to the deals and accounts where they came up.

**Full** (required + recommended): the same, plus competitive signals from email threads and Slack — where a competitor is named in writing, where a rep flags a competitive threat, and the full back-and-forth around an objection. Same workflow, significantly more depth.

See the Customer Context Graph for how each source feeds the analysis.

## Build in Claude or ChatGPT

Run the analysis right where you work. Open Claude or ChatGPT with the Clearskies MCP connected, and the readout appears in your conversation.

### The Prompt

Paste this (or modify to your needs). Replace the competitor name with your own.

```text theme={null}
Using the Clearskies Context Graph, give me a competitive readout on
Northwind.

Cover:
- Which deals and accounts they came up in
- The objections and comparisons buyers raise
- How our team responds, and which responses land
- Any pattern in where we win and lose against them
- The one thing I should change about how we handle them

Be direct. Quote the customer's actual words where they're sharper than a paraphrase.
```

### What you get back

A readout generated from your data, structured like this:

```text theme={null}
Competitive Readout — Northwind

Where they come up
Named in 14 deals over the last 90 days. Most often in mid-market
evals where the buyer already runs a point solution and is weighing
consolidation.

Common objections / comparisons
• "Northwind is cheaper for just attribution" — raised in 6 deals.
• "We already have Northwind for reporting" — incumbency, 4 deals.
• Concern that switching means re-training the team — 3 deals.

How our team responds
Top reps reframe from price to scope: we replace 3 tools, not 1.
Daniel's May 8 call with Acme is the cleanest example — he walked
through the consolidation math and the objection dropped.

Where we win / lose
Win: deals where consolidation and a single source of truth matter.
Lose: deals scoped narrowly to attribution where price leads.

The one thing
The "already have Northwind" objection is our most common and our
least consistently handled. Worth a shared response in enablement.
```

Refine the prompt to fit how your team tracks competition.

### Make it yours

* Add `Compare this quarter to last` to surface whether a competitor is gaining or fading in your deals.
* Add `Focus only on deals we lost` to turn the readout into a loss post-mortem.
* Add `Draft a one-page battlecard from what you found` to make it usable in the field.

### The Skill (Claude)

The `clearskies:win-loss` skill in the Clearskies plugin for Claude includes competitive analysis as part of its deal-pattern work — which competitors you see most, which you lose to, and what winning reps do differently — all from your Context Graph. For continuous single-competitor tracking, the same workflow can be packaged as a dedicated competitive skill for your team.

#### Trigger phrases

* "Where does \[competitor] come up in our deals"
* "How do we handle the \[competitor] objection"
* "Competitive readout on \[competitor]"

#### Customize it for your team

* Match the readout to how your team tracks competition — by competitor, by segment, or by deal stage
* Add the competitive signals your team cares about
* Layer in battlecard, post-mortem, or trend framing depending on context

<Tip>
  Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow.
</Tip>

## The Plugin

**Ready to make this part of your team's workflow?** We'll set up the Clearskies plugin with you — Claude skills tailored to how your team works.

[**Book 15 minutes →**](https://calendly.com/pouyan/new-meeting)

## Next steps

1. [Sign in to Clearskies](https://app.clearskies.cc/)
2. Connect your data sources
3. Get your [Clearskies MCP server](https://www.clearskies.cc/docs/building-with-clearskies/mcp-server) and try with [Claude](https://www.clearskies.cc/claude) or [ChatGPT](https://www.clearskies.cc/chatgpt)