CRM
Stage, amount, close-date movement, owner, next step, forecast category.
Revenue Intelligence Briefings
Sales leaders already have CRM reports, call recordings, and dashboards. They still spend the week working out what changed and where to step in. In a RevOps role, I built a weekly workflow that pulled those sources into a short brief with evidence and suggested actions. This page rebuilds it with made-up companies, deals, and numbers.
A sample weekly brief
Four numbers, what changed, where leadership should step in, and what not to conclude yet.
Weekly Revenue Intelligence BriefIllustrative week · synthetic SaaS data
Commit$4.2M
WoW change-7%
Deals needing review4
Manager actions3
What changed
Forecast
Two enterprise opportunities moved into the following month, reducing current-period commit by $310K.
Qualification
One of the slipped deals has strong product engagement but no confirmed economic-buyer meeting or funding path.
Execution
Mid-market stage-two conversion improved for the second week while average time in stage fell.
Evidence: Salesforce close-date history + forecast category changes · Gong stakeholder and next-step signals · segment conversion baseline.
Where leadership should intervene
- Enterprise Deal A: Ask the seller to test the internal sponsor against the commercial-champion standard before restoring the prior close date.
- Enterprise Deal B: Review procurement timing and dated compelling event with the manager; the CRM next step is seller-owned and stale.
- Mid-market team: Inspect what changed in discovery behavior before treating the conversion improvement as a durable trend.
What not to conclude yet
The mid-market improvement is two weeks old and does not yet justify changing targets, capacity assumptions, or coaching standards. The brief surfaces the pattern; leadership decides whether it is signal or noise.
Decide what’s worth flagging before a model gets involved
Asking a language model to “find insights” gets you confident noise. RevOps defines which changes matter, at what threshold, and from which source. The model drafts after those rules run, and leaders decide what to do.
Conversations
Economic-buyer access, objections, competitor mentions, next-step language, inactivity.
Performance data
Win rate, cycle, conversion, attainment, segment baselines, historical patterns.
Operating signals
Pricing exceptions, support issues, marketing activity, leadership notes, enrichment.
Close-date slip30+ days on material opportunityInspect compelling event, procurement path, and seller forecast call.
Champion riskHigh engagement, no access to powerTest whether contact is a product champion or a commercial champion.
Conversation silenceLate-stage deal with no customer meeting in 14 daysInspect next-step ownership and whether the deal should remain in stage.
Rep patternConversion or activity changes outside normal rangeGive the manager a coaching question, not an automated performance verdict.
What’s real and what’s rebuilt
- The original
- A weekly AI-assisted GTM insight workflow I built that combined more than ten data sources into leadership recommendations and rep-level coaching signals.
- This page
- A rebuild of that workflow’s logic and output format with synthetic names, values, and examples. Nothing here is employer data.
- Next iteration
- Claim-level source citations, tracking how often past flags turned out to be right, a review step for false positives, and a record of which recommendations actually changed an outcome.