Measuring founder dependency: the Scorecard
The Autonomy Scorecard is a free, two-minute diagnostic that shows founders exactly where their business depends on them. It scores the business across three pillars, finds the weakest one, and hands back a short “where to start first” plan.
The methodology: what the pillars are, how the scoring works, and how to read your result.
The premise: dependency is measurable, not just felt
Most founders feel founder dependency long before they can name it. The late-night decisions, the holidays cut short, the sense that nothing important moves unless you’re in the room. Real signals. But hard to act on, because “I’m too central” is a feeling, not a map.
The Scorecard turns that feeling into a map. It splits the dependency into three measurable pillars and scores each, so you can see where the dependency concentrates, not just that it’s there.
You can run the Scorecard yourself in two minutes at freedomarchitects.co.uk/scorecard. The result is free and yours whether or not you go further.
The three pillars
Founder dependency isn’t one thing; it shows up in three distinct places. The Scorecard assesses each separately.
1. Team empowerment
Can your team solve non-standard problems without you? This pillar measures whether the people around you can carry decisions, or whether every non-routine situation routes back to you.
The honest test: when a non-standard problem arises, what does your team do by default? If the answer is “they escalate it straight to me,” the dependency lives here.
2. Decision-making
Where do the important decisions actually land? This pillar maps whether your business has clear authority (decisions owned by named people with a mandate) or whether “ask the founder” is the operating system.
A founder-dependent business often has no documented decision rights. Everything is implicitly the founder’s call, because that’s the path of least resistance.
3. Operational systems
Do your workflows run on documented systems, or on your memory? This pillar measures how much of “how things work here” lives in your head versus in a playbook the team can run.
The signal: if you were unreachable for two weeks, which workflows would break, and would anyone know how to fix them?
How the scoring works
Each pillar is assessed through a small set of questions. Each carries a points value reflecting how much autonomy it represents; the more autonomous your answer, the higher the points. The pillar scores and an overall score (0-100) come from your answers.
Three things to know about reading the score:
- The overall score is directional, not absolute. A 72 isn’t “better” than a 68 in any precise sense; both tell you the business is meaningfully dependent. The score’s job is to show you the shape and track progress, not to rank you.
- The pillar breakdown matters more than the total. A business that scores evenly low across all three needs a different starting point than one that’s strong on team but weak on systems. The pillar map points you at the right corner to fix first.
- The weakest pillar is your starting line. The Scorecard finds your lowest-scoring pillar and hands back three concrete starter actions for it. That’s deliberately more useful than a generic “improve your autonomy” line.
How to read your result
Once you’ve got your score, the read is straightforward:
| Result pattern | What it means | Where to start |
|---|---|---|
| Low overall, one pillar clearly weakest | The dependency is concentrated | Fix that pillar first; the starter actions are tuned to it |
| Low overall, pillars roughly even | The dependency is structural, not local | Start wherever the cost of inaction is highest, then expand |
| High on team, low on systems | You’ve hired well but the playbook is in your head | Document the workflows before the team turnover tests them |
| High on systems, low on decisions | The tools exist but you’re still the approval gate | Push decision rights down; the architecture is ready for it |
In every case, the next step is to change how the weakest part runs so it no longer needs you, then prove it holds. That’s the four-phase framework covered in how to make your business run without you.
Why a free diagnostic?
The Scorecard is free on purpose. The most useful thing a founder can do with founder dependency is see it honestly, and putting that behind a paywall or a sales call would defeat the point. The result’s yours whether or not you ever speak to me.
If the score surfaces something you want help closing, the natural next step is a paid hands-on diagnostic that ends with a 90-day plan: the Freedom Roadmap. But that’s optional, and always will be.
Frequently asked questions
How long does the Scorecard take? About two minutes. Short on purpose, because the value’s in the honesty of the answers, not the length of the assessment.
Is my score saved or shared? No. The score’s computed in your browser. If you want a copy, you can drop in your email for a short PDF. That’s opt-in, never a requirement.
Does the Scorecard work for businesses under £2M revenue? It’ll still surface useful signals, but the framework it feeds into is built for established £2-15M businesses, where the dependency has had time to go structural. Earlier-stage businesses often have a different shape of dependency.
How often should I re-take it? After you’ve acted on the weakest pillar for a few months. Re-scoring shows whether the change actually held, which is the whole point of phase 4 in the framework.
Ready to see where your business depends on you? Take the free Autonomy Scorecard: two minutes, an honest score, and three starter actions for your weakest pillar.
See where your business still depends on you.
The free Autonomy Scorecard shows you, in two minutes.