What an engagement is
I embed a second brain into an organization. Not a licence, not a template, and not a product you configure yourself: a record built around how your company actually works, software workers that keep it true, and a dashboard that shows its state. The point of it is that the organization gets cheaper to run and easier to operate, because questions that used to cost someone a day stop costing anyone anything.
What does an engagement leave behind?
- An inventory of where decisions, money, clients and access actually live today
- A structure built for your organization, not lifted from a template
- Approved figures, each with a named owner
- Your own material turned into linked pages: one per client, deal, person and service
- Finance, clients, communication and spend brought into the same record
- The systems you already run, connected and tested against it
- Agents that file what arrives, update what changed and flag what contradicts
- A dashboard on a private address, regenerated from the record and never by hand
- Written rules: what goes in, who owns which figure, what nobody may touch
- Your team trained on it, recorded, and an audit of what the record found wrong on the way in
Why is it developed rather than installed?
Two organizations of the same size in the same industry keep their decisions in different places, disagree about different figures, and depend on different people. A template flattens all of that and produces something nobody trusts. So the structure is designed for your company, the agents are written for the jobs your company actually repeats, and the dashboard shows the state your company needs to see. That is development work, done by hand, and it is why I take a small number of organizations at a time.
How long does it take?
It depends on how much of the organization comes in and how much material already exists, so the timeline is named in your scope rather than promised on this page. What I do promise is that the scope, the timeline and the number arrive together within twenty-four hours of the ten questions, and that the timeline in it is the one I hold myself to.
What does it ask of my team?
Access, and one person who can settle a question. The rest is mine. Your scope names the hours it asks of you before you agree to anything, and that number is part of what you are agreeing to.
What continues after it is embedded?
A record nobody feeds goes stale in weeks, so the work does not end at handover.
- The agents keep running, so the record stays true without anyone maintaining it by hand
- Contradictions, stale facts and unowned figures surface as they appear, not at audit time
- New parts of the organization come into the record as they become worth having there
- I stay on it at the depth your organization needs, month by month
What is not included?
Custom software built on top of the record is a separate piece of work with its own scope and its own number. So is replacing a system you already run. I embed the record and the agents that keep it true; I do not rebuild your stack, and I say so before you pay rather than after.
How is the number arrived at, and why is it not on this page?
Because it is not the same number for two companies. It follows the size of the organization, how many parts of it come into the record, how much material already exists and what has to be connected. The ten questions are how I work that out without taking an hour of your time. The number comes back in writing with the scope, it is fixed for that scope, and if the work runs long that is mine to absorb. I do not discount.
What does it cost to change my mind?
Nothing, before you pay: the scope is written first and costs you four minutes to ask for. After that, a change you ask for is scoped and priced on its own, never billed by the hour.