A fixed-fee review and diagnostic for product engineering organizations with 25–80 engineers. I identify the few system-level issues causing delivery drag and give you a concrete 30-day action plan.
Growth was supposed to make delivery more predictable. Instead, roadmap commitments slip, managers are overloaded, planning feels heavier but less clear, teams are busy without moving faster, and product and engineering alignment gets worse.
You know something is off. The hard part is that the visible symptoms are rarely the real cause.
Offers
Not sure yet? Start with the Review. If you book the Diagnostic within 30 days, the full Review fee rolls into it.
€1,250 fixed
A fast outside read before committing to a full diagnostic.
Full fee credited toward the Diagnostic if booked within 30 days.
Core engagement
€6,500 fixed
A bounded diagnosis of why delivery slowed and a 30-day action plan.
What you get
The Diagnostic report is structured for leadership to act on quickly. It contains:
Best fit for post-product software companies where engineering grew, management layers appeared, and delivery became less predictable.
Typical fit:
This is not the right engagement if:
This is a bounded diagnostic. Sharp, fast, and specific.
Why me
Current operator. I lead engineering in a live scale-up environment. My perspective comes from the operating seat, not retrospective consulting theory.
Pattern recognition across engineering systems. I've spent 20 years across IC, management, and leadership roles in multiple industries. The same failure patterns repeat more often than founders think.
Real AI adoption experience. Over the past two years, I designed and ran three AI adoption pilots in a real organization. That experience matters because it connects AI to delivery, hiring, and team design — not just tooling.
Diagnostics are confidential by default. References from past clients are available on request, under NDA where appropriate.
I don't publish client work. Diagnostics are confidential by default — clients share sensitive operating reality, and that stays between us. Before you buy a diagnostic, you should know what you're getting. An illustrative example — not from a real engagement — shows the depth, structure, and voice.
See the sample →An operator case study on what three AI adoption pilots exposed about engineering operating systems — from inside a live scale-up, not from the outside.
Read the case study →The process is designed to stay bounded. Leadership involvement is concentrated, and interviews are targeted rather than open-ended. Most leadership teams spend 3–5 hours total across the 15 business days.
That is normal. I do not need a perfect metrics stack to identify operating friction. Interviews, planning artifacts, and structural patterns usually tell the story.
Only where it materially affects delivery, hiring, or org design. It is not forced into the output if it is not relevant.
You can execute the action plan internally, or we can discuss a short follow-on advisory engagement if there is a clear fit. I do not publicly offer ongoing fractional leadership work.
I do not take embedded or hands-on execution roles. My role is to diagnose the problem clearly, help set priorities, and support leadership decision-making where needed.
Contact
I take on a small number of engagements at a time. Expect a response within 2 business days.