The De-Keying Roadmap | Stan Tscherenkow

The De-Keying Roadmap: take yourself out, in the order that does not break the business.

A buyer pays a premium for a company that runs without you and a discount for a job with your name on it. The work of removing yourself is the single biggest lever on your multiple, and most owners do it in the wrong order, pulling out of the wrong things first and breaking the business on the way out. This is the eighteen-month sequence that takes you out cleanly.

UseWork the tool now

FormatEighteen-month sequenced plan

Lever onYour multiple

Apply for advisory

Read the manual it comes from

The order you remove yourself in decides whether the business survives it.

The De-Keying Roadmap is the structured eighteen-month plan for moving the business off its dependence on you, in a deliberate sequence. Which relationships to transfer first, which decisions to delegate before which, what to document, and what to stop doing entirely, so that by the time a buyer looks, they are buying a company and not your personal Rolodex.

Everyone knows they need to do this. Almost no one knows the order, and the order is most of the difference between a clean de-key and a stall.

Pull yourself out of the wrong thing first and the business wobbles, the team panics, and you rush back in, which sets you back six months and teaches everyone that you are still the answer. The owners who de-key badly remove the visible things first and the load-bearing things last. The roadmap inverts that, so the business is provably standing on its own well before anyone runs diligence on whether it can.

Three phases over eighteen months.

Phase 01 · months 1–6

Map every place the business needs you.

Before you remove anything, you inventory the dependencies: the relationships only you hold, the decisions only you make, the knowledge only you carry. You cannot de-key what you have not named, and the map is usually longer and scarier than you expect.

Phase 02 · months 6–14

Transfer in the order that holds.

Relationships before decisions, decisions before knowledge, with the load-bearing dependencies moved while you are still there to catch a drop. This is the sequence most owners get wrong, and the roadmap is mostly about getting it right.

Phase 03 · months 14–18

Prove it by stepping back.

You deliberately step out of things and watch whether they hold. The gaps that show up here, with months to spare, are the diligence findings you would otherwise discover in front of a buyer. Better to find them now.

For the owner who is still the company, and knows the buyer will notice.

If the honest answer to "what happens to this business if you disappear for ninety days" is "it suffers," this is for you. It is built for owners 18 or more months from an exit who still hold the key relationships and make the key calls, and who want to fix that on purpose instead of discovering it in diligence.

It is not for a business that already runs without its owner. If your team holds the relationships and makes the calls, you are de-keyed already. Spend your pre-work time elsewhere.

The page is open for operators who need the tool before the work gets expensive.

The roadmap exists and runs inside engagements. What is being packaged is the standalone version: the dependency-map templates and the phase-by-phase checklist an owner can run without a guide.

If de-keying is the work standing between you and a clean exit, apply. Advisory clients run the sequenced plan inside the engagement, with the order tailored to their business, and the standalone version opens to that list first.

A roadmap is the sequence. It does not do the letting go for you.

The plan tells you the order. You still have to actually step back.

De-keying fails on emotion more than on method. The hard part is not knowing the sequence, it is tolerating the months where the team does it worse than you would before they do it better. The roadmap gives you the order and the pace. It cannot make you stop rescuing. When you keep stepping back in, that is the pattern an outside read is for. The manual names that line, and the advisory is where it gets held.

Back to the manual →

Bring in a read when

You keep stepping back into things you handed off.
The dependency map has a load-bearing item you cannot see how to move.
The team keeps proving they still need you, and you secretly like it.
The exit window is closing and the de-key has stalled.

The De-Keying Roadmap: take yourself out, in the order that does not break the business.

The order you remove yourself in decides whether the business survives it.

Three phases over eighteen months.

Map every place the business needs you.

Transfer in the order that holds.

Prove it by stepping back.

For the owner who is still the company, and knows the buyer will notice.

The page is open for operators who need the tool before the work gets expensive.

A roadmap is the sequence. It does not do the letting go for you.

The plan tells you the order. You still have to actually step back.

Apply, and the sequence runs inside the engagement.
The standalone roadmap opens to that list first.

The De-Keying Roadmap: take yourself out, in the order that does not break the business.

The order you remove yourself in decides whether the business survives it.

Three phases over eighteen months.

Map every place the business needs you.

Transfer in the order that holds.

Prove it by stepping back.

For the owner who is still the company, and knows the buyer will notice.

The page is open for operators who need the tool before the work gets expensive.

A roadmap is the sequence. It does not do the letting go for you.

The plan tells you the order. You still have to actually step back.

Apply, and the sequence runs inside the engagement.The standalone roadmap opens to that list first.

Apply, and the sequence runs inside the engagement.
The standalone roadmap opens to that list first.