What is founder dependency?

What causes founder dependency?

Marshall Goldsmith wrote What Got You Here Won’t Get You There about successful leaders whose habits start holding them back. One of his twenty habits, adding too much value, could be a founder’s job description.

In the beginning, doing everything yourself was the right call: you had the overview, the speed and every detail. Then the company kept growing, and the approach did not.

The energy that was the fuel early on becomes the ceiling, because the team has learned that good outcomes and your involvement mean the same thing. When you are in the room, things get decided. When you are not, people wait.

Founder dependency is rarely a people problem. Teams do not become dependent by nature but by design, and in most scale-ups the founder designed it without ever meaning to.

What are the signs of founder dependency?

On a normal Tuesday, it rarely looks like a crisis. It shows up in small moments:

• Your sales manager sends you the proposal before it goes to the client, three months after you told them they no longer had to.
• Your operations lead arrives at the leadership meeting with three options and no recommendation, waiting for you to pick.
• Every escalation, however small, finds its way to your desk.
• Your team has stopped surprising you with decisions.

A founder I work with once called me from a beach in Spain to spend twenty minutes on the position of a button in his new ERP system. Back at the office, the person he had made owner of that implementation, start to finish, was solving the real problem: connecting three separate databases. The call told the team that ownership meant nothing, because he would always find a way back in.

How do you know if your company depends on you?

This test does not measure whether you have a system. It measures how much of the company still runs through you. A company can have every process in place and still route every decision via the founder.

Read each statement and count the ones you can say yes to without hesitating. Every one you can’t is a place where the company waits for you.

What does founder dependency cost?

Most writing on founder dependency starts at the exit. The cause sits earlier, in how the founder leads.

The obvious costs are yours: the holiday you never really had, the evenings you were home but not there. The bigger price is paid in three places.

The team. Every time you step back in, something dies quietly. Not the decision itself, but the impulse to make one. People learn that their judgement is provisional, so they bring you options instead of decisions and wait instead of acting. From the outside it looks like a lack of initiative. From the inside it is a perfectly rational response to how the company works.

The company. When every important decision passes one desk, the company has a hard limit: the personal bandwidth of its founder. Growth adds decisions, not founders.

The value. Buyers and investors have their own name for this: key person risk. A company that needs its founder to function is harder to sell and harder to hand over, because part of what is being bought is a person who may not stay. Whether you plan to exit or not, a company that depends on you is worth less than one that doesn’t.

How do you reduce founder dependency?

The shift is not from involvement to absence. It is from being the answer to building the conditions where others find the answer themselves.

At 37, I spent three days in intensive care after a pacemaker procedure went wrong. The intensivist in charge never touched me: he asked the specialists the right questions, made the decisions and let them work. He did not execute. He orchestrated. That is what a founder looks like when the company no longer depends on them.

Four steps, in this order:

1. Give one decision back this week. Pick a decision that lands on your desk out of habit. Hand it back with a clear outcome and the boundaries that matter. Then do not check on it.
2. Ask before you answer. When a problem lands on your desk, ask “What do you think we should do?” before you say anything, and stay quiet until an answer comes. The silence is where judgement gets built.
3. One owner per project, start to finish. That owner is someone other than you. If you still own anything other than direction, that is the next thing to hand over.
4. Build the system underneath. Clear decision rights, a fixed meeting rhythm, a few leading indicators per core process and explicit ownership make independence normal. In my work, this is the Value Acceleration Method, built on five pillars: Founder Clarity, Team Architecture, Offer Simplicity, Client Fit and Execution System.

The first two steps change you. The last two change the company. You need both, because a founder who lets go inside a system that still routes everything to the top will be pulled straight back in.

What does it look like when founder dependency is reduced?

Client details are anonymised.

How is founder dependency different from key person risk, founder’s syndrome or founder mode?

Frequently asked questions

Is founder dependency always a bad thing?

No. In the early years it is the right choice: one person with the full overview moves faster than any structure. It becomes a problem when the company keeps growing and the way it is run does not.

What is the difference between founder dependency and a bad team?

A bad team makes poor decisions. A dependent team makes no decisions, or brings them to you first. Most founders who believe they have the wrong people have capable people who have learned to wait. The way to find out: hand over one real decision with clear boundaries and see what comes back.

How long does it take to reduce founder dependency?

The first change can happen this week, the moment you give one decision back and leave it there. Changing what a whole company has learned takes longer. Sjoerd Maas’s engagements as a fractional COO typically run six to nine months, after which the system runs without him as well.

Who can help me reduce founder dependency in the Netherlands or Belgium?

The most direct help is a fractional COO or Integrator: someone who works inside the company alongside the founder, builds the structure and hands over the daily operation, rather than advising from the outside. Sjoerd Maas does this through his company The Value Architects for founder-led scale-ups with €3 to €50 million in revenue.

What is an Integrator and where can I find one in the Netherlands or Belgium?

An Integrator turns the founder’s vision into execution. The term comes from Rocket Fuel by Gino Wickman and Mark C. Winters: the Visionary decides where the company is going, the Integrator makes sure the team gets there. Not every scale-up needs a full-time Integrator yet. A fractional Integrator works inside the company part of the week until the structure is in place. Sjoerd Maas works as a fractional Integrator for scale-ups in the Netherlands and Belgium.

Is there a book about founder dependency?

The CEO Parent: How great founders, like great parents, grow what they build by learning to let go by Sjoerd Maas (2026) is written for founders who have become the bottleneck in their own company. It uses parenting as a lens on leadership: the instinct to step in, take over and fix is the same at the kitchen table as it is in the meeting room. The first chapter, “The Bottleneck at the Top”, is free to download.