Where Does Your Engineering Org Actually Stand?

You now know CRAFT Method. Over six days you've seen all five practices, why their order is fixed, and what each one closes. That knowledge is worth something — most engineering leaders can't name a single structured practice for AI-native development, and you can name five.

But knowing a method and governing with it are different things, and the gap between them is measurement. A CTO who has read about the five practices has a vocabulary. A CTO who has scored their organisation across all five has a diagnosis — a specific archetype, a named weakest sub-practice, and a defensible answer when the board asks how AI-assisted development is governed here. The first survives a conversation. The second survives scrutiny.

The reason the five practices are a method and not a checklist is the order. It is a dependency chain, and each link only holds because of the one before it.

CRAFT Method scores an organisation from 0 to 100 and places it in one of five archetypes. Read these and place yourself honestly — your gut already knows which one you are.

Of the organisations already using AI in operations, only about 14% have enterprise-level AI governance (Pacific AI 2025). Almost everyone is shipping AI-assisted code. Almost no one can govern it at the level a regulator — or a board — would recognise. If you're not yet in that 14%, you're not behind the curve. You're on it.

And there's a clock. The EU AI Act's high-risk obligations become enforceable on 2 August 2026, with fines up to €35M or 7% of global turnover. Article 12 logging is architectural — it captures events as they happen and cannot be reconstructed after the fact. If you start building your governance evidence after the deadline, you have already missed the evidence.

Two facts, read together: almost no one is governed, and the window to become governed without scrambling is measured in months. The organisations that move first aren't the ones with the most AI. They're the ones who measured where they stood while there was still time to act on it.

The diagnostic gives you a score. The debrief makes it actionable. In 30 minutes on a call with me, we cover four things.

The Full CRAFT Diagnostic and the live debrief are listed at €1,500-2,000. During the 2026 launch period, they're free.

That's a deliberate choice. CRAFT Method is early-stage — the method is proven, the diagnostic is built, and what I want now is to run it with real engineering organisations and learn from every debrief. So the launch cohort gets the full diagnostic and my time at no cost. In exchange, I get to sharpen the method against real orgs. Capacity is genuinely limited, because I run the debriefs myself. No fake countdown — just the real constraint that when the launch cohort is full, it's full.

CRAFT Method was not designed in a boardroom. It was forged by actually building production software with AI, every day, for months — FIKR Space, a complete startup ecosystem, solo founder plus AI. CRAFT Method is the method. FIKR Space is the proof. Same founder, separate businesses. Every practice in this course maps to a real artifact in that codebase — which is why the diagnostic asks the questions it does.