Good morning. Pipeline map updated as of 06:00. Active deals to push today: 3 (including a corporate deal whose signing window closes Friday). Deals at risk: 2 in prolonged silence (last activity 18 and 24 days ago). Follow-ups requiring a head-of-sales decision: 5. HubSpot record links ready.
AGENT · REVOPS BRIEF
The sales summary is ready before the morning meeting.
RevOps Brief works overnight. It reads the previous day's activity in the CRM, calendar events, the team's outbound emails, and deal updates. At the start of the day, the head of sales finds the pipeline map in the work channel — active deals, deals at risk, and decisions that need their call.
RevOps Brief at work.
Confirmed. The corporate deal is mine. I'll open the legal file this morning.
Decisions recorded. Notification sent to deal owners in the team thread. Audit registry updated.
Why it exists.
The half-hour before the morning meeting is preparation work, not decision work. Someone reads the same systems they read yesterday, orders numbers already written somewhere, and formulates three observations the team could have spotted on their own. It is exactly the kind of work an agent does well.
How it works overnight.
RevOps Brief activates overnight. It reads the previous day's activity in the CRM (updated deals, open tickets, calendar events, outbound emails), compares the numbers against the monthly baseline, identifies deals at risk (prolonged silence, close deadlines, churn signals from the customer success system), and builds a day map with direct links to each customer's CRM record. The summary arrives in the team's work channel at the start of the day, before the meeting.
The decision stays with the team.
The customer decision stays with the head of sales. The agent does not close deals, does not write emails to the customer, and does not update states without approval.
Three business functions that change the way they open the commercial day.
Head of sales
Receives the day map ready at the start. They no longer delegate preparation of the morning meeting, and no longer lose the half-hour of CRM reading that is hard to keep consistent.
RB RevOps Brief
Idritech SpA silent 8d · proposal expiring
Nexar Group proposal sent · no reply
Aludra Srl signature expected this week
Head of RevOps
Reclaims the time of the operations team, which today spends half a day a week generating manual briefs for different commercial clusters (corporate, retail, large account, indirect channel). RevOps Brief handles the clusters in parallel, with different configurations for each.
CustomerSignalRisk
Idritech SpA Silent 12 days · 3 emails unanswered high
Nexar Group Proposal expired · no extension med
Orbis Srl Meeting cancelled 2× med
Proxa Corp Active contact · reply < 24h low
CRO or head of sales
Sees the real pipeline instead of the pipeline filtered by middle managers. Deviations from the baseline arrive in a structured way, before they become a quarterly problem.
87 Tone too formal — try a direct opener
71 Long message: summary in the first 2 lines
94 Excellent — consistent with the customer history
A night's work that changes how the meeting starts.
During the night, RevOps Brief reads the CRM.
For the head of sales at a corporate bank, the day starts on Slack. RevOps Brief worked overnight: it read the previous day's activity (outbound emails from ten corporate sales reps, CRM tickets, calendar events, updated deals on HubSpot), compared the numbers against the monthly baseline, and identified deals in prolonged silence. The summary reached the manager's channel at six in the morning, with the day map in three blocks.
At the opening, the summary is already in the team channel.
Three active customers to push today (including a corporate deal whose signing window closes this week). Two deals at risk for prolonged silence (flagged with the date of last activity and the assigned rep). Five follow-ups requiring a head-of-sales decision (a corporate deal whose amount requires legal authorisation, escalation of a support ticket, confirmation of a proposal to send today).
The head of sales decides. The agent records and notifies.
In a few minutes the head of sales approves the priority actions directly in the Slack thread. RevOps Brief gathers the decisions, notifies each customer owner's channel with the day map, and writes the next action on every deal into the CRM. The trace of the decision, the rule triggered, and handling time stays in the audit registry, readable by the compliance team with a standard SQL client.
Declarative rules from the customer's sales operations team.
RevOps Brief's rules are declarative. The customer's sales operations team defines in a human-readable format what "deal at risk" means for the company (e.g., silence beyond 14 days on a corporate deal above 100k, a ticket opened on an account in renewal phase), which metrics enter the monthly baseline, and in which order the blocks appear in the map. Rules live in the customer's repository, version-controlled, validated at agent startup.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, tool-rate-limit, message-length-limit
- Native delivery channels
- Slack, Telegram, WhatsApp, OpenAI-compatible HTTP
- Scheduling
- configurable per instance (typically 04:00 team time zone)
- CRM integrations
- HubSpot native (contacts, deals, tickets, meetings, tasks, notes, company, email)
- Other CRMs
- Salesforce, Microsoft Dynamics, sector-specific systems: integration delivered during the project by the Exelab team
- Memory
- persistent per instance, pgvector + PostgreSQL FTS
- Registry
- immutable, queryable with a standard SQL client
Frequently asked questions about the agent.
Polyant talks to the CRM through dedicated tools. HubSpot tools are native (contacts, deals, tickets, meetings, tasks, notes, company, email). For other CRMs (Salesforce, Microsoft Dynamics) and sector-specific management systems, the integration is delivered during the project by the Exelab team. The logic is the same throughout: the agent talks to the tool, the tool talks to the APIs of the customer's system.
The typical pattern for a first RevOps Brief is 4-6 weeks. Discovery one week, rule and baseline configuration two weeks, CRM integration one or two weeks, hand-off to the sales operations team one week. The main factor is the depth of declarative rules and the number of management systems involved. The effective duration is defined in discovery on the real case.
The customer's sales operations team, via the graphical admin panel or directly in TypeScript. Rules are declarative, in a human-readable format, version-controlled in the repository. When a threshold is changed (e.g., maximum silence on corporate deals), the rule is written, tested, and promoted to production. For those who want to delegate operational management too, Exelab provides managed services in three profiles (Core, Advanced, Ultra): details are at /managed.
The value of RevOps Brief is measured on three kinds of result. Time reclaimed by the sales operations team versus the pre-agent baseline on manual morning summary preparation. Speed of head-of-sales reaction on deals at risk, ahead of the prolonged-silence date. Reduction in deals slipped by a week for lack of action. The numerical baseline is defined during discovery and measured in the first weeks of operation. RevOps Brief is one of the agents the customer can choose to build for their sales team.
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how RevOps Brief would be configured for the customer's case. Which CRM systems, which cadence, which metrics enter the baseline.