Engagements
Four ways to work together. Every engagement begins with a free briefing. From there: a Sprint, an Architecture engagement, or a hands-on Build engagement.
— I
Briefing
Free
Diagnostic conversation. Decide if systems architecture fits the problem, and walk away with a written read either way.
Diagnostic conversation Structural read on the problem Mutual go / no‑go decision 1‑2 page diagnostic memo
Recommended Start
— II
Sprint
Fixed-Scope
One defined deliverable in a tight box. A decision-ready artifact — 8-20 pages, sharp enough to act on.
One defined deliverable, agreed in writing Two sync checkpoints 8-20 page output Post-delivery Q&A window
— III
Architecture
Fixed-Scope
Full systems specification: decision graph, ownership maps, dependency layout, implementation plan. Built to operate, not just to read.
20–60 page systems specification Decision graph & ownership maps Scope, dependency map, risk register Two revision cycles built into the scope
— IV
Build
Retainer
Hands‑on implementation alongside your team. Engagement ends when the system is operating without us in the room.
Everything in Architecture, plus implementation Hands‑on build alongside your team Continuous validation against the spec Operating handoff documentation
