Automated Business Reporting: The Brief That Gets Read

Automated business reporting means a system that gathers your numbers on a schedule, decides which of them moved enough to matter, and delivers a short written brief naming the change, saying why it matters, and asking for the one decision it needs. The deliverable is prose with a recommendation attached, not a screen somebody has to remember to open.

We run one across our own group of companies. It lands before the working day starts. Most mornings the useful part is two lines: what broke, and what needs a decision today.

The argument is not that dashboards are bad. It is that a dashboard puts the work of noticing onto the reader, and the reader is busy.

Most small businesses never had a dashboard to abandon

Eurostat measured business intelligence software use across EU enterprises for reference year 2025, with data extracted in May 2026. The headline: 16.28% of enterprises used BI software at all. Split by size, that was 69.24% of large enterprises against 11.45% of small ones. Information and communication led every sector at 41.08%. Construction sat at 6.77%.

So for a company under fifty people, the honest framing is not “replace your dashboard”. Close to nine in ten never bought one. The incumbent reporting system is a spreadsheet somebody maintains by hand, plus a Monday meeting where the numbers get read out loud.

The same Eurostat release found 33.02% of EU enterprises ran data analytics with their own employees, and the size split repeated: 78.84% at large enterprises, 27.86% at small ones. The capability sits where the headcount is.

If you want the widely quoted “only a quarter of employees use the BI tools their company pays for”, it is a real figure, but it comes from BARC and Eckerson Group’s adoption study of 214 companies published in 2022, which put average employee usage at 25%. Nobody has refreshed that measurement with a primary study since. Four-year-old numbers make a weak business case, and the Eurostat 2025 data makes the point better anyway.

Writing is the thing businesses actually use AI for

The US Census Bureau published a working paper in April 2026, CES-26-25, drawn from its Business Trends and Outlook Survey AI supplement covering November 2025 to January 2026. It found 18% of US firms had deployed AI in a business function, and 23% had workers using AI for tasks. Among those workers, the leading generative applications were writing, document analysis and information search.

That is the shape of a written numbers brief. It is not the shape of an exploratory dashboard.

The same paper found 65% of firms restricted worker AI use to three or fewer tasks, and 57% of adopting firms confined integration to three or fewer business functions. Narrow beats broad in the field data. One agent producing one recurring brief sits comfortably inside the pattern that is already working for other people.

Firm size shows up here too. Census reported separately in May 2026 that 37% of US firms with 250 or more employees were using AI, against under 20% of firms with four or fewer, and that growth over the December 2025 to May 2026 window was concentrated in firms above 20 employees. Small firms are not behind because the technology is hard. They are behind because nobody sold them something that fits in a day that has no analyst in it.

The constraint is delivery, not access

McKinsey’s State of AI, published November 2025, surveyed 1,993 respondents across 105 nations between 25 June and 29 July 2025. It found 88% of organisations regularly using AI in at least one business function, and only 39% reporting any enterprise-level EBIT impact. Around two thirds had not begun scaling.

That gap is the entire problem stated in one line. Having the tool is not the constraint. Getting a number in front of the person who can act on it, at the moment they can act, with the reasoning already done, is the constraint.

BARC’s Data, BI and Analytics Trend Monitor 2026, published 12 November 2025 from 1,579 professionals worldwide, ranked data quality management first and data security and privacy second, both at 7.9 out of 10 on importance, ahead of every AI-specific trend on the list. The people doing this work say the fundamentals decide the outcome.

Gartner predicted at its Data and Analytics Summit in June 2025 that by 2027 half of business decisions will be augmented or automated by AI agents. That is a forecast rather than a measurement, and it should be read as one.

What our own brief actually does

The reporting agent is a tomte, our word for one production agent with one defined job. Here is what it does, in order.

It checks freshness before it checks numbers. A daily job confirms every bank feed and sales-settlement channel actually delivered data inside a set window. Anything stale gets flagged by name and an escalation task is filed against the person who owns that source. A brief built on a feed that quietly stopped three days ago is worse than no brief.

A financial-control agent watches the books continuously and pushes a daily pulse, the current position plus a recommended direction, into our chief-of-staff agent. Nobody opens anything for this to happen.

It closes what it can and escalates what it cannot. Routine close tasks with sufficient evidence get completed by the agent itself. The brief is framed around exceptions, not a full dump of every figure the system holds.

The line between “mention it” and “escalate it to a human” is written policy, not model discretion. Thresholds on financial impact and anomaly detection are set in advance, in text, and reviewed like any other rule.

Scheduling is split by whether judgment is involved. Anything purely mechanical, a fixed script that reads data and reports, runs on deterministic cloud cron. Anything that needs reasoning or a drafted recommendation runs as a scheduled language-model routine. The two never share a job.

The dashboard we do keep is a display surface only. It holds no scoring or business logic of its own. That logic lives in one place, the agent that produces the number, so the screen and the written brief can never disagree.

	Dashboard	Scheduled report email	Numbers brief
Who initiates	The reader, if they remember	The scheduler	The scheduler
What arrives	Every metric	Every metric, as an attachment	The two or three that moved
Interpretation	Reader’s job	Reader’s job	Done before it sends
Knows its data is stale	Rarely	No	Yes, and says so by name
Asks for a decision	No	No	Yes, with a recommendation
Records the answer	No	In somebody’s inbox	Logged against the item

What we got wrong first

Proof over promises means publishing the failures, so here is ours.

Version one was a digest. It listed what was outstanding, correctly and on time, and it changed almost nothing. Surfacing an item is not the same as asking somebody to decide it.

We rebuilt it to pick the small number of decisions actively blocking other people’s work, assemble a real question for each (what it is, why it needs the decision-maker, what it is holding up, plus a recommendation), ask conversationally, and log the answer verbatim against the item. The volume of decisions actually cleared went up by a wide multiple. That exact figure is not public yet, so I am not quoting it here.

The second weakness is live. Escalation thresholds are hand-set. Set them tight and the brief turns into noise nobody trusts; set them loose and something real slips past for a day. There is no clever fix. Somebody reviews them, and the review is a calendar item.

What it costs to install

A reporting brief is not usually a standalone build. It is the reporting half of a Fractional AI Officer engagement at $2,900 per month: one new automation shipped monthly, monitoring of everything already running, and the written brief itself. Cancel monthly, documentation always current, so leaving is safe by design. You own the repository, the data and the accounts throughout.

As of July 2026 our own fleet stood at 41 registered agents, with 5,450 runs and zero failures across one measured 13-day stretch. Each one has an owner, a fence it works inside, and a run log, which is what makes watching the fleet possible at all. The reporting agent is one of them and is watched the same way.

If the reason you want this is to prove value to somebody above you, read how to report AI ROI to leadership first, because the brief is only useful if the numbers in it survive scrutiny. If you are weighing the monthly model against a hire, what a fractional AI officer does sets out the scope.

Send us the three numbers you check most often, where each one currently lives, and who has to act when one of them moves. You get a written fixed-price scope and a plain statement of what the agent will and will not decide on its own, inside one business day. No meeting. Start async.