Technical and product team coaching

Your engineers are good and the system around them isn’t: releases drag, quality wobbles, new managers are guessing. We coach your team inside their real work until better habits hold without us.

How we coach

We pair with your people rather than working around them. That means joining the code review, sitting in the planning session, and coaching the 1-1 as it happens. Advice from outside the work is cheap and mostly ignored. The goal is independence; a coaching engagement that creates dependence on the coach has failed.

Themes we coach

  • Engineering practice: TDD, BDD, continuous delivery, code review, architecture decisions
  • Product discovery and experimentation
  • Engineering management and the 1-1 discipline
  • Adopting AI and agentic workflows safely and effectively
  • Scaling from founding engineers to an organised function

Who it’s for

Engineering and product teams from 2 to 50, and the leaders responsible for them. Common triggers: a first-time engineering manager, a team growing past the point where heroics work, or an organisation that wants AI leverage without quietly lowering its engineering bar.

What comes next

Engagements grow into one another. Most clients arrive at one step and stay for the next.

  1. You are here

    Technical and product team coaching

  2. Technology judgement at board level, once the function runs without us.

    Board advisor

    Read more

Engagement shape

0.5 to 2 days per week, 3+ months. Often runs alongside a fractional CTO or bootstrapping engagement.

Start with a conversation

No pitch, just a conversation about where you are.