revops without a revops team

One day in June, a lead channel went quiet at the installation company whose systems I run. No error. No email from the platform. The enquiries just stopped, and they stayed stopped for days. Want to know who caught it? Not the system. The office planner, because she had a feeling it was quieter than usual. She was right. The channel had been dry for days while everything looked fine from the outside.

That one kept nagging at me, because nothing was broken on any side we could see. The integration worked, the CRM worked, everyone did their job. And still, revenue leaked away for days without a single link in the chain finding that remarkable. A failure like that makes no sound. It’s exactly the kind of problem big companies stand up an entire team for. That team is called RevOps these days.

what revops is, in plain language

Revenue Operations is the idea that marketing, sales and service form one chain that produces the revenue together, rather than three departments with their own tools and their own version of the truth. So: one place where the data comes together, one set of numbers everyone looks at, and someone minding the machinery underneath. The term came out of Forrester around 2018 and has grown hard since; a couple of years back, Director of Revenue Operations sat in LinkedIn’s list of fastest-growing jobs in America. Dutch never even bothered translating it. Here it’s just RevOps, and it lives almost entirely at SaaS companies and scale-ups, in vacancies full of HubSpot and Salesforce.

And that’s where it stays. I don’t know a single installation firm, painting company or maintenance outfit with a RevOps manager. Never going to happen, either. Doesn’t need to.

you don’t have the team. you do have the problem

Look at the average SMB revenue chain. Enquiries arrive by email, a web form and three lead platforms. Quotes live in a quoting tool, or in Word. Invoices sit in the bookkeeping software. Three islands, and between those islands: little ferries of retyping and hoping for the best.

At my installation company, the question “how are we actually doing” could only be answered by someone digging through three systems and adding it up in her head. The CRM knew what was in play, the bookkeeping knew what came in, the old project system knew what once was. Each held a piece of the truth, nobody held the whole. So I built a dashboard on top that pulls those three sources together: revenue, open quotes, and how fast we respond to new enquiries. I call the thing the Meter Cupboard, after the spot in a Dutch house where all the gauges live. Since it went up, “how are we doing” isn’t excavation work anymore. It’s one glance at one screen.

That’s half of what a RevOps team does. And you don’t need a team for it.

the other half is monitoring, and everyone forgets it

The glamorous side of RevOps is the dashboard. The indispensable side is duller: finding out something has stalled before a human happens to feel it.

After that silent June week I set this up the way I now recommend everywhere. Every morning an automatic check runs across the chain, and the very first check is the dumbest one imaginable: are leads still coming in. That’s it. Everything else comes after. And just as important: the check isn’t allowed to cry wolf. We’d switched off an earlier monitor here because it kept firing false alarms, and an alarm you’ve learned to ignore is worse than no alarm. So the check first looks for an innocent explanation on its own, and only makes noise when things are genuinely off.

Since then, the question isn’t whether someone notices a silence. The system notices its own silences. It wouldn’t have prevented that June week, but it would’ve cut it off on day one instead of day four. What a missed enquiry costs, I rarely have to explain to a business owner. That a system should watch itself, apparently I do.

why this suddenly became affordable

Five years ago this story was simply out of reach for a fifteen-person company, let’s be honest about that. A dashboard across three systems, automated monitoring, follow-up that keeps itself moving: that was agency custom work, at agency prices.

What changed isn’t that the systems got simpler. It’s that one builder with AI agents can now handle the entire chain. The integrations, the checks, the dashboard: I build them these days with an agent alongside doing half the digging, and through MCP those agents talk to the systems directly and safely. America has since invented a job title for the person doing this work. You don’t need to hire that title. You do need to steal its logic: one truth across your chain, monitoring that speaks up on its own, and a handful of numbers you genuinely look at every week.

You don’t need a RevOps team. You need a revenue system that keeps an eye on itself, and one person who builds it.