More revenue does not necessarily buy an owner more freedom. If every exception comes back to your desk, a growing company can simply give you more to carry. The interviews below look at different parts of that problem: ownership, operating structure, and the everyday work of a team.
Where does the business still depend on you?
Look at a normal working week. This diagnostic is our synthesis of the conversations and helps you identify dependence before choosing a handoff.
- Routine decisions
- Which approvals wait for you? Notice whether the team needs a clearer standard, better information, or permission to decide.
- Key relationships
- Which customers, suppliers, or partners communicate only with you? Look for important context held in your memory or personal inbox.
- Recurring work
- Which regular tasks stop during your absence? Identify the knowledge, access, or capacity that nobody else currently has.
- Repeated exceptions
- Which problems keep returning? Look for the operating constraint that makes each incident need your attention.
Choose one dependence with a clear recurring cost. Use the conversations below to understand what needs to change, then work through a single handoff before widening the effort.
Decide what the business must do without you
From the conversation with Brian McNally
Brian McNally describes starting his company with an eventual buyer in mind. That decision shaped what he and his partner built, which functions they kept lean, and how they thought about replacing their own involvement. The exit was part of the design from the beginning.
In the same conversation, Sam describes looking at a business where the owner still carried much of the work. Revenue alone did not resolve that dependence. The question for another operator is practical: what would stop if the founder stepped away?
You do not need to be preparing a sale to ask that question. Start with decisions only you can make, customer relationships only you hold, and work nobody else knows how to complete. Those are useful places to begin a handoff.
Read the source conversation with Brian McNallyBuild for the next stage of the business
From the conversation with Carl Gould
Carl Gould uses an overloaded landscaping truck to explain a familiar operating problem: adding more work to something that was never designed to carry it. In his account, the same pattern appears when early software, informal processes, and generalist roles remain in place as a business expands.
He distinguishes doing more of what works from building the infrastructure that lets a larger operation work. He also argues that businesses tend to reflect the strengths and blind spots of their owners. A founder who is comfortable selling may overlook an operational weakness that another leader can see clearly.
Before adding another tool or another person, identify the constraint. Is the team waiting for information, authority, specialist knowledge, or capacity? The answer changes what you should build next.
Read the source conversation with Carl GouldMake the system serve the people
From the conversation with Will Bamber
Will Bamber describes connecting proposals, invoices, and business data so a small team can spend less time moving information between tasks. Those examples make systems tangible. A useful system removes a repeated obstacle in someone’s working day.
He also puts people first. The guest experience depends on the team doing the fundamentals well; software supports that work. This is a helpful check on a founder’s instinct to automate everything. A process can be efficient on paper and still make the customer experience worse.
Choose one repeated handoff, such as moving an accepted proposal into delivery. Make the required information, next action, and responsible person clear. Then ask the people doing the work whether the change actually helps.
Read the source conversation with Will BamberChoose your first handoff
Here is a practical exercise to apply these conversations. This is our synthesis of the lessons, rather than a framework attributed to any one guest.
- Notice where work waits for you. For one week, record routine approvals, repeated questions, and tasks that pause until you step in.
- Choose one repeatable decision. Write down what a good outcome looks like, what information is needed, and when the team should bring an exception to you.
- Give someone ownership. Agree on responsibility and decision boundaries with the person doing the work. Walk through a real example together.
- Review the handoff. Look at what stalled or needed rework. Improve the instructions or authority before deciding the task must come back to you.
The aim is not to disappear from the business. It is to make your involvement a choice in more places, while the team can still deliver work you are proud of.
