A practical RevOps playbook: shared definitions, one source of truth, engineered handoffs and system-level reporting for scaling B2B revenue teams.
Most B2B teams do not have a demand problem. They have a friction problem. Leads arrive and sit unrouted. Marketing calls something qualified that sales quietly ignores. The CRM says one thing, the finance report another, and the Monday pipeline meeting is spent arguing about whose spreadsheet is right rather than which deals need help.
Revenue operations, RevOps, is the discipline that removes that friction. Not a job title or a software category: the practice of running marketing, sales, and customer success as one revenue system with shared data, shared definitions, and shared accountability. This playbook covers what that means in practice for a scaling UK B2B team.
The symptoms that say you need it
You rarely need RevOps at ten people. You almost always need it by fifty. The signs are consistent: nobody can answer "what is our lead-to-revenue conversion rate" without a week of spreadsheet work; handoffs between marketing and sales rely on goodwill rather than process; forecasting is a feeling; every new hire invents their own way of using the CRM; and reporting meetings debate the numbers instead of the decisions.
Each symptom looks small. Together they compound into a real commercial cost: slower cycles, leads lost in gaps, and leadership flying blind precisely when growth decisions matter most.
The playbook: four moves in order
1. Agree the definitions. Everything else fails without this. What is a lead, an opportunity, a qualified deal? What are the pipeline stages, and what evidence moves a deal between them? Get marketing, sales, and leadership to sign the same one-page glossary. This costs nothing and fixes more reporting arguments than any tool.
2. Make the CRM the single source of truth. One system holds the customer record, the pipeline, and the history, and every other tool feeds it. That means ruthless cleanup: deduplication, dead field removal, required fields cut to the few that drive decisions. Our work on choosing the right CRM covers the platform decision; the harder work is the operating discipline around it, which is where our CRM and revenue operations practice spends most of its time.
3. Engineer the handoffs. The revenue leaks are almost always between teams, not within them. Define what happens, automatically and within minutes, when a lead qualifies, when a deal closes, and when an account shows risk. Routing, notification, context attached. When we rebuilt these flows for Edinburgh Whisky Academy, administrative workload dropped by 40 percent and follow-up stopped depending on who happened to be at their desk. Our sales process optimisation work lives almost entirely in this step.
4. Report on the system, not the silos. Once definitions and data are sound, build the small set of numbers leadership actually runs the business on: pipeline coverage against target, conversion by stage, velocity, acquisition cost by segment, and revenue per rep. Weekly, automated, argued about never. The meeting changes from "whose number is right" to "what do we do about it".
What to avoid
Three failure modes account for most abandoned RevOps efforts. Buying tools before agreeing definitions, which automates the confusion. Building for an imagined future scale, with forty pipeline stages and mandatory fields nobody fills honestly. And treating RevOps as an IT project rather than a commercial one; the point is faster, cleaner revenue decisions, and every design choice should trace back to that. It is the same standard we hold every engagement to across our CRM and customer data work: judged by commercial outcomes, not by system elegance.
What good looks like a year in
Teams that run this playbook properly describe the same changes. Forecasts within a sensible margin of actuals. New reps productive in weeks because the process teaches itself. Marketing and sales sharing one funnel view and one definition of success. Leadership decisions made in the Monday meeting rather than deferred for better data. None of it is glamorous. All of it compounds, quarter after quarter, into the thing that actually matters: a revenue engine that scales without multiplying headcount.
If your team is showing the symptoms, the fix is more structured than you might fear and less expensive than the friction. Talk to us about a revenue operations review, and we will show you where the leaks are before you commit to anything.
