Under the surface
How it is built
Most of what makes our Leads worth having sits below the surface. Here are seven pieces of the engineering behind them, drawn plainly.
01
Our Leads are educated, then examined, before they take charge of anything
Our Leads do not arrive knowing your business. Each one studies a canon first: the methodology it will lead by, and whatever your organization has written down about the way you actually work. Then it sits boards. The questions are named and specific, the marking is kept, and the result goes on a register anyone can read.
A Lead that fails its boards is not certified, and one that is not certified does not take charge of anything. When a new version ships there is a supervised period before full practice resumes, the same way a person returning to a role is watched for a while.
02
Every reply is checked three times, and the first check can stop it
The first check runs while the reply is still being written, and it can stop that reply from ever reaching you. It watches for the things that must never happen: personal information going somewhere it should not, a regulated line being crossed, a price being quoted that nobody approved.
The second check reads the same reply once it has gone and writes up anything that looked wrong. It is slower and more careful, because it is not holding anybody up. The third runs once a day. AuditLead reads every finding from the day before and reports the pattern rather than the incident, which is the difference between knowing a thing went wrong and knowing why it keeps going wrong.
03
Our Leads remember your organization between engagements
Most AI forgets you the moment a conversation ends. Ours does not. Who decides what, where the resistance sits, which arguments have already been had and settled, what was tried two years ago and did not work: that carries across engagements, and across the Leads who share your work.
This is the part that compounds. A Lead you have worked with for a year is worth considerably more to you than the same Lead on its first day, and none of it is sold back to you as an upgrade. It comes with the license.
04
Your data is fenced off inside the database, not by the application
Separation is not a filter in the application code that somebody could one day forget to apply. Every row carries its own policy, and the database checks it on the way in and on the way out. We sort data into six classes, from published methodology through to personal information, and each class has its own rule about who may see it.
The practical consequence is that your organization cannot read another, and we cannot quietly widen that. Widening it means changing a written policy that can be read and argued with.
05
One record surface, so nothing about your engagement is half-seen
People, projects, impacts, actions, decisions, and evidence sit on one surface instead of being scattered across dozens of separate tables. It is an unusual choice and it is a deliberate one. Our Leads can read the whole picture of an engagement in a single pass, rather than stitching it together from fragments and quietly guessing at the parts that did not come back.
Measurement data is the one thing we keep apart. It grows fastest, it is read differently, and it has none of the relationships the rest of it has.
06
Convenor puts the work in front of whichever Lead it belongs to
You should not have to know which of the Leads owns a question before you are allowed to ask it. Convenor takes what you need, works out whose discipline it falls in, and hands it over. It facilitates and it routes. It does not scope the work and it does not decide the answer.
Where a piece of work crosses two disciplines, the Leads involved share what they have learned about your organization rather than each of them starting cold and asking you the same questions again.
07
Change is priced the way an asset is priced
Change work is usually reported as a list of activities and a color. We price it instead. Each impact carries a value with a worst case and a best case, mitigation is tracked as cumulative return, and organizational momentum runs through a stochastic oscillator.
That oscillator exposes two lines worth watching: the floor where leadership buy-in gives out, and the ceiling where the organization stops being able to absorb any more. It reads like a trading terminal because the questions turn out to be the same questions. This method is patent pending.
Who answers for it
A Lead is responsible for its work; a human is always accountable for it. Nothing above changes that, and none of it is meant to. The engineering is there so the responsibility a Lead carries is one you can actually inspect: an examination you can read, a check that leaves a record, a boundary written as policy rather than promised in a sales meeting.