The Lab is live. 15 essays from the frontier of AI-native GTM.

Read

Customer Daily Briefing

The first half hour of a CS day goes on reconstruction: the CSM reads dashboards and last night's email, the manager scans for trouble, the leader asks around, RevOps pulls a report. Four people, four private versions of the same book. This skill compresses customer state into a daily briefing per role, applying your Goals & Objectives, Customer Health, Customer Risk, Renewal, Expansion and Escalations memories: the CSM gets today's accounts and the reasons, the manager gets exceptions across the team, the leader gets material change against goals, RevOps gets where reality is leaving the plan. People act, dismiss, approve or override, and what gets used or ignored feeds what surfaces tomorrow.

Used across
Customer Daily Briefing·8 ACCOUNTS FLAGGED TODAY
Briefing Hollowmere's state…
TriggerMorning briefing · 8:20 AM · Hollowmere, 4 roles
Live stateReading Customer State · Hollowmere · health, risk
Applying skillRunning Customer Daily Briefing v4
Compresses Hollowmere's state into 4 role briefings
RevOps view confirms Hollowmere is not drifting
CSM view shows Hollowmere due a touch before the QBR
Manager view surfaces Hollowmere as one exception
Reference memoryAgainst Goals/Objectives · Customer Health · Customer Risk · Renewal
ActionBriefing compressed, exception flagged across all 4 roles
Skill
Customer Daily Briefing
v4v5
Customer Daily BriefingHollowmere briefed all 4 roles
See the capability Run 29 times today
Upgrade proposed
Dismissed items resurface once evidence changesv5
8 accounts needed a CSM touch today; 3 drifted from plan.
Approve upgrade to Daily Briefing?
The current way > AI added on > AI-native

Attention, assembled before the day starts

Every role begins the day choosing what to look at first; the briefing does the choosing, with reasons, differently for each chair.

01 | The Current Way

02 | AI Added On

03 | AI-Native

Each role rebuilds its own morning view

Everyone triages alone

Each role reads a different surface: dashboards, check-ins, the weekly deck, a report. The views disagree and nobody knows by how much.

One summary for four different jobs

The summary reads the same to a CSM and a leader. It cannot supply what each role should do next, judged by health, risk and renewal logic.

Each role opens on what it can act on

The CSM opens on accounts to touch, the manager on who needs backup, the leader on what moved, RevOps on drift. One state under all four.

Referenced by

Capabilities that run this skill

Customer Success

Customer Daily Briefing

Active
Customer State is current before the day starts
Health, risk, renewals and usage reflect overnight change before tools are opened.
The briefing splits by role
CSMs see actions, managers exceptions, leaders movement and RevOps system health.
Exceptions are ranked by your logic
Health, risk, renewal and escalation logic decides what needs judgement.
+
Each change arrives with an action
The CSM or manager acts, dismisses, overrides or approves a recorded recommendation.
A role-specific daily briefing cuts reconstruction and status meetings without another tool to check.
SEE HOW IT WORKS

Customer Success

Portfolio Review

Active
The CSM starts with material exceptions
Customer State aggregates the book before the one-to-one and surfaces material change.
Manager and CSM share one state
Both work from the same evidence, so differences are judgement rather than data gaps.
Evidence narrows disagreements
The specific change behind a flag shows what deserves greater weight.
+
Agreed action becomes owned state
The intervention or question attaches to the account and its owner for next week.
The one-to-one starts from accounts needing a decision, giving managers capacity and improving outcomes.
SEE HOW IT WORKS
The Platform

One system that understands, decides, acts and learns.

Every GTM signal flows through an AI-native operating layer into a system that runs on the surfaces your team already uses.

Explore the GTM System →
GTM Data & Knowledge
CRM · Emails · Calls · Marketing · Product · Support · Documents · Research
AI-Native Operating Layer
Context · Memory · Skills · Agents · Decision Traces
AI-Native Customer Success System
Understand
Account Health
Churn Drivers
Expansion Signals
Product Usage
Decide
Renewal Risk
Expansion Opportunity
Account Plan
Intervention Priority
Act
Meeting Prep
QBR Prep
Sales Handover
Save Plays
Learn
Upgrade Health Model
Upgrade Onboarding
Upgrade Playbook
Upgrade Forecast
Surfaces
CRM · Slack · Teams · ChatGPT · Claude · MCP · API
Output
Briefings · Artifacts · Alerts · Recommendations · Approvals · Actions

SEE WHY REVOPS + MARKETING LEADERS CHOOSE REVENUE LABS

The GTM teams that learn fastest will win. Build yours a system that learns.

An advantage competitors cannot buy back: years of success and failure, codified.

FAQ

What buyers ask

If it's not here, we'll answer it live.

Talk to us

From state, by role, on cadence. The briefing reads customer state, applies your Goals & Objectives, Customer Health, Customer Risk, Renewal, Expansion and Escalations memories, and compresses the result into what each role should attend to today, with reasons. Each item carries its evidence.

Selection differs; the facts do not. All four briefings read one state, and each selects for its reader's decisions: a CSM is choosing calls, a manager is choosing interventions, a leader is watching the goals, RevOps is watching the plan. When two roles compare notes, the facts match.

It sits with a judgement longer. Portfolio Review prepares the manager's review: exceptions, questions, evidence. The daily briefing runs the day in between, pointing each role at what needs attention now. The two share one state, and a week of briefings often hands the review its shortlist.

Nobody has to. The Customer Daily Briefing capability delivers it wherever each role already spends the morning, so nobody opens a new tool for it. The person's job starts at deciding, because the gathering is already done.

Act, dismiss, approve or override, each recorded. Dismissals matter: an item nobody uses is evidence the prioritisation is off, and it feeds the next version. The briefing itself never leaves the team; if an item ends in a customer conversation, a person starts it.