RevOps case / 06 · Forums, evidence & adoption signals

Running commercial management cadence from the CRM

The CRM became valuable the month the reviews started running from it.

The case in brief

Current reality

Sellers are asked to keep the CRM current, but every management meeting runs from spreadsheets—so the system is maintained for nobody.

What must become true

Every recurring forum has a purpose, participants, evidence, decision rights and outputs—and runs from one CRM view built for it. Adoption is measured by whether the forums actually use the system.

Design question

Which forums run the business, what evidence does each use—and how do we know they run from the system?

01The reality · current state

How the business is steered today.

A commercial organization rolled out a CRM with good stage definitions and dashboards. Usage dropped after six months. Managers still prepare weekly reviews by exporting data into slides, monthly performance meetings discuss regional totals, and nobody records what was decided. Sellers conclude that updating the CRM changes nothing.

  • Weekly reviews are prepared by exporting CRM data into slides
  • Monthly meetings discuss totals, not accounts or plans
  • Decisions made in reviews are not recorded anywhere
  • Sellers update the CRM on the day before the review, if at all
  • Dashboards exist for every forum, but nobody knows which one is used
  • Adoption is measured by logins

02Operating loop

Each step with what happens, who owns it and how often.

Systems and partiesCRMData platformCollaboration tools

  1. 01Daily

    Sellers work from their home view: next steps due, new leads, overdue actions.

    Owner
    Sellers
    Cadence
    Daily
  2. 02Weekly

    Pipeline review from the team view: stage changes, stale deals, commit movement.

    Owner
    Sales manager
    Cadence
    Weekly
  3. 03Monthly

    Performance and recovery review, account by account and plan by plan.

    Owner
    Sales managers; sales operations
    Cadence
    Monthly
  4. 04Quarterly

    Targets, motions and coverage goals reviewed from the same definitions.

    Owner
    Sales leadership
    Cadence
    Quarterly
  5. 05Adoption

    Signals that show whether each forum runs from the system—reviewed like any other KPI.

    Owner
    Sales operations
    Cadence
    Monthly

The outcome of the last step changes the first one next period.

03Key dimension · Forums, evidence & adoption signals

Four forums, each with evidence and decision rights

A forum is designed like a process step: who attends, what they look at, what they may decide and what they produce.

Select a forum to see its rhythm, evidence, decisions and output.

DailyDaily execution

Participants
Sellers; inside sales
Evidence
Next steps due; new leads; overdue actions
Decides
What to work on today
Produces
Updated next steps; logged activity

WeeklyPipeline review

Participants
Sales manager and team
Evidence
Stage changes; stale deals; commit movement; coverage
Decides
Advance, push, requalify or close specific deals
Produces
Manager forecast call; actions per deal

MonthlyPerformance review

Participants
Sales managers; sales operations
Evidence
Segments; open recovery plans; overdue actions
Decides
Accept, challenge, escalate or close plans
Produces
Plan outcomes; escalations

QuarterlyTarget review

Participants
Sales leadership; finance
Evidence
Attainment; forecast accuracy; motion performance
Decides
Reprioritize; approve target revisions
Produces
Updated plan; new target version

Compare all 4 in one table
Forums: rhythm, participants, evidence, decisions and output
ForumParticipantsEvidenceDecidesProduces
Daily executionDailySellers; inside salesNext steps due; new leads; overdue actionsWhat to work on todayUpdated next steps; logged activity
Pipeline reviewWeeklySales manager and teamStage changes; stale deals; commit movement; coverageAdvance, push, requalify or close specific dealsManager forecast call; actions per deal
Performance reviewMonthlySales managers; sales operationsSegments; open recovery plans; overdue actionsAccept, challenge, escalate or close plansPlan outcomes; escalations
Target reviewQuarterlySales leadership; financeAttainment; forecast accuracy; motion performanceReprioritize; approve target revisionsUpdated plan; new target version

Adoption signals, not login counts

  • Reviews run from the system

    Share of forums opened from the forum view, not an export

    ResponseRemove the slide template; coach the manager
  • Next-step discipline

    Open opportunities with a dated next step

    ResponseDiscuss in the weekly review, deal by deal
  • Freshness before the forum

    Deals updated in the week, not the hour before the review

    ResponseManager coaching, not a reminder email
  • Decisions recorded

    Plans and deals with a recorded review outcome

    ResponseMake the outcome a required step in the view

Logins measure access. These signals measure whether the business is run from the system—which is the only adoption that matters.

04KPI contracts

Every measure with an owner, a cadence and an action.

KPI contracts: definition, owner, cadence and required action
MetricDefinitionOwnerCadenceAction
Forum run from systemForums held from their system view ÷ forums heldSales operationsMonthlyCoach the forum owner; retire parallel reports
Next-step coverageOpen opportunities with a dated, future next stepSales managersWeeklyDeal-by-deal follow-up in the pipeline review
Recorded review outcomesPlans reviewed this month with a recorded outcomeSales managersMonthlyComplete in the forum, not afterwards

05Accountability

Who owns what, decides what—and escalates to whom.

Commercial accountability: role, ownership, decision rights and escalation
RoleOwnsDecidesEscalates to
Forum owner (manager)Running the forum from its view and recording decisionsOutcomes within the forum’s rightsNext forum up
Sales operationsForum design, views and adoption signalsView changes, via governanceSales leadership
Sales leadershipThe cadence as a wholeWhich forums exist and what they may decideExecutive team
SellersKeeping their deals and plans currentNext steps and stage progressSales manager

Design decision

Design the forums first and build one system view per forum, instead of building dashboards and hoping forums adopt them.

06The trade-offs

Credible options, judged against these premises.

Rejected

More dashboards and usage reminders

Teams that already run forums from the system

Cost: Adds reports; does not change the meetings
Rejected

Mandate CRM usage by policy

Short-term compliance

Cost: Data entered for nobody; quality drops
Selected

Design forums first, one system view per forum

Any organization where management routines exist

Cost: Managers must change how they prepare and run meetings

07The second layer

Questions that change the design.

Forums

  1. Which forums actually run the business today?
  2. What may each forum decide?
  3. Which evidence does each one need?

System

  1. Which view does each forum open?
  2. Where are decisions recorded?
  3. Which parallel reports can be retired?

Adoption

  1. How do we know a forum ran from the system?
  2. Who coaches managers who don’t?
  3. Which signals replace login counts?

08Decisions & outputs

What the work produces.

  1. 01Forum catalogue
  2. 02Evidence per forum
  3. 03Decision rights per forum
  4. 04One system view per forum
  5. 05Adoption signals
  6. 06Coaching routine