the engagement
One conversation, one readout, one loop, one handover. No retainer that never ends, no deck of recommendations — a running system and the keys to it.
fig. 01 — discovery, readout, first loop, keys. The loop back happens on results, not on contract.
step 01
Ninety minutes of questions asked out loud — how it actually happens today, who it depends on, what it eats. Scored while you watch; readout delivered before the next morning.
step 02
Usually the map core; sometimes the top-ranked adjacent loop. Built embedded — inside your systems, next to your team. Scope is three rows: input → output → replaces. Anything outside the rows is the next loop, not scope creep on this one.
step 03
Code, gates, documentation your team can extend, and an operator who runs it without us. The engagement is designed to end — that is the proof it worked.
Billed hourly, plainly: one rate agreed up front, sliding with scope and commitment — an estimate before work starts, hours visible as they land, a cap you set. The first conversation and the readout cost nothing. Want more loops after the first? That's the loop engine: reserved hours each month at a rate that rewards the commitment. It's earned, never assumed.
Yes — and you should own it either way. The question is whose quarter it costs: your builders', pulled off your offering, or an embedded operator's whose whole job is this. Either way your team runs it afterward; the difference is what your best people were doing during the build.
Your people — and that's a deliverable, not a hope. Every organization has a drawer of internal tools nobody maintains; loops stay alive because the engagement ships an operator, gates, and a specimen page, not just code. Training the person is half the work.
Keep it. The suite stays the system of record; loops ride on top of it. What stops is paying people to compensate for its gaps by hand.
It doesn't. Loops run inside your systems with the narrowest access that works — read-only wherever possible, human sign-off before anything sends or publishes. Even the discovery form on this site never transmits anything.
That's the most common sentence in a discovery, and it's fair: by the time a team gets one tool under its thumb, the ground has moved again. Keeping up is a full-time job — which is exactly why it shouldn't be your team's second job. You bring the problems; staying current is mine.
That's the opportunity, not the objection. Your competitors aren't either — the first firm in a category to run its go-to-market as systems takes ground that is expensive to retake. The method doesn't care what you sell; it cares that you have offerings, audiences, and too little time.