The suite
Ten agents
Seven run on your CRM alone and install in minutes. Three get materially better when call
recordings are connected — and all three still produce their CRM-side findings without them,
clearly marked as partial rather than clean.
CRM Hygiene
/crm-hygiene:run
CRM onlyRead-onlyStart here
Audits whether the data underneath every one of your reports can be trusted,
and scores it as a single Hygiene Index you can move quarter over quarter.
Typical findings
- Duplicate accounts and contacts, clustered by domain and normalised company name
- Dead custom fields — the hundreds sitting under 5% fill
- Open pipeline owned by people who have left the company
- Open opportunities whose close date is already in the past
- Picklist rot: values nobody has used in a year, and near-duplicates
Pipeline Inspection
/pipeline-inspection:run
CRM onlyRead-onlyWeekly
Not "what will we close" — which deals are violating your own rules.
A ranked call list for a manager's Monday, measured against your team's real medians rather
than someone else's benchmark.
Typical findings
- Deals past twice the measured median days-in-stage — with the medians shown
- Close dates pushed three or more times, counted from field history
- Six-figure deals with a single contact on them
- Close dates clustered on the last day of the quarter
- Open deals whose close date has already passed, totalled in dollars
Forecast Agent
/forecast-agent:run
CRM onlyRead-onlyAudit-first
Runs in two modes, and the audit is the default. Because the hard part
was never the forecast — it's that close dates are fiction and stages aren't exit-criteria
based, so the forecast was never going to hold.
Typical findings
- A Forecast Integrity Score, with the formula shown
- Stage conversion measured on stage entered, not current stage
- Deals committed in two consecutive quarters
- Worst / likely / best, and the gap versus the rep-called commit
- The real slip distribution behind the worst case
Stage Architect
/stage-architect:run
CRM onlyRead-only
Derives what your stages actually mean from your own closed history,
and puts it next to what your team believes they mean. The gap is the deliverable.
Typical findings
- Adjacent stages with indistinguishable conversion — one stage wearing two hats
- Stages skipped by most deals, which are therefore not stages
- Zero-dwell stages that exist for process compliance only
- Time-in-stage at median, p75 and p90, not a mean a few zombies destroyed
- Proposed exit criteria that are buyer-verifiable, not rep-asserted
Lead Source of Truth
/lead-source:run
CRM onlyRead-only
Deliberately not multi-touch attribution — that needs your MAP and ad
platforms and never installs cleanly. This measures whether the source data feeding your
channel report can be trusted at all.
Typical findings
- Null / "Other" / "Unknown" rate, broken down by how the record was created
- Near-duplicate values — "Paid Search", "PPC", "SEM", "Google Ads"
- Whether source survives the lead-to-opportunity conversion, measured per hop
- UTMs that disagree with the source field, or get overwritten on later form fills
- Source values carrying real volume and zero closed-won
System Map
/system-map:run
CRM onlyRead-onlyCheapest run
Inventories what is actually wired into your CRM and contrasts it with
what your team thinks is wired in. The cheapest run in the suite and usually the most
alarming.
Typical findings
- Two or more automations writing the same field on the same object
- Automation and connected apps owned by people who left
- Integration users still holding write access and no longer used
- Flows, triggers, workflow rules and scheduled jobs, with last-modified dates
- The third-party tools genuinely connected, versus the ones you listed
Executive Reporting
/executive-reporting:run
CRM onlyRead-onlyBoard-facing
Builds the pack leadership actually runs the business on — and audits whether
your CRM can support it before it publishes a number. Every metric lands against a goal;
every metric opens into the rows underneath it.
Typical findings
- A stage that isn't being stamped — conversion into it computes above 100%, so the rate is withheld rather than printed
- The gap between the conversion rate you quote and the one your data supports
- Cohorts too young to report, suppressed instead of flattering the quarter
- Bookings concentrated in one rep, or a book concentrated in ten accounts
- The share of bookings closing with no channel attached at all
Sales Coach
/sales-coach:run
CallsRead-onlyManager-first
Coaches against your qualification framework — MEDDPICC, MEDDIC, BANT,
SPICED, Challenger or your own. The primary output is one team pattern report for the manager,
because reps ignore per-call feedback and managers act on patterns.
Typical findings
- The dimension your team fails most often, with the specific calls that show it
- Every score carrying a verbatim quote and a timestamp — no evidence, no score
- Tenure-aware coaching: ramping reps judged differently from tenured ones
- Talk ratio, longest monologue, question rate, next-step-set rate
- Framework gaps correlated against the deals that later slipped
Customer Health
/customer-health:run
Calls optionalRead-only
Scores every account twice — sentiment and commercial risk — because
they diverge, and the divergence is the point. The account that churns is very often the happy
one with an unsigned renewal forty days out.
Typical findings
- The happy-but-unsigned quadrant, called out explicitly
- Champion departures detected from contact status and transcript absence
- Renewals inside the notice window with no renewal opportunity open
- Meeting-attendance decay — the senior people quietly stopping
- A kickoff baseline captured at setup, so later runs can prove movement
Meeting to CRM
/meeting-to-crm:run
CallsProposes writesDaily
Reads the call and proposes the CRM updates the rep would have typed, as an
approvable diff. The boring one — which is exactly why it's the one that gets used every day.
Dry-run by default; it never writes on the turn it proposes.
What it proposes
- Next step and next-step date, from what was actually agreed on the call
- Your qualification-framework fields, mapped to your real field API names
- New stakeholders heard on the call, as contact roles
- Competitor mentions, pain, decision process and timeline
- Every proposal carries the quote and timestamp that justifies it