What does a founder
dependency audit examine?
A founder dependency audit examines six places the owner is still required: decision rights, sales and customer relationships, operations and quality approvals, finance, hiring and people, and knowledge and access.
Decision rights
Which decisions have a named owner, and which ones still come back.
Sales and customer relationships
Quotes, pricing, key accounts, and the vendor calls that wait on the owner.
Operations and quality approvals
Work that cannot start, ship, or be accepted without the owner's sign-off.
Finance
Spending, pricing exceptions, and the numbers only the owner will release.
Hiring and people
Who gets hired, who is let go, and the leadership calls the team will not make alone.
Knowledge and access
Logins, files, standards, and know-how that exist only with the owner.
How does a founder
dependency audit work?
A founder dependency audit works in five steps: log where the founder gets pulled in over a few weeks, sort the log by cause, score each area, transfer what the founder is holding, and test the transfer with an absence window.
-
1
Log where the founder gets pulled in
For a few weeks, write down each time work stops for the owner: an approval, a rescue, a question, or a relationship.
-
2
Sort by cause
Group the log by why it came back: a missing decision right, a missing standard, a relationship only the owner holds, missing access, or a habit.
-
3
Score each area
Score each area from 1 to 5. The score is how far the work gets without the founder, not how busy the founder feels.
-
4
Transfer
Move the decision, the standard, the relationship, or the access to a named person who can hold it, and write the limit.
-
5
Test with an absence window
The owner steps out of that area on purpose. Two consecutive weeks is long enough that the team cannot simply wait. If the work still moves, the transfer held. If it stacks up, the transfer is incomplete.
The sequence for doing this, area by area, is in How to reduce founder dependency.
How is founder
dependency scored?
Inside an engagement, each area is scored from 1 to 5. 1 means the area runs without the founder. 5 means it stops without the founder.
This page's quiz is separate. It counts how many of eight statements are true this month: 0 to 2 is Low, 3 to 5 is Moderate, and 6 to 8 is High. The quiz says how wide the pattern is. The 1 to 5 score says how stuck each area is. A company can mark few statements and still have one area at 5. A company can mark many statements while some areas sit at 2.
-
1
Runs without the founder
Decisions, standards, and access sit with the people who do the work. The founder is informed, not required.
-
2
Exceptions only
The founder is consulted on exceptions. Routine work does not need them.
-
3
In the regular loop
The founder is in the regular loop. Non-routine work waits for their read.
-
4
Can start, cannot finish
Most real decisions in the area route to the founder. The team can start the work. They cannot finish it.
-
5
Stops without the founder
The area stops without the founder. Quotes, approvals, hires, or access do not move until the founder is in the room.
Keep the design ahead of the growth. The most useful thing at this stage is knowing which decisions you still hold and why.
This is the window where structural work is cheapest. The team exists. The habits are not yet permanent. Most of our engagements start here.
The instinct is to hire a senior operator. It usually fails, because the new hire inherits the same system that routes everything to you. The system moves first, then the hires work.
What does a worked
example look like?
Quotes that wait on the owner are a common shape. The transfer is a pricing framework for standard work and an approval limit someone else can use. The test is an absence window: if quotes still go out while the owner is away, that area moved.
An owner writes every custom quote. The team can take the call. They cannot send the price. Over a few weeks the log is the same pull: a price, a discount, a job outside the usual scope. Sorted by cause, it is not a talent gap. There is no written pricing framework, and no one else has a limit they can approve.
The transfer is the framework for standard work, a written path for the exceptions, and an approval limit. Then the absence window. If the quotes wait in a pile, the framework or the limit is still incomplete. This is not a result. No company is named here.
Why does a founder
dependency audit matter?
Founder dependency is a design stage, not a character flaw. The owner is the patch the company grew around. The audit shows where that patch is, before the company hires someone to inherit it.
Every company that grows past its original design produces the same pattern. Strategy expands faster than it can be transferred. Structure lags behind complexity. Leadership steps in to cover both, and becomes the system.
Decisions route to the owner because routing there works, and it keeps working until the calendar is the constraint on growth. Nothing is failing. Leadership is compensating.
The owner is not the problem. The owner is the patch.
What do you get
from Norsten?
Three partners diagnose where the business depends on the owner and why, across the full operation, before The First 90 Days. If they do not see a fit, they say so in that conversation. The First 90 Days moves the load onto the business: documentation, a scoreboard, a hiring system.
Which of these are
true this month?
This is the public quiz. Eight statements. Two minutes. It counts how many are true and reads them as Low (0 to 2), Moderate (3 to 5), or High (6 to 8). It does not average the 1 to 5 area scores above.
It is a self-reported instrument. It is not a professional assessment, a valuation, or a diagnosis of a specific company. Click each box that is true this month. Selected boxes raise the count.
Each selected statement adds one. More selected = more founder dependency.
Select the statements above that are true, then get your read. Nothing is gated.
Questions
owners ask.
What is a founder dependency audit?
A founder dependency audit is a structured review of where an owner-led business still depends on the owner. It names the decisions, relationships, standards, and access that stop when the owner is not in the room.
What does a founder dependency audit examine?
A founder dependency audit examines six places the owner is still required: decision rights, sales and customer relationships, operations and quality approvals, finance, hiring and people, and knowledge and access.
How does a founder dependency audit work?
A founder dependency audit works in five steps: log where the founder gets pulled in over a few weeks, sort the log by cause, score each area, transfer what the founder is holding, and test the transfer with an absence window.
How is founder dependency scored?
Inside an engagement, each area is scored from 1 to 5. 1 means the area runs without the founder. 5 means it stops without the founder. This page's quiz is separate. It counts how many of eight statements are true this month: 0 to 2 is Low, 3 to 5 is Moderate, and 6 to 8 is High. The quiz says how wide the pattern is. The 1 to 5 score says how stuck each area is.
What does a worked example look like?
Quotes that wait on the owner are a common shape. The transfer is a pricing framework for standard work and an approval limit someone else can use. The test is an absence window: if quotes still go out while the owner is away, that area moved.
Why does a founder dependency audit matter?
Founder dependency is a design stage, not a character flaw. The owner is the patch the company grew around. The audit shows where that patch is, before the company hires someone to inherit it.
What do you get from a Norsten founder dependency audit?
Three partners diagnose where the business depends on the owner and why, across the full operation, before The First 90 Days. If they do not see a fit, they say so in that conversation. The First 90 Days moves the load onto the business: documentation, a scoreboard, a hiring system.
Is founder dependency a character flaw?
No. Dependency is not a character flaw. It is a design stage. The owner is not the problem. The owner is the patch.
What do Low, Moderate, and High mean?
Low, 0 to 2, means the system is carrying most of the load. Moderate, 3 to 5, is the window where structural work is cheapest. High, 6 to 8, means the instinct is to hire a senior operator, and that usually fails until the system moves first.
How do you reduce founder dependency after the score?
The First 90 Days moves load onto the business: documentation, scoreboard, hiring system. The Year is the embedded rhythm after it. The score is a starting read, not the work.
How to reduce founder dependency is the sequence: see the pull, sort the cause, transfer the decision right with a standard and a limit, and test it.
A diagnostic conversation.
The purpose is diagnosis, not performance. We will tell you what we see, including when what you need is not us. If there is a fit, we say so directly. If there is not, we say that too.
Apply for a Conversation