design partners the first few
The first estates this runs on shape what it becomes.
The engine is gate-checked on a synthetic estate and has not yet run on a real one. A handful of operators will change that — and in return they get immediate value on their own network, and direct influence on a product designed around their real constraints rather than our assumptions.
This is a learning system, not a pipeline. We are looking for a few estates, not many, and we would rather say no in week zero than disappoint in week four.
0100 who it is for
A complex estate, a live reason to look, and someone who can open it read-only.
0200 what a design partner gets
Immediate insight, lower transformation risk, and a hand on the product.
See the real network
A read-only comparison of declared, configured and observed across the scope: stale rules, undeclared connectivity, segmentation gaps — each with its reason, in a pack you keep.
Value before transformation
No change window, no agent, no new architecture. An actionable baseline lands before anyone commits to a broader programme — and it is the baseline that tells you whether the programme is worth it.
Prioritise what to fix
Evidence-based decisions — keep, retire, investigate, redesign — in place of a broad clean-up programme nobody can scope. The retirement list is conservative by construction.
Reduce change risk
Dependencies, legitimate flows and unintended reachability, visible before the next change rather than discovered by it.
Shape the product
Workflows, integrations, evidence outputs and the order things get built — decided around your architecture and operating model, with founder and product attention that will not exist at scale.
Early commercial terms
A commercial relationship formed before the offer is standardised. The first technical validations are free for a few named estates; after them, the audit is a paid engagement, and we say that out loud too.
0300 what we ask, and what we are learning
Thirty minutes of exports. An hour a week. A straight answer.
What we ask
The exports: firewall policy, config archives, flow exporters pointed at a listener, and whatever inventory you have in whatever state it is in. A weekly hour with the champion. Honest feedback on what was useful, what was noise, and what blocked you. Published kill criteria, invocable by either side.
What we are trying to learn
Which gap creates urgency. Who actually owns the budget. What proof is credible to whom. How long data access really takes. Which outputs drive action and which get filed. What blocks production. Which unit of value feels natural to pay for.
We cap this at a handful of named estates. After them, the audit is always paid.
Everything produced stays with you whether or not the relationship continues. The audit is read-only, so there is nothing to roll back.
e000 End.DT6 deliver
Ask about it.
Use the form and write design partner in the note, or email. 30–60 minutes to look at which exports exist and whether the estate is a fit — for both of us.