Leak Check

Two minutes to see where your profit is leaking.

Ten statements about how your company wins and keeps revenue. You say how true each one is. You get a score and the area under the most strain, on screen and in your inbox.

The check

Ten statements. Answer for your company as it is today.

Each one covers one of the six places a company leaks profit. Answer as you would to a colleague, not as you would to the board.

Question 1 of 10

Our commercial strategy is specific enough that teams can make consistent decisions without asking leadership to interpret it each time.

What the score is not

A direction to look in, not a finding to act on.

Ten answers from one person show where the strain is concentrated. They cannot tell a leak in the system from a busy quarter, and they cannot put a number on anything.

Self-reported

One person’s read of the company, not the interviews across roles that a Diagnosis checks against the records.

Relative, not absolute

It shows which area carries the most strain compared with the others, not how much any of it costs.

Yours, then ours

The answers stay in your browser until you ask for the read. Then they sit on your contact record, read by Cem, and deleted when you ask.

What to do with it

Four sound responses to a result.

A directional read is useful only if it changes what you do next. Three of these four cost you nothing, and one of them is to do nothing yet.

  1. 01

    Act internally

    Where the strain sits in one handoff or one missing owner, the fix is often your own decision. Read the area the check flagged, name the owner, and see whether it moves.

  2. 02

    Find the cause

    Where the pattern repeats across roles and you cannot tell the system from the people, that is what a Diagnosis reads. It ends with a figure the evidence can defend, or a named gap where it cannot.

  3. 03

    Design the system first

    Where your answers describe something that was never designed, there is no pattern to read yet. Build writes the first version down with you.

  4. 04

    Do nothing yet

    A low reading is a fair result. So is a high one in a company that has just changed shape. Waiting for the pattern to repeat is a decision.

FAQ

Leak Check FAQs.

Is this the same as a Diagnosis?
No. This is ten answers from one person, your own read of how your company wins and keeps revenue. A Diagnosis interviews the people, reads the records and puts a figure on the leak at your own rates.
Do you store my answers or my email?
The ten answers stay in your browser until you ask for the read. Then they are sent to Kihon's CRM with your email, so the read can reach you and Cem can see it before a call. You also receive Kihon Labs Weekly; every email carries an unsubscribe link, and the privacy policy says how to have the record deleted.
What if the score comes back as low strain?
Then nothing you were asked about points to heavy strain, which is a fair result. At that level the leaks worth finding tend to be growth that never happened, not deals that visibly broke.
Can I take it again?
Yes. The result screen has a restart button, and a second pass with more considered answers is a reasonable thing to do. Asking a colleague in another function to take it is more useful still.
Where do the six areas come from?
From the socio-economic approach to management, created by Henri Savall and developed with Véronique Zardet and the ISEOR team at Université Jean Moulin Lyon 3. The framework page explains how Kihon applies it.
Get started

Bring the result to thirty minutes with us.

You say what the check showed and what keeps repeating. We tell you what we would look at first, and whether the next step is a Workshop, a Diagnosis, Build, or nothing yet.

Book a strategy call