Self-reported
One person's read of the system, not the role-based interviews a diagnosis compares against operating evidence.
Built on the KIHON frameworkStrain Check
A free Strain Check that shows where your commercial system is breaking down.
Ten questions. Two minutes. A directional score and the area carrying the most strain, instantly. A first read, not a diagnosis: nothing is stored and nothing is sent.
The KIHON framework scoring · about two minutes · nothing stored
Question 1 of 10
Our reps have the territories, tooling and quota structure they need to do the job without working around the system.
Go deeper
Need a deeper, professional read?
The two-minute check gives you a direction to look in. The Diagnosis delivers the cause named, the cost priced at your own rates, and a sequenced roadmap, in six to eight weeks, at €12,000 flat.
Explore the DiagnosisWhat the score is not
A direction to look in, not a finding to act on.
Ten self-reported answers can show where strain is concentrated. They cannot separate a structural cause from a busy quarter, and they cannot price anything.
Relative, not absolute
It shows which area is carrying the most strain compared with the others, not how much any of it costs.
Private
The answers stay in your browser. There is no submission step and no record kept on our side.
What to do with it
Four honest responses to a result.
A directional read is only useful if it changes what you do next. Three of these four cost you nothing, and one of them is to do nothing yet.
Act internally
Where the strain is concentrated in one named handoff or one missing owner, the fix is often an internal decision rather than an engagement. Read the area the check flagged, name the owner, and see whether it moves.
Establish the cause
Where the pattern repeats across roles and you cannot separate structure from effort, that is what a Diagnosis reads. It ends with a figure the evidence can defend, or an explicit gap where it cannot.
Design the system first
Where the answers describe something that has never been designed rather than something that has drifted, there is no pattern to read yet. Build makes the first operating choices explicit.
Do nothing yet
A low reading is a legitimate result. So is a high reading on a system that has just changed shape and has not settled. Waiting for the pattern to repeat is a decision, not an absence of one.
Either way the check is the start of a conversation, not the end of one. It cannot price anything, and it does not become evidence by being repeated.
FAQ
About this self-check.
Is this the same as the full Diagnosis?
No. This is a ten-question self-read based on your own impression of the system.
Do you store my answers or my email?
No. Nothing is saved, logged or sent anywhere.
What if my score comes back low strain? Does that mean nothing is wrong?
It means nothing you were asked about points to acute strain, which is a legitimate result. The costs worth finding at that level tend to be the quiet ones, growth that never happened rather than deals that visibly broke.
Can I retake it if my answers do not feel accurate?
Yes, the check restarts at any time with the button on the result screen. It is a self-read, so a second attempt with more considered answers is a reasonable thing to do.
Get started
Go deeper than the score.
Discuss what the result may indicate, where its limits are and whether the next step should be Build, Diagnosis or no engagement at all.
Discuss the result