Design partners
Paid, fixed-scope, founder-led work in the systems you already run. Checks agreed before anything starts.
FIG.1 · one engagement, start to decision amber = the branch we take if the checks fail
01 · Situations
Each card names a question rebuilt by hand, where its pieces sit today, and the honest reason it may not fit. Shapes of problem. Not proof of prior work in your sector.
You run technology or security for many client organisations. Each review restarts from scratch.
“What changed for this client, what did we promise, and what still needs attention?”
Where the pieces sit today
May not fit if AX0S must replace monitoring, ticketing, or a control framework.
The account record says one thing. The people doing the work know another.
“What did we commit to on this account, and what has changed since?”
Where the pieces sit today
May not fit if someone owns that record already and keeps it accurate.
A claim, file, or case passes through several hands. Status gets rebuilt each time.
“What is the status now, what supports it, and what changed since the last review?”
Where the pieces sit today
May not fit if it needs a certification or residency guarantee the proof register cannot evidence.
Several companies or locations, each with their own tools. One weekly review.
“Which commitments and exceptions need attention this week, and what proves each one?”
Where the pieces sit today
May not fit if the goal is standardising every system at once.
verified row on the integration register row in build no row yet, so mapping it is part of the first piece of work Register checked 2026-08-23
02 · First deployment
The right column is not a no. It is a not yet, with the one thing that would change it.
Good first deployment
Not yet, and what would change it
03 · The engagement
A design partner is an early customer. Not a reseller, a referral, or an integration partner.
You bring one question, one source, one owner who can approve read-only access, and an honest read of the result at the end.
Most first deployments involve at least one source we have not connected before. Establishing whether it can be connected, and at what permission scope, is part of the first piece of work.
Read-only at your source first. Writing back into a source system is a separate, reviewed decision, and it is not claimed here.
The first boundary
Both founders take the call. You leave with a connection map, or a straight no.