What is RevOps
“It's the difference between companies that scale predictably and those that throw money at problems hoping something sticks.”
After spending the last decade in the sales trenches and helping clients generate over £706M in pipeline, I've learned that RevOps isn't just another buzzword that'll disappear faster than your New Year's gym membership.
Here's what I wish someone had told me five years ago about building a RevOps team that actually moves the needle.
What the Hell is RevOps Anyway?
“RevOps is when your revenue teams finally work together like a well-oiled machine.”
Revenue Operations is basically the grown-up version of "let's all just get along."
It's when your marketing, sales, and customer success teams stop operating like separate kingdoms (with their own currencies, languages, and weird territorial disputes) and start working together like a well-oiled machine.
Think of it this way: if your revenue process was a relay race, RevOps ensures nobody drops the baton. Because right now? Your marketing team is running full sprint toward sales, sales is looking the wrong direction, and customer success is still trying to figure out which race they're in.

“Most companies are losing 40-60% of qualified leads during handoffs — that's not a leak, that's a waterfall”.
Why RevOps Isn't Just Another Corporate Initiative
“You can't wait for 'things to calm down'. They never do.”
I've watched too many companies treat RevOps like it's some nice-to-have project they'll get to "when things calm down."
But let’s be real - things never calm down.
Here's what happens when you actually implement proper RevOps though:
- Deal velocity increases by 30% (because nobody's waiting three days for someone to respond to a hot lead)
- Your sales team spends more time selling instead of hunting through 47 different spreadsheets
- Marketing can finally prove their campaigns actually generate revenue (revolutionary, I know)
- Customer success stops being the team that only talks to clients when something's broken
The Hidden Cost of Wing-It Operations
Before we dive into building your team, let's address what poor RevOps is actually costing you.
When I audit prospective clients (and trust me, I've seen some things), here's what I consistently find:
The Data Disaster Zone
- Marketing thinks they generated 500 leads this month
- Sales says they only received 300
- Customer success has no idea what promises were made during the sale
- Finance is wondering why the revenue projections are always wrong
The Handoff Horror Show
- Marketing qualified lead comes in at 3 PM Friday
- Sales doesn't see it until Tuesday (because weekends, obviously)
- Lead has already moved on to a competitor who called them within 30 minutes
- Everyone blames everyone else
The Technology Tower of Babel
- Marketing uses HubSpot
- Sales swears by Salesforce
- Customer success built their own system in Excel (I wish I was joking)
- Nobody can tell you which customer is actually profitable
One client told me they were spending £50K annually on sales tools that didn't talk to each other. Their sales team was manually copying data between systems. In 2024. Let that sink in.
How to Build a RevOps Team That Actually Works

Step 1: The Reality Check Audit
Don't start by hiring people. Start by figuring out where your revenue engine is currently on fire.
I use what I call the "RevOps Emergency Triage":
The Bleeding Test: Where are you losing the most money right now?
- Is it leads disappearing after marketing hands them off?
- Sales reps spending half their time on admin work?
- Customers churning because onboarding was a disaster?
The Speed Test: How long does everything actually take?
- First response to a new lead
- MQL to SQL conversion
- Proposal to signature
- New customer onboarding
The Truth Test: What do your teams actually think is broken? (Pro tip: Ask them individually. You'll get more honest answers.)
I once did this audit for a client who thought their main problem was lead quality. Turns out, their leads were fine. Their sales team just wasn't following up because the CRM was so clunky they avoided using it. Six months of blaming marketing for the wrong problem.
Step 2: Stop Trying to Boil the Ocean
The biggest mistake I see? Companies trying to fix everything at once.
You know what happens when you try to implement 15 new processes simultaneously? Nothing. People get overwhelmed, revert to their old ways, and you're back to square one with less budget and more cynical teams.
Pick ONE thing. The one thing that's costing you the most money right now. Fix that first.
For most companies, it's the MQL to SQL handoff. Marketing says a lead is "qualified," sales disagrees, lead gets ignored, everyone points fingers.
Start here: Get marketing and sales in a room (yes, physically in the same room if possible) and agree on what "qualified" actually means. Not in theory. In practice.
What job title? What company size? What specific actions did they take? What questions did they ask?
Write it down. Make it measurable. Test it for 30 days. Adjust.
Boom. You just did RevOps.
Step 3: Your First Hire (And It's Not Who You Think)
Everyone thinks they need to hire a "RevOps Director" with a fancy resume and a bigger salary than your sales manager.
Wrong.
Your first hire should be someone I call a "Revenue Detective." This person is part analyst, part project manager, part diplomat.

What they actually do:
- Dig into your data to find where revenue is getting lost
- Map out your actual processes (not what's in the employee handbook)
- Get teams talking to each other without starting World War III
- Implement quick fixes that show immediate ROI
What they DON'T do:
- Build complex attribution models (yet)
- Redesign your entire tech stack
- Create 40-slide PowerPoints about "alignment"
I've seen companies transform their revenue operations with someone making £45K who just cared enough to ask the right questions and follow up relentlessly.
The fancy stuff can come later. First, stop the bleeding.
Step 4: The Technology Trap
Here's where most companies screw up: they think RevOps is a technology problem. It's not.
RevOps is a people and process problem that technology can help solve. But if you start with technology, you'll end up with expensive, shiny tools that nobody uses properly.
The Punch! Tech Stack Philosophy:
- Fix the process first
- Find the simplest technology that supports the process
- Get everyone actually using it
- THEN optimize and add complexity
I watched a client spend six months implementing a sophisticated marketing automation platform. Know what happened? Their sales team ignored all the leads because they didn't trust the scoring algorithm. The process was broken, not the technology.
Start with these questions:
- How are we capturing leads right now?
- Where is that data stored?
- Who needs access to it?
- What do they actually do with it?
Step 5: Making Teams Actually Work Together
This is the hard part. Not the technology. Not the processes. Getting humans to change how they've been doing things for years.
I've found that the secret isn't motivation speeches or team-building exercises (though a good pizza party never hurt anyone). It's making it easier to do things the new way than the old way.
Example: Instead of forcing sales to log into a new system to get lead information, push that information directly into the tools they already use. Make the right way the lazy way.
Another example: Instead of asking marketing to change their entire reporting structure, show them how the new process will make their campaigns look more effective (because they'll actually be more effective).
People don't resist change. They resist being made to feel stupid or having their work become harder.
The Metrics That Actually Matter
Forget vanity metrics. Focus on the numbers that directly impact your bank account:
Primary Revenue KPIs:
- Pipeline velocity (how fast deals move through your funnel)
- Customer Acquisition Cost by channel
- Revenue per employee
- Customer lifetime value by segment
Leading Indicators:
- Time to first response on new leads
- Percentage of leads contacted within 4 hours
- Number of meaningful conversations per week
- Proposal-to-close conversion rate
The Punch! Secret Metric: Multi-stakeholder engagement rate. In B2B sales, you need to engage multiple decision-makers. Track how often you're having conversations with more than one person at target accounts.
This metric alone can predict deal success better than most scoring algorithms.
Common RevOps Mistakes
Mistake #1: Perfectionism Paralysis
I've seen companies spend 18 months building the "perfect" system while their revenue suffered. Done is better than perfect. Always.
Mistake #2: Technology Before Process
If your process is broken, technology will just help you fail faster. Fix the fundamentals first.
Mistake #3: Ignoring External Partners
If you work with external agencies (ahem), integrate them into your RevOps planning from day one. We've seen too many companies treat their outsourced partners like afterthoughts, then wonder why handoffs are messy.
Mistake #4: Treating RevOps Like IT
RevOps is a business function, not a technical one. Your RevOps leader should understand strategy, not just spreadsheets.
“One client told me they were spending £50K annually on tools that didn't even talk to each other.”
The Bottom Line on RevOps
RevOps isn't about having the fanciest tech stack or the most sophisticated attribution model. It's about getting your teams to work together efficiently so you can grow predictably.
I've seen companies triple their revenue with nothing more than better communication and cleaner processes. I've also seen companies spend hundreds of thousands on RevOps initiatives that failed because they focused on complexity instead of fundamentals.
Start simple. Fix the obvious problems first. Hire people who care more about results than titles. Focus on processes before technology. And for the love of all that's profitable, get your teams talking to each other.
Your future self (and your bank account) will thank you.


“I focus on leading the direction of the business to maximise team efficiency and ensure client success”
“It's the difference between companies that scale predictably and those that throw money at problems hoping something sticks.”
After spending the last decade in the sales trenches and helping clients generate over £706M in pipeline, I've learned that RevOps isn't just another buzzword that'll disappear faster than your New Year's gym membership.
Here's what I wish someone had told me five years ago about building a RevOps team that actually moves the needle.
What the Hell is RevOps Anyway?
“RevOps is when your revenue teams finally work together like a well-oiled machine.”
Revenue Operations is basically the grown-up version of "let's all just get along."
It's when your marketing, sales, and customer success teams stop operating like separate kingdoms (with their own currencies, languages, and weird territorial disputes) and start working together like a well-oiled machine.
Think of it this way: if your revenue process was a relay race, RevOps ensures nobody drops the baton. Because right now? Your marketing team is running full sprint toward sales, sales is looking the wrong direction, and customer success is still trying to figure out which race they're in.

“Most companies are losing 40-60% of qualified leads during handoffs — that's not a leak, that's a waterfall”.
Why RevOps Isn't Just Another Corporate Initiative
“You can't wait for 'things to calm down'. They never do.”
I've watched too many companies treat RevOps like it's some nice-to-have project they'll get to "when things calm down."
But let’s be real - things never calm down.
Here's what happens when you actually implement proper RevOps though:
- Deal velocity increases by 30% (because nobody's waiting three days for someone to respond to a hot lead)
- Your sales team spends more time selling instead of hunting through 47 different spreadsheets
- Marketing can finally prove their campaigns actually generate revenue (revolutionary, I know)
- Customer success stops being the team that only talks to clients when something's broken
The Hidden Cost of Wing-It Operations
Before we dive into building your team, let's address what poor RevOps is actually costing you.
When I audit prospective clients (and trust me, I've seen some things), here's what I consistently find:
The Data Disaster Zone
- Marketing thinks they generated 500 leads this month
- Sales says they only received 300
- Customer success has no idea what promises were made during the sale
- Finance is wondering why the revenue projections are always wrong
The Handoff Horror Show
- Marketing qualified lead comes in at 3 PM Friday
- Sales doesn't see it until Tuesday (because weekends, obviously)
- Lead has already moved on to a competitor who called them within 30 minutes
- Everyone blames everyone else
The Technology Tower of Babel
- Marketing uses HubSpot
- Sales swears by Salesforce
- Customer success built their own system in Excel (I wish I was joking)
- Nobody can tell you which customer is actually profitable
One client told me they were spending £50K annually on sales tools that didn't talk to each other. Their sales team was manually copying data between systems. In 2024. Let that sink in.
How to Build a RevOps Team That Actually Works

Step 1: The Reality Check Audit
Don't start by hiring people. Start by figuring out where your revenue engine is currently on fire.
I use what I call the "RevOps Emergency Triage":
The Bleeding Test: Where are you losing the most money right now?
- Is it leads disappearing after marketing hands them off?
- Sales reps spending half their time on admin work?
- Customers churning because onboarding was a disaster?
The Speed Test: How long does everything actually take?
- First response to a new lead
- MQL to SQL conversion
- Proposal to signature
- New customer onboarding
The Truth Test: What do your teams actually think is broken? (Pro tip: Ask them individually. You'll get more honest answers.)
I once did this audit for a client who thought their main problem was lead quality. Turns out, their leads were fine. Their sales team just wasn't following up because the CRM was so clunky they avoided using it. Six months of blaming marketing for the wrong problem.
Step 2: Stop Trying to Boil the Ocean
The biggest mistake I see? Companies trying to fix everything at once.
You know what happens when you try to implement 15 new processes simultaneously? Nothing. People get overwhelmed, revert to their old ways, and you're back to square one with less budget and more cynical teams.
Pick ONE thing. The one thing that's costing you the most money right now. Fix that first.
For most companies, it's the MQL to SQL handoff. Marketing says a lead is "qualified," sales disagrees, lead gets ignored, everyone points fingers.
Start here: Get marketing and sales in a room (yes, physically in the same room if possible) and agree on what "qualified" actually means. Not in theory. In practice.
What job title? What company size? What specific actions did they take? What questions did they ask?
Write it down. Make it measurable. Test it for 30 days. Adjust.
Boom. You just did RevOps.
Step 3: Your First Hire (And It's Not Who You Think)
Everyone thinks they need to hire a "RevOps Director" with a fancy resume and a bigger salary than your sales manager.
Wrong.
Your first hire should be someone I call a "Revenue Detective." This person is part analyst, part project manager, part diplomat.

What they actually do:
- Dig into your data to find where revenue is getting lost
- Map out your actual processes (not what's in the employee handbook)
- Get teams talking to each other without starting World War III
- Implement quick fixes that show immediate ROI
What they DON'T do:
- Build complex attribution models (yet)
- Redesign your entire tech stack
- Create 40-slide PowerPoints about "alignment"
I've seen companies transform their revenue operations with someone making £45K who just cared enough to ask the right questions and follow up relentlessly.
The fancy stuff can come later. First, stop the bleeding.
Step 4: The Technology Trap
Here's where most companies screw up: they think RevOps is a technology problem. It's not.
RevOps is a people and process problem that technology can help solve. But if you start with technology, you'll end up with expensive, shiny tools that nobody uses properly.
The Punch! Tech Stack Philosophy:
- Fix the process first
- Find the simplest technology that supports the process
- Get everyone actually using it
- THEN optimize and add complexity
I watched a client spend six months implementing a sophisticated marketing automation platform. Know what happened? Their sales team ignored all the leads because they didn't trust the scoring algorithm. The process was broken, not the technology.
Start with these questions:
- How are we capturing leads right now?
- Where is that data stored?
- Who needs access to it?
- What do they actually do with it?
Step 5: Making Teams Actually Work Together
This is the hard part. Not the technology. Not the processes. Getting humans to change how they've been doing things for years.
I've found that the secret isn't motivation speeches or team-building exercises (though a good pizza party never hurt anyone). It's making it easier to do things the new way than the old way.
Example: Instead of forcing sales to log into a new system to get lead information, push that information directly into the tools they already use. Make the right way the lazy way.
Another example: Instead of asking marketing to change their entire reporting structure, show them how the new process will make their campaigns look more effective (because they'll actually be more effective).
People don't resist change. They resist being made to feel stupid or having their work become harder.
The Metrics That Actually Matter
Forget vanity metrics. Focus on the numbers that directly impact your bank account:
Primary Revenue KPIs:
- Pipeline velocity (how fast deals move through your funnel)
- Customer Acquisition Cost by channel
- Revenue per employee
- Customer lifetime value by segment
Leading Indicators:
- Time to first response on new leads
- Percentage of leads contacted within 4 hours
- Number of meaningful conversations per week
- Proposal-to-close conversion rate
The Punch! Secret Metric: Multi-stakeholder engagement rate. In B2B sales, you need to engage multiple decision-makers. Track how often you're having conversations with more than one person at target accounts.
This metric alone can predict deal success better than most scoring algorithms.
Common RevOps Mistakes
Mistake #1: Perfectionism Paralysis
I've seen companies spend 18 months building the "perfect" system while their revenue suffered. Done is better than perfect. Always.
Mistake #2: Technology Before Process
If your process is broken, technology will just help you fail faster. Fix the fundamentals first.
Mistake #3: Ignoring External Partners
If you work with external agencies (ahem), integrate them into your RevOps planning from day one. We've seen too many companies treat their outsourced partners like afterthoughts, then wonder why handoffs are messy.
Mistake #4: Treating RevOps Like IT
RevOps is a business function, not a technical one. Your RevOps leader should understand strategy, not just spreadsheets.
“One client told me they were spending £50K annually on tools that didn't even talk to each other.”
The Bottom Line on RevOps
RevOps isn't about having the fanciest tech stack or the most sophisticated attribution model. It's about getting your teams to work together efficiently so you can grow predictably.
I've seen companies triple their revenue with nothing more than better communication and cleaner processes. I've also seen companies spend hundreds of thousands on RevOps initiatives that failed because they focused on complexity instead of fundamentals.
Start simple. Fix the obvious problems first. Hire people who care more about results than titles. Focus on processes before technology. And for the love of all that's profitable, get your teams talking to each other.
Your future self (and your bank account) will thank you.