opsmarshal
Workflow 02 — Pipeline Creation

Account Intelligence & Territory Carving

Research agents maintain a living dossier per account — firmographics, initiatives, stack, org changes — score ICP fit against a versioned rubric, and propose territory rebalances that RevOps signs off as diffs. Territories stop being an annual spreadsheet war.

At a glance

Account Intelligence & Territory Carving is a governed agent workflow that maintains a per-account dossier, scores ICP fit against a versioned rubric, and proposes territory rebalances as diffs a RevOps owner signs off rather than an annual spreadsheet exercise. It is one of fifteen workflows in the Enterprise GTM Agent Stack, an Opsmarshal series on AI enablement and agentic workflows.

Owned by
RevOps
Writes back to
CRM account, Territory object, Audit log
Held to
≥ 95% — Citation validity
Gate
Permission → Evidence → Approval → Audit
Writes to: CRM account + territory objectApproval: RevOps on every rebalanceRefresh: continuous, cited
Business Pain

Why this exists

The status quo

Territory planning happens once a year on stale data. By Q2, half the “A-tier” accounts have reorged, churned a champion, or pivoted — and reps prospect against a map of last year's market.

What this workflow changes

Dossiers refresh continuously with cited evidence. Fit scores recompute when the underlying facts change, and rebalance proposals arrive as diffs with rationale — RevOps approves the diff, not a 4,000-row spreadsheet.

Architecture

Reference architecture

Evidence Sources
Company web + filingsinitiatives, hiring, expansions
Enrichment vendorsfirmographic + technographic
CRM historyengagement, past opportunities
Agent Layer
Research Agentassembles dossiers; every claim carries a citation + fetch date
Fit Scorerversioned ICP rubric; hysteresis before proposing moves
Territory Differproposes map changes as reviewable diffs
Governance
Gate: permission → evidence → approval → auditdossier writes auto-pass · every territory change requires RevOps approval · rubric changes are versioned config
Systems of Record
CRM accountdossier fields + fit score + lineage
Territory objectmap + change history
Audit logevery score change and rebalance verdict
DecisionChoiceRationale
Dossiers carry citationsEvery claim links to its source with a fetch dateAn uncited dossier is a hallucination risk wearing a suit. Citations make dossiers auditable and let reps verify a “fact” before quoting it to a prospect.
Rebalances ship as diffsPropose changes; never rewrite the mapWholesale re-carving destroys rep trust and pipeline continuity. Diffs with rationale keep every change explainable and reversible.
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.

Territory Rebalance Proposer

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.

Account Intelligence & Territory Carving — Ops Console

Owner: RevOps

Daily monitors

  • Dossier refresh failures — accounts running on stale evidence
  • Fit-score drift — any score moving >20 pts gets its trigger verified

Weekly reviews

  • Citation spot-check — 10 dossiers audited for source validity
  • Rebalance queue — proposals reviewed, approved, or rejected with reasons

Alert thresholds → who gets paged

  • Unapproved rubric version change → sev-1, RevOps lead
  • Enrichment source outage → RevOps within 1 hour

Manual controls

  • Territory write freeze during fiscal planning windows
  • Per-account pin — exclude from rebalancing entirely
  • Kill switch — halts all writes; dossiers keep refreshing read-only
Eval Metrics

What this workflow is held to

≥ 95%
Citation validity
sampled dossier claims that check out against their source
< 5%
Territory dispute rate
rep-raised disputes per planning cycle
100%
Rebalance approvals logged
no map change without a named approver
Failure Modes

How it breaks, and what catches it

Zombie facts

An outdated initiative stays in the dossier after the source page dies, and a rep leads a call with it. Mitigation: Citations carry fetch dates and class-specific TTLs; expired claims are re-verified or dropped, never silently kept.

Score churn

Volatile signals make fit scores oscillate, thrashing territory proposals weekly. Mitigation: Hysteresis — rebalance proposals require a sustained score change across two refresh cycles before they're raised.

Press-release bias

The agent over-weights PR language and inflates fit for loud companies. Mitigation: Rubric weights favor verifiable operational signals — headcount, stack, filings — over announcement volume.

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