What happens after you send a brief
Pick the draft that matches the work: Client Systems when you need something installed in an existing business (e.g. Odoo, an internal app, a dashboard, a growth loop), Venture Partnership for a partner-originated co-owned thesis, Advisory when you need a written go or no-go only. Plausible briefs get a reply from this inbox within 2–3 business days, next steps, or a direct no-go with the reason. No chase sequences.
Brief review
2–3 business days
Fit call or no-go
Not a free pitch meeting
Validation or stop
No billing if gates fail
Client Systems path: Fit Read → Decision Diagnostic → Install. Fit Read: A short written read: fit, not fit with reason, or what to clarify, plus a prioritized list of what is broken first. You keep that list either way. Paid stages stay closed until a seat opens; every open stage has a written stop. Venture Partnership briefs are for co-owned theses only (not Client Systems). Decision Diagnostic is not open currently. No retainer tail.
Method terms used here
- RECON
- Discover + Validate: decode the reference model, test the gap, decide with evidence before build.
- RAID
- Build + Launch + Scale: execution only after gates clear; weak evidence stops the work.
- Model Transfer Evaluation
- Venture Partnership only: a scoped 2–4 week engagement that turns a co-owned transfer thesis into a go/no-go memo with a locked proof metric. Not used for Client Systems installs.
- corridor
- A proven model paired with an underserved market it has not reached yet.
- Autonomy Ladder
- Assist, draft, execute-with-review, execute: autonomy expands one rung at a time when eval evidence supports it.
- five-point loop test
- Reach, conversion, payback, repeatability, and decay: five criteria before a loop earns budget.
- Decision Diagnostic
- Client Systems paid entry (when open): map the bottleneck, architecture, and go/no-go criteria before open install scope. Separate from Model Transfer Evaluation.