The Drop Test: will your business break?
One question that exposes structural cracks in your business.
In this article: The Drop Test reveals the operational health of a founder-led business by asking a single practical question: could a competent person walk into your business on Monday and keep it running? Not fix it, not improve it – run it. The test focuses on two levers: authority beyond the founder and whether the information needed to run the business is accessible. The answer often exposes more structural fragility than founders expect.
A business can look fully operational from the outside — growing clients, running projects, revenue coming in — and still be held together by a single person. Not because the team isn't capable, but because the architecture was never built for them. The difference between a business that runs and one that runs without its founder is not always visible until the founder isn't there.
That’s what the Drop Test measures.
Most founders don’t realize they have structural fragility.
What the Drop Test looks like
Imagine the Drop Test as a real week: it’s Monday morning, you’re suddenly unavailable, and a capable operator is dropped into your business with access to your systems and files – but no briefing or handover, just whatever exists.
By Friday, what’s broken?
Your dropped-in operator opens your sales spreadsheet or CRM on Monday. The pipeline is there, but the context isn’t – why certain deals are stalled, what was promised last, which clients need attention. That lives with you. Despite seeing data, they’re running blind, literally feeling their way through in front of clients and prospects. It does not inspire confidence.
That afternoon, they look for process documentation. Some exists. Most is incomplete or describes how things used to happen. The team generally knows what to do. It’s in their heads, but final review and sign-off are typically yours, and a change of some kind is almost always needed.
A client escalation comes in on Tuesday. The team knows who would normally handle it – you. The dropped-in operator asks who else has authority to resolve it. No one is sure. In the meantime, the client is getting angrier.
On Wednesday, much-needed Marketing and IT purchasing decisions stall. Approval thresholds aren’t written anywhere – they’re calibrated to what people think you would say yes or no to. The team makes their best guess on one and suggests the other wait.
By Thursday, after delayed projects, angry clients and lackluster sales, your operator has a clear picture: the business runs on your touchpoints, undocumented “tribal” knowledge, authority that was never delegated and relationships that have not been transferred (or even shared).
Net observation? The team is capable. The architecture isn’t there.
The team is not the problem – the architecture is.
What it measures
The Drop Test measures two critical things:
Accessibility – whether the information, context and process to run the business today actually exists somewhere a competent person can find and use it. Not in someone’s head. Not in an email thread from 18 months ago. Accessible.
Authority – whether the people in the business have the clarity and mandate to make the calls that need to be made without escalating to the founder. Not whether they’re capable of deciding, whether they know they’re (really) allowed to.
Most businesses have gaps in both, and they compound: when authority is unclear, people look for documentation to guide them. When documentation is insufficient or doesn’t exist, they escalate. And when the person they escalate to isn’t there…things stop.
Accessibility and authority gaps are interconnected. Fixing one exposes the other.
Running it properly
The Drop Test is most useful when run in two passes.
First, as a thought experiment: go through your business function by function and ask what your dropped-in operator would find. Be specific. Not “client relationships are a risk” – name the three clients where your absence would create an immediate problem. List exactly how and why.
Then, as a live test, take yourself out of the day-to-day for five days. Be genuinely unavailable, not on a vacation where you’re checking in. Ask your team to log each time they wanted to reach you and why. That log is your diagnostic. If there’s too much risk in being out of touch for five days, try one or two to start.
The two passes together give you something no self-assessment can: the gap between what you think exists and what your team actually reaches for when the pressure is on.
The gap between what you think exists and what your team needs is where the risk lies.
What to do with what you find
Organize your findings into accessibility gaps and authority gaps.
Accessibility gaps: fix these with systematization – pulling key context out of your head and into searchable, current documentation and tools. Unglamorous, but effective.
Authority gaps: fix these by explicitly transferring authority (not just delegating) – who owns what, where the boundaries are, what requires escalation – and make sure it is genuinely left up to them, meaning once it’s explicit, don’t step in or outwardly second-guess them later. If you delegate, be clear that the person is meant to handle things for you, but final authority still rests with you. It is an important distinction.
Start with the gap that causes the most frequent breakdowns. In most businesses, it’s authority and delegation. The team can find a process document. They can’t manufacture the confidence to act without it.
You can document a process. You can’t document real permission.
WHY THIS MATTERS:
The Drop Test is often framed as exit preparation. It’s better used as a health check. A business that passes the test isn’t just easier to sell, it’s easier to run, more likely to scale and considerably less dependent on the founder being available, healthy and present at all times. It gives the founder options and a valuable asset.
The test is worth running whether a transaction is a few years away or not on the horizon at all.
What it tells you is whether you’ve built an asset or just a job that happens to employ other people.