An estate nobody is still tending starts describing a company you used to be, and it does it quietly, while continuing to work. So the subscription is one thing: the platform, and the standing work that keeps it true as your operations change.
What the subscription covers
The running estate, and the work of keeping it right — lanes added as each earns its place, directives revised when the operation moves under them, autonomy widened against decisions you have already watched it make.
What implementation costs
Scope determines the fee. A single workflow and a multi-lane operation are different pieces of work, so we price against your operations rather than a list. There is no list price to look up and none is being kept from you.
Not a hypothetical risk register. These are the three failure modes that make custom automation a liability by month nine, and every one of them is a maintenance failure rather than a build failure — which is why the ongoing work is part of what you buy rather than an aftercare option.
1 of 3
You reorganise, change suppliers, add a line of business. The prime directive still describes last quarter’s company, so the estate keeps making last quarter’s decisions — correctly, every time, which is exactly what makes it hard to notice.
What answers itRevising the directive is a standing act with an owner, not something that happens when somebody finally complains.
2 of 3
Thresholds set once during a launch go one of two ways. Either everything reaches you and you stop reading, or nothing does and you stop trusting it. Both end with a system nobody looks at, and the second one ends there quietly.
What answers itWhat escalates is retuned against decisions you have actually watched it make, and widened only where it has earned it.
3 of 3
Why a lane exists, why that approval is two-key, why that supplier is an exception — it lives in somebody’s head until it does not, and then the estate is a black box nobody dares change.
What answers itThe reasoning lives in the estate’s own memory and its event history rather than in a person, which is the one answer to this that does not depend on staff turnover.
Five steps, in order. The first four get an estate running against real work; the fifth is the one that never finishes.
The workflows, the systems those workflows touch, and the decisions people are currently making by hand. We are looking for the place where the cost of the status quo is already visible to you, because that is where a first lane pays for itself.
What the estate is for, what it must never do, and which decisions always reach a person. This is the part that cannot be delegated to a form: a directive written by someone who has not seen your operation produces an estate nobody meant.
Personas, lanes, and connectors to your own systems, running on your own keys. Nothing is pointed at real work until the environment around it is sized, hardened and reversible.
The early weeks are when escalation is miscalibrated and everyone is still deciding whether to trust it. We are there for that, tuning what reaches you, until the estate has earned the autonomy you choose to give it.
New lanes, revised directives, personas retired and added, as your operations change. This is the half that does not end, and it is the half the subscription is really for.
The product is the estate. Standing one up in a real company needs three more things, and they are the part of this that is genuinely consulting work.
The environment the estate lives in: sized, hardened, reversible, and yours. An agent estate is ordinary infrastructure with unusual consequences, and it earns the same care as anything else you run.
Departments, ownership, cadence, and what "done" means in each. An estate needs an org model to staff, and most companies keep theirs in people’s heads. Writing it down is most of the first phase, and it is useful to you whatever we build.
The delivery discipline around every later change: tests that fail before a fix exists, review by someone who did not write it, and a way back that is in place before it is needed. It is what keeps month nine from breaking what month two got right.
These are not a methodology we wrote for a brochure. They were extracted from a live multi-app venture operation — our own — and generalized for customers. What we have never done is run this estate inside someone else’s organization, and you should hear that from us rather than discover it.
The closer
Every AI demo shows agents moving fast. Here the estate waited 15 min, because one decision was not its to make. Then a person answered — and the action ran, once.
Raised · 13:42
Priya would not decide this alone — 3 options, with a recommendation.
The chips are empty because the stream is: it records how many options there were and which one was recommended, never what they said.
The decision moved from manager to executive.
Held · 13:45 → 14:00
15 min
Nothing moved.
Nadia stopped and put the question in front of a person, and the estate waited 15 min for an answer. No lane went on without it.
Answered · 13:59
A person chose option 2 after 14 min.
It was the estate’s own recommendation. Both the advice and the choice are in the stream, so that is measured rather than claimed.
Armed by a person and executed by Nadia — two different hands, which is what makes it an approval.
Derived from 59 synthetic events, seed estate-day-1, against schema 1.0.0 — the same event contract the product emits. No event carries a content attribute, so nothing here is a transcript of anything an agent said. Read the whole day.
You subscribe to an implemented estate. Implementation is scoped against your operations; the subscription covers the platform and the iteration that follows.
If you can include these, the first conversation gets much further:
A person reads this mailbox and a person will reply — it is not a ticket queue. If it is easier, say when you are free and we will find a time.
A synthetic day in an estate, rendered from the same event contract the product emits — and the library of named roles it is staffed from.