Stop trying to fix the fruits. Fix the roots.

Hard-working teams. Underperforming revenue. It's more common than you'd think, and the fix is rarely the people.

The founder or senior exec who can't work out why their revenue operation isn't performing has usually already tried the obvious things. Hired a stronger acquisition lead. Demanded more from the CRM team. Run an NPS survey. None of it shifted the growth line in any meaningful way. So the question moves to: is it the market? Is it the product? Is it the tools? Is it the team?

Usually, it's none of those. The problem is aim and coherence: a revenue system where every stage of the growth funnel is being managed, but the targets and system itself were never properly built. Stages with no clear owner. Metrics that generate noise without signal. A customer journey that someone documented at launch and nobody has looked at since. And the joins between stages: the handoffs where one team's job ends and another's begins, owned by nobody.

This post is a framework for defining your revenue operation clearly. The five keys. What they look like when they're missing. What they look like when they're working. And why fixing the visible symptoms without addressing the underlying structure is how companies spend years busy but not growing.

Why Revenue Operations Breaks Down (And Why It's Rarely the People)

The conventional diagnosis of a revenue operations problem - revops, in common usage - reaches for one of four explanations: wrong tools, wrong skills, wrong org chart, or better KPI targets. Each one addresses something real. None of them addresses the root.

Tooling is the most common culprit people reach for. If your CRM isn't clean, your attribution is broken, or your data warehouse is a mess, fixing those things matters. But the same tools that underperform in a structurally incoherent system will underperform after the upgrade too. Tools don't create coherence. They amplify or obfuscate whatever's already there.

Skills and headcount are the second instinct. Hire a RevOps Director. Bring in an acquisition specialist. Bring in a single-stage consultancy. These interventions help when the problem is capability. They don't help when the problem is that capable people are pointing at the wrong things, in the wrong sequence, with the wrong practices, and without anyone owning the joins between them.

Org chart redesign and KPI targeting are the same problem, one step removed. You can reorganise teams around a broken system and produce a tidier version of the same results. You can assign sharper targets to stages that are poorly defined and generate activity that doesn't compound.

The real problem, in almost every case, is that the revenue operation was never coherently designed. It grew.

Stage by stage, hire by hire, quarter by quarter. Each addition made sense in isolation. The system that resulted wasn't designed. It accumulated, one decision and hire at a time.

The four instincts that send RevOps in the wrong direction

The tooling question. The hiring question. The org design question. The KPI question. All four are fruit-level interventions: they address what's visible at the surface. They don't address why the tree keeps producing the same fruit.

When you audit the tooling, you find tools that could work if the stages they serve were properly defined. When you audit the team, you find people doing their jobs well inside a system that doesn't connect their work to the outcome they're nominally responsible for. When you redesign the org chart, you find that the handoff problem moves to the new boundary lines instead of disappearing. When you sharpen the KPI targets, you find that hitting them harder doesn't close the gap between what the business is doing and what it needs to achieve.

Stop fixing the fruits. Fix the roots.

Revenue Engine's KPI/KRA/KIT model, developed and refined across years of commercial diagnostic work, is the operating framework that does root-level work. It's worth understanding precisely, because the terms are often used loosely elsewhere.

KPIs (Key Performance Indicators) are the metrics that tell you whether a stage is performing. The problem is that the universe of trackable metrics is vast. Many teams are measuring too many things simultaneously, or the wrong things entirely: this is often caused by the tools they use, as the average single tool has a multitude of metrics, many of which are low-priority polish. The result is high noise, low signal, and lower accountability. Because when everything is a priority, nothing is.

KRAs (Key Result Areas) are the strategic result areas intrinsically linked to each KPI. You don't chase the KPI directly. You define and own the result areas that, when performing well, move the KPI as a natural consequence. KPIs and KRAs are symbiotic: you can't define the right result areas without knowing which metrics you're trying to move, and you can't know which metrics matter without understanding what's achievable in your result areas.

KITs (Key Implementation Tasks) are the best practice operating layer that enables the KRAs. Not a metric. Not a target. The how: what you do consistently, at the right cadence, with the right ownership, to make the KRA perform. KITs enable KRAs. KRAs move KPIs. That's the chain.

Fix the KITs and you fix operational excellence. Fix the KRAs and you fix strategic excellence. KRAs + KITs = healthy roots, and the fruits follow. Chase the KPIs directly and you're fiddling with the branches while the roots stay broken.

The Five Keys to a Revenue Operation That Actually Works

The five keys below are sequential and compounding. Each one enables the next. Missing one doesn't just create a gap in that area, it limits everything downstream. A company with strong stage ownership but no customer journey awareness is optimising stages that don't connect into a coherent experience. A company with a functioning customer journey but no KRA discipline underneath it is a well-coordinated team pointing at the wrong things.

Read through all five before deciding which one your operation is missing. The answer is usually further back in the sequence than it first appears.

Key 1: Customer Journey Awareness

You can't own what you haven't mapped. Not mapped in the sense of a process diagram that lives in a Notion doc. Mapped in the sense of a commercially honest account of what happens to a customer from the moment they become aware of the product to the moment they either churn or become an advocate.

Deloitte's research puts the commercial value of genuine customer centricity at 60% higher profitability than organisations that aren't (Deloitte, 2014). That figure is often cited. What's less often acknowledged is how many organisations believe they're customer-centric while operating without a customer journey map, or on one that hasn't been updated since the product launched and was written by the teams responsible for each stage. That's not a map. That's self-delusion.

Two failure modes produce this consistently. The first is lack of honesty: companies don't like owning a poor customer experience. The map reflects what they wish were true. When you ask a CRM team to document the customer journey through CRM, you get a CRM team's version of a journey that works. You don't get an honest read of what the customer actually experiences.

The second failure mode is narrowly committed leadership. The technical founder who prioritises product features above all else. The visionary founder who prioritises brand and PR. Either way, the result is a strong customer experience in a thin slice of the full journey, and a system that leaks everywhere else, because nobody with authority over the whole was ever committed to the whole.

Strategic journey mapping: honest, full-journey, commercially owned at the top, produces substantially higher marketing ROI, cross-sell conversion, and referral revenue than journey mapping done stage by stage. It also produces a fundamentally different picture of where the revenue system needs work. Usually an uncomfortable one.

Key 2: Stage Ownership and the Right KPIs

Once the journey is honestly mapped, every stage needs two things: a clear owner and a metric that actually reflects efficiency and revenue health at that stage, not just activity within it.

Stage ownership fails in two directions. The first is nobody's job: the stage exists in the journey, generates some data, but has no single named person accountable for its performance and the decisions that affect it. The second is everybody's job, which produces the same outcome by a different route.

The KPI problem is at least as common. Only 26% of senior managers strongly agree their KPIs align with strategic objectives (MIT Sloan/BCG, 2018). How does that happen? Not because they don't care. Because the key drivers remain undiscussed, metrics and reports proliferate, dashboards multiply, signal gets buried under noise, and busyness keeps it that way.

A useful discipline is to define two KPIs per stage: one that reflects efficiency health, one that reflects revenue contribution. Efficiency matters because operational hygiene compounds into revenue outcomes. Revenue matters because that's what the system exists to produce.

The right KPIs for a stage are the ones that, if they moved in the right direction, you'd be confident the stage was healthier. Not the ones that are easiest to report. Not the ones that make the team look productive. The ones that connect stage performance to critical efficiency and revenue growth.

Key 3: KRAs and KITs - the Operating Layer Beneath the Metrics

This is where the KPI/KRA/KIT model does its most useful work, and where most RevOps programmes stall.

Knowing the right KPIs for a stage tells you what to watch and aim for. It doesn't tell you what to build.

KRAs (Key Result Areas) are the bridge: the strategic result areas that, when functioning well, produce the KPI outcome you need. An onboarding team with the right Day-14 activation KPI might have KRAs around core product value demonstration sequencing, friction point identification, and progressive disclosure of key benefits. These aren't sub-metrics. They're the strategic areas where ownership and improvement produce the KPI result.

KITs (Key Implementation Tasks) sit beneath the KRAs: the specific recurring actions, processes, and operating disciplines that make each KRA perform. A KRA around friction point identification might have KITs covering the user session review cadence, the drop-off analysis schedule, and the product feedback loop protocol. Not exciting. Absolutely critical.

KITs underpin KRAs. KRAs drive KPIs. Combined KPIs shape growth. That's the chain.

The distance between a team that hits its KPIs and a team that doesn't is almost always found in the KRA and KIT layer, not in the skills of the people or the quality of the tools. What gets done, by whom, at what level of excellence and cadence, with what ownership. That's the bedrock of revenue operations. But without strategic intent excellent operations can become well managed futility.

Key 4: Team Cohesion and Journey Cohesion: the Flywheel

The first three keys produce a system with clear journey ownership, stage accountability, and operating discipline beneath correctly defined metrics. Key 4 is what makes that system compound across the full growth funnel rather than just function.

When teams understand the interrelatedness of their KPIs, the system starts to generate its own momentum. Improvements in one stage feed improvements in others. Problems surface earlier, because the teams adjacent to a failing stage can see it before it shows up in the stage's own metrics. Organisations that truly align around the customer see 2.4 times higher revenue growth and twice the growth in profitability (Forrester, 2023). That's game, set and match for fully enacted cross-functional customer journey alignment. Cross-functional coherence doesn't just improve individual stage performance, it changes the trajectory of the whole.

Our Customer Journey Council model is the mechanism for making this happen in practice. A cross-functional group with representatives from every stage of the journey, meeting with sufficient regularity and seniority to make decisions rather than just share updates. Its job is not to replace stage ownership. It's to own the joins. To make explicit what happens at the boundary between one team's work and the next.

Most companies that describe themselves as cross-functional are describing a reporting structure. Genuine journey cohesion is about shared accountability for the handoffs, not just shared visibility of the metrics. When that happens, the system stops being managed and starts being owned. That's when it compounds.

Key 5: Iterative Implementation: Walk, Run, Sprint

A common pitfall in revenue operations implementation is trying to act on all of it simultaneously. A company that identifies five structural problems in its revenue operation and launches five workstreams to fix them in parallel will, in most cases, fix none of them properly. Resources split, ownership blurs, progress is reported on all five fronts, and eighteen months later the underlying system is marginally tidier than it was.

The Pareto principle applies to implementation sequencing. Eighty per cent of the revenue and efficiency improvement available from a RevOps programme comes from twenty per cent of the work, if that twenty per cent is identified correctly and actioned first. Walk phase: the fundamentals, customer journey mapped honestly, stage ownership assigned, KPIs defined. Run phase: the KRA and KIT layer, and the CJC. Sprint phase: specialisation, more sophisticated behavioural triggers, advanced attribution, pricing architecture refinement, and deeper KPI layers for each stage.

Revenue Engine's diagnostic framework is built around this principle. The KRAs and KITs we deploy aren't one-size-fits-all: they're staged to the maturity of the business. The diagnostic tells you which phase you're actually in, not which phase you think you're in.

Don't bother polishing acquisition targeting before onboarding is fixed. The returns on acquisition optimisation are a fraction of the returns on fixing what happens to the users you're already acquiring. Walk first. Sprint later.

The Five Keys: Typical vs. Good

Where the Five Keys Connect: Handoff Health as the Multiplier

The five keys, working together, produce a coherent revenue operation. Handoff Health is what multiplies efficacy and ensures they stay coherent over time.

Handoff Health is the diagnostic of the joins between stages: what happens at the transition from acquisition to onboarding, from onboarding to CRM, from CRM to customer service, from customer service to product. In almost every revenue operations diagnostic Revenue Engine runs, a significant concentration of revenue leakage is not inside a single stage. It's in the handoffs between them, where one team's remit ends and the next begins, and nobody has a KRA for what happens in between.

The reason is structural. KPI ownership tends to be defined by stage. The acquisition team is pushing for its KPIs. The onboarding team focuses on completion rates. At the boundary between them, ownership goes fuzzy. What happens in between: the expectation the acquisition messaging set, the customer journey the user now needs to find, is nobody's stated KRA.

A revenue operation with strong individual stage performance but weak handoff health will consistently underperform its potential, not because any team is failing, but because the joins between the teams are leaking.

This is where a revenue operations audit earns its return: not just identifying which key is underdeveloped, but mapping the entire journey and where the keys are failing to connect. Where the KIT layer exists within a stage but breaks down at the handoff point. Where the customer journey map is honest about stages but silent about transitions. For a full-funnel view of where these leaks show up in practice, our growth audit post covers what a full diagnostic of leak points produces: the revenue operations audit is the companion piece that diagnoses why the system keeps producing those leaks.

The next post takes this framework and makes it operational: how to assess your own revenue operation, identify which key is your weakest link, and the right sequence to fix it.

Get Your Revenue Operation Working as a Growth System

If you've been fixing fruits while the roots stay broken, the Revenue Engine diagnostic finds your roots and tells you exactly what to fix first. A structured read across all nine stages of your growth funnel, acquisition, website conversion, ASO, onboarding, CRM and lifecycle, referral, customer service, monetisation, and handoff health, that maps your customer journey, builds your CJC foundation, and locks in the KRAs and KITs that make each stage perform.

Book a demo

Jonathan Stanton-Humphreys spent a decade as a commercial executive in B2C and B2B tech, watching good teams lose revenue in the gaps between them. Revenue Engine is what he built to fix that.

FAQ: Revenue Operations

What is revenue operations and why does it matter?

Revenue operations (commonly referred to as revops) is the discipline of designing, owning, and improving the system through which a business converts its market opportunity into revenue. It covers every stage of the customer journey, including acquisition, onboarding, retention, expansion, and advocacy, and the operational infrastructure that connects those stages. It matters because many revenue problems aren't stage problems. They're system problems. And a system that was never properly designed will keep producing the same results regardless of how well individual stages are managed.

What's the difference between revenue operations and sales operations?

Sales operations focuses on the sales function: pipeline management, forecasting, CRM hygiene, sales team performance. Revenue operations covers the entire customer lifecycle, including stages that have nothing to do with sales in the traditional sense: onboarding, lifecycle communications, customer service, pricing. In product-led or subscription businesses, the majority of revenue is generated outside the sales stage. Revenue operations is the discipline that owns the whole.

What are KRAs and KITs in a revenue operations context?

KRAs (Key Result Areas) are the strategic result areas that, when performing well, produce the KPI outcome a stage needs. KITs (Key Implementation Tasks) are the recurring operating practices that make the KRAs perform. The distinction matters because many RevOps programmes focus on KPIs: what to measure, without defining what to build and do to make those measurements move. KRAs and KITs are the layer beneath the metrics: the root-level work that determines whether KPIs improve or stay stuck.

In the Revenue Engine Platform, this layer is built in. Activate a module and you get primary KPI benchmarks tuned to your sector and stage, the KRAs that drive them, and a selectable KIT library covering the specific implementation tasks for that stage. Activate what's relevant. Track how well your team is executing the elements that move your KPIs.

How do I know if my revenue operation has a coherence problem?

Three signals. First: your customer journey map is either non-existent or hasn't been updated honestly in more than six months. Second: asking your stage leads what their key KPIs are, how they know that's the right target, and what they're doing right now to get there, gets vague answers or blank stares. Third: when something goes wrong at a stage boundary, there's no clear owner. It's a cross-team problem that takes weeks to diagnose because nobody has a KRA for the handoff. Any one of these is a real problem. All three together is calamity.

When should a founder start thinking seriously about revenue operations?

The earlier the better, and certainly before you scale acquisition. Scaling acquisition into a system with no stage ownership, unclear KPIs, and poor handoff health doesn't accelerate growth, it amplifies the leaks.

There are two ways to approach it. Wait until you have enough customer volume to see patterns in the journey data, enough team structure to have stage owners, and enough growth ambition to care whether the system compounds or just functions. That's the traditional route, and for many businesses it arrives earlier than they think. Or implement the Revenue Engine Platform with a small team from the start. The diagnostic, the KPI benchmarks, the KRAs and KITs, built in from day one. No fixing a cobbled-together system down the line: just best practice and clarity from day one.