How we work · 06
Standing capacity,
past the first build.
Direction, not
account management.
Founders’ direction on your roadmap. Workforce hours on demand for maintenance, evolution and new capabilities. Eval harness maintenance with new adversarial cases and regression alerts. Security and dependency updates with tested deployments. Quarterly architecture review with the senior engineer seat.
You hold: ongoing capacity, direct founder access and a maintained evals harness.
What a retainer here is not
Strategic direction, not account management.
The default consulting retainer degrades predictably. It starts as senior attention, then becomes a monthly call with someone whose job is the relationship rather than the work, and the hours get consumed by status reporting. It is a well-known failure mode and it is structural, not personal.
This one is built differently. The founders’ time goes on direction — what to build next, what to stop, where the architecture is going to hurt in two quarters. The delivery capacity is the same governed workforce that did the original build, so nothing is being re-learned. And there is a quarterly architecture review with the senior engineer seat, which is where the awkward findings usually surface.
Eval maintenance is the part clients undervalue at signature and value most by month six. A harness written a year ago is measuring a world that has moved — new adversarial cases, new failure modes, a new model version from a provider who changed something quietly. Regression alerting on the harness is how you find out from your own system rather than from a customer.
Scope is re-contracted, not stretched
Quarterly scope review is a condition, not a courtesy. Where the work has drifted from the original problem, we re-contract rather than absorbing it — unbounded scope is how retainers stop being defensible for either side.
What is in it
Five things, and an exit.
Monthly, rolling, cancellable with 30 days’ notice on both sides. The exit clause is in the engagement letter.
- DurationMonthly, rolling, 30 days’ notice
- DirectionFounders’ time on your roadmap, not account management
- CapacityWorkforce hours on demand
- MaintenanceEval harness, security and dependency updates, tested deployments
- ReviewQuarterly architecture review with the senior engineer seat
Founders’ direction on the roadmap
What to build next, what to stop, and what is going to hurt in two quarters. Strategic direction from the people who signed the original build.
Workforce hours on demand
Maintenance, evolution and new capability from the same governed workforce that built it. No re-learning, no handover to a team you never met.
Eval harness maintenance
New adversarial cases as the threat picture moves, and regression alerting so a provider’s quiet change fails your build rather than your customer’s experience.
Security and dependency updates
Applied and deployed with tests, not filed as advisories. Supply-chain risk reviewed as its own workstream.
Quarterly architecture review
With the senior engineer seat, against the standards corpus. Findings arrive with options and a recommendation, never as a bare question.
The two lists that matter
What you hold, and what we will not do.
Both are in the engagement letter before you sign it. The second list is the one worth reading twice — it is where most disappointment in this market actually comes from.
What you hold at the end
- Ongoing capacity, drawn down as you need it
- Direct founder access — direction, not account management
- A maintained evals harness, with regression alerting
- Security and dependency updates, applied and tested
- A quarterly architecture review, and a quarterly scope review
What we won’t do
- Retainers without quarterly scope review
- Work that drifts from the original problem
- Unbounded scope without re-contracting
- Junior-only delivery on retainer hours
- Engagements without an exit clause
The other thing it buys
Standing capacity is also the way into the Lab.
Working notes, prototypes and lab time are available to client partners under NDA — the six dossiers on the bench, red-teaming methodology, agentic governance models. A Feasibility Sprint is the usual first way in; a retainer buys the standing version.
See the dossier wall →Or leave it with your team
Team Enablement runs under this shape and is designed to reduce what you need from it — the gate is your team shipping the last increment without us.
What happens after handover?
Thirty minutes with a founder. Tell us what you have running and we will tell you honestly whether it needs standing capacity or just a maintained harness.
Rolling · 30 days’ notice on both sides · Reviewed quarterly