A module. It needs the brain.
You explained it in March. In June it comes back the same.
The short version
The company brain already learns from what your team approves and edits. That is part of the core product, and this module does not add it.
What this module adds is a record a person can read: what changed, what the brain now believes, which approval or edit caused it, and who confirmed it. It makes learning explicit and reviewable instead of quiet. If you are content for the learning to stay quiet, you do not need this module.
1. The problem it is for
A small firm's growth is capped by its admin capacity, not its demand. Most of how a 5 to 50 person service firm runs sits in people's heads: which client gets called back first, which template is the current one, what a note in the system actually means. When that knowledge is corrected out loud, the correction lives for a while and then fades. Someone re-explains it a quarter later, and nobody can point to where the rule is written down.
Software that learns quietly has the same weakness in a different shape. If a system adjusts itself and shows you little, it is hard to judge whether it took the right lesson from a correction or the wrong one.
2. What the brain already does
The brain holds what it knows in three states. Working is understood but not confirmed. Canonical is confirmed with the owner: process, clients, history, decisions. Unresolved is where your systems disagree with each other.
It runs a loop: it reads, it proposes, a person approves at the gate, it acts, and it learns from what that person did. Approvals and edits already feed back into the brain. Read the company brain page for how that works before you consider any module.
3. What this module adds, honestly
This module sits on the last step of the loop, the learning step, and turns it into something you can look at. Four things become visible:
- A change record. What the brain believed before, what it believes now, and which approval or edit moved it.
- Where the confirmation happens. Canonical context is confirmed with the owner either way. This module gives that confirmation one place to happen and a name against it, so you can see who agreed to what.
- A queue of what is waiting. The things the brain has understood but nobody has confirmed yet, in one list instead of scattered through the work.
- The disagreements, kept in view. The unresolved list is where your systems contradict each other. It tends to be uncomfortable reading, which is the point of it.
If something confirmed turns out to be wrong, a person can unconfirm it, and it sits back in working until someone confirms it again.
4. What it does not do
- It needs the brain under it. Modules are bought one at a time, and a module without the brain has no context to work from. There is no record for this one to write until the brain is in place.
- It does not teach itself in the background. A person confirms what becomes canonical. Actions that reach a client or a system of record wait for approval, and that rule does not change because a module was added.
- It does not learn from other firms. Each firm's brain is sealed. What travels between firms is a benchmark of what good looks like in your trade, not anyone's data.
- It does not replace the install week. Connecting, mapping and baselining still happen first.
- It does not come with an accuracy figure. We have no customers yet, so any number we quoted you there would be invented.
5. What a baseline typically turns up
These are the figures we estimate a baseline turns up in a firm of this size. We have not run your install, so read them as an estimate of a starting point, not a promise about your firm. Your own numbers get measured in the install week and written down before anything is automated.
- 34% of submissions with no follow-up in five days
- 22 dormant client relationships
- 3.2 day average response time
- Around 31 admin hours a week
6. What it costs
The module is $750 per month, added to the monthly brain. The brain is priced by staff count, with a one-off install.
| Staff | Install | Brain, monthly | This module |
|---|---|---|---|
| Up to 10 | $1,500 | $1,000 | +$750 |
| 11 to 25 | $2,500 | $2,000 | +$750 |
| 26 to 50 | $4,000 | $3,500 | +$750 |
More than five source systems adds a day and $500 to the install, and we say so during scoping rather than on the invoice.
We do not price per seat. We are selling you less admin work, and a seat licence would charge you for headcount and bill you more for succeeding at the thing you hired us for.
For the first five design partners, install is half price and the brain sits one band down for 12 months.
If you want a straight answer on whether this module earns its $750 per month in your firm, tell us how the work moves today and we will tell you which parts of it we would leave alone.
A module on its own has no context to run on. The brain is the thing you buy first, and this one is $750 per month on top of it.