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

use cases

Customer retention, seen months before the renewal.

Every customer relationship, on one current record - the early warning signs joined months before the renewal, and every client action held for the account owner.

“We find out an account is at risk when the cancellation arrives. Growth means hiring more account managers.”

§ 01 Is this you?

Is this you?

  • We find out a client is unhappy when the cancellation arrives, not when the trouble starts.
  • When our main contact leaves a client, nobody on our side hears about it for weeks.
  • The full picture of an account lives in two or three people's heads, and in the meeting before the renewal.
  • The standard price rise goes out to customers we have been letting down on service.
  • Every time we grow, the answer is another account manager.

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 main contact leaves the client Someone notices weeks later, if at all, and the account drifts without a champion. The departure is read alongside falling usage and a quiet inbox, and the account owner has the risk, the history and a next step months before the renewal.
The renewal comes up The standard uplift goes out on schedule, whatever the service record says. An uplift on an account with service breaches and ageing invoices is held, and the owner is asked to call first.
A former champion moves firm The relationship is lost to somebody's memory. The move is spotted, the history travels with it, and an introduction is drafted for the owner to sign.
Who has the whole picture Sales, service, delivery and finance each hold a slice. The whole account is assembled only in meetings. One current record of every account: its contacts, usage, service, invoices and contract, with its owner.
§ 03 What you would see

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

What you would see

risk note

Account at risk: sponsor gone, usage falling

what changed
The sponsor who championed the deal has left the client, usage has drifted down across the quarter, and the account has gone quiet.
why it matters
None of these would justify a call alone. Together they describe an account at risk, months before the renewal window opens.
history
How the account was won, who else you know there, and what was promised at the last renewal.
recommends
Find and meet the new decision-maker before the renewal conversation starts.
how sure
Sure of the signals. Less sure how the new contact sees you.

recommend routed to the account owner

renewal hold

Renewal uplift held: service in breach this period

what was queued
The standard price rise at renewal.
why it is held
Repeated service-level breaches this period, and invoices on the account ageing.
recommends
Call the customer first, and consider a credit before asking for more.
sources
The service tickets, the breach log and the ledger entries, each linked.

recommend uplift held, owner asked to call

warm introduction

Former sponsor, now an executive at another firm

where it came from
A public filing and a press mention.
history
Their years with the account: what they bought, what went well, who they worked with.
what it holds
An introductory note, drafted in the account owner's voice.
owner
The account owner who knew them.

draft drafted, held for the account owner's signature

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 Contacts leaving, usage changing, tickets stalling, invoices ageing and renewals coming due, in the systems where they already land.
  2. 02 it connects Each signal to the account it belongs to, and each account to its contacts, its contract, its service record and its owner.
  3. 03 it judges Whether the signals together describe an account at risk, and what the customer is owed before they are asked for more.
  4. 04 it checks Every action against your rules: who may see which accounts, and what needs a signature before a client sees it.
  5. 05 it acts Within the permission you have granted: it notes, recommends, drafts, or acts where you allow it.

It reads from your CRM, service desk, billing and ledgers, product usage and email, and from public filings. It does not replace any of them, and nothing is migrated.

§ 05 What it runs on

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

What it runs on

01The record
Every account's contacts, contract, usage, service history and invoices, in one record with its history.
02Finding the answer
Answers about an account with their sources, or a plain "I can't answer that well".
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 CRM, service desk, billing and product usage, and public filings, from sources you have named.
06Who may see and do what
Who may see which accounts, checked before every answer.
07Agents and actions
Holding an uplift or drafting an introduction, only through actions agreed in advance, with the account owner named.
08Where people use it
Where the account owner reads the risk note, approves a hold or signs an introduction.
09Testing it on your own questions
Tested against your own past accounts, the lost, the saved and the surprises, 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 customer retention 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 of our top accounts have lost their main contact this quarter, and what did we promise them at the last renewal?”

It compounds

The account record it builds is the one cash collection, subscription renewals and project margins read too, so the same customer is understood the same way everywhere.

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.

Anything a client receives, from a price change to an introduction, waits for the account owner's signature, permanently if that is your policy.

§ 07 Where it starts

Where it starts

first scope
Your top 20 to 50 accounts by value or risk: the relationships that cost you most to lose.
how it proves itself
It runs at observe against your own past accounts first, one lost, one saved and one that surprised you, so you see what your record already held, and when, before it is allowed to do anything.
what it connects to
The systems you already run: your CRM, service desk, billing and ledgers, and product usage. Connectors are built for you, as part of the work. How it connects.
what you own
You own the result: the account record, the warning signs it watches for, the rules and the permissions, handed over to your team or run for you.
§ 08 Questions

Questions

Does it replace our CRM?
No. It reads from it, and from your service desk, billing and everywhere else the relationship leaves a trace. Your CRM stays where it is; the company brain joins what it holds to what it does not.
Is this a customer health score?
No. A score tells you an account is red, not why. Here the account owner sees the signals themselves, joined together, with the history and a suggested next step, and decides what to do.
Who can see what?
Only what each person is allowed to see. Permissions are checked before every answer, and every question is recorded.
Will it contact a client on its own?
No. Introductions, price changes and anything else a client sees wait for the account owner to sign, 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 accounts: one you lost, one you saved at the last minute, and one that surprised you late. What did your own record know, and when did you find out?

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 customer retention 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)