Key person dependency
Your company shouldn't grind to a halt when someone is away.
You included. I review your structure, show you where everything rests on one person, and help you spread what they know: written down, shared, up to date.
3 to 5 minutes · No credit card needed
The problem
Who's irreplaceable in your company?
Ask the question out loud. The names come straight away; yours, often first.
The bottleneck owner
Every quote, every invoice, every call goes through you. The team waits, and you never look up any more.
The one who knows
Lina is the only one who knows how to run payroll. The day she leaves, the company finds out what she was doing.
The client who follows someone
The relationship rests on a salesperson, not on the company. They leave; their clients think twice about staying.
The company that won't sell
A buyer, an investor, a bank all look at the same thing: what holds up without you.
What you're looking for
A company that keeps running, even when someone is missing.
- Knowing where the dependencies are, named, in order of urgency
- What the key person knows, written by them, before they leave
- Responsibilities shared out, with up-to-date job descriptions
- Decisions the team makes on its own, within the framework you've set
- A team that finds the answer without calling the only person who knows
How it works
From dependency to handover, in four steps.
I show you where everything rests on one person.
I review your strategy, your organisation and your Library. A process nobody has written down, a role with no job description, a decision that always ends up back with you: I name them for you.
The key person writes down what they know, with me.
I ask them the questions one by one, and I draft in their voice. A typical method often fits in one session.
You set who decides what.
Organisation, job descriptions, governance: whatever should be the rule becomes an Essential, which the whole team applies.
Everyone uses it, without you.
The team finds the answer in my app or in their own Claude or ChatGPT, with the source cited. Documents due for a re-check come up in the Review.
An example
“What am I missing to be able to delegate?”
I answer about your company, not in general: what isn't written down, what has no owner, what always comes back to you.
The proof
See for yourself.
What's missing, named
In the demo, Klaris Digital has written eleven job descriptions out of fifteen, and not yet its invoicing. I recommend them at the top of the Library.
Who does what, written down
An organisation with its roles, responsibilities and job descriptions, which everyone can read according to their permissions.
It all belongs to you
Strategy, organisation, Library: as PDF, Word or Markdown, at any time. For a buyer, a bank, a new partner.
Your questions
Where do I start?
With whatever stops the day someone is missing, and that the company needs every week: often invoicing, payroll, relationships with big clients, or your own decisions. I show them to you by reviewing your structure.
Will the key person play along?
They don't have to write everything alone: I ask the questions and draft, they correct. Their name stays on the document, and nobody calls them on holiday any more.
What if the dependency is me?
That's the most common case. We start with your direction: strategy, goals, organisation, in a 20 to 30-minute session. Whatever the team knows about where you're heading, they no longer need to ask you.
Does it help to sell or hand over my company?
A company whose strategy, organisation and methods are written down is quicker to understand. Everything can be exported, at any time; the valuation itself remains a matter for your advisers.
