Many CRMs can send a daily email. Two widely used CRMs describe their daily emails in their help pages, and both are written for one salesperson. One lists that person's meetings for the day. The other summarises the notifications the person received in the past day.
A board needs something else. It needs a short account of what the whole business did yesterday, and a way to check each number in it. This post covers what such a brief reads and what the board should receive. It also covers two rules that make a brief worth trusting: every figure opens its source record, and the brief says when a system could not be read.
Why the CRM alone cannot brief the board
Each system in a company holds part of the record. Your CRM knows what was sold. Your accounting program knows what was invoiced and paid. Your ERP knows what was made and shipped. A board question usually needs more than one of them.
The systems also count at different moments. A CRM records a sale when the sales team marks the deal as won. An ERP records it when the order is created, delivered or invoiced, depending on the company's accounting policy. Two correct reports can therefore show different totals for the same week.
Gaps open between the systems as well. A deal is marked won, and no sales order or invoice follows. An order arrives by phone and never reaches the CRM. Where the systems are not connected, salespeople have to ask accounting whether an invoice was paid, because the deal record does not show it.
What the brief reads, and what the board receives
A board brief reads the CRM, the accounting program and the ERP each morning. It does not replace them. They remain the systems of record, and the brief reports what they hold.
What the board receives is short and written in plain sentences. It covers the day before:
- what was sold, invoiced, collected and delivered;
- what did not move, such as an order that was not shipped or an approval that is still waiting;
- where two systems disagree about the same customer, order or amount;
- when the data was taken from each system.
The list of what did not move often matters more than the totals. Totals show how the day went. The exceptions show where to ask.
Every figure should open its source record
A summary written by software can be wrong and still sound certain. A revenue operations guide on AI-written CRM notes states it briefly: a confident wrong value is worse than an empty one. An accounting guide on AI reports makes the same point about numbers: a number that cannot be traced to a transaction is a guess.
So each figure in the brief should open the record behind it: the deal, the invoice, the order or the payment. A board member who doubts a number can open that record and check it before the meeting.
The brief should also say when it read each system. A brief is only as current as the systems it reads. A cash balance taken early in the morning, before the night's bank settlements are complete, may not be the final figure for the day before.
When a system could not be read
Connections fail. A server is restarted during the night, or the password a connection uses expires.
Two shortcuts are tempting, and both mislead. One fills the gap with the previous day's number. The other leaves the line out without comment. In both cases the board reads an incomplete brief as a complete one. A guide on automated briefings for chief executives says it directly: telling the reader which data is not available is worth more than silently putting in an incomplete figure.
The better behaviour is simple. The brief names the system that could not be read that morning, leaves its part empty and does not guess. The accounting guide quoted above adds that an AI allowed to answer "I do not have this" invents fewer answers than one that is not.
Analysis mode: asking where a problem comes from
The brief says what happened. Sometimes the board needs to know why a number is off. An analysis mode answers that. You ask where a problem comes from, and it reads the CRM, the accounting program and the ERP together, then reports where they disagree and where work is stuck.
Typical findings look like this:
- a won deal that was never invoiced;
- an invoice with no order behind it;
- a payment that is late;
- an approval nobody has acted on.
Finding a gap does not settle it. Someone has to say which system is right. We ask for two named people for this: one in sales and one in finance, who decide which record is correct when two disagree. Any change to the accounting program or the ERP then waits for a named person's approval.
How our AI CRM does it
Our AI CRM with a Daily Board Brief is one way to get such a brief. It is a CRM connected to your accounting program and your ERP. Each morning the board receives a short written account of the day before: what was sold, invoiced, collected and delivered, and what did not move. Every figure opens the record it came from. When a system could not be read that morning, the brief says so.
Its analysis mode reports where the three systems disagree and where work is stuck. We analyse the connections your accounting program and ERP offer and write the connection for them. Those stay your systems of record. Some vendors license their interface separately, and we check that during the analysis, before any work is quoted. Nothing changes in your accounting program or your ERP without a named person's approval.
The CRM is modular. It is redesigned for each customer and updated as the business changes. If you add our phone agent, every call lands in the CRM, and calls and meetings are written there for your team to confirm. It runs on your own servers or on our cloud, and you choose. Your data is yours, and terms are agreed per engagement. Our ERP Built to Fit comes with the same daily brief and analysis mode.
If you would like to see what a morning brief could look like on your own systems, tell us which systems you run.