In this article
Where the leaks are, and why nobody owns them
Draw the path a customer takes: an enquiry from an ad or a search or a referral; qualification; a deal worked through stages; an order; onboarding; service; reorder or renewal. Then mark who owns each step. In most SMEs, marketing owns the first, sales the middle, delivery the end, and nobody owns the handovers — which is where the enquiry sits unassigned for a day, the qualification notes never reach the salesperson, the order arrives at delivery with the promise the salesperson made missing, and the customer who is going quiet is seen by nobody because each function looks only at its own list.
RevOps is naming an owner for the path as a whole. The owner does not do the selling or the marketing; they make sure the path works.
Alignment across marketing, sales and customer success
Alignment means the three functions share definitions, a system and a number. Definitions: what a lead is, what a qualified lead is, what an opportunity is, what a customer is, what churn is — written once and used by everyone, so that marketing’s “fifty leads” and sales’s “five real ones” are the same conversation. A system: one CRM that every function writes into and reads from, so the handovers are records rather than messages. A number: revenue, and the funnel that leads to it — enquiries, qualified, opportunities, customers, retained — on one page, with each function’s contribution visible in the same units.
The practical effect is that marketing is judged on customers rather than leads, sales on conversion of what marketing sent rather than on excuses about it, and service on the customers who stayed. The arguments stop, because the numbers are shared.
Process, technology, data and reporting responsibilities
Process: the RevOps owner holds the written path — the sales process, the qualification standard, the handover rules, the onboarding steps, the service standard — and changes it when the evidence says so, in consultation with the people who run it. Technology: they own the CRM and what connects to it — the website form, WhatsApp, email, call tracking, the accounts link — so that one person can answer “why is this enquiry not in the system?” Data: the standards, the required fields, the monthly clean, the source tagging that makes attribution possible. Reporting: the one page the owner reads weekly — the funnel by source, pipeline coverage, response time, conversion by stage, retention — and the monthly review that turns it into decisions.
Four responsibilities, one person. In an SME that person is often the operations lead, the marketing manager, or a capable coordinator — someone who likes systems and is trusted by the salespeople.
A lightweight RevOps model for a small business
One owner, a few hours a week. One CRM, with the path configured as stages and the integrations writing in. One page of definitions. One funnel report, weekly, by source, from enquiry to retained customer. One monthly review — an hour — with marketing, sales and delivery in the room, on the page, ending in three decisions. One data-quality check a month. One automation added a month once the basics run — lead assignment, a follow-up sequence, a stale-deal flag, a health score. That is the whole model, and it fits a business of ten people as well as a hundred.
The first quarter is spent on the definitions, the CRM configuration and the funnel report; after that the job is the weekly page, the monthly review and the improvements. The owner’s responsibility is to read the page and attend the review; the RevOps owner’s is to make the page true.
Map · use it here or print it
A lightweight RevOps model for an SME
Five responsibilities that make marketing, sales and customer care one revenue engine — held by two or three people part-time, not a department.
One funnel, one set of definitions
Lead, qualified, opportunity, customer, at-risk: defined once, in writing, used by everyone.
- Owner: the sales head, with marketing
- Output: a one-page glossary and the CRM stages that match it
One process across the handoffs
Marketing to sales, sales to delivery, delivery to account management — each with what is passed and within what time.
- Owner: the operations or admin lead
- Output: the response standard, the handover form, the onboarding plan
One system of record
The CRM holds every enquiry, deal, customer and interaction; other tools feed it.
- Owner: the CRM owner
- Output: integrations, data standards, the monthly clean-up
One set of numbers
A weekly page from enquiry to renewal that every function reads, with the same definitions.
- Owner: whoever builds the reports — often the finance or admin lead
- Output: the weekly funnel, cost per qualified lead by source, win rate, retention
One review
A fortnightly hour with marketing, sales and delivery in the room, reading the page and deciding what changes.
- Owner: the business owner
- Output: three actions, each with a name and a date
Whether you need it: a business with one salesperson and no marketing does not. One with a marketing spend, two or more salespeople and repeat customers is already doing RevOps badly by accident; this makes it deliberate.
Free to print and share with your team.
Mistakes, and whether you need it
The mistakes: hiring a RevOps person before there is a process to operate; buying a stack of tools and calling it RevOps; giving the job to the sales manager, who optimises for sales; reporting activity rather than the funnel; and running the monthly review as a recital rather than a decision meeting. A safeguard: if nobody can produce the funnel from enquiry to retained customer by source, for last month, on one page, the job is not being done — whatever it is called.
Does an SME need it? If marketing, sales and delivery are three people or more, if enquiries come from more than one source, and if the owner cannot see the funnel without asking — yes, as a job. This is the RevOps assessment we do — the path mapped, the leaks found, the definitions written, the CRM and integrations configured, the funnel page built, and the monthly review run with you for a quarter, with a named person on your side trained to own it afterwards — and the free audit starts by drawing your customer’s path and marking who owns each step.
Questions owners ask
Is RevOps just a new name for sales operations?
Sales operations serves sales. RevOps owns the whole path — marketing, sales and customer work — and the handovers between them, which is where the customers are lost. The difference is the scope.
Do we need to hire someone?
Usually not at first. A capable operations or marketing person, or a coordinator who likes systems, can own it in a few hours a week once the path and the CRM are set up. Hire when the volume outgrows the hours.
What tools does RevOps need?
One CRM with the enquiry sources and the accounts link connected, and a spreadsheet or the CRM’s own reporting for the funnel page. Tools are the least of it; definitions and ownership are most of it.
What should the monthly review cover?
The funnel by source from enquiry to retained customer, the handovers that leaked, the three numbers that moved, and three decisions with names on them. An hour, with marketing, sales and delivery in the room.
How do we know it is working?
The funnel page exists and is trusted, response time and stage conversion improve, marketing is judged on customers, and the arguments between functions turn into decisions about the path.
What does GullySales do?
The path map and leak analysis, the definitions page, the CRM and integration setup, the funnel report, and the first quarter of monthly reviews, with your person trained to own it afterwards. Scoped in the free audit and priced in writing.