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

use cases

Product performance, read whole and proved fair.

Every product line, on one current record - margin, complaints and customer outcomes read together, a failing line caught before the quarter closes, and the proof that it is fair already written.

“Nobody can tell me which lines actually make money, or prove the product is fair when asked.”

§ 01 Is this you?

Is this you?

  • Nobody can say with confidence which of your products or services actually make money.
  • Finance sees the margin, the service team sees the complaints, and nobody puts them side by side.
  • A line you should have repriced or retired a year ago is still running.
  • The complaints keep coming back to the same products, and it takes a quarter to notice.
  • When someone asks you to prove a product is fair value, the evidence has to be rebuilt from scratch.

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
Complaints start to cluster Service logs them, finance sees the margin slip, compliance sees outcomes drift, and nobody is alarmed. The three are read together on the line, and a root-cause review is proposed with the pattern attached.
A margin erodes It is found when the quarter closes, and the decision waits for the next one. The owner gets the options, to reprice, restructure or withdraw, each with the numbers attached.
A fair-value review falls due The evidence is reconstructed under deadline from four different systems. The pack is drafted from what actually happened on the line, and held for sign-off.
Who has the whole picture Every function sees its own slice of a product. The line as a whole belongs to no one. One current record for each line: its price, its margin, its complaints, its customer outcomes and its fair-value evidence.
§ 03 What you would see

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

What you would see

product review

One line: complaints, margin and outcomes moving together

what changed
Complaints on one line are clustering, its margin is eroding and customer outcomes are drifting.
why it matters
Each team holds one of the three and none is alarmed. Together they show a line failing on fairness and on economics.
recommends
Open a root-cause review now, before a regulator or the quarter's numbers force it.
how sure
Sure the three are moving together. The root cause is what the review is for.
sources
The complaints log, the margin reports and the outcome records, each linked.

recommend routed to the product owner

margin options

A line whose margin falls quarter on quarter

what changed
Margin on the line has fallen each quarter, as costs rose and the price stayed where it was.
options
Reprice, restructure or withdraw the line, each with what it would earn and what it would cost.
owner
The product owner, with finance.
how sure
Sure of the trend. The options rest on current costs, which are stated.
sources
The finance system, the price history and the cost records, each linked.

recommend decision put to the product owner

fair-value evidence pack

Fair-value assessment due: one product line

what it holds
What customers paid, what they received, how their complaints were resolved and how their outcomes compared, drawn from what actually happened.
gaps
One quarter's outcome data arrived late. The reason is on the record.
owner
The product owner, who signs it before it is filed.
sources
The pricing, complaints and outcome records, each linked.

draft drafted, held for the product owner's sign-off

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 Complaints, margin and cost movements, price changes, customer outcomes and review dates, where they already arrive.
  2. 02 it connects Each one to the product line it concerns, so the line is seen whole rather than one function at a time.
  3. 03 it judges Whether movements read together mean a line is failing, whether it earns its keep, and whether the evidence that it is fair is complete.
  4. 04 it checks Every action against your rules: who may see what, and what needs a signature before it is filed or reaches a customer.
  5. 05 it acts Within the permission you have granted: it notes, recommends, drafts, or acts where you allow it.

It reads from your product, finance, complaints and customer service systems. It does not replace them, and nothing is migrated.

§ 05 What it runs on

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

What it runs on

01The record
Every product line's price, margin, complaints, customer outcomes and fair-value evidence.
02Finding the answer
Answers about a line with their sources, joining what finance, service and compliance each hold.
03The company manual
What fair value means for each product, and who owns each line.
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 product, finance, complaints and customer service systems.
06Who may see and do what
Who may see margins and costs, checked before every answer.
07Agents and actions
Drafting a review or an evidence pack, only through actions agreed in advance.
09Testing it on your own questions
Tested against your own past quarters 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 product performance 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 product lines have rising complaints and a falling margin at the same time?”

It compounds

The fair-value evidence it gathers is what compliance files, and the complaints it reads are the ones customer retention watches, so one record serves all three.

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.

Repricing, withdrawing a product and anything a regulator relies on stay behind a named person's signature, permanently if that is your policy.

§ 07 Where it starts

Where it starts

first scope
One product line or one segment of the range: the one you are least sure earns its keep.
how it proves itself
It runs at observe against your own past quarters first, so you see what it would have caught before it is allowed to do anything.
what it connects to
The systems you already run: your product and finance systems, the complaints log and your customer service records. Connectors are built for you, as part of the work. How it connects.
what you own
You own the result: the product record, the rules, the permissions and the way it runs, handed over to your team or run for you.
§ 08 Questions

Questions

Does it replace our product or finance systems?
No. It reads from them, and from complaints and customer service. Your numbers stay where you keep them; the company brain puts them side by side for each line.
We are not regulated. Is this still for us?
Yes. The margin half stands on its own: knowing which lines make money, and which ones the complaints keep coming back to. The fair-value evidence matters where a regulator asks for it, and is left out where nobody does.
Who can see what?
Only what each person is allowed to see. Margins and costs stay with the people entitled to them, permissions are checked before every answer, and every question is recorded.
Will it change a price or contact a customer on its own?
No. Repricing, withdrawing a line and anything a customer or regulator sees wait for a named owner, 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 lines: one you retired too late, one whose margin drifted for a year unseen, and one you could not prove was fair when asked. What did your own record 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 product performance 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)