How bad is your tech debt, really?

You get your full result, then a short sequence of emails matched to your zone — what teams in your situation usually do next. Unsubscribe is one click. Nobody calls you unless you book a call yourself.

No. The zones are fixed before you answer — your score is the sum of your answers, nothing else. If you land in Green, the result says keep doing what you're doing, and the only link you'll want is a newsletter.

It maps your symptoms. It can't see causes, because it never reads your code. But self-reporting is more honest than it sounds. When you pick 'we have areas nobody wants to touch,' that's data no static analysis tool will ever give you.

That's the best time to run it. Most teams we work with aren't broken — they're healthy companies whose codebase is slowly falling behind their ambitions. Catching Yellow before it turns Orange is the whole point of measuring.

Please do. Comparing results is the interesting part: when the CEO and the CTO score the same codebase two zones apart, that gap is a finding in itself. Same link, separate runs.

No repo access, no metrics dashboard, no prep. If you can answer 'how long does a medium feature take from spec to production,' you're ready.

It can't read your code, so it can't tell you what to fix first or what the fix costs. That's what a technical audit does — ours start at €4,000 and end with a written report and a prioritized recovery plan. But the scanner first. If your result says you need more, you'll know.