Your company brain.
Built with you, owned by you.

use cases

Management reporting, every number traced to its source.

The monthly pack, built from the live record - every figure carrying its source, a hand-changed number caught before the board reads it, and nothing distributed that cannot be stood behind.

“The report takes weeks to build, and by the time it arrives the numbers have been shaped by everyone who touched it.”

§ 01 Is this you?

Is this you?

  • Month-end is a fortnight of people extracting, chasing and reconciling numbers that already sit in your systems.
  • The first question in the board meeting is where a figure came from, and nobody in the room can answer it.
  • Each department sends up its own numbers, summarised in the way that reflects best on it.
  • The board pack is out of date before it is sent.
  • A measure quietly changed its definition, and the trend line no longer compares like with like.

If two or more of these sound familiar, this is the use case to start with.

§ 02 Before and after

Before and after

today with a company brain
The period closes Each department extracts its own figures, and someone spends two weeks stitching them together in spreadsheets. The pack is drafted from the systems the figures live in, each one carrying its source and its variance against plan and the prior period.
A figure is changed by hand The adjustment survives three layers of reporting, and nobody can say who made it or why. Both values go to the figure's owner, and the pack waits until someone owns the difference.
The board challenges a number It takes a meeting and three days to walk back to the records behind it. The answer is drafted from the underlying records, with its evidence attached.
A measure is redefined This quarter's definition is not last quarter's, and nobody notices until the trend misleads someone. The change is flagged with a fix proposed, so the trend means what it says.
§ 03 What you would see

Illustrative: the shape of what you would receive, not a client's record.

What you would see

board pack draft

Monthly management pack: the period has closed

what it holds
Revenue by line, work-in-progress ageing and pipeline movement, with the narrative drafted.
what changed
Each figure against plan and the prior period, with the largest variances explained first.
how sure
Sure of every figure drawn from the ledger. Two pipeline figures rest on estimates, and say so.
sources
The ledger, the plan and the pipeline records, each figure linked to the record it came from.

draft held for the finance director's sign-off

held figure

A revenue line changed after it was submitted

what it saw
A figure submitted at one value and sourced at another, with no reason recorded.
why it matters
The board would read a number that nobody can stand behind.
owner
The head of the business unit that submitted it.
recommends
Record the reason for the adjustment, or restore the sourced value.

recommend pack held until the owner signs

challenge answer

Board question: why is this line down?

the answer
Most of the fall comes from a change in how the line is measured, not from trading.
what changed
The measure was redefined this quarter, so it no longer compares with last quarter.
recommends
Restate the prior quarter on the new definition, and record the change against the measure.
sources
The underlying transactions and both versions of the definition, each linked.

draft drafted for the finance director to send

Every output says what it saw, why it matters, what it recommends and how sure it is, and links each fact to its source.

§ 04 How it works

How it works

  1. 01 it notices Period close, submitted figures, hand adjustments, changed definitions and questions back on the pack, where they already happen.
  2. 02 it connects Each figure to its source record, its owner, its definition, the plan and the prior period.
  3. 03 it judges Which variances matter, whether a figure can be traced, and whether this period compares with the last.
  4. 04 it checks Every action against your rules: who may see which cut of the pack, and what needs sign-off before it is distributed.
  5. 05 it acts Within the permission you have granted: it notes, recommends, drafts, or acts where you allow it.

It reads from your finance system, ledgers, CRM and the spreadsheets figures are kept in today. It does not replace them, and nothing is migrated.

§ 05 What it runs on

The parts of a company brain management reporting relies on, in the framework's own terms.

What it runs on

01The record
Every figure with its source record, its owner and its history.
02Finding the answer
A board question answered from the underlying records, with the evidence attached.
03The company manual
What each measure means, who owns it, and which system is the authority for it.
04The way in for AI tools
How your people ask it from the AI assistant they already use, on the same permissions as everyone else.
05Connectors
Your finance system, ledgers, CRM and the spreadsheets figures are kept in today.
06Who may see and do what
Who may see which cut of the pack, checked before every answer.
07Agents and actions
Drafting the pack, only through actions agreed in advance, and holding it for sign-off.
09Testing it on your own questions
Tested against your own past packs, and run alongside the one your team builds now.
the company brain keeping it trustworthy, under all of it your systems documents email, calendar business systems your ai tools your people namedsources checked,then kept checkedfirst read in your terms a question,and its answer approvals acting, througha second door 05 connectors 01 the record 06 who may see and do what 02 finding the answer 03 the company manual 04 the way in for ai tools 08 where people use it 07 agents and actions 09 testing on your questions 10 keeping it running 11 keeping every brain current 12 before anythingis built
The twelve parts of a company brain, with the ones management reporting runs on drawn in red. Read left to right: what comes in, what it knows, and who and what uses it.

what this shows about a company brain

It works through the AI tools you already use

Your people reach it from the assistant they already have, on the same permissions. They might ask:

“Why is this revenue line down on last quarter, and has the way it is measured changed?”

It compounds

The definitions it settles in the company manual are the ones every other use case reports in, so the numbers in a customer review, a supplier review and the board pack finally agree.

It is yours

The record, the rules and the permissions it builds belong to you, not to a vendor: handed over to your team or run for you. The same company brain runs every use case you add.

§ 06 You stay in control

You stay in control

  1. observeIt reads silently and measures its own accuracy against what really happened.
  2. recommendIt puts the case and a proposed action to a named owner.
  3. draftIt prepares the action, and holds it for a person to sign.
  4. actIt acts within the bounds you set, and logs everything it does.

Each permission is granted or withheld, taken back as easily as it was given, and expires unless someone renews it. Everything starts at observe, and a permission is granted on the measured record, never on a promise. Every action is checked against your rules before anything goes out.

Nothing is distributed without the sign-off your policy requires, and who sees which cut of the pack stays a setting you control, permanently if that is your policy.

§ 07 Where it starts

Where it starts

first scope
One pack: the monthly management accounts, or the executive scorecard.
how it proves itself
It runs at observe first, against your own past packs and alongside the one your team builds today, so you judge it on numbers you already know before it is allowed to do anything.
what it connects to
The systems you already run: your finance system, ledgers, CRM and pipeline. Connectors are built for you, as part of the work. How it connects.
what you own
You own the result: the reporting record, the rules and the permissions, handed over to your team or run for you.
§ 08 Questions

Questions

Does it replace our BI or reporting tool?
No. It reads from your finance and operational systems, and your dashboards stay where they are. What it adds is the pack itself: assembled, sourced and explained, with every figure traceable to the record it came from.
Does it cover our regulatory and statutory returns?
No. This is internal management information: the pack your executive team and board run on. Regulatory returns and their evidence belong to compliance, which runs on the same company brain.
Who can see what?
Only what each person is allowed to see. Who sees which cut of the pack is a setting you control, permissions are checked before every answer, and every question is recorded.
Will it send the pack to the board on its own?
No. The pack is drafted and held for the sign-off your policy requires, and you can keep it that way for good.
Is this available today?
It is built for each company that runs it, on that company's own brain, not installed off a shelf. The question audit comes first and shows what it would and would not do for you before anything is built.
§ 09 Start

Start

try this on your own record

Take three past packs: one that landed too late to act on, one with a number that was challenged and could not be traced, and one that surprised the board. What did your own systems know, and when?

Questions like this are what the question audit answers: about two hundred real questions from your business, each answered in writing, so you know what management reporting on a company brain would and would not do for you before anything is built. It is a small fixed fee, credited against the build or the service if you go ahead.

book a discovery call → take the diagnostic · 10 min (opens in a new tab)