Get a structured account read straight from your CRM.

“Is this deal real, or is the stage just telling me what the rep wants to hear?”

A sixty-second summary, a multi-source activity audit, a qualification-vs-stage gap check, and an 8-state deal-risk verdict.

CONVERT MORE PIPELINEADVANCEDCRMPRODUCT-ANALYTICS TOOLMEETING OR MESSAGING TOOL✓ APPROVED 4/4
EXAMPLE PROMPTS
>Analyze [account] from the CRM. What is the current state and last real touch?
>Is this opp healthy, or did the rep skip the qualification work the stage claims?
>Do a deal autopsy on this closed-lost [pastes opportunity]
ABOUT THIS SKILL

What this skill does

Reads a single account or deal out of your CRM and gives a straight, structured read: current state, when it was last actually touched, whether the rep did the qualification work the stage claims, and one risk verdict on the deal. It is the sixty-second account summary that tells you what to do next, and the "is the rep BS-ing this deal" check that a single CRM field misses.

Inputs

  • Works today with: a CRM export for the account or opp, with stage, amount, close date, last-activity dates, the qualification fields, and the contacts on the record. Paste it or upload a CSV.
  • More powerful connected to a CRM: it reads all of the above automatically, and audits activity across every source, not one field.
  • Sharper with an enrichment tool: adds firmographic and buying-committee context. Deepline is one generic example.
  • Sharper with a meeting or email tool: tightens the last-touch and champion-drop checks.

How it works

  1. 1
    Multi-source activity check

    Days dark is today minus the most recent touch across ALL your activity sources: the account record, the opp record, completed tasks, and logged events. Never a single field. This solves the classic CRM bug where the opp-level last-activity date is blank because reps log emails and meetings at the account or contact level, so a live deal gets falsely flagged as dead. The skill takes the max across sources and shows the dates.

  2. 2
    Account summary (one screen)

    Current state, owner, value, days in current stage, last real activity, and the single risk flag. The read a rep or leader needs before walking into a meeting, on one screen.

  3. 3
    Qualification-vs-stage gap

    If a deal claims a late stage but the qualification fields for that stage are empty, flag it and name the exact field that is missing. This is the sandbagging detector. It is only as good as the fields you map.

  4. 4
    Deal-risk verdict

    One verdict per open opp: HEALTHY, MOMENTUM, AT_RISK, SLIP_RISK, STUCK, STALE, CHAMPION_DROP, GHOST. GHOST needs every activity source cold and the dates to prove it. CHAMPION_DROP means the main contact has gone quiet. AT_RISK means single-threaded.

  5. 5
    Account context

    Pull the firmographic and buying-committee context that lives on the record: decision maker, tech stack, hiring or expansion signals. An optional enrichment tool fills what the CRM does not carry.

Output format

ACME CORP · Customer · CSM: owner

Verdict: REACH_OUT (renewal-defence read)
  Last activity: TODAY (account level) - 6 email replies + meeting in 1h
  Days in current stage: 12d (late stage)
  Qualification: 4/4 complete - problems, leverage, decision dynamics, next steps
  Fit-score check: score looks low, but real usage present -> false negative

The qualification read
  PROBLEMS: inbox plateau, no signal on adoption depth
  LEVERAGE: multi-team rollout across Sales, RevOps, CS
  DECISION DYNAMICS: CFO signs, RevOps lead champions
  NEXT STEPS: finalize commercial terms by the 15th

Tech stack: email, CRM, an outbound tool
Decision maker: the CFO
Signal: hiring 14 reps at this account - expansion

Next move: the meeting today. Late stage means commercial close is the gate.

Tips

  • No GHOST verdict without showing the activity dates, across every source, that prove it.
  • Qualification gaps surface field by field, named, never "incomplete."
  • The activity check reads every source, never one field. A single-field read systematically misses real activity.
  • Never report a field the export does not contain. A missing field is a prompt, not a guess.
RELATED SKILLS
ALL CONVERT MORE PIPELINE SKILLS →