Plenty of organisations do not need a studio. They need two days of senior attention to settle an argument, confirm a hunch, or tell a board that the platform is fine and the problem is elsewhere.

We keep a small amount of capacity for that kind of work. It is deliberately separated from delivery, and we will say when the honest recommendation is to change nothing.

What you get

  • An answer you can act on this quarter Findings are ranked by risk and effort, with the three things to do first stated plainly on the first page.
  • Independent of the build We are happy for the conclusion to be that you need nothing, or that your incumbent supplier is doing fine.
  • Due diligence that looks at the real risks For investors and acquirers: dependency health, key-person risk, licence exposure, security posture and the true cost to run.
  • Leadership while you recruit A fractional head of engineering or design one or two days a week, including sitting in on your hiring loop.

How we work

  1. Frame the question

    A 60 minute call to agree what decision the work has to support and what evidence would change it.

    1 day
  2. Review

    Repository, infrastructure, documentation and process, plus interviews with the team doing the work.

    3 to 7 days
  3. Report

    Written findings ranked by risk, with effort estimates and an explicit list of what we could not verify.

    2 days
  4. Debrief

    A working session with leadership, and a follow-up call four weeks later at no charge.

    1 day

Deliverables

  • Written report with ranked findings
  • Risk register
  • Cost-to-run analysis
  • Debrief session
  • Four-week follow-up call
Case studies

Related work

Next step

Tell us what you are building

A 30 minute call is usually enough to tell whether we are the right studio for the problem. No pitch deck, no obligation.