opsmarshal
Workflow 05 — Pipeline Creation

Champion & Relationship Graph Tracker

Watches the people, not just the accounts: job changes, promotions, single-threaded deals, and dark spots in the buying committee — and drafts the re-engagement play the moment a champion lands somewhere new.

At a glance

The Champion & Relationship Graph Tracker watches people rather than accounts — job changes, promotions, single-threaded deals and dark spots in the buying committee — and drafts a re-engagement play the moment a champion moves. It is one of fifteen workflows in the Enterprise GTM Agent Stack, an Opsmarshal series on AI enablement and agentic workflows.

Owned by
Sales Ops
Writes back to
CRM contacts, Opportunity flags, Audit log
Held to
≥ 80% — Committee coverage
Gate
Permission → Evidence → Approval → Audit
Writes to: CRM contacts + opportunity flagsApproval: rep before any outreachGraph: committee coverage per deal
Business Pain

Why this exists

The status quo

Champions change jobs mid-deal and the CRM finds out at the loss review. Multithreading gaps are invisible until the one contact goes silent. Relationship risk is the most predictive deal signal nobody instruments.

What this workflow changes

The graph makes relationship risk a first-class field: thread count, role coverage, champion stability on every deal. A champion move triggers two drafted plays — protect the old deal, open the new door — both waiting on rep approval.

Architecture

Reference architecture

Signal Sources
Job-change monitorstwo-source verification before action
CRM contact rolesbuying committee mapping
Engagement patternswho's active, who went dark
Agent Layer
Graph Buildermaintains the relationship map per account and deal
Risk Detectorsingle-thread flags, champion-move detection, dark-committee gaps
Play Drafterprotect + pursue drafts from the approved play library
Governance
Gate: permission → evidence → approval → audittracking limited to a legal-reviewed public-professional signal allowlist · every play requires rep approval · every lookup logged
Systems of Record
CRM contactsroles, moves, verification status
Opportunity flagsthread count + relationship risk
Audit logsignals used, plays drafted, approvals
DecisionChoiceRationale
Two-source verificationJob changes confirmed across two sources before any actionFalse job-change signals trigger embarrassing outreach. Two-source verification trades a day of latency for credibility.
Plays draft, never sendRelationship moves are always human-approvedThe agent's job is watching and drafting. The rep's job is the relationship. The gate keeps that boundary structural, not aspirational.
Live Demo

Run a scenario through the gate

Three curated scenarios — one that passes, one that flags for a human, one that the gate blocks. Watch the verdict, the evidence rows, and the audit log.

Relationship Risk Detector

Governance audit log

[ready] agent idle — pick a scenario
Operator Control Panel

Someone has to run this thing

Agents don't remove operators — they change what operators watch. Console spec: who owns it, what they check, what pages them, and how they pull the plug.

Champion & Relationship Graph Tracker — Ops Console

Owner: Sales Ops

Daily monitors

  • Unverified job-change queue — pending second-source confirmation
  • Single-threaded deals above $50k, ranked by stage

Weekly reviews

  • Graph coverage — % of active deals with a mapped buying committee
  • Play acceptance rate — drafts reps actually used, by play type

Alert thresholds → who gets paged

  • Champion departure on a commit-stage deal → rep + manager, same hour
  • Graph source API failure → Sales Ops

Manual controls

  • Per-contact do-not-track — legal or personal sensitivity
  • Play library editor — Sales Ops owned, versioned
  • Kill switch — detection continues; all drafting and flag write-backs pause
Eval Metrics

What this workflow is held to

≥ 80%
Committee coverage
active deals with a mapped buying committee
< 24h
Champion-move detection lag
event to verified flag on the deal
≥ 60%
Play acceptance
drafted plays reps approve and use
Failure Modes

How it breaks, and what catches it

Privacy overreach

Tracking drifts from professional signals into territory that damages trust if surfaced. Mitigation: A hard signal allowlist — public professional data only — reviewed by legal, with every lookup logged.

Graph rot

Contacts change roles internally and the map silently misleads deal strategy. Mitigation: Engagement-pattern anomaly detection prompts re-verification of stale nodes.

Alert flooding

Every profile update pings reps until they mute the whole system. Mitigation: Alerts are ranked and budgeted per rep per week; below-threshold changes batch into a digest.

Opsmarshal builds workflows like this one inside client stacks — see AI enablement and agentic workflows and revenue operations, or book a call to walk through your own.

opsmarshal

Revenue Operations and AI Agentic Workflows for B2B companies in transformation. We build the machine. You run the company.

Services

Company

© 2026 Opsmarshal. All rights reserved. Privacy  ·  Terms