Walk. Run. Sprint. In that order.

When it comes to building a revenue operations strategy, many businesses start with the roof. Bright shiny tools with a million metrics. It looks impressive briefly. Then it falls. Building a lasting RevOps system is a construction project, not an ego flash. Sequence matters as much as the work. Walk lays the foundations. Run builds the structure. Sprint adds the fit-out. Skip the foundations and the roof doesn't hold. It's not a faster route: it's a more expensive version of starting again.

The rollercoaster is rough. Big month, thin month, strong quarter, inexplicable dip. The team is working hard but the numbers aren't compounding.

The most common cause isn't bad people, bad tools, or bad product. It's a revenue system that was assembled reactively, stage by stage, without coherent architecture underneath it. Acquisition does its job. Onboarding does its job. CRM does its job. Nobody owns the joins between them, and nobody owns the full customer journey view that would make the joins visible.

Forrester’s research on revenue team alignment puts a concrete number on this: organisations where revenue teams operate with genuine alignment across the full growth funnel grow revenue 2.4x faster than those where they don’t (Forrester, 2023). Slow revenue growth rarely comes down to talent or budget. It comes down to whether the system connecting your teams was designed or just grew. Build a revenue operations strategy correctly, in the right sequence, and the people you already have start producing results that change the rollercoaster to a smooth upwards ride.

Before You Build: What RevOps Actually Needs to Do

Before sequencing anything, it’s worth being precise about what a revenue operations strategy is supposed to achieve. This step gets skipped. It shouldn’t.

RevOps is the connective tissue between acquisition, conversion, and retention - across every stage of the full growth funnel. Its job is to make sure that what marketing promises, product delivers; that what onboarding starts, CRM and lifecycle finish; that what customer service hears, product and acquisition learn from. Without that connective tissue, each stage optimises for its own metrics, the joins between stages leak, and the overall system produces less than the sum of its parts.

The Three Things RevOps Must Connect

The first is data: a single, honest read of what’s happening across the full customer journey, not five separate dashboards that each tell a different story.
The second is process: defined handoffs between stages, owned by named people, with explicit Key Result Areas covering strategic best practice and what happens at the boundary.
The third is accountability: not shared accountability (which is non-accountability in a collegial wrapper), but stage-level ownership that rolls up into full-journey responsibility at the leadership level.

A RevOps strategy that doesn’t address all three produces partial coherence. Build them in order. Data informs process. Process enables accountability. Accountability drives improvement.

The Most Common Misread: Why the Obvious Fixes Don’t Fix It

The instinct when RevOps is broken follows one of three patterns. The first is misattribution: a systemic problem gets assigned to a single stage, that stage gets fixed, and the underlying incoherence (and the revenue underperformance) stays intact. The second is internal ownership: someone realises the whole funnel is disjointed and hands it to an existing team, typically product, CRM, or marketing. That team now owns a system that the other teams also live in. Let the funnel politics minefield begin. The third is an operations hire brought in to direct a system that doesn’t yet exist.

All three responses are applying the wrong medicine to the underlying issue. What’s needed is a system solution to a systemic problem.

Walk: Get the Foundations Right

Walk phase is as unglamorous as it is non-negotiable. Everything in Run and Sprint is built on top of it, which means that skipping or rushing Walk phase produces a system with surface sophistication but structural fragility.

Four things must exist before Walk phase is complete.

First: an honest customer journey map, updated at minimum once every six months, preferably as part of a quarterly review. Not written by the teams responsible for each stage, which reflects how those teams wish the journey worked. An honest, data-based account of what actually happens to a customer from first awareness to either churn or advocacy. This is a quest for truth, not a defence exercise. The uncomfortable parts are the most useful parts.

Second: a Customer Journey Council. A cross-functional group with representatives from every stage of the journey, meeting at minimum bi-monthly. Its job is to own the right KPIs for each stage and the joins - the handoffs between stages where revenue often leaks. The journey map gets written and forgotten without a CJC to own it. The CJC is the collaborative and governance layer that makes everything else stick.

Third: handoff definitions between stages. Explicit agreements about where one team’s job ends and another’s begins. Who owns the transition from acquisition to ASO to onboarding. What signals trigger the handoff from onboarding to CRM. What the customer service team passes back to product, and at what cadence. These definitions feel overly administrative. In practice, the absence of them is what drives the revenue rollercoaster.

Fourth: a basic shared KPI and data view. Not the full single source of truth infrastructure - that’s Run phase. Walk phase requires a decision about what to measure and a view that every stage lead is working from. One version of the numbers, not five dashboards telling five different stories. Walk phase isn’t the moment to redesign what gets measured. It’s the moment to get everyone looking at the same thing. That conversation happens in Run.

At Walk stage, the foundational 20% of the work that delivers 80% of the available return gets done. The businesses that skip it and go straight to tooling and automation are building on sand. The rollercoaster continues, just with more metrics and reports.

What Good Looks Like at Walk Stage

A Walk-stage business that has done the work has a customer journey map that leadership has seen, found uncomfortable, and owned. It has a basic CRM that the whole team uses consistently. It is regularly meeting to discuss shared metrics across the entire growth funnel. It has written handoff definitions that nobody disputes. That’s it. That’s Walk.

The Most Common Walk-Stage Mistake: Jumping to New Tooling

The mistake is understandable: you want a solution, the tool promises a lot, and tooling feels like progress (and an easy way out). Signing a contract for a new attribution platform or a lifecycle automation tool produces a clear deliverable and a launch date. But tooling up without fully understanding the problem is like buying parts for your broken car from Amazon without knowing what the issue is. Good luck with that. Tools don’t create coherence. A broken system with better tooling is a faster version of the same broken system. Complete Walk phase before touching the tool stack.

Run: Build for Visibility and Repeatability

Run phase starts once the foundations exist. The focus shifts from laying foundations to building for clarity, excellence and repeatability across the full growth funnel.

This is where Forrester’s 2.4x growth finding becomes operational. The mechanism behind that figure is ownership clarity, reporting what matters and attribution that’s coherent enough to tell the CJC and leadership which activities drive revenue and which consume budget without compounding it.

When done properly, results like onboarding conversion dialled up from 5% to 35% are achievable. That’s what a Run-phase rebuild produces when the foundations underneath it are solid. Run phase is what turns a Walk-stage foundation into a system that compounds.

KPI Discipline

Run phase requires decisions about what to focus on - and what to turn away from. The average CRM or marketing automation platform tracks a multitude of metrics. Many teams track all of them because it all looks so professional. The result is high noise, low signal, and lower accountability: because when everything is a priority, nothing is.

The discipline: two KPIs per stage. One for efficiency health. One for revenue contribution.

Why that combination? Because it embeds two critical disciplines into each team. Be efficient and contribute to the bottom line. When those two metrics move in the right direction, the business moves in the right direction. They are not the ones easiest to report, or the ones that make the team look good. They are the two KPIs that most connect stage performance to real business outcomes. This doesn’t mean everything else falls by the wayside, there will be supporting-cast metrics within funnel stages, but those are internal team measures. What gets shared at the CJC, what gets reported on, what gets focused on: the two most powerful revenue and efficiency metrics per stage.

KRA Establishment

KPIs tell you what to watch. KRAs tell you what to build. Key Result Areas are the strategic capabilities that, when functioning well, produce the KPI outcome. They sit beneath the metrics and answer the question the KPI can't: why is performance at this level, and what needs to change?

KRAs should build in layers. For example, an acquisition team's KRAs should cover at least six strategic capabilities that drive CPA and LTV:CAC:

• Target Audience Clarity: do you know exactly who you're after and what to say to them?

• Channel Strategy: are you in the right mix of paid, owned, and earned, and can you prove it?

• Creative Excellence: are your assets fresh, tested, and technically sound across every platform?

• Campaign Execution: is every audience getting a joined-up journey from ad to landing page to ASO to action?

• Attribution: can you trace spend through to outcome, not just to click?

• Optimisation Cadence: are your learning loops fast enough to actually matter?

Each stage of the full growth funnel has its own equivalent set. We also map each KRA against a maturity arc: Foundation, Traction, and Scale. The arc matters because sequence is everything - running multi-channel strategies with mature segmentation (Scale) is pointless if you don't yet have documented and tested personas (Foundation). Sophistication has to match where you actually are. KRA reviews should run on a 90-120 day cycle, indefinitely, because what counts as strong execution at seed stage is table stakes by Series A.

The KRA layer is what makes the two-KPI discipline stick. Without it, teams know what they're being measured on but not what to actually do differently. With it, the path from current performance to better performance is explicit, measurable and understood.

KIT Development

KRAs define what strategic excellence looks like. KITs (Key Implementation Tasks) define what doing it actually involves. They are the operating-level layer beneath the KRAs: specific, ownable, executable disciplines that ensure the strategy is being implemented properly, not just reported on.

Most growth diagnostics stop at the strategy layer. "Your Meta targeting needs work." "Consider testing TikTok." Helpful? Sort of. There's a gap between knowing what you should be doing and knowing whether the thing you're doing is actually set up properly. That gap is where lack of efficiency and excellence compounds across the funnel to reduce growth and negatively impact the bottom line.

You can have the right channel strategy and still have a Google Ads account that's a dumpster fire. Wrong campaign types. No conversion tracking. Broad match keywords burning cash at three times the CPA they should be. A CRO looking at a dashboard sees "paid acquisition: active" and assumes it's handled. KITs go one level deeper and check whether it actually is. That's the gap the KIT layer closes. And it's exactly what the Revenue Engine platform is built to surface.

Each KIT maps to a specific channel or tool and stacks elements by impact priority: Foundation (the non-negotiables: conversion tracking, campaign structure, basic targeting hygiene), Traction (the levers that turn a functional account into an efficient one), and Scale (the sophistication layer: value-based optimisation, incrementality testing, first-party data integration). KITs, unlike KRAs, have a finish line. Every element implemented, confirmed, marked complete. For a team that's been told for months that their growth machine needs work, seeing an entire KIT turn green is the kind of proof of progress that keeps momentum alive.

That's the chain. KPIs sit at the top. KRAs sit beneath them. KITs sit beneath the KRAs. Fix the KITs and you fix operational excellence. Fix the KRAs and you fix strategic excellence. Chase the KPIs without either and you're pulling on branches while the roots stay broken.

The Shared Dashboard

The infrastructure that makes all of this visible should be a shared dashboard: one live view that the CJC and every stage lead is pushing data to and working from. Not a reporting tool that gets opened before a meeting and closed after it. A permanent, shared source of truth that makes the health of the full revenue system readable at a glance.

At Run phase, the dashboard doesn't need to be sophisticated. It needs to be honest. The two primary KPIs per stage, tracked consistently, visible to everyone with a stake in the outcome. Alongside those stage KPIs, the dashboard carries the topline business metrics that tell the full story: MRR, LTV:CAC, payback period, churn rate, retention. The numbers that show whether the system is compounding or just functioning.

The CJC meeting should run from this dashboard. KRAs are shared, progress logged, blockers surfaced. Not a polished presentation: a working document that reflects reality. When a stage lead can see how their numbers affect the stage downstream, and when the CJC can see the full picture in one place, the conversations change. Problems surface earlier. Accountability stops being abstract.

This is the infrastructure Sprint is built on. Get it wrong here and Sprint-phase optimisation is polish on rusted metal.

Sprint: Optimise What You Can Now Measure

Sprint is for optimisation. It assumes that what's being optimised is already working. Advanced behavioural triggers assume the journey is mapped and the handoffs are clean. Predictive pipeline modelling assumes the data is coherent enough to model from. Pricing architecture refinement assumes the conversion and retention mechanics are stable enough that price changes can be isolated as a variable. If any of those assumptions aren't true, Sprint-phase work produces noise, not signal. Which is precisely why trying to implement mature CRM practice, segmentation, behavioural-driven automation, and lifecycle sequencing before Walk and Run phases are complete is a nightmare of confusion and missed expectations. It simply cannot be done effectively.

Mature CRM and Lifecycle Practice

Walk phase gets the CRM clean. Run phase gets it consistent. Sprint phase gets it intelligent. Behavioural-driven automation that responds to what users actually do, not just when they signed up. Segmentation that reflects real differences in user intent and value, not just demographic buckets. Lifecycle sequencing that moves customers towards their next milestone - upgrade, referral, expansion - based on signals the system is already capturing. This is the layer that moves real retention numbers. Built right, it compounds. Built early, it's expensive noise.

Attribution and Acquisition Optimisation

Sprint phase is where acquisition gets precise. Walk phase established what to measure. Run phase built the reporting infrastructure. Sprint phase closes the loop: tracing spend through to outcome, not just to click, and feeding those findings back into channel strategy, creative decisions, and audience targeting at a rapid pace. Costs fall, retention improves, organic growth accelerates, and the fundamental unit economics move in the right direction. CAC drops. LTV rises. The acquisition engine stops being a cost centre and starts behaving like a growth lever.

The Dashboard as Decision Engine

At Run phase, the shared dashboard is a source of truth. At Sprint phase, it becomes a decision-making engine. Real-time signals trigger action. Patterns in the retention data inform the CRM sequencing. Attribution findings feed back into acquisition. The topline metrics - MRR, LTV:CAC, payback period, churn, retention - stop being lagging indicators and start being predictive ones. The system tells you what's coming before it arrives.

Sprint phase isn't a destination. It's a compounding state. It requires keeping a steady eye on Walk and Run implementation fundamentals, to ensure you can consistently scale your optimisation maturity. The businesses that reach it and maintain it are the ones that stopped enjoying the rollercoaster and built the growth curve instead.

How to Know You're Ready for Sprint (Many Aren't)

Four questions.

Can your leadership team describe the customer journey accurately: the full growth funnel, supported by data, including the parts that don't reflect well on any particular stage? If the answer involves hedging or disagreement, Run phase isn't finished.

Can every stage lead name their two primary KPIs, explain why those are the right metrics, and describe what they are actively doing this week to move them? If the answer involves convoluted answers, blank stares, or a pause while they check a spreadsheet, Run phase isn't finished.

Are teams deeply collaborating at stage boundaries without top-down pressure? Or do stage boundary issues become a confusing problem that takes weeks to surface? If the latter, Run phase isn't finished.

Can teams articulate their KRAs and give a clear, honest Red/Amber/Green assessment of how far they are in implementing them? If the answer is vague or defensive, Run phase isn't finished.
Sprint begins when all four answers are yes. For many businesses reading this, that’s a future state, not a current one. That’s not a criticism. It’s a sequencing reality.

Where Are You Now? The Walk/Run/Sprint Diagnostic

Use this table to identify your current phase. The accurate answer is whichever phase describes the majority of your rows. If walk and run are mixed, you’re in walk.

Ready to get off the rollercoaster?

The Revenue Engine platform diagnoses your full growth funnel, shows you where it's leaking, and tells you what to fix first — in priority order, not gut feel.

Exit the rollercoaster

Jonathan Stanton-Humphreys is Founder and CEO of Revenue Engine. He spent a decade as a commercial executive in B2C and B2B tech - and built Revenue Engine after watching revenue leak through strategic and implementation disfunction and joins that nobody owned.

FAQ: Revenue Operations Strategy

What is a revenue operations strategy?

A revenue operations strategy is a sequenced plan for designing and improving the system that converts market opportunity into revenue. It covers the full customer journey: acquisition, onboarding, retention, expansion, and the infrastructure that connects those stages. The key word is ‘sequenced.’ A strategy without a build order produces parallel workstreams that compete for resource and typically finish nothing properly.

Where do I start with RevOps if I have no system yet?

Walk phase. Map the customer journey honestly. Establish a Customer Journey Council. Define handoffs between stages. Get everyone working from the same basic data view. That’s the foundation. Everything else is built on top of it. Resist the temptation to start with tooling or to hire a RevOps lead before the foundation exists: both are common mistakes with predictable outcomes.

How long does it take to build a functioning RevOps system?

Honest answer: it depends on the lifestage of your business. Walk phase, done properly, can be as quick as three weeks or as long as twelve. Run phase is an ongoing build: three to six months to establish the KRA and KIT layer and the cross-functional accountability structure. Sprint phase follows from there. The businesses that try to compress this timeline typically find themselves revisiting walk-phase problems twelve months later. It’s highly recommended to bring in outside help to drive this process, unless you have internal resources with the time and skills to get it done.

What’s the difference between RevOps and a CRM implementation?

A CRM implementation solves a data and process problem within a single stage or function. Revenue operations is a system-level discipline that covers every stage of the customer journey and the connections between them. CRM is one component of a RevOps system. Treating a CRM implementation as a RevOps strategy is one of the most common ways businesses end up with cleaner data inside a structurally broken system.

Do I need a dedicated RevOps hire to make this work?

Not necessarily. Walk and run phase can be led by a founder, a commercial lead, or an external consultant: the requirement is honesty about the current state and authority to make decisions about ownership and accountability. A dedicated RevOps hire makes sense at late run into sprint stage, once there’s enough system for them to direct. Hire before that and you’re paying a senior person to build foundations that could have been laid for a fraction of the cost. Or use the Revenue Engine platform: a RevOps specialist and growth strategist in one, with complete KPI benchmarks, KRAs and KITs across all funnel elements.