The framework · Technology & Future
26 Resilience, Scalability & Enterprise Independence
14 sub-categories. The three numbers on each are the typical opportunity in that area across businesses — not your result.
Time7.0/10Financial8.1/10Automation7.4/10
These three numbers are researched cross-business benchmarks for the area — the typical opportunity available in it. They are not your score, not a forecast, and not a promise. What is actually critical depends on your business, which is what the audit is for.
26.1Founder dependency
Time8/10Financial8/10Automation5/10
▸
- What this is
- How much of the business depends on the founder personally.
- Why it matters
- Founder dependency is the single largest discount applied when a small business is valued, and the main reason owners cannot take a holiday.
- You have a problem here if
- Revenue would fall noticeably if the founder stopped working for a month.
- What to automate
- Five out of ten — automation helps but does not solve it. Systematically identify what only the founder does, then document, delegate or automate each item. The relationships and judgement are the hard part and need deliberate transfer over time.
26.2Key-person dependency
Time8/10Financial8/10Automation5/10
▸
- What this is
- The same exposure for anyone else the business cannot function without.
- Why it matters
- Key-person risk is often larger than founder risk and much less visible, because the person is competent and never complains.
- You have a problem here if
- One person's two-week absence would stop a critical process.
- What to automate
- Map single points of failure by process, then cross-train and document. Automate what is genuinely mechanical so the remaining dependency is expertise rather than access or knowledge of a routine.
26.3Customer concentration
Time5/10Financial9/10Automation7/10
▸
- What this is
- How much revenue comes from too few customers.
- Why it matters
- Nine out of ten financially. Concentration is invisible while everything is fine and existential when one relationship ends.
- You have a problem here if
- Your largest customer accounts for a substantial share of revenue.
- What to automate
- Automate concentration reporting with an alert against a threshold you set. The mitigation — deliberate diversification, or longer contracts, or both — is a commercial strategy decision.
26.4Supplier concentration
Time5/10Financial8/10Automation7/10
▸
- What this is
- The same concentration exposure measured on the supply side rather than the customer side.
- Why it matters
- A supplier who cannot deliver stops your revenue as effectively as a customer who stops buying, and usually with less warning.
- You have a problem here if
- One supplier is irreplaceable within your lead times.
- What to automate
- Automate spend concentration monitoring. Qualifying alternatives before you need them is procurement work with a clear payback the first time it is used.
26.5Knowledge dependency
Time9/10Financial8/10Automation9/10
▸
- What this is
- Critical knowledge that exists only in people's heads.
- Why it matters
- Nine for time and nine for automation. Undocumented knowledge is the mechanism by which key-person risk actually bites, and it is now far cheaper to capture than it used to be.
- You have a problem here if
- Answering a routine question requires finding one specific person.
- What to automate
- High value: capture knowledge as work happens — recorded procedures, decision records, a searchable internal knowledge base. Language models make drafting documentation from a recording genuinely fast, which removes the excuse that has always been used.
26.6Documentation
Time9/10Financial7/10Automation10/10
▸
- What this is
- Whether how the business runs is written down.
- Why it matters
- Ten out of ten for automation. Documentation is what converts a set of individuals into a business that can be trained into, delegated within, and eventually sold.
- You have a problem here if
- A capable new manager could not run a core process from your written material.
- What to automate
- Generate procedures from recordings of the work being done, keep them beside the work rather than in a folder, and automate a review reminder so they do not silently go stale. Stale documentation is worse than none because it is trusted.
26.7Operational redundancy
Time5/10Financial7/10Automation7/10
▸
- What this is
- Whether critical functions have a backup — people, systems, premises, equipment.
- Why it matters
- Redundancy is the difference between an incident and an interruption. It costs money, which is why it should be applied deliberately to what actually matters.
- You have a problem here if
- Several critical functions have no alternative if the primary fails.
- What to automate
- Automate technical redundancy and failover where it is cheap. For people and premises, decide what warrants the cost — full redundancy everywhere is not the right answer for a small business.
26.8Disaster recovery
Time7/10Financial9/10Automation9/10
▸
- What this is
- Whether you can actually recover systems and data after a serious failure.
- Why it matters
- Nine out of ten financially. Recovery capability is binary in effect: it either works on the day or the business discovers it does not.
- You have a problem here if
- Your recovery plan has never been executed as a test.
- What to automate
- Automate backup, replication and the recovery test itself. Record how long a real restore takes and compare it to how long the business can actually tolerate being down — the gap between those two is the finding.
26.9Business continuity
Time7/10Financial9/10Automation8/10
▸
- What this is
- Continuing to serve customers through disruption.
- Why it matters
- Continuity is what determines whether customers wait for you or find someone else during the worst week of your year.
- You have a problem here if
- You have no plan for how customers would be served if your main site were unavailable.
- What to automate
- Automate the technical continuity and the contact-list maintenance. Write the short plan, rehearse it once, and note that most of the value came from the rehearsal rather than the document.
26.10Capacity to scale
Time7/10Financial9/10Automation8/10
▸
- What this is
- Whether the business could handle substantially more volume without breaking.
- Why it matters
- Nine out of ten financially. Growth that arrives faster than the ability to deliver damages reputation permanently and is a real cause of failure.
- You have a problem here if
- You are not sure what would break first at double the volume.
- What to automate
- Model the constraint — capacity, systems, cash, people — and monitor how close you are to each. Knowing which one binds first is what makes growth investment targeted rather than general.
26.11Systems scalability
Time8/10Financial8/10Automation9/10
▸
- What this is
- Whether the technology can carry growth without redesign.
- Why it matters
- Systems that require re-architecture at exactly the moment you are growing fastest are the most expensive kind of constraint.
- You have a problem here if
- Manual workarounds already appear at peak volume.
- What to automate
- Automate capacity monitoring against defined thresholds, and choose systems with headroom relative to your plan. The architectural decision is human and should be made before the ceiling, not at it.
26.12Succession
Time5/10Financial7/10Automation3/10
▸
- What this is
- Who takes over each critical role, and whether they are being prepared.
- Why it matters
- Three out of ten for automation — one of the lowest scores in the framework. Succession is a people programme, not a system, and it takes years rather than months.
- You have a problem here if
- There is no identified successor for the owner or for any critical role.
- What to automate
- Very little. Keep the plan current and automate the review reminder. The actual work is identifying, developing and progressively handing over — starting long before it is needed.
26.13Geographic/system dependencies
Time5/10Financial7/10Automation7/10
▸
- What this is
- Reliance on a single location, platform, market or piece of infrastructure.
- Why it matters
- Dependencies of this kind are usually invisible until the thing you depend on changes its terms, its algorithm, or its availability.
- You have a problem here if
- A large share of your demand comes from one platform you do not control.
- What to automate
- Automate monitoring of the dependency's share and alert on threshold breaches. Reducing it is a strategic choice — usually building a channel you own alongside the one you rent.
26.14Ability to operate without constant owner intervention
Time10/10Financial9/10Automation9/10
▸
- What this is
- Whether the business runs without constant owner involvement.
- Why it matters
- Ten for time and nine financially — the summary line of the whole framework. This is what separates a business from a demanding job, and it determines whether the thing you built can ever be sold, handed over, or simply left for a fortnight.
- You have a problem here if
- The business needs you to make ordinary decisions every day.
- What to automate
- This is where all twenty-six categories converge. Documented processes, delegated authority with automated guardrails, exception-based management and reporting the owner reads rather than builds. Test it honestly: leave for two weeks, see exactly what breaks, and fix that. Then do it again.
Category totals
Time 98/140 · Financial 113/140 · Automation 103/140. The sum is the official roll-up; the averages above exist so categories of different sizes can be compared.