Services
Four specialist services for organisations who need a clear picture — and the confidence to act on it.
For investors & acquirers
"The spreadsheet tells you what a company is worth. The engineering organisation tells you whether it can deliver what comes next."
Most M&A due diligence focuses on financials, product, and market position. Engineering — the function that will ultimately determine whether the integration succeeds — is often assessed superficially or too late. I help investors, acquirers, and leadership teams understand what they're actually buying before the deal closes.
Drawing on direct experience navigating M&A at Booking.com and Marktplaats/Adevinta, I assess engineering organisations across four dimensions: technical debt and platform maturity, delivery capability, leadership depth and team health, and organisational design and scalability.
What the assessment covers
This is for you if
What you can expect
Engagements typically run 2–4 weeks depending on organisation size. I work with a small number of clients at a time to ensure rigour and confidentiality throughout.
Start the conversation →For CTOs & VPs Engineering
"Most leaders have a sense that something isn't working. The hard part is knowing exactly what — and why."
Engineering organisations are complex systems. When delivery is inconsistent, morale is low, or alignment is elusive, the root cause is rarely what it first appears to be. This assessment gives you a clear, honest picture of where your organisation actually is — across delivery, culture, leadership, and technical practice.
I conduct structured interviews, observe team rituals, review delivery data, and synthesise findings into a diagnostic that leadership can act on. This isn't a survey or a framework checklist — it's a considered assessment from someone who has led engineering organisations through exactly the challenges you're facing.
What gets assessed
This is for you if
What you'll get
Assessments typically take 3–5 weeks for a single engineering department. Everything shared with me is treated with full confidentiality.
Let's talk →For leadership teams
"OKRs don't fail because people don't understand the framework. They fail because product, engineering, and commercial can't agree on what matters most."
Most organisations that struggle with OKRs aren't struggling with the mechanics. They're struggling with alignment — between functions, between levels, and between what the business says it wants and what teams are actually incentivised to do.
Having aligned OKRs across multiple product engineering domains at Marktplaats/Adevinta — connecting product, platform, and commercial goals across teams — I understand both the strategic and operational challenges. My approach is practical and facilitated: I work with your leadership team to design a system your teams will actually use.
What the engagement covers
This is for you if
What you'll walk away with
Typically a focused 4–6 week sprint aligned to your planning cycle, though longer partnerships are available for teams who want ongoing facilitation support.
Let's talk →For engineering leadership teams
"The teams that learn fastest are the ones where it's safe to be wrong. That doesn't happen by accident — it's built, deliberately, over time."
Psychological safety isn't a soft concept — it's the foundation of high performance. Teams where people feel safe to speak up, challenge decisions, admit mistakes, and give honest feedback learn faster, ship better software, and navigate change more effectively.
I design and facilitate practical, grounded workshops for engineering leadership teams — not theoretical sessions about frameworks, but hands-on experiences that shift how people relate to feedback, difficulty, and each other. Drawing on direct experience building feedback cultures at Booking.com, Marktplaats, and Shpock.
Workshop formats
This is for you if
What participants leave with
Workshops are designed for groups of 6–20 and can be delivered in-person or remotely. I work with you in advance to tailor content to your team's specific context and goals.
Let's talk →