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

Read

Sales Daily Briefing

Sales Daily Briefing reads Deal State every day against goals, sales process, qualification, forecasting and escalation logic, and hands each Sales role only the deals, changes and actions that are actually theirs to work on today.

Connects to
Departments
Sales

RevOps

Sales Daily Briefing·12 reps briefed today
Briefing Amara Osei…
TriggerSchedule · Amara Osei - Tue 8:00 AM · runs every weekday
Deploy agentDeploying Sales Daily Brief agent on the rep's book
Use skillLoading skills · Deal Risk Assessment · Forecast Assessment · Recommended Action
Reference memoryReading memory · Goals & Objectives · Forecasting · Escalations
ReasoningCommit at risk is $760K and one deal carries it; the EB hasn't replied in 7 days and the multi-thread draft is ready, so send before 10:00
ActionCompose daily brief: deals, meetings, risks → deliver to Slack before the day starts
Briefed in 6 seconds
Surfaces inWorkspaceviaSlackTeams
Revenue LabsAPP8:00 AM LIVE
Daily Briefing: Amara Osei · Tue 21 Jul
You have 3 meetings, 2 time-sensitive actions, 1 new deal risk, and 1 high-propensity account to progress.
$760K
Commit at risk
$210K
Creation gap
2.6x
Coverage · target 3.0x
Medium ↘
Pipeline health
TOP RISK
New deal risk · Fairholm Capital
Health remains Poor after 7 days without Economic Buyer engagement. Rosa Ferreira has not replied, and the multi-thread recommendation is still outstanding.
WHAT CHANGED SINCE YESTERDAY
Orchard warmed up: intro opened twice, pricing visited. Your discovery is well timed.
Forecast slipped: coverage fell to 2.6x against a 3.0x target, and creation is $210K behind pace.
Bluecrest went stale: close date passed with no next step logged.
RECOMMENDED ACTIONS TODAY
1. Send the Fairholm multi-thread email to Rosa Ferreira before 10:00. A draft is ready.
Ask Agent

What should each sales role know before the day begins?

Rep, manager and leader all start from the same Deal State; what differs is whether each of them reconstructs it by hand, gets one generic recap, or opens a brief already split into what they actually need to act on today.

01 | The Current Way

02 | AI Added On

03 | AI-Native

Before the rep logs in

Reconstructed from four tools

Before the day starts, the rep opens the CRM dashboard, their inbox, call recordings and a spreadsheet to work out what actually happened on their deals overnight.

A generic recap

A summary covers yesterday's activity and dashboard changes, built after the fact, and reads the same whether it reaches a rep chasing their number or a leader watching the forecast.

Already current at login

Deal State updates through the night, so the brief the rep opens already reflects what changed since yesterday, before they've touched a single tool.

The moment the brief splits by role

One dashboard, four questions

Rep, manager, leader and RevOps all open the same CRM view, and each has to work out separately which part of it is actually theirs.

One digest, every inbox

An automated digest goes to the whole team in the same shape, with no sense of what a rep needs to act on against their own number versus what a leader needs to see move in the forecast.

Split by what each owns

The rep sees their own deals and what needs action, the manager sees team exceptions, the leader sees pipeline and forecast movement, and RevOps sees system health and what's waiting on their approval.

The moment a deal needs a manager's call

Buried until a review

A deal that stalled overnight sits in a call recording or a rep's private notes until a manager happens to ask about it days later in a pipeline review.

Flagged, not weighed

An alert fires the moment a deal's stage or close date shifts, with no read on whether it actually threatens this quarter's number or just needs a routine nudge.

Escalated against the plan

Exceptions are ranked against goals, forecast targets and the escalation thresholds sales leadership sets, so what reaches a manager before the day starts is only what genuinely needs their judgement.

The moment someone acts

Still the rep's call

The brief or the CRM shows something changed; deciding what to do about it, and whether to loop in a manager, is still down to the rep alone.

A tip, no deal context

A bolted-on suggestion proposes a generic next step from the activity alone, with no read on this deal's stage, its stakeholders, or how the rep actually sells.

Act, override, approve, traced

Every change or exception carries a recommended action with it; the rep or manager acts, dismisses, overrides or approves it, and that choice is recorded against the deal.

The moment the deal proves the call right or wrong

Nobody checks back

Once a deal closes or stalls, nobody goes back to see whether the read on it last week was actually right, so the same blind spot shows up again next quarter.

Same weighting, every morning

The automated summary keeps treating the same signals the same way, whether the deals it called healthy went on to close or the ones it missed slipped away.

One deal, every rep learns

Whether a flagged deal closed, stalled or was overridden feeds back into what the brief prioritises for every rep and manager, and RevOps decides whether the update applies on its own or waits for their review.

It reads Deal State continuously against goals, sales process, qualification, forecasting and escalation logic, and produces a brief split by role, what changed overnight, what's overdue, what's at risk and what's waiting on approval, delivered where the team already works, with the reasoning behind every read traceable.

It gives reps and managers back the time spent reconstructing the pipeline every morning, and cuts the recurring status meetings that exist only to work out what changed overnight.

SEE IT RUNNING
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 Sales System
Understand
Deal State
Qualification
Stakeholders
Risk
Decide
Pipeline Review
Forecast
Meeting Prep
Prospecting
Act
Follow-up
Next Steps
Updates
Escalation
Learn
Upgrade ICP
Upgrade Prospecting
Upgrade Sales Process
Upgrade Messaging
Surfaces
CRM · Slack · Teams · ChatGPT · Claude · MCP · API
Output
Briefings · Artifacts · Alerts · Recommendations · Approvals · Actions

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.

Frequently Asked Questions

AI-native GTM Systems didn't exist two years ago - here are the questions everyone wants answered.

Talk to Us→
Doesn't a sales daily briefing just add another dashboard reps have to check?

A sales daily briefing only becomes another dashboard if it's built as a bolted-on summary. Sales Daily Briefing reads Deal State continuously against goals, sales process, qualification, forecasting and escalation logic, and opens already showing what changed overnight and what a rep, manager or leader actually needs to act on, so there's nothing left to reconstruct first.

What stops the wrong deal being flagged urgent for the wrong role?

Sales Daily Briefing weighs every change against goals, forecast targets and escalation logic before deciding who needs to see it. A rep only sees their own deals and actions, a manager only sees exceptions across the team, and anything that needs strategic judgement escalates to a person to decide.

How current is what a rep sees first thing in the morning?

Sales Daily Briefing reflects Deal State as it stands the moment it opens. It's held against sales process, qualification and forecasting logic continuously, so a deal that stalled overnight, or a new stakeholder who joined a thread, shows up in the brief itself, before anyone has gone looking for it.

Does the briefing get better at knowing what actually needs a rep's attention?

Sales Daily Briefing does get sharper, because every flagged deal has an outcome attached to it, closed, stalled, or overridden by a rep or manager who knew something the brief didn't. That pattern updates every rep and manager's briefing across the team, and RevOps decides whether the change applies on its own or waits for their review.

How should manager and rep sales briefings differ?

A rep's briefing and a manager's briefing pull from the same Deal State but show different things. The rep sees their own deals and what needs action today. The manager sees the exceptions across the team: the deals that are genuinely off pace or at risk and need a manager's judgement before the day starts.

What should an AI sales daily briefing include?

It should show what changed since the last one, which deals now need attention and why, and route each of those to the role that owns it, a rep's own deals, a manager's team exceptions, a leader's pipeline and forecast movement. Sales Daily Briefing does exactly this, built from Deal State held against goals, sales process, qualification, forecasting and escalation logic.