I started in marketing. Demand generation, campaigns, then marketing operations. I liked the mix of figuring out what we wanted to do and building the systems that would actually let us do it.
What frustrated me was what happened between teams. Marketing had its processes. Sales had theirs. Both had operations people, but that didn’t necessarily mean we were working from the same picture. Getting something done across that line could involve more negotiation than the work itself.
That’s a big part of what pulled me into RevOps. I wanted visibility into the whole go-to-market lifecycle, not just the part that happened to sit in my department.
The craft still belongs to the teams.
Marketing knows how to reach the market. Sales knows how to work a deal. Customer success knows what it takes to help customers get value and stay. RevOps shouldn’t pretend to replace any of that.
But someone needs to care about how it all fits together. What counts as a qualified opportunity? What actually happens when a deal closes? Where does the renewal process start? And why do three dashboards give three different answers to the same question?
RevOps is where the operational work between teams has a home.
The teams lead the craft
One operating model. Connected to Finance.
Specialization shouldn’t bring the silos back.
At an early-stage company, that might be one or two people. Nobody has a neatly defined lane. You’re working on routing in the morning and renewal reporting in the afternoon. The important thing is that someone is looking across the whole system.
As the company grows, specialization makes sense. Marketing ops, sales ops, and CS ops need people who understand the detail of those teams’ work. The mistake would be growing those capabilities and quietly rebuilding the same disconnected structure.
My preference is a shared RevOps organization, with clear leadership and close working relationships with each business team. Not because every decision needs to go through one person. Because priorities, definitions, and handoffs need somewhere to come together.
There’s more to the team than the CRM.
You need people who can turn data into something useful. People who can own the systems. Increasingly, people who can connect tools and build AI-enabled workflows. That might mean a data analyst, a systems administrator, or a GTM engineer. In a smaller team, it might mean the same person wearing a few of those hats.
The titles matter less to me than the responsibility. Someone needs to understand what happens downstream when a field, workflow, or definition changes. Finance belongs in that conversation, too. The customer lifecycle doesn’t end at closed-won.
The org chart is only part of it.
Putting everyone under a RevOps leader won’t magically create collaboration. You still need shared priorities, agreed definitions, and people who understand the teams they support. Otherwise you’ve just put the silos inside a bigger box.
That’s the version of RevOps I’m interested in building. Specialized enough to understand the work. Connected enough that the customer doesn’t disappear in the space between departments.
Human thoughts, polished with AI