Technical orientation
One focused conversation
- A short brief read in advance
- A focused call on the immediate question
- A short written note on the sensible next move
No build, source or project-content access.
Start herePricing
Every engagement has a defined purpose, fee and boundary. Start with the smallest useful decision; move into deeper work only when the evidence says it is warranted.
Studio work
Early steps use a brief, a call and evidence you choose to provide. Source code, project content and a working client environment are reserved for a full-access engagement.
One focused conversation
No build, source or project-content access.
Start herePreparation, working session and written recommendation
For a bounded engineering choice, not a build review.
Session detailsOne consulting day
No repository, build or project-content access.
Discuss an evidence reviewTwo consulting days
No repository, build or project-content access.
Discuss an assessmentThree consulting days
No repository, build or project-content access.
Plan a reviewFive consulting days over 1–2 weeks
Full-access work is booked as a five-day engagement.
Review detailsBefore full access
The five days are for answering technical questions, not for discovering how the environment works. The required setup is agreed before the engagement starts.
If the agreed environment is not ready, the start date moves with it. Any work needed to prepare or repair that environment is scoped separately before it begins.
Larger engagements
Seven consulting days over 2–3 weeks
Build, cook, DDC, sync-to-playable, CI, code flow and the working day.
Review detailsFour consulting days over a committed ten-working-day window
A focused go/no-go view before full technical diligence.
Screen detailsFixed scope · typically 2–3 weeks
Technical delivery risk, capability, dependencies and cost to finish.
Diligence detailsNon-sterling figures are indicative only. Invoices can be raised in GBP, USD, EUR, SGD or THB by agreement.