Direct answer
A daily owner brief is a short message, sent at the same time each morning, with the five to eight numbers you'd otherwise look up yourself: cash, overdue invoices, today's jobs, new enquiries and anything off track. Each number needs a written definition, a source system and a named person who checks it when it looks wrong.
It does the job a KPI dashboard is meant to do, with one difference: it comes to you. A dashboard waits for someone to open it. A brief arrives, says what changed, and names who is dealing with each problem.
A sample brief
Here is what one might look like for a small trades or services firm. Every name and figure is made up.
EXAMPLE · made-up figures · Tuesday, 07:30
Cash in the bank: £42,180 (down £3,900 since yesterday: VAT payment)
Owed to us, overdue: £18,640 across 9 customers
Over 60 days: Customer A £4,200, Customer B £1,150 → Jo is calling both today
Jobs finished, not yet invoiced: 4 (£6,300) → Sam to raise by noon
Today: 11 jobs booked. Thursday: 2 engineers short → Alex to move jobs
New enquiries yesterday: 14 (9 WhatsApp, 4 web form, 1 phone)
Not replied to after 4 working hours: 2 → Priya
Quotes sent, no answer after 7 days: 6 (£23,400)
Bills due this week: £7,950
Alerts: 4 of 6 fired, each marked → with a name. Nothing else needs you.
Seven numbers, four named people, one line saying nothing else needs you. If a morning's brief is longer than this, it has turned into a report, and nobody reads reports at 07:30.
The numbers, defined
The brief is only as good as its definitions. "Overdue" can mean past the due date, past 30 days, or past the date the customer promised, and if two people use different meanings the brief starts arguments instead of settling them. Write each one down, once, before anything is built.
Swipe or scroll to compare the columns.
| Number | Definition | Source system | Who checks it |
|---|---|---|---|
| Cash in the bank | Cleared balance across business current accounts at 06:00, from the bank feed | Accounts software (Xero or QuickBooks) | Bookkeeper |
| Overdue invoices | Total of sales invoices past their due date, unpaid, split into 1–30, 31–60 and over 60 days | Accounts software | Whoever chases invoices |
| Jobs finished, not invoiced | Jobs marked complete in the job system with no matching sales invoice | Job management software and accounts software | Office manager |
| Today's jobs | Jobs booked for today, with staff assigned; gaps against the rota for the next five working days | Job system or calendar, and the rota | Operations lead |
| New enquiries | Enquiries received yesterday, by channel, and how many have had no reply after four working hours | CRM, shared inbox, WhatsApp | Whoever owns enquiries |
| Quotes awaiting an answer | Quotes sent more than seven days ago with no accept or decline | CRM or quoting tool | Sales lead or owner |
| Bills due this week | Supplier bills due in the next seven days | Accounts software | Bookkeeper |
| Gross margin on last week's jobs | Invoiced value minus labour and materials booked to each completed job | Job system and accounts software | Owner, monthly with the accountant |
Pick the five to eight that you actually act on. A number that never changes what anyone does in a week doesn't belong in a daily brief; move it to the monthly pack.
Notice how many rows need two systems. Cash and bills come straight from the accounts. "Jobs finished, not invoiced" and margin need the job system and the accounts to agree on what a job is, which is usually the first piece of real work.
Alerts: thresholds and the named person behind each
A brief that reports numbers without saying which ones matter just moves the looking-up to a different screen. Each number gets a threshold, and each threshold gets a person.
Swipe or scroll to compare the columns.
| Alert | Fires when | Goes to | What they do |
|---|---|---|---|
| Low cash | Balance below the amount set aside for next week's wages and bills | Owner and bookkeeper | Decide which bills wait, which invoices to chase first |
| Old debt | Any invoice over 60 days, or any customer over a set amount | Whoever chases invoices | Call the customer, log the outcome, flag disputes |
| Uninvoiced work | A completed job with no invoice after two working days | Office manager | Raise the invoice or record why not |
| Short-staffed | Booked jobs exceed available staff on any of the next five days | Operations lead | Move jobs, call in cover, or tell the customer |
| Slow reply | An enquiry with no reply after four working hours | Whoever owns enquiries | Reply, or hand it to someone who can |
| Stale quote | A quote over a set value with no answer after seven days | Sales lead | Follow up, or mark it lost with a reason |
Set thresholds so that most mornings nothing fires. If an alert fires every day, either the threshold is wrong or the problem needs fixing rather than reporting. And the brief should say when an alert has been dealt with, so the owner isn't the one checking whether Jo made the call.
Building it on the AI seat you already pay for
You may not need new software. There are two practical routes.
Start with what the accounts software already does. Xero's UK pricing page lists graphs and customisable dashboards on its Grow and Comprehensive plans, and KPIs, ratios and industry benchmarks on Ultimate. On 16 September 2026 Xero listed "recurring reports or briefs" and a "business pulse" among the workflows Claude for Small Business can prepare from Xero data, for a person to review. QuickBooks lists a finance AI that tracks KPIs on its UK Advanced plan. If every number in your brief comes from the accounts, try these first.
Join the other systems for the rest. Most briefs need the job system, the CRM or the rota too, and the accounts software's assistant can't see them. Connecting Claude or ChatGPT to Xero explains what those assistants see and the safe ways to add other systems. For a brief, the method that holds up best is:
- A scheduled job pulls each number from its source system, read-only, and calculates it by the written definition. Code does the arithmetic, so the same inputs always give the same answer.
- The thresholds are checked by rules, and alerts are addressed to the named people.
- The AI model you already pay for (Claude, for example) writes the short summary at the top and answers follow-up questions during the day, such as "which customers make up the £18,640?", from the same figures.
- The brief goes out by email, Teams, Slack or WhatsApp at a fixed time, and every number links back to the record it came from.
Letting a language model compute the figures itself is the step to avoid. It reads well and is hard to check. The model's job is to explain numbers that rules have already worked out.
What an "AI chief of staff" can and can't do
"AI chief of staff" is the name some products give this idea. The brief above is the useful core of it. Here is what the phrase covers in practice, and what it doesn't.
It can gather numbers from the systems it's connected to, summarise them in plain English, spot that something has crossed a line you set, draft the email or task that follows, and answer questions about the figures at any hour. With the right connections and permissions, it can also prepare work for a person to approve, such as a list of reminders to send or a draft month-end pack.
It can't see systems nobody has connected, so its picture of the business is exactly as complete as its access. It doesn't know what was agreed on the phone yesterday unless someone recorded it. It can't be accountable: if a number is wrong or an alert is missed, a person has to own that, which is why every row in the tables above has a name. And it shouldn't decide anything that changes money, staff or what a customer receives. Rules where you need certainty, AI where you need judgement, and a person signing off where mistakes are expensive.
The point of the brief is that you stop being the person who knows how the business is doing because you looked it all up. That only works if someone else checks each number, and if the business would still run on the days you don't read it.
Sources and dates
Checked 24 October 2026: Xero's UK pricing page (dashboards and KPI features by plan); Xero blog, 16 September 2026 (Claude for Small Business workflows); Intuit QuickBooks UK AI page (finance AI on Advanced). The sample brief uses invented figures and names.
