Technical Diagnostic

You suspect something is wrong. You just don’t know what exactly.

Your team is slow. Costs are climbing. The codebase is a mess — or so they tell you. You’re not sure if you need to rewrite everything, hire three more developers, or just make a handful of targeted decisions.

Before committing to a six-month engagement or a €50,000 project, you need a clear picture.

That’s what the Technical Diagnostic is for.

Who this is for

• CEO or founder without a CTO, who wants an honest external assessment before deciding what to do next
• CTO or IT lead who needs an outside perspective on risks and priorities — without the politics
• Anyone before a larger commitment — a Fractional CTO engagement, an Architecture Sprint, a funding round, or a strategic hiring decision

If you’re not sure where to start, the Diagnostic is the right starting point.

What gets done

Two days. Focused. No fluff.

Stakeholder interviews I talk to the people who know the system — your CEO, your lead developer, your ops team. Not a survey. Real conversations.

Architecture review I look at your actual system — code, infrastructure, integrations, processes. What’s there, what’s missing, what’s held together with duct tape.

Risk and technical debt identification Not a laundry list of everything that could be improved. A prioritized map of what will actually hurt you — and when.

Prioritized roadmap Concrete recommendations. What to fix first, what can wait, what to stop doing entirely.

Verbal debrief I walk you through the findings. You can ask questions. No death-by-slide.

What you get

• Written report, 10–15 pages — in plain language, not developer jargon
• Prioritized action list with effort/impact assessment
• Debrief presentation (remote or on-site)
• Clear recommendation on next steps: whether a Fractional CTO engagement, an Architecture Sprint, or something else entirely makes sense

The report is delivered within 48 hours of the engagement.

How it works

Before we start (30 min call) We talk about your context. What you’re worried about. What access I’ll need. If there’s an obvious mismatch, I’ll tell you upfront.

Day 1 — On-site or remote Stakeholder interviews. Review of existing documentation, architecture diagrams, codebase samples.

Day 2 — Analysis and writing I synthesize, write, and structure the report. You get a draft by end of day.

48h later — Debrief We go through the findings together. Questions, pushback, discussion — all welcome.

Investment

€3,500 — fixed price

Everything included: preparation, interviews, analysis, written report, debrief presentation.

Travel costs billed separately for distances over 50km from Utrecht.

No hourly billing. No hidden extras. One price, one deliverable.

A note on what this is not

This is not a rubber stamp. If your architecture is solid, I’ll say so. If it’s not, I’ll tell you exactly why and what to do about it.

This is also not the start of an upsell funnel. The Diagnostic stands on its own. If a longer engagement makes sense after, we’ll discuss it. If it doesn’t, the report gives you everything you need to act on your own.

Next step