Operating Model Design for a Growing Business: Structure, Decision Rights and Cadence
Most growing businesses do not have a bad operating model; they have an accidental one, assembled decision by decision as the firm grew, which worked well enough at fifteen people and now quietly resists everything you try to change. Operating model design for a growing business is the deliberate replacement of that accident with something chosen, and it is far less abstract than the phrase suggests. It comes down to four concrete things: who leads what, who can decide what, how the business checks itself, and how often people meet to steer it. If you can sketch those four on a single page, you can usually see where your decisions are stuck.
The accidental operating model, and why it stops working
In the early years the operating model is the founder, in the sense that structure, decision rights, governance and cadence all collapse into one person who knows every client, approves every hire and unblocks every problem. That is not a design flaw at ten people, because at that size the founder genuinely is the fastest route through the business, but somewhere between 20 and 60 people the arithmetic turns against you. There are now more decisions per week than one person can absorb, so decisions start to queue, and the people best placed to make them learn instead to wait, which is how a capable team ends up looking passive.
Call this pattern the founder-as-routing-layer: nothing in the business is formally blocked, yet everything routes through one desk, so the constraint on growth is no longer sales or delivery capacity but the founder's calendar. Redesigning the operating model is how you remove that constraint without removing the standards the founder was protecting.
Operating model design for a growing business: the four parts
1. Leadership structure
Structure answers one question: who owns each outcome, end to end. In a services business the outcomes are reasonably standard, namely winning work, delivering work profitably, and running the machinery of people, finance and systems that supports both, which is why most firms at this stage converge on a small leadership team covering commercial, delivery and operations. The common failure is not the shape of the chart but the honesty of it, because many firms have a tidy chart on paper and a shadow structure in practice, where titles say one thing and the flow of real decisions says another. Structure only counts if the person named on the chart is the person people actually go to.
2. Decision rights
Decision rights are the part most founders skip, and they are the part that matters most. Structure tells people who they work for; decision rights tell them what they can do without asking. For each recurring decision in the business, hiring, pricing, discounting, scope changes, resourcing, spend above a threshold, you should be able to say who decides, who must be consulted, and who simply needs to be told, and if you cannot answer that in a sentence, the answer in practice is almost certainly the founder.
Rule of thumb: if a decision routinely reaches the founder and the founder is not adding information the team lacks, the decision right is in the wrong place.
3. Governance
Governance is how the business checks itself without anyone having to be heroic, which in a services firm means a small set of numbers reviewed on a fixed rhythm: pipeline coverage, utilisation, project margin, cash, and delivery health on the accounts that could hurt you. It does not need a board pack or a dashboard project; it needs the same one page reviewed the same way every month, so that drift shows up as a trend rather than as a crisis. Firms that skip this tend to discover margin erosion two quarters after it started, at which point the choices are all worse. If delivery is where the strain shows first, the practices in scaling a technology services business without breaking delivery sit inside this governance layer.
4. Meeting cadence
Cadence is the operating model made visible, because whatever your chart says, the business is really run in its recurring meetings. A workable cadence for a firm of this size is a weekly leadership meeting focused on this week's commitments and blockers, a monthly business review against the governance numbers, and a quarterly session where you lift your heads and set priorities, and almost nothing else that recurs. The test of a good cadence is not how few meetings you have but whether decisions come out of them, since a meeting that reviews information without deciding anything is a report, and reports can be emails.
A worked example: a 40 person services firm, before and after
Before
Picture a 40 person technology services firm with a founder CEO, a head of delivery who is really the most senior project manager, and a finance function that is one part time person and an accountant. Every proposal above a modest value goes to the founder for pricing, every hire needs the founder's sign off regardless of level, and resourcing is settled in a Monday meeting that the founder chairs and that regularly runs to two hours because it is also the sales meeting, the delivery review and the place grievances surface. Margin is reviewed when the year end accounts arrive. Nothing here is stupid; every piece of it made sense when it was introduced, but the combined effect is that the firm makes decisions at the speed of one person's diary.
After
The redesign is deliberately modest, not a 40 point transformation plan but a handful of changes that, if they hold, materially alter how the firm runs. The head of delivery becomes accountable for project margin as well as project outcomes, and with that accountability comes the right to make resourcing calls and approve scope changes up to an agreed threshold without asking. Pricing moves to a rate card with defined discount authority, so the founder sees only the exceptions. A monthly business review is introduced with five numbers on one page, and the Monday meeting is split into a 30 minute delivery stand up and a separate weekly commercial call. The founder's involvement in routine decisions falls sharply, not because the founder stepped back but because the model stopped requiring them.
The takeaway: the after picture contains no new software, no reorganisation and no new hires, only clearer ownership, explicit decision rights and a cadence with fewer, sharper meetings.
Sketch your current model in an afternoon
You do not need a consultant to see your own operating model; you need a whiteboard and honesty. List the ten decisions your business makes most often, and against each one write who decided it the last three times it came up, because the pattern of actual deciders is your real operating model regardless of what the chart claims. Then list every recurring meeting, what it decided last month, and what it merely reported, and finally ask which numbers you would want to see monthly if you could only see five. Wherever the same name appears against most of the decisions, and wherever meetings report without deciding, you have found where growth is stuck.
Where Vitori fits
Sketching the model is something you can do yourself, and for some firms that exercise, followed by a few disciplined changes, is enough. The harder part is making the new model hold, because decision rights drift back to the founder the first time something goes wrong, and cadences decay the first busy quarter. Vitori works on exactly this problem with founder-led technology services firms, using the Operational Scale Framework to assess where the operating model is straining across Growth, Delivery and Operations, and then either advising leadership or embedding directly through the Operator model to implement the redesign and stay accountable until it is embedded. Where the gap is a missing operational leader rather than a missing design, a fractional COO can be the right answer, and sometimes an internal promotion is. Whichever route you take, with Vitori or anyone else, the goal is the same: a business that runs, and scales, without the founder in every decision.
