From Founder to Leader: How to Build a Business That Doesn’t Depend on You

What would happen if you disappeared for two weeks?

In a recent All Together workshop on leadership, host Bruce Alexander posed this question to a room of founders and CEOs – people running businesses at various stages, from early-scale consumer brands to multi-country agencies and purpose-led digital platforms. The answer, he said, may be a determining factor in whether your business is truly scalable.

Bruce brings a specific kind of experience to his question. After 15 years at Nestlé and senior roles in the food industry, he moved into SME leadership, running Montezuma’s Chocolate through a private equity transition. More recently, he’s taken on the role of MD at Marco, a 40-year-old engineering business navigating life after its founders’ exit. Alongside this, he qualified last year as an executive coach, giving him unique insight into life as a business leader.

What Happens When the Founder Leaves the Room

Bruce opened with two case studies from his own career, offered not as cautionary tales but as illustrations of how the same challenge, founder dependency, plays out differently depending on the culture a business has built.

The first was Montezuma’s. A husband-and-wife-founded premium chocolate business with a genuinely warm culture and a loyal team. When they sold to private equity and moved into a minority shareholder role, there was inevitably a shift in focus. The business priorities and goals for a PE-owned business compared with a privately owned business are very different, and this resulted in many difficult conversations about strategy, culture and investment.  This was made even more acute when Covid struck, resulting in the temporary closure of the retail stores, with the shift to online and cashflow challenges.

The second was Marco. A 40-year-old business built by two brothers with a very direct, autocratic culture. The team was loyal but not routinely empowered to make decisions independently. When the company was sold to a Canadian parent organisation in 2020, there was no integration, no handover, and no muscle memory for autonomous decision-making, all exacerbated by Covid. The business was rudderless, not because the people were incapable, but because they’d never been given the chance to try.

“Every phase of a business requires a different leadership approach. It’s not about saying one is right and one is wrong. It’s about evolution.”

Bruce was careful to separate the critique of culture from any criticism of founders themselves. In both cases, the founders had built something real. The challenge was that they hadn’t built structures that could survive their own departure.

Letting Go Isn’t a Decision – It’s a Practice

Bruce shared a third story that took the conversation somewhere more personal. Amelia Christie Miller, founder of Bold Bean, a business that has elevated a commoditised category, appeared on Dragon’s Den, and featured in the Times top 100 growth companies, was a coaching client of Bruce’s. During her first trimester of pregnancy, she had severe morning sickness and was forced to step back from the business.

She codified processes, set clear goals, removed herself from email and Slack more deliberately, created an escalation structure that didn’t route through her, and made her biggest hire: a marketing director to carry the function she had always owned herself. What followed surprised her. Her team stepped up. Not just adequately… impressively.

When she returned, she wrote: “These people are incredible. I cannot believe they work for me. Do I have a role now?”

The point wasn’t that the founder had become redundant. It was that the circumstances of her pregnancy had done what most founders can’t bring themselves to do voluntarily – force genuine delegation. And the team, given the space, had risen to it.

“My team is learning to work without me and they’re doing it better.”

The Two-Week Test

When Bruce put the question to the room, “what would happen if you stepped away for two weeks?”, the responses were honest and varied.

One founder who had recently been deep in a fundraise described coming back to find her team had drifted. Without her direction on product-market fit and go-to-market strategy, people had retreated into their own silos, not out of disengagement, but because there was no escalation mechanism and no agreed owner for the decisions she’d been carrying. The absence had revealed a gap she hadn’t been aware of.

Another, who described himself as “incredibly lazy as a person,” (perhaps code for efficient?) had built a delegation model almost by instinct. High expectations, high support, and a deliberate habit of removing himself from the operational detail. Things just got done.

A third had been forced to take unexpected time off and returned to find, to her relief and mild surprise, that the clinical service had kept running. She’d spent years as a self-described ‘control freak’. It was reassuring to learn that the world hadn’t fallen apart without her.

What these stories had in common was the gap between what founders imagine will happen when they step back, and what really does. The anxiety is usually bigger than the reality. But the anxiety is also not entirely wrong – the businesses where things did drift were the ones where a clarity and decision-making structure hadn’t been built in advance.

The Decision-Making Model

One of the more practically useful frameworks Bruce introduced was a simple decision-making model, prompting founders to think about which decisions they are actively holding and whether that’s the right call.

The levels run roughly from “I will make this decision and tell you” to “I want to understand your recommendation before I decide” to “This is yours to own – I trust your judgement.”

Several founders in the room identified themselves as operating mostly at the more directive end, not because they didn’t trust their teams, but because they hadn’t yet built enough shared context for delegation to feel safe. One member described consciously working towards giving her key person more room, finding that the bad hire she’d made two years earlier had pulled her back into over-involvement, and that removing that person had changed the whole dynamic. Her trusted second-in-command, it turned out, hadn’t needed to step up. They’d just needed to be given space.

Another founder, managing an MD who was still developing, described a more complex picture: a board with expectations, an FD wearing multiple hats, and the challenge of being seen to support her MD’s decisions in meetings while still needing to provide direction behind the scenes. The complexity wasn’t about trust so much as architecture, who owns what, and what does good escalation look like in a business with investors expecting results?

“The question isn’t whether your team can make decisions. It’s whether you’ve built the conditions that make it safe for them to try.”

Accountability and Role Clarity

The conversation shifted into a thread that several founders in the room recognised: the challenge of holding people accountable when their roles have evolved organically and expectations have never been explicitly reset.

One attendee described team members who had been in post for three or four years, whose job descriptions had shifted multiple times without any formal renegotiation. Asking them to step up to a new standard felt like criticism of their existing performance. The question she posed to the room – how do you define expectations without it landing as a telling-off?

The responses drew on several different angles. One founder described her approach, make the expectations for every role explicit, and use company-wide goal-setting sessions to create shared accountability, not just between manager and report, but across the team. When people can hold each other to agreed standards, the dynamic shifts from top-down enforcement to collective ownership.

Another offered a simpler reframe, hold the conversation up against the values or the strategy, not against your own subjective reading of someone’s performance. When the reference point is something the team has agreed to together, the conversation becomes about the gap between where we said we’d go and where we are – not about one person’s judgement of another.

Bruce added a vital distinction: separate the issue from the person. What you’re addressing is a behaviour or a decision, not a character trait. That framing doesn’t make the conversation easy, but it makes it possible to have without the relationship becoming collateral damage.

Working On the Business, Not Just in It

Bruce wrapped up the session with a question you’ve probably heard before: are you spending more of your time working IN the business or ON it?

One founder with a board and investors in the picture described how her structure had shifted her role without anyone fully designing it. She sat in meetings largely listening, building oversight rather than directing. She spent more time now thinking about strategy and where the MD needed support than on operational detail. It wasn’t quite what she’d imagined, but it was closer to how a business with investors needed her to show up.

Several others in the room admitted they’re still deep inside the day-to-day, not because they wanted to be, but because the clarity, processes, or people needed to pull them out weren’t yet in place. The aspiration was there. The infrastructure wasn’t.

Bruce shared that this is the transition most founder-led businesses hit, and few fully plan for. The skills that build a business in its early stages, instinct, energy, direct involvement, are not the same skills that scale one. And the shift isn’t a one-time event. It’s a continuous renegotiation.

Five Things to Take Away:

1. Ask the two-week question honestly. If the answer makes you uncomfortable, that says a lot. The discomfort usually points to a specific gap, a person, a process, or a decision that’s still routing through you unnecessarily.
2. Be deliberate about which decisions you’re holding. Not all of them need to sit with you. Mapping out where your team is empowered to act, and where they’re still waiting for you, is often the first practical step towards getting out of the way.
3. Don’t wait for a crisis to create an escalation structure. Pregnancy or illness can force the conditions for delegation. Most founders don’t get that nudge until something goes wrong. Build the scaffolding before you need it.
4. Reset role clarity without making it personal. If job descriptions have drifted, hold the conversation against the strategy or values rather than your own assessment of someone’s performance. Make it about where you’re going, not what they’ve failed to do.
5. Be kind to yourself. More than one founder in the room identified this as their key takeaway. Managing cash, leading a team, responding to investors, and trying to build a scalable culture simultaneously is hard. Getting the leadership piece right is a long-term project, not a single decision.

Bruce Alexander is an executive coach and leadership specialist, and an advisor to All Together members. To access workshops like this one, or to speak with Bruce directly, visit alltogether.company/memberships.