---
name: deal-drift
description: Catches committed deals that are quietly dying, diagnoses why the specific human pulled back, and prescribes the move to win them back. On invocation it offers three options... Watch (activity-based drift scan on your own CRM + Gmail, works for anyone), Diagnose (the per-human behavioral read + the prescribed move, powered by the GTM Heroes MCP), and Automate (run either one on a schedule). Trigger when the user says "watch my pipeline," "what deals are drifting," "which deals are stalling," "why is [deal] going quiet," "diagnose this deal," "scan my pipeline," "put my deal scan on autopilot," or "set up my Monday deal scan."
---

# Deal Drift

Your CRM tells you a deal is at risk. It cannot tell you why this specific human pulled back, or what to do about it, because it scores the deal's activity and has no model of the person. Deal Drift closes that gap. It watches your pipeline for the deals quietly going cold, then... with the GTM Heroes MCP connected... diagnoses the behavioral mismatch behind the silence and prescribes the move that re-engages the actual human.

Built by GTM Heroes. Lift it, drop it in your own Cowork, make it yours.

## The root menu

On invocation, unless the user's request already points at one, offer these three options:

```
What do you want to do?

  1. Watch      Scan your pipeline for deals quietly drifting. Run now or on a schedule.
                Needs: your CRM + Gmail. Works for anyone.

  2. Diagnose   Read WHY a specific deal went cold and get the move to win it back.
                Run now or on a schedule. Needs: the GTM Heroes MCP.

  3. Automate   Put Watch and/or Diagnose on autopilot... pick what runs, when,
                and where the results land.
```

Each of Watch and Diagnose ends by asking *run this once now, or put it on a schedule?* ... so automation is reachable from any path, not just option 3. Option 3 is the front door for someone who already knows they want it hands-off.

**The honest line, every time:** never claim a CRM "can't" flag an at-risk deal. Modern CRMs (Einstein, Breeze) score deal health off activity. Deal Drift's difference is the per-human diagnosis and the prescribed move, which activity data structurally cannot produce. Watch is roughly parity with what the CRM already does. Diagnose is the part it can't.

---

## Setup (one time)

**Watch needs:** y�ur CRM (HubSpot or Salesforce) + Gmail connected in Cowork (Settings -> Connectors).

**Diagnose adds:** the GTM Heroes MCP. Start a trial at gtmheroes.ai, grab your MCP access from the trial dashboard, add it as a connector in Cowork. One-time, a couple of minutes.

**Guardrail, baked into every option:** read-only on the CRM. This skill never edits, writes, or moves a deal. It reads and recommends.

---

## Option 1 ... Watch (your own connectors)

Scores deal health off activity and flags stalls. Useful, and honestly close to what Einstein and Breeze already do. It tells you *what* is slipping, not why.

Run this against the connected CRM + Gmail:

```
You are my deal-health watcher. Using my connected CRM and Gmail, read-only:

1. Pull my open deals in commit and best-case.
2. For each deal, compute:
   - days since the last inbound reply from the buyer
   - the trend in reply latency across the last 5 exchanges (speeding up or slowing down)
   - days since the last meeting
   - days in the current stage vs my average for that stage
3. Flag a deal as drifting if ANY of these are true:
   - reply latency is increasing
   - no inbound reply in 10+ days
   - stage age is more than 1.5x my average
4. Output a ranked watchlist: deal name, value, close date, the signals that
   tripped, and a one-line "why this looks stalled."

Do not modify any deal. Read and report only.
```

Output: a ranked stalled-deal watchlist. Then ask: *"Run this once, or put it on a schedule (Automate)? And want me to Diagnose the top one now? That needs the GTM Heroes MCP."*

---

## Option 2 ... Diagnose (+ GTM Heroes MCP)

The per-human read, plus the prescribed move. Diagnoses *why* this specific champion pulled back and hands you what to do about it.

Run this with the CRM, Gmail, and the GTM Heroes MCP connected:

```
You are my deal-drift diagnostician. Using my CRM, Gmail, and the GTM Heroes
MCP, read-only on my CRM:

1. Take the named deal (or the top stalled deal from a recent Watch run).
   Call list_deals to confirm its stage, value, close date, and company.
2. Identify the champion. Call list_individuals to check if they are already
   profiled. If not, call profile_individual with their LinkedIn URL to get
   their HBX Relationship Lens and communication style.
3. Call research_prospect on the company for account context, persona
   prioritization, and the likely objections.
4. Pull our engagement from my CRM activity + the Gmail thread. Read two things:
   the reply-latency trend, and the tonal shift in the champion's language
   (commitment language sliding to hedging language).
5. Diagnose the disconnect. Compare how I have been selling this deal against
   the champion's Lens. Name the specific mismatch and score how far our recent
   engagement has drifted from what that Lens rewards (a congruence read).
6. Prescribe the move. If the gap is proof/credibility, call generate_case_study
   for this individual, rewritten for their Lens. If the gap is economic, call
   generate_roi_calculator weighted to their role instead. Then draft how to
   frame the re-engagement so it matches how this human decides.
7. Output, in order: the named champion and their Lens, the disconnect in one
   sentence, the congruence drift read, the prescribed next move, and the
   generated asset (or a link to it).

Do not modify any deal and do not send anything. Read, diagnose, and recommend only.
```

Output: champion + Lens, the one-sentence disconnect, the congruence delta, the prescribed move, and the archetype-tuned proof asset, ready for the user to review and send themselves.

---

## Option 3 ... Automate (schedule Watch and/or Diagnose)

Turn either capability into a recurring task so Deal Drift works the pipeline for the user. Walk them through three choices:

**a. What runs**
- **Watch only** ... the activity scan. No MCP credits. The safe default.
- **Watch + auto-Diagnose the top drifter** ... runs Watch, then Diagnoses the single highest-priority drifting deal automatically. Uses GTM Heroes MCP credits each run... say so plainly before scheduling.
- **Diagnose a specific deal on a cadence** ... keep a behavioral read fresh on one critical deal. Uses MCP credits.

**b. When**
- Default Monday 7:00am in the user's timezone (cron `0 7 * * 1`). Offer to change day, time, or frequency.

**c. Where results land**
- A Cowork summary, an email to themselves, or a Slack post if connected. Ask once, then remember it.

Then create the scheduled task with the chosen scope, cadence, and delivery surface, and confirm in plain language:

> *"Done. Every Monday at 7am I'll scan your pipeline and surface what's drifting"* ... and, if they chose auto-Diagnose, *"...then diagnose the top one and tell you why it's slipping and the move to make. You'll get it as [surface]. This run uses MCP credits each week."*

If the user picked an MCP-powered automation but has not connected the GTM Heroes MCP yet, schedule the Watch portion now and tell them Diagnose will switch on the moment they connect it.

---

## Lift and shift

This skill is built to be portable. Anyone can drop it into their own Cowork:

- **Watch** runs on your own CRM + Gmail. No GTM Heroes account required. This is the free floor, and it is genuinely useful on its own.
- **Diagnose** lights up when you connect the GTM Heroes MCP (trial at gtmheroes.ai). That is where the per-human behavioral layer comes from... the Relationship Lens, the congruence read, the archetype-tuned proof asset. The moat is the MCP and the behavioral model, not the prompt text, which is why the whole skill is published in the open.
- **Automate** works with either... schedule the free Watch, or the MCP-powered Diagnose, your call.

If you are reading this because you watched MCP Mondays Episode 1: this is the thing I built on screen. It is yours. Run Watch on your own pipeline today. Connect the MCP when you want to know *why*. Automate it when you want it to run without you.
