01 · What we do directly
The part software can't do
What to feed it first, how to resolve the contradictions it finds, and how to turn a governed archive into the proposals and decisions it was built to support.
The kit gives anyone the structure. The judgment about what goes in it is the work: what is canon and what is superseded, which figure to trust, which client material can be repeated and which never can. That part is done with you, on your material, on your machine.
Then there is the second half: once the vault holds your judgment, software can act on it. That is the automations work below, and it is the same discipline pointed at your week instead of your archive.
02 · Three engagements
A ladder, not a menu
Each one is the natural next step from the last. The Diagnostic is the place to start.
The Intellectual Capital Diagnostic
The first engagement. We read what you have already written and tell you, in writing, what is in there: what you still stand behind, what has gone stale, where your own material contradicts you, and what it would take to make it usable.
The Intellectual Capital Build
The full system: your accumulated material turned into a governed, AI-accessible vault on your own disk, with the ingestion, retrieval and governance rules set for your practice. You finish able to run it yourself.
The Advisory Retainer
For a client already running a vault. Bounded, ongoing access as the archive grows and the questions change: new sources, new contradictions, the periodic check that the thing is still true.
For field-service businesses, a Runbook comes with it. An operating manual for the office, covering phones, dispatch, estimates, reviews and the Monday numbers. It ships into the vault already written and is then corrected, procedure by procedure, at the desk it belongs to. How Runbooks work.
03 · Custom automations
Software for the part you do by hand
A governed vault is worth more when something runs on it. We build that something: agents, pipelines and small internal tools, on your machine or in your own accounts, and you own what we build.
An agent that knows your canon
A Claude plugin or skill set built for your practice: your templates, your rules, your positions. Drafting a proposal or a report starts from what you have already decided instead of from an empty page.
The pipes into the vault
Material arrives from where it already is (mail, Drive, transcripts, whatever the system of record is), gets classified and filed on the way in, and stops being a cleanup project you keep postponing.
The jobs that run on a schedule
The weekly reconciliation, the digest, the follow-up list, the check that nothing has gone stale. Written once, run by a machine, reported to you with what changed.
One-off internal tools
A small piece of software for a job no product sells. Built to run where your material lives, handed over with the source, documented in the vault like everything else.
The rules do not change for automation. It runs on your machine or in your own accounts, we take no copies of your material, and anything it drafts is a draft until you say otherwise. Automation earns its place by removing the typing, not the judgment.
04 · How it starts
With a conversation, not a rate card
We don't publish prices. Every archive is a different size and a different shape, and so is every job worth automating. We would rather quote you against yours than against a table.
Write to us with what your body of work is, what you would want to ask it, whether any of it is someone else's confidential material, and the one task you would hand to a machine tomorrow if you could. If it isn't a fit, we'll say so in the first reply.
05 · Fit
Who this is for
Written for
- Independent consultants and advisors whose practice runs on accumulated judgment
- Testifying experts whose standing rests on the consistency of opinions given over decades
- Boutique firm founders whose IP is the asset
- Owner-operators of a field-service business whose office runs on procedures nobody has written down
- Anyone already running a vault who keeps doing the same task by hand every week
Probably not for
- Work that doesn't accumulate. If each engagement leaves nothing durable, there's no body of work to govern
- A corporate buyer with vendor onboarding. We work with the individual whose judgment it is
- Anyone who wants the archive uploaded somewhere and searched. It stays on your machine, or it doesn't happen
- Automation of a process nobody has written down yet. The procedure comes first; a machine repeating an unexamined habit is the wrong kind of fast
The thinking behind this. Both halves of this page, the governance and the automation, come out of one argument about what a body of work has to be before software can use it. The whole argument is published: Your Archive Is Not a Memory.