Carlos EscasainCommercial Systems & Process Architect
ENES

Operating Model & Process Design / 04 · Signal → obligation → action

Designing account management as a performance, development and recovery system

A fictional, composite case that joins three things usually run apart—account plans, performance dashboards and recovery plans—into one accountable loop.

Fictional scenario10 min readUpdated 29 Sep 2026
Fictional scenario

Independently created. Contains no employer or client implementation detail, internal names or figures.

The case in brief

Current reality

Account plans, performance dashboards and recovery actions lived in three places; underperforming accounts were visible every month, and nothing was obliged to happen next.

What must become true

Every account has a plan against its potential; every relevant deviation creates an owned obligation; every obligation ends in a recorded outcome—recovered, escalated or accepted.

Design question

What must a performance signal change—in attention, ownership and action—for it to have operational value?

01Reality

What the organization actually did.

A fictional B2B manufacturer manages several hundred established accounts against annual targets. Sales, orders and invoices are available every month and the analytics are sound. But account plans are yearly slides, performance reviews discuss totals, and recovery depends on which manager happens to notice.

  • Account plans were written once a year and never checked against actual performance
  • Each manager defined “at risk” differently
  • Monthly meetings discussed totals, not accounts
  • Recovery plans lived in slides, without owners or dates
  • Accounts dropped off the watch list without anyone deciding they had recovered
  • Lost volume, lost share and no-sale situations were treated as one problem

02One process?

What made one process insufficient?

Existing customers do not all need the same management. What changed the obligation:

  1. Trajectory against targetAhead, behind but stable, or declining?
  2. Growth potentialHow much more could the account buy—and where?
  3. Cause of the deviationPrice, service, competition, customer demand—or our own activity?
  4. Volume or shareIs the customer buying less, or buying elsewhere?
  5. No-sale situationsA lost account, a paused one—or a data problem?
  6. Relationship healthAre contacts, service and activity what the plan assumes?
  7. Open opportunitiesIs there pipeline to close the gap?

The pointA performance signal has no operational value until it changes somebody’s attention, decision or action.

03Segmentation

How the reality was segmented

Performance states are set by rule from the data—not by opinion. The state decides the obligation.

FromEvery managed account, every period

  1. On TrackThe plan runs; no extra obligation.
  2. UnderperformingBelow target, trend stable: the owner diagnoses.
  3. At RiskBelow target and declining: a recovery plan is mandatory.
  4. No SaleNo orders where a target exists: reviewed within the cycle.

Design decision

Run account management, performance management and recovery as one loop, and give each performance state an explicit owner, obligation, cadence, escalation and exit rule.

04Target model

Target operating model

The loop the account manager and the sales manager run together, every period.

  1. Understand the account
    Owner
    Account manager
    Exit criterion
    Potential, plan and relationship map are current
  2. Measure
    Owner
    Data platform (automated)
    Exit criterion
    Sales, orders and trend against target published for the period
  3. Detect
    Owner
    Rule
    Exit criterion
    State assigned; deviations and opportunities flagged
  4. Diagnose
    Owner
    Account manager
    Exit criterion
    Cause recorded from a shared list
  5. Decide
    Owner
    Sales manager
    Exit criterion
    Response chosen: act, escalate or accept
  6. Commit
    Owner
    Account manager
    Exit criterion
    Actions with owners and due dates
  7. Act
    Owner
    Action owners
    Exit criterion
    Actions done—or visibly overdue
  8. Follow up
    Owner
    Sales manager
    Exit criterion
    Plan reviewed at the cadence of its state
  9. Reassess
    Owner
    Rule and sales manager
    Exit criterion
    State recomputed; plan closed as recovered, escalated or accepted

05What changes by path · Signal → obligation → action

States that change what somebody must do

The labels matter only because each state changes attention, owner, obligation, cadence, escalation and exit.

  1. Understand
  2. Measure
  3. Detect
  4. Diagnose
  5. Decide
  6. Commit
  7. Act
  8. Follow up
  9. Reassess

Performance states

Performance states
StateAttentionOwnerObligationCadenceEscalationExit
On TrackNormalAccount managerRun the account planQuarterlyNoneFalls outside tolerance
UnderperformingRaisedAccount managerDiagnose the cause; a plan is optionalMonthlyTwo periods without improvement → At RiskBack within tolerance for a period
At RiskHighAccount manager and sales managerRecovery plan mandatoryMonthly, plan by planPlan overdue → regional sales leaderTwo periods back on trajectory—or an accepted loss
No SaleImmediateSales managerReviewed within the cycle: a plan or a documented exitMonthly until resolvedNo decision in the cycle → regional sales leaderOrders resume, or the account is exited with a reason

A recovery plan is an accountability mechanism, not a CRM object

  1. Signal
  2. Owner
  3. Diagnosis
  4. Commitment
  5. Actions
  6. Due dates
  7. Review
  8. Outcome

It closes only with a decision: recovered, escalated or accepted.

Thresholds are illustrative. What is designed is that no state is only a colour.

06Exceptions and return paths

The happy path is never the whole process.

When
WhenThenOwnerReturns to
The data is wrong—a no-sale caused by an invoicing change or merged accountsState suspended; a data correction is raised with its ownerSales operationsMeasure
The cause lies outside sales: service, quality or deliveryEscalated to the owning function; the plan records the dependencySales managerCommit
Actions are overdueVisible in the review; escalated at the second missSales managerFollow up
The loss is structural—the customer leaves a marketAccepted loss decided and recorded; targets revised through planningRegional sales leaderClosed, as accepted
An account recovers without a planThe state updates by rule; the review notes the causeRuleReassess

07Supporting capabilities and system encoding

Only now, the technology.

Systems and partiesCRMERPData platformPlanning

Supporting capabilities

  • Data platformComputes performance and states from ERP transactions and targets
  • CRMAccount plans, diagnoses, commitments and actions—where the account manager works
  • OrchestrationPublishes each period’s states once, reliably—see the monthly performance orchestrator
  • NotificationsTell owners when a state changes or a plan is overdue

How the system encodes the model

  1. Operating decision: States set by rule

    System response: States computed on the data platform and written back to the account

  2. Operating decision: Obligations by state

    System response: A recovery plan required for At Risk; review tasks at each state’s cadence

  3. Operating decision: Diagnosis from a shared list

    System response: Cause codes on the plan

  4. Operating decision: Decisions that close a plan

    System response: Plan outcome—recovered, escalated or accepted—with the approver

  5. Operating decision: One review per period

    System response: Review lists by state and owner, not a dashboard of totals

08Measurement

What is measured—and what it triggers.

Metric
MetricWhyOwnerCadenceTriggers
Accounts by state, over timeShows whether the portfolio is getting healthierSales leadershipMonthlyRebalance attention and capacity
Plans reviewed on timeA plan without follow-up is a slideSales managersMonthlyEscalate overdue plans
Recovery rate by causeShows which actions actually workSales operationsQuarterlyUpdate the action playbook
Time from signal to planRecovery slows when diagnosis waitsSales managersMonthlyTighten the review cycle

09The second layer

Questions that change the design.

Classification

  1. Who owns the state—and who may override it?
  2. One bad month or a trend: what triggers intervention?
  3. Is a no-sale a sales problem, a customer event or a data problem?

Obligation

  1. When is a recovery plan mandatory?
  2. Which actions are expected, and who decides they are enough?
  3. What happens when nobody acts?

Closure

  1. When is an account recovered?
  2. Who may accept a loss?
  3. How does development against potential sit beside recovery against target?

10Decisions & outputs

What the work produces.

  1. 01Account management loop
  2. 02Performance state model
  3. 03Obligations by state
  4. 04Recovery plan mechanism
  5. 05Review cadence and escalation
  6. 06KPI-to-action linkage
Disciplines involvedRevenue OperationsProcess ArchitectureData & Integrations