The Founder Dependency Test: Score How Much Your Business Relies on You
The founder dependency test is a 10-question self-assessment that scores how much your business still runs through you, on a scale of 10 to 50. You rate ten honest statements about your decisions, your knowledge, your client relationships, and your time. Add up the numbers. A low score means the company runs on systems. A high score means it runs on you, and that number is the ceiling on both your growth and your eventual sale price.
Score first. Fix second. The test shows you where you're the constraint. The plan to escape it comes after, and we cover that in how to escape founder dependency.
What the founder dependency test measures
Dependency hides in four places. Decisions that wait for you. Knowledge that lives in your head. Clients who only trust you. Time you can't get back. Plenty of self-assessments test how you feel. This one tests how your business is built.
That difference matters. Founder dependency isn't a willpower problem. It's a design problem. You can be disciplined, delegate often, and still be the single point of failure if the systems don't exist yet. The test is built to catch the design flaw, not grade your effort.
The quickest gut-check behind the whole thing is the owner absence test: if you vanished for 30 days with no phone and no laptop, would revenue keep coming in and would clients stay happy? The ten questions below break that one question into parts you can score.
Take the test: 10 questions
Rate each statement from 1 to 5. A 1 means almost never true. A 5 means almost always true. Be honest, not aspirational. Score the business you have today, not the one you're building.
# | Statement | Your score (1-5) |
|---|---|---|
1 | Decisions above a small dollar amount wait for my sign-off. | |
2 | My team escalates calls back to me that they're capable of making. | |
3 | Core processes live in my head, not in a document someone could follow. | |
4 | Onboarding a new hire means weeks of me explaining things. | |
5 | Clients ask for me specifically, and a handoff feels like a downgrade to them. | |
6 | If I went dark for a week, at least one key client relationship would wobble. | |
7 | Revenue slows down when I take time off. | |
8 | I'm still the only person who can close a sale or ship the core work. | |
9 | I spend more time working in the business than on it. | |
10 | I can't take two weeks off, fully offline, without things breaking. |
Add the ten numbers. That total is your dependency score.
Score your result
Score | Where you stand | What it means |
|---|---|---|
10 to 20 | System-run | The business makes most decisions without you. You're close to optional for the day to day. Protect it and keep documenting. |
21 to 34 | Founder-reliant | The business leans on you more than it should. A few key decisions and relationships route through you, and they slow everything behind them. |
35 to 50 | Founder-dependent | You are the business. It moves at your speed and stalls when you step back. This is the trap, and it's structural, not personal. |
Where you land matters less than which questions scored a 4 or 5. Those are your bottleneck, ranked by your own hand. A 50 and a 32 get fixed the same way: one high-scoring decision at a time.
What your score is really telling you
A high score feels like a time problem. You're buried, you work 50-plus hours, and there's never margin. That part is real. But the score is measuring something that costs more than your calendar.
When a buyer looks at your business, they ask one question: does the revenue belong to a system or to a person? If it belongs to you, they discount it hard. Systematized businesses in the lower middle market tend to sell at roughly 7 to 8 times EBITDA, while founder-dependent companies often struggle to clear 3 to 4 times, a discount of 30 to 50 percent (Strategic Exit Advisors). Your dependency score is a rough preview of that discount.
So the number taxes you twice. It costs your hours now, and it costs a chunk of your net worth the day you try to sell. That stall you feel around the $2M mark is usually the same thing wearing a different mask, which we broke down in the real reason you can't scale past $2M.
The fastest way to move your score down
You don't lower the score by working harder. You already do that. You lower it by moving one decision at a time out of your head and into a system your team can run. Start here:
Circle your highest-scoring question. That's where the business depends on you most. Start there, not with the easiest thing.
Write the decision, not just the task. Capture the inputs you look at, the rule you actually use, and what a good outcome looks like. You're exporting your judgment, not your to-do list.
Hand it off with an owner and a definition of done. Name the person. Tell them what finished looks like. Resist taking it back the first time it's 80 percent right.
Run a stress test. Block four to eight hours fully offline and let the team run it. What breaks is your next system to build.
Re-score in 90 days. Retake the test every quarter. The number should fall as the systems grow.
If you want the deeper mechanics of step two, we laid them out in how to buy back your time. And the place all of this is supposed to live is a company operating system, the single connected home for your decisions, SOPs, and client knowledge. Here's how to build one in Notion.
Frequently asked questions
What's a good founder dependency score?
Anything in the 10 to 20 band means the business runs on systems more than on you. A lot of founder-led companies between $1M and $10M land in the 21 to 34 range, which is normal and fixable. A score of 35 or higher means you're the single point of failure and should treat it as the priority, not a someday project.
How often should I retake the test?
Quarterly. Dependency creeps back as you add clients, hires, and complexity, so treat the score like a recurring vital sign. Retaking it every 90 days also tells you whether the systems you built are actually holding.
Isn't some founder dependency unavoidable in a small business?
Early on, yes. In the first days you are the sales, the delivery, and the invoicing because there's no one else. The problem isn't being the dependency at the start, it's staying there once you have a team. The goal isn't zero involvement, it's being optional for the day to day so your time goes to the few calls only you can make.
Can AI lower my score?
Only after your context is written down. If your decisions and standards live in a system, AI can draft, triage, and answer against them and clear a lot of the small approvals clogging your day. It can't fix a dependency that only exists in your head, because it has nothing to work from. Write the context down first, then point AI at it.
Score it this week
The feeling that everything runs through you is hard to act on. A number isn't. Take the ten questions, add them up, and circle the one that scored highest. That single decision is where your business depends on you most, and it's the first one to move into a system your team can run.
Do that, re-score next quarter, and watch the number fall. A business that scores low is also the one that's worth more, because it runs without you.
Want a faster read on where you're the constraint? Start with our free operations audit. And if you want the decisions, owners, and standards built into one system, that's what we do when we build your Company OS.
Written by Damon Flowers, Modern Operators. We build AI-powered operating systems that get founders out of the dependency trap and back to the work only they can do.
