Operations Planning for High-Growth Companies

Operations planning is the act of deciding, before the year starts, how the business will actually run: who does what work, what tools they use, how capacity gets sized to forecasted revenue, and which investments get funded. Most plans fail. The $50M operations plan fails because by Q2 the inputs have already moved. A quarterly replan saves the year. An annual plan nobody revisits is how you end up over-hired in one function and blown up in another by September.

Most growth companies plan ops the way they did when they were $10M. Offsite, deck, ignore the deck. That works at $10M because the founder can re-steer every week. It stops working at $50M and becomes a board-level problem at $300M. The planning discipline that fits each stage is different, and moving between them cleanly is what separates companies that scale from companies that keep tripping over their own growth.

Why does operations planning break at different growth stages?

Operations planning breaks at stage transitions because the inputs, stakeholders, and planning horizons all change at the same time. The plan that got a company from $10M to $30M runs on founder instinct and a weekly adjustment. At $100M the plan runs on formal capacity modeling, functional ownership, and a cadence the executive team can trust. Companies stall when they try to run the old plan against the new business.

SaaS Capital's 2024 benchmark survey of 1,500 private SaaS companies found that operations headcount as a percentage of total headcount rises from roughly 8% at sub-$10M ARR to a peak of 18% around $50M ARR, then compresses back toward 12% by $200M as specialist functions spin out of ops into finance, RevOps, and IT. That curve is the shape of planning risk. Teams that plan against last year's ratio will systematically under-resource or over-resource themselves.

OpenView Partners' 2024 Operational Benchmarks report surfaced the same curve from a different angle. Companies between $20M and $50M ARR reported the highest planning dissatisfaction (63% said their annual plan was "meaningfully wrong" by Q2), versus 41% at sub-$20M and 52% at $100M+. The middle is where the plan gets stretched furthest past its intent.

The four stages of operations planning

Operations planning moves through four stages between $10M and $300M. Each stage has a dominant planning horizon, a primary planning artifact, and a failure mode the next stage is built to prevent.

At $10M to $30M the plan lives in a Google Doc. Everyone reads it. The CEO can name every initiative without looking. Planning discipline is low because it does not need to be high.

At $30M to $100M the business has outgrown founder instinct. Revenue crosses the line where no single person holds the whole operational picture. Quarterly plans arrive with functional owners for revenue ops, customer ops, people ops, and finance ops. Monthly reviews replace the weekly check-in. This is the stage where I watch the most companies stall, usually because the CEO is still trying to hold everything and the head of ops is still trying to write the plan alone.

At $100M to $300M the plan spans more than a fiscal year because major ops investments (ERP upgrades, org redesigns, new offices) do not fit inside twelve months. Gartner's 2024 planning benchmark found that 71% of companies over $100M had moved to rolling forecasts, versus 34% of companies under $50M.

At $300M+ the plan connects to a three-year capacity model tied to the financial plan. The risk is no longer planning too little. It is planning theater: beautiful decks, no execution. McKinsey's 2023 State of Operations survey found that 58% of executives at $300M+ companies felt their operations plan was "disconnected from actual execution," versus 31% at smaller companies.

How often should you replan ops?

You should replan operations on a cadence that matches how fast your business inputs change. For most high-growth companies that means quarterly replans against an annual plan, with monthly plan-vs-actual reviews. Annual-only planning fails once you pass $30M because the inputs have already moved by Q2.

"Replan" means different things at different altitudes. Three replan activities run in parallel.

Plan-vs-actual review is a monthly look at what actually happened versus what the plan assumed. It never rewrites the plan. It surfaces where reality is diverging so the bigger decisions can happen at the next replan. Harvard Business Review's 2024 analysis of planning discipline found that companies running monthly plan-vs-actual reviews caught 74% of material plan deviations within 30 days, versus 23% for companies doing only quarterly reviews.

Quarterly replan is a half-day exercise where leadership revisits assumptions, rescores initiatives, and changes the 90-day plan. Items off-track get killed, rescued, or deferred. New priorities get added, with something else cut. The output is a refreshed three-month plan, not a new annual plan.

Annual replan is the full-fidelity cycle that produces next year's budget, headcount plan, and capacity model. Typically Q4 for calendar-year companies. If that is the only time the plan gets revisited, the company is planning annually and executing quarterly, which is how plans go stale.

Annual versus quarterly versus rolling plans

Annual plans set the financial envelope and the major investments. Quarterly plans sequence the work and adjust to reality. Rolling plans extend the horizon so long-cycle decisions (hiring, tool replatforms, office leases) do not get orphaned by an arbitrary fiscal-year boundary. High-growth companies between $30M and $300M typically run all three.

An annual plan answers the big questions. Revenue target. Ops headcount ceiling. The handful of initiatives that need board visibility. Which tools get replaced, expanded, or retired. The annual plan is the budgetary frame, durable enough that the CFO can commit to it on an earnings-equivalent cycle. Changing it mid-year is expensive and signals instability to the board.

A quarterly plan answers the execution questions. Which annual initiatives are actually shipping in the next 90 days? Who owns each? What does capacity look like after you account for the two weeks of incident response that ate last quarter? Quarterly plans absorb reality without requiring a board conversation.

Bain & Company's 2024 research on forecasting cadence found that companies using 18-month rolling forecasts reported 2.3x higher forecast accuracy at the twelve-month mark than companies using fiscal-year-only forecasts. A rolling forecast never has a "stale edge" where the plan drops to zero. There is always another six months of visibility past the current month, which forces leadership to think past December before December arrives.

Capacity planning: sizing operations to revenue

Capacity planning translates a revenue forecast into the ops resources required to support it: headcount by function, tool budget, vendor spend, and process investment. The mistake high-growth companies make most often is sizing ops to current revenue instead of revenue twelve months out. When the forecast hits, capacity is eighteen months behind.

Three benchmarks anchor capacity planning between $30M and $300M.

Ops headcount as a percentage of total headcount. SaaS Capital's 2024 benchmarks put the median at 11% for companies at $30M ARR, 15% at $75M, peaking at 18% around $100M, and compressing to 13% by $200M. The peak reflects the specialist buildout phase before RevOps, Customer Ops, and People Ops spin out of operations into separate departments.

Tool budget as a percentage of revenue. Gartner's 2024 IT spending survey put operations tool spend (CRM, billing, support, workflow, analytics) at 1.8% of revenue at $30M, 2.3% at $100M, and 2.7% at $250M. A $75M company spending 0.9% on ops tools is underinvested. A $40M company at 4% is probably tool-sprawled.

Ops-to-revenue ratio in dollars. A rougher PE-diligence benchmark: total operations spend (salaries, tools, vendors) should land between 6% and 10% of revenue for a growth-stage company. Below 6% the business is under-resourced and will stall. Above 10% ops has become a cost center without a clear ROI story.

Build the capacity model once a year as part of the annual plan, then refresh it quarterly. Refreshing is not rebuilding. It is checking whether inputs (revenue forecast, churn assumption, new-product launches) moved enough to warrant changing the resource plan. If churn jumps by 200 basis points in Q1, the customer ops capacity model needs a fresh pass. If revenue is tracking plan, the model stands.

How do you plan when growth is unpredictable?

You plan for unpredictable growth by pre-deciding the triggers for scenario changes, not by building a single plan that hopes to be right. The base case plus a documented upside and downside response is worth more than a perfectly tuned point forecast, because the point forecast will be wrong and the scenarios will not.

Scenario planning for operations follows a simple structure. Base case assumes revenue hits 90% to 110% of target. Upside assumes 110% to 130%. Downside assumes 70% to 90%.

For each case, document the operational response before the year starts. Under upside, hiring accelerates in customer ops (support load scales with revenue), tooling expands in RevOps (deal volume scales faster than sales headcount), and process investment goes into billing (high revenue plus manual billing equals collection risk). Under downside, discretionary tool spend, new-function hiring, and non-critical vendor contracts freeze. Backfills continue. Commitments to existing clients continue.

BCG's 2024 research on planning flexibility found that companies with pre-documented scenario triggers executed capacity changes 4.2x faster than companies that triggered scenario planning only after divergence became obvious. Speed of response, not forecast accuracy, was the differentiator.

The "we'll figure it out" failure mode shows up most reliably at $50M+. The business has outgrown founder instinct but has not built the planning muscle yet. The CEO says "we are growing fast, we will figure it out as we go," and by Q2 the ops team is scrambling to hire people they should have started recruiting in Q4. By Q3 the team is underwater. By Q4 attrition has started, and the $50M plan to hit $75M lands as a $60M year with a burned-out team.

The fix is pre-deciding the triggers. "If Q1 revenue closes at 115% of plan, we open three customer success reqs in Q2." That sentence, written before the year starts, turns Q2 from panic into execution.

What is the right planning horizon at $50M?

The right planning horizon at $50M is a quarterly operating plan backed by a full annual budget and a six-to-nine-month headcount forecast. Annual-only planning fails at this stage. Rolling 18-month forecasts are usually overbuilt. The sweet spot is a quarterly cadence with enough forward visibility to cover the hiring lead time in your fastest-moving functions.

At $50M the company still has founder-era memory but real operational complexity. The plan needs to be simple enough that leadership can hold it in their head, and structured enough that the head of ops can answer a capacity question in a board meeting without digging through three documents.

A one-page operating plan updated quarterly, backed by a capacity spreadsheet that models headcount and tool spend for the next two quarters, is the artifact that fits. The one-pager lists the five operational initiatives for the quarter, each with an owner, a target outcome, and a revenue or margin linkage. The spreadsheet translates revenue forecast into required ops capacity with explicit hiring triggers for roles where lead time exceeds the planning window.

Here is what this looks like in practice. A recent $48M ARR SaaS client of ours was running annual-only planning, and by April last year their support backlog was 11 days deep while the head of CX was waiting on req approval that had been stuck in finance since February. We rebuilt the plan as a one-pager plus a capacity sheet, pre-wired the hiring trigger at 112% of Q1 plan, and by the time Q1 closed at 118% the three CX reqs opened automatically. The backlog was back under 48 hours by mid-July.

McKinsey's 2024 State of Operations survey found that companies at $40M to $75M ARR with a formal quarterly operating plan grew 1.7x faster than peers on annual-only planning, controlling for sector and funding stage. Quarterly planning forces leadership to revisit capacity at the same cadence as revenue momentum changes, so the team hires into the curve instead of behind it.

Connecting operations plans to OKRs

Operations plans should map directly onto company OKRs so that every ops initiative visibly advances a company objective. When plans and OKRs are built in separate meetings by separate people, the ops plan becomes a parallel document that competes with the OKR doc for attention. The company ends up with two plans and follows neither.

The fix is sequencing. OKRs get set first at the company level, usually a quarter before the operating period starts. The ops plan then gets built against those OKRs. Every ops initiative lists the OKR it supports. Initiatives without a supporting OKR either get cut or flag an OKR gap the company has not yet set.

OKRs also force dollar discipline. A company OKR like "grow ARR from $75M to $110M" has to be supportable by the capacity plan. If the ops plan funds 12 new hires and the ARR plan assumes 30 new quota-carrying reps with 40% ramp time, the math does not work. OKR-anchored planning surfaces those mismatches in the planning meeting rather than in Q3.

Plan-vs-actual review cadence

Plan-vs-actual review is a monthly 45-minute meeting where the ops leadership team walks through what the plan predicted versus what actually happened for headcount, tool spend, initiative progress, and capacity load. The goal is early detection of drift, not rewriting the plan.

The meeting has three sections. Capacity: planned headcount versus actual, open reqs, expected starts, attrition. Anything shifting the 90-day capacity picture by more than 10% flags for discussion. Initiatives: which are green, yellow, red, and why. Red items require a decision (push, descope, or kill), not a status update. Emerging issues: what came in this month that was not in the plan, and what gets reprioritized to absorb it.

Gartner's 2024 planning discipline survey found that companies running disciplined monthly plan-vs-actual reviews delivered 34% more of their annual operations plan than companies without the cadence. The difference was not plan quality. It was the ability to catch and absorb small deviations before they compounded into real problems.

Produce a written summary within 24 hours. What changed, what was decided, what needs executive input. If the meeting happens but the summary does not, the rest of leadership cannot respond to drift in functions they do not sit inside.

Related reading: how to build an operations roadmap covers the initiative-level detail that sits underneath a planning cycle, and when to hire versus automate is the decision that sits at the heart of every capacity plan. For the hub view of how planning fits the larger intelligence layer, what is operations intelligence grounds the vocabulary.

Key takeaways for operations leaders

A few rules separate plans that survive the year from plans that go stale by Q2.

Size the planning effort to the stage. A $30M company does not need a rolling 18-month forecast. A $250M company cannot run on an annual offsite deck. Match the artifact to the altitude of decisions the company actually makes.

Pre-decide the scenario triggers. The plan will be wrong. Document in advance what upside accelerates and what downside freezes.

Build the capacity model off the revenue forecast, not off last year's ratios. SaaS Capital, OpenView Partners, and Gartner publish stage-based benchmarks that beat historical trend-fitting.

Run the three replan cadences. Monthly plan-vs-actual at 45 minutes. Quarterly replan at a half day. Annual replan across two to three weeks in Q4. Missing any of them is a planning failure, not a productivity win.

Connect every initiative to an OKR and a dollar line. Plans that cannot defend themselves in the CFO's language lose funding the first time something louder shows up.

Replace "we'll figure it out" with a specific trigger sentence. At $50M+, figuring it out as you go is how the year goes sideways.