The Operating Cadence From $10M to $100M
Companies climbing from $10M to $100M rarely replace their operating cadence. They lay a new rhythm over the founder-era one and run both, and the cost surfaces as decisions that get made twice.
Between $10M and $100M, a company is rebuilt while it runs.
A company crossing from $10M to $100M is not scaling one design; it is exchanging one company for another while both are in motion. Headcount moves from tens into the hundreds. A single leadership table becomes three layers of management. The founder goes from being in every deal to hearing about most of them a week later. An operating cadence for a $10M to $100M company has to serve both ends of that climb, and no single rhythm can.
We have written before about the cadence a company is already running: inherited rather than chosen, and properly set by the length of the loops it closes. That argument holds at any size. What this band adds is the transition itself. The cadence does not need tuning once; it needs replacing at least twice, while targets rise every quarter and no one has a spare month. Under that pressure, replacement is rare. What happens instead is accumulation.
What accumulation looks like
The pattern that repeats across companies in this band is not a wrong cadence but a doubled one. The founder-era rhythm survives: informal, presence-based, settled in whichever room or channel the founder happens to be in. It was never designed, but it was fast, and for years it was accurate, because the person deciding was also the person who knew the most. On top of it arrives a formal layer, usually imported in a hurry around the first revenue plateau or the first outside capital.
The new cadence gets installed; the old one never gets switched off.
The imported layer looks close to identical from one company to the next.
- A monthly business review with a pack and a pre-read.
- A quarterly planning cycle with targets cascaded by function.
- A weekly leadership meeting with an owned agenda.
- A forecast call, because a board now expects a forecast.
Each of these is reasonable, and most companies in the band need some version of all four. Together they describe a record-based company: decisions proposed in writing, examined in a named forum, minuted, owned. The difficulty is that the presence-based company underneath was never decommissioned. Nobody chose to keep it. It persists because it is made of habits rather than calendar entries, and habits have no owner who can cancel them.
One decision, two verdicts
So every consequential decision is now made twice: once in the forum that is supposed to close it, and once in the informal circuit that used to be the whole company. Sometimes the forum goes first and the corridor revises. Sometimes the corridor pre-decides and the forum ratifies. Either way the company pays twice for one decision — twice the elapsed time, twice the meetings, and a standing ambiguity about which of the two verdicts was the real one.
The tell is a decision that passes the forum and then moves.
The symptom is precise enough to test for. A proposal clears the monthly review. Two weeks later it has changed shape: a scope trimmed, a hire re-graded, a launch date moved. The change traces back to a conversation that included the founder and did not include the forum. Nobody hid anything, and nobody acted in bad faith. The presence-based rhythm simply kept its override rights, and everyone senior enough to matter knows that it did.
The calendar says the company has one operating rhythm. Its decisions say it has two.
What managers learn
Managers respond to what is real rather than to what is written. Once it is understood that a forum's verdict is provisional until it survives contact with the corridor, effort migrates. Pre-reads get thinner. The meeting before the meeting returns. People close to the founder become a channel, and people far from the founder start reopening decisions they never felt bound by. The calendar says the company has one operating rhythm. Its decisions say it has two.
This gets read as a culture problem — a founder who cannot let go, managers who lack discipline. The field observation is duller. Nobody ever said which rhythm was final for which decisions. In the absence of that statement both rhythms claim jurisdiction, and the tie is resolved by proximity.
The transition is a handover of finality, not a redesign of meetings.
The useful move in this band is not another meeting audit. It is an explicit handover: naming, decision type by decision type, which rhythm now issues the final verdict. Pricing beyond an agreed threshold belongs to the monthly review and nowhere else. Senior hires belong to the written forum, with the founder holding one voice rather than a veto. Product direction stays in the founder's room for now, said out loud, so that nobody has to pretend otherwise.
Presence is not a pathology
Sequenced this way, the cadence for the climb is less a template of frequencies than a dated series of handovers. At the low end of the band, presence is the fastest accurate mechanism a small company has, and heavy ceremony installed against it mostly adds cost. At the high end, the record has to be final, because the number of people acting on each decision has outgrown any one person's reach. The expensive failure is the middle held too long: ceremony installed for appearances, presence retained for comfort, both paid for.
A handover holds only if it is dated and revisited. A decision type moved to the forum in March drifts back by summer when the move was never written down. The discipline that closes a single decision, a sentence with an owner and a review date, closes a jurisdictional one too.
Where the handover becomes deliberate work.
In consulting engagements in this band, the first artefact is not a new meeting structure. It is a record of the last dozen consequential decisions: where each was supposed to close, where it actually closed, and who moved it. That distance, decision by decision, is the whole diagnosis, and assembling it rarely takes more than a day.
The jurisdiction conversation
What follows is harder than any calendar change, because it is about the founder's own jurisdiction, made explicit and given a date. Teams that want to carry the discipline themselves afterwards take it up as training: reading the decision record each quarter, keeping the jurisdiction list current, and treating every proposed forum as a transfer of finality rather than an added meeting. It belongs to the argument that runs through everything under operating cadence — that a company's rhythm is a claim about who may decide, and in a scaling company that claim has to be re-made on purpose, roughly every time the company doubles.