How a modern revenue operations function turns company goals into owned, funded, and measured work, run as a continuous discipline rather than a once-a-year plan.
When a revenue operations function plans well, every leader can name the three to five company goals, the number attached to each, and who owns it. Any given day’s work traces back to one of them.
The common failure comes at the first step: leaders agree on a growth rate and never agree on what the numbers mean. This article explains how the discipline closes that gap: the problem it solves, the instrument at its center, the way goals cascade into daily work, and the four-phase cycle that runs it across a year.
This is the third article in our AI-Driven Revenue Operations series, and it sits under the anchor guide. The anchor covers the full model. This piece goes deep on the planning discipline that runs the building side of the function.
Strategic planning is a way of operating, and it runs continuously rather than ending when a plan is signed. At its core, it is a simple discipline: agree on the goals in specific, numbered terms, assign clear ownership for each, and hold the work to those numbers. Three things make it work.
The first is a shared definition of success. Leaders agree what good looks like in specific, quantified terms, so everyone works from the same numbers.
The second is clear ownership. Every goal has a named owner and is threaded across the leadership team, so accountability is shared rather than pushed onto one function.
The third is that it stays a working discipline, running from the weekly standing cadence up to the annual cycle instead of being written once and filed away.
Most growth plans stall for the same reason: leaders never agree on what the numbers mean. Everyone agrees the company should grow, then each leader defines retention, expansion, and cross-sell differently and reaches for different numbers. Agreeing on a growth rate still leaves the plan undefined.
We call this the specificity gap, and it is why the planning work has to come before any analysis.
Closing it takes three things.
Shared definitions, so retention, expansion, and cross-sell mean the same thing to everyone, backed by one authoritative set of numbers. A quantified plan, so priorities carry real figures like growing the top line 20 percent, and progress can be measured against something. And owned accountability, so the leadership team owns each goal rather than delegating it to a single function.
The specificity gap closes when every goal becomes a joint OKR. The objective states what the organization is trying to achieve in plain terms. The key results attach the numbers that prove it.
What makes the OKR joint is that it is threaded across the C-suite, so no single function can claim it or dodge it.
An illustrative example: the objective is to grow net revenue retention, or NRR, to a durable, top-tier level, with key results to lift NRR from 108 to 118 percent, raise expansion bookings 30 percent, and hold gross churn under 6 percent, owned jointly by the CRO, CCO, and CFO with RevOps operationalizing it.
Three properties make a joint OKR work. First, it is quantified: every key result has a real number and a baseline, and progress is unarguable.
The second is that it is jointly owned, so each leader owns a share and can’t delegate accountability. Third, it is operationalized, so RevOps translates it into the coverage, capacity, and process that make it achievable.
Joint OKRs are the output of the alignment work and the input to everything after. The rest of strategic planning builds, funds, and measures against them.
Strategic planning starts with a few company goals and cascades them down into owned, funded work, with each level answering what it uniquely contributes.
The goal cascade. Company goals become initiatives, then quarterly team OKRs, then the daily work that ladders back up.
The company sets three to five core goals for the year. Each cascades into the initiatives that will move it, and each initiative carries a funded business case and named owners.
Those initiatives cascade into the OKRs each team commits to each quarter, which are reset quarterly and checked weekly. Those cascade into daily work, so a seller day traces back to a company goal. The cascade runs top-down for direction and bottom-up for input, and it resets each quarter and is reviewed continuously, so alignment holds through the year.
At full depth, the discipline runs as a four-phase cycle across the year. The cycle repeats annually, with goals set once a year and OKRs reset each quarter. Planning opens in the third quarter and peaks in the fourth, while leading and reviewing the initiatives run all year.
On a January to December fiscal year, Align and Set Goals runs in the third quarter, Build the Case in the fourth, Deploy and Lead from the first quarter onward, and Review and Reset at mid-year and on the standing cadence.
The four-phase strategic planning cycle. It repeats each year, with the initiatives led and reviewed continuously.
Phase 1: Align and Set Goals
Agree on the three to five company goals and the joint OKRs, and cascade them into candidate initiatives. This is where the specificity gap closes, in leadership working sessions that define the definitions and numbers before any analysis begins. The output is a set of quantified goals, a joint OKR framework with named owners, and a first cut of the initiatives that would move each goal.
Phase 2: Build the Case
Turn each candidate initiative into something fundable and ready to run. That means a business case tying the initiative to a revenue or margin outcome, a prioritized and sequenced set of initiatives, approved resources and budget, and written requirements so the team can build it. The output is a cost-approved plan the business will run against.
Phase 3: Deploy and Lead
Stand up the initiatives, assign owners, and lead them through delivery against their OKRs. This is where Strategic Business Operations, the internal group that runs major initiatives, does most of its work, much like a business transformation office. It carries initiatives from plan to delivery, clears blockers, and keeps them on track against the key results they committed to, across the whole year.
Phase 4: Review and Reset
Track outcomes on the standing cadence, reset the OKRs each quarter, and feed what was learned into the next cycle. Weekly and monthly reviews catch drift early, the quarterly reset keeps the OKRs current while the annual goals hold, and results feed into next year’s planning. The cycle closes and opens again.
Do the alignment work before the analysis. The instinct is to gather data first and let the findings shape the goals. That inverts the order and produces an assessment that arrives with its own agenda instead of measuring against the goals the leadership team actually owns. Set the joint OKRs first, then run the analysis against them. The plan is more useful and far more likely to survive the room it is presented in.
Strategic planning is the method behind the building side of the operating model in the anchor guide. It also connects to how a RevOps strategy is optimized in practice, covered in Optimizing Your RevOps Strategy. The goals it sets then organize the six capability areas described in The Integrated RevOps Operating Model.
Strategic planning turns a shared ambition to grow into specific, owned, funded work. The specificity gap is why most plans stall; joint OKRs close it, the cascade carries goals down to daily work, and the four-phase cycle runs the whole thing across a year. Run this way, planning is how the function operates all year.
Work with us
Talk to our team about your revenue operations.
This article covered how the function plans and builds. The next one covers what it actually owns: the six capability areas and three layers of the operating model.
Read next: The Integrated RevOps Operating Model
Sources
The strategic planning discipline, specificity gap, joint OKR example, goal cascade, and four-phase cycle represent RevEng’s position and are illustrative. The cascade draws on widely held OKR practice, reported directionally. Visuals are drawn from the RevEng AI-Driven Revenue Operations guide.