The infrastructure most scaling businesses are missing
A business operating system – or BOS – is the single most important piece of infrastructure a scaling business puts in place, and most founders don’t know they need one until they’re already in pain. It’s the combination of concepts, tools and disciplines that turns a founder-dependent business into an enduring, founder-independent company. It’s how a scaling business runs without the founder being in every decision. And it’s the thing I spend most of my fractional COO engagements building, installing or repairing.
I’ve worked closely with founders in growing businesses since 2014, and the pattern I’ve watched play out more times than I can count is this: the founder is the bottleneck, the leadership team is waiting on the founder to make decisions, the founder knows intellectually that they should delegate more, and nothing actually changes – because there’s no system for decisions to be delegated into. A BOS is that system. This article explains what a BOS is, why every scaling business needs one, the three best-known frameworks and their trade-offs, and how to think about installing one in your business.
What a business operating system actually is
A BOS is the essential set of concepts, tools and disciplines needed to build and run an effective company. At its most useful, a BOS covers:
- Vision – a compelling big-picture direction that people want to get behind.
- Goals – a way of setting long- and short-term goals that ensures alignment from the founder down.
- Customers – a clear, shared understanding of what you’re selling and to whom.
- People – high-performing, capable people in well-defined roles, working effectively in teams.
- Structure – an organisational structure that’s right for the work being done, not for the founder’s career history.
- Process – standardised ways of working that balance predictability with space for autonomy.
- Meetings – a cadence of effective meetings to oversee and steer the business.
- Data – reliable numbers that drive insights and action, not vanity metrics that drive conversation.
The right combination of these things, consistently implemented over time, is what turns a founder-dependent business into an enduring, founder-independent one. None of the components are especially clever on their own. What creates the value is running them all together, coherently, as a system the whole organisation has internalised.
Why every scaling business needs one
There’s a pattern I see in founders who haven’t yet installed a BOS that has two versions – one sad and one hopeful.
The sad version is where the founder holds decision-making power close and doesn’t really enable others to take decisions. The business hires good people into leadership roles, and those people work out pretty quickly that the only way to get anything done is to stay close to the founder. Their energy goes into jockeying for influence instead of leading the business. Messy politics build up. Frustration builds. Growth slows. The most talented newly hired leaders get the picture and leave. I’ve been in rooms with founders watching this unfold in real time, and it’s painful because the cause is almost always the founder’s own ambivalence about letting go, not a shortage of good people around them.
The hopeful version is where the founder recognises the need to create a system that allows them to spread decision-making more widely – so people can stay focused on goals, work autonomously with the protection of clear guardrails, and take ownership of outcomes without second-guessing what the founder would do. That’s what a BOS does. It creates the scaffolding that makes devolved decision-making safe, which is the thing most scaling businesses need more than any new hire, new strategy or new product.
If you read nothing else in this article, read this. The reason every scaling business needs a BOS isn’t because frameworks are good. It’s because the alternative to a BOS – founder dependence – is the single biggest reason scaling businesses get stuck between £3m and £15m in revenue.
The three best-known frameworks (and what to make of them)
You don’t have to invent a BOS from scratch. Three well-known frameworks do most of the thinking for you, and each has its own feel.
Entrepreneurial Operating System (EOS)
Developed by Gino Wickman and documented in the book Traction, EOS combines vision with execution through a disciplined set of tools: getting the right people in the right seats, building a clear vision, setting quarterly “Rocks” (priorities), running a weekly leadership meeting (the L10), and solving issues through a defined process (IDS – Identify, Discuss, Solve). It’s the most widely adopted BOS in the SME world for good reason – it works, it’s internally coherent, and it gives founders a handbook they can actually follow. It’s also notably top-down in feel, which is either a feature or a bug depending on your temperament.
Scaling Up
Verne Harnish’s Scaling Up grew out of his work studying the strategy and execution practices of successful entrepreneurs. It focuses on setting priorities, achieving quarterly wins, using data for accountability and adhering to proven processes. If you’ve spotted a theme between this and EOS, you’re not wrong – the fundamentals of every good BOS rhyme. Scaling Up is stronger on metrics and cash than EOS, and weaker on the softer work of team dynamics.
System & Soul
System & Soul is a newer framework that, functionally, does much of what EOS and Scaling Up will give you but through a human lens as well as an organisational one. It feels more modern, less rigid, and more honest about the emotional reality of running a scaling business – which, in my experience, matches how founders actually live. I tend to recommend System & Soul to founders who know they need a BOS but recoil from the top-down feel of EOS.
I take a progressive view on how companies should run – flatter structures, devolved decisions, less hierarchy – which means the more hierarchical edges of EOS and Scaling Up don’t sit comfortably with my own instincts. They come from an era where top-down control was still the default management theme. Useful, but not where I’d start from in a 2026 scale-up.
How to choose (or compose) the right BOS for your business
Most founders don’t need a pure off-the-shelf BOS. They need the discipline of one. The way I approach this in fractional COO engagements is to start with the components a BOS needs to cover – vision, goals, customers, people, structure, process, meetings, data – and then choose the simplest tool for each component that fits the culture of the business.
A few principles I come back to:
Pick a framework you can stand. The best BOS is the one you’ll actually run. A founder who loathes the EOS weekly Level 10 meeting will let it quietly die within six months, and the whole system will lose its spine. Pick a framework whose rhythms match how you want the business to feel.
Implement all the components together. A BOS isn’t a buffet. If you only install the meetings without the goals, you’ll have disciplined status updates that lead nowhere. If you install the goals without the data, you’ll have aspirations nobody can measure. The system is the system.
Run it for at least two quarters before judging it. A new BOS feels clunky for the first six to eight weeks. The rhythm hasn’t bedded in, the leadership team is still working out how to use it, and the founder is tempted to abandon it and reinvent. Don’t. Give it two full quarters before you decide whether it’s working.
Appoint an owner who isn’t the founder. A BOS that lives in the founder’s calendar is a BOS that will collapse the first time the founder is overwhelmed. Appoint an integrator – a COO, a chief of staff, or a fractional COO – to own the cadence. The founder is the visionary; somebody else is the keeper of the system.
“Simon is a highly experienced and grounded leader who demonstrated he was capable of walking into the business and quickly making a difference. He is a strong business thinker, capable of taking apart a complex problem and putting it back together to solve it.”
Peter O’Brien, CEO, Hidden Creative
Why the BOS is the thing I install first as a fractional COO
When I come into a business as a fractional COO, the first structural thing I usually work on is the BOS – not because frameworks are glamorous but because almost every other operational problem a founder is experiencing is a symptom of a missing or broken business operating system. The team isn’t “being accountable” because there’s no goals framework to be accountable against. Meetings are a waste of time because there’s no operating cadence to hold them in. Decisions queue up on the founder’s desk because there’s no process for anybody else to take them. Good people leave because the only way to get work done is to be close to the founder.
Installing the BOS doesn’t solve any of these problems directly. It creates the conditions under which they can be solved. That’s why it’s the load-bearing piece of work in almost every fractional COO engagement I run, and it’s the piece of work most likely to still be delivering value in the business a year after I’ve gone.
The BOS is also the operational expression of the B³ framework® – the model I developed from interviews with fifty-plus founders, which puts founder development, leadership team and the business operating system together as the three components of any scaling business. A founder without a BOS is a founder whose only lever is themselves.
Next step. If you’re reading this and thinking we don’t really have a BOS, we have a collection of half-implemented tools and a weekly meeting nobody likes, that’s a signal worth taking seriously. The gap between a half-installed BOS and a properly running one is usually the gap between a business the founder runs and a business that runs itself.
