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

use cases

Key-person risk, seen while there is still time to act.

Where the business depends on one person, seen months early - work, load and certifications on one current record, with every decision about a person left to people.

“Everything routes through the same three people, and I'll learn one of them is leaving when it's too late.”

§ 01 Is this you?

Is this you?

  • Everything important routes through the same few people, and you could name them without thinking.
  • One person holds the client relationship, the know-how and the work, and nobody else could pick it up next week.
  • You learn about a bottleneck when it breaks, and about a departure from the resignation letter.
  • A certification lapses, and the first anyone hears of it is the file review or the audit.
  • Your best people have been running flat out for months, and nothing in your systems shows it.

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
Work concentrates on one person It builds quietly across several clients, and is obvious only in hindsight. The concentration reaches the people lead months early, with the exposure and a cover and succession plan.
A critical role runs hot It sits unseen in the practice system until it becomes a resignation or a mistake. Sustained load on a critical role is put in front of the people lead while there is still time to rebalance it.
A certification nears expiry Nobody notices until it lapses, and the gap surfaces in a review. Renewal training is proposed before the lapse, and the evidence is kept current for the next audit.
Something happens in a regulated role The assessment is assembled by hand, from wherever the records happen to be. The assessment is prepared with its evidence, and nothing about the person moves without HR and legal.
§ 03 What you would see

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

What you would see

dependency note

Critical work concentrating on one role

what it saw
The critical work on three clients now sits with one person, and the role has run above a sustainable load for two quarters.
why it matters
If that person is away or leaves, three client relationships and their delivery have no cover.
recommends
Name a backup for each client, and start a succession plan for the role.
how sure
Sure of where the work sits. Load is read from time records, which may be incomplete.
sources
The practice system, resourcing records and client assignments, each linked.

recommend routed to the people lead

assessment pack

An event recorded against a regulated role

what it saw
An event recorded against a person in a role that carries a fit-and-proper requirement.
what it holds
The role's duties, the requirement and the current evidence, gathered in one place.
who decides
HR and legal, with the person kept informed as your policy sets out.
what it does not do
Form a view of the person, or change anything about their role.

recommend held for HR and legal

certification renewal

A required certification expires before the next audit

what it saw
A certification the role requires runs out before the next scheduled audit.
recommends
Book the renewal training now, within the existing training budget.
owner
The line manager, with the people lead for the budget.
evidence
The record is updated as soon as the renewal is complete.

recommend proposed to the line manager

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 Where work concentrates, sustained load, certifications nearing expiry, events against regulated roles, joiners and leavers.
  2. 02 it connects Each role to the people who hold it, the clients and work that depend on it, the certifications it requires and its cover.
  3. 03 it judges Where a single point of failure is forming, and which gaps would matter before the next audit or departure.
  4. 04 it checks Every action against your rules, with anything about an individual held for HR and legal before it moves.
  5. 05 it acts Within the permission you have granted: it notes, recommends, drafts, or acts where you allow it.

It reads from your HR, practice-management, resourcing and training systems. It does not replace them, and nothing is migrated.

§ 05 What it runs on

The parts of a company brain key-person risk relies on, in the framework's own terms.

What it runs on

01The record
Every role, who holds it, the work and clients that depend on it, its certifications and its cover.
02Finding the answer
Each question answered with its sources, or a plain "I can't answer that well".
03The company manual
Which roles are regulated, what each requires, and who owns the decisions about people.
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 HR, practice-management, resourcing and training systems, and only the records you agree.
06Who may see and do what
Detail about an individual limited to the people your policy names, checked before every answer.
07Agents and actions
Proposing training or a cover plan, only through actions agreed in advance. Nothing about a person moves on its own.
08Where people use it
Where the people lead, HR and legal review and decide.
09Testing it on your own questions
Tested against your own past departures and lapses before it is trusted.
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 key-person risk 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:

“Which client relationships depend on a single person, and who could cover them?”

It compounds

The roles and owners it records are the named owners every other use case routes to, so a risk note, a supplier alert or an audit request always reaches someone who is actually there.

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.

Every decision about a person stays with people: anything that touches an individual waits for HR and legal, and what staff can see about themselves is a setting you choose, not an afterthought.

§ 07 Where it starts

Where it starts

first scope
One team, or one regulated role: wherever losing a person would cost you most.
how it proves itself
It runs at observe against your own past first, so you see how early it would have spotted the departures and lapses you already know about before it is allowed to do anything.
what it connects to
The systems you already run: your HR system, practice management, resourcing and training records. Connectors are built for you, as part of the work. How it connects.
what you own
You own the result: the record of roles and cover, the rules and the permissions, handed over to your team or run for you.
§ 08 Questions

Questions

Does it replace our HR system?
No. It reads from it, and from the practice-management, resourcing and training systems you already run. Your records stay where they are; the company brain connects them to the work that depends on each role.
Does it monitor individual staff?
It is about roles and knowledge, not about watching people. It reads only the records you agree it may, such as work assignments, time records and certifications, to show where the business depends on one person. Those permissions are set with HR and legal, and what staff can see about themselves is your choice.
Who can see what?
Only what each person is allowed to see. Detail about an individual is limited to the people your policy names, permissions are checked before every answer, and every question is recorded.
Will it act on anything about a person on its own?
No. It raises a risk and proposes a plan. Anything that touches an individual waits for HR and legal, 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 people events: a key departure you learned about too late, a certification that lapsed before anyone noticed, and a bottleneck you only saw under load. What did your own records 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 key-person risk 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)