01
Survey
A short written brief from you, then a working session. Code, contracts, and the political map if it affects the build. The output is a one-page reading of what is actually true.
Approach
Read the system. Name the risk. Then build.
The sequence is the product. Order matters here because skipping a step is how teams buy the wrong platform and call it strategy.
02
Decision
Options with costs, not a single “recommended journey.” You pick the bet. Farrukh will say when the cheaper path is the honest one.
03
Build
Scoped delivery with visible checkpoints. AI work includes evaluation. Web work includes the content and ops path, not just the pretty route.
04
Handover
Docs your team will actually open, a backlog they can own, and a clean exit. Retainers exist for when you still want a named person on call — not by default.
No twelve-week alignment theatre.
Working rules
- Write it down Decisions live in a note, not in a call that evaporates.
- Show the cut If scope has to shrink, you see what was dropped and why.
- Refuse theatre If the problem is people or process, the report will say so.