Somewhere around month three, you realize the RevOps firm you hired hasn’t touched your pipeline once. They’ve cleaned your Salesforce. They’ve built twelve dashboards. They’ve written a 40-page process doc nobody reads. But the number of qualified deals moving through your funnel is exactly what it was when you signed the contract.
This is the default outcome when you hire a revops agency that operates like a Salesforce consultancy. And most of them do.
The framing below is a buyer’s diagnostic. Six questions you ask before you sign anything. Each one is designed to surface whether you’re hiring operators or advisors.
Why Most RevOps Firms Leave You With a Cleaner CRM and the Same Broken Pipeline
The market for revenue operations help is genuinely confusing. You have pure-play CRM implementers, RevOps practitioners who focus on pipeline visibility, fractional CROs who advise but don’t execute, and GTM agencies that bolt RevOps onto the side of an outbound engagement. Most of them call themselves a revenue operations agency.
The distinction that matters isn’t in the name. It’s in what they’re accountable for after the system goes live.
A CRM rebuild is not a revenue system. It’s table stakes. If your RevOps infrastructure isn’t connected to your outbound motion, your CS team’s retention data, and your pipeline attribution, it’s just a prettier spreadsheet.
The companies with tools but no revenue system almost always have one thing in common: they paid someone to build a component, not a system. The CRM got rebuilt. The outbound sequences got written. The onboarding playbook got documented. Nothing talks to anything else.
The Six Questions
Use these before you sign. They’re not gotcha questions. Any good revops firm will answer them without hesitation. The ones who can’t are telling you something.
- Do you operate after you build, or do you hand off and leave? This is the most important question. Most RevOps consultants are project-based. They scope the work, deliver the build, and move on. Ask specifically: who is responsible for running the system in month four? If the answer is “your internal team with our documentation,” you’re buying a build, not infrastructure.
- Do you own pipeline outcomes, or just reporting outputs? Anyone can build a dashboard that shows pipeline stage velocity. The question is whether they’re accountable when the numbers go sideways. Ask: what happens if pipeline drops 20% in month two post-launch? Do they adjust the system, or do they send you a report explaining why it dropped?
- Does your pod touch outbound and CS, or only the CRM? Revenue operations without a connection to outbound execution is just database management. The same is true on the other side: if your CS team’s retention signals aren’t flowing back into the CRM, your attribution is fiction. Ask which specific systems the team will integrate and operate, not just configure.
- Do you integrate across the stack, or does your work silo into one tool? A real RevOps engagement touches your CRM, your sequencing infrastructure, your enrichment layer, your CS platform, and your reporting. If the scope of work only names one tool, you’re getting a consultant, not a system builder. Ask them to describe the last full-stack build they shipped, and name the tools involved.
- Do you report on pipeline movement, or just on activity metrics? Activity reports (emails sent, calls logged, tasks completed) are easy to generate and tell you almost nothing useful. Ask what the default reporting cadence looks like and whether it includes deal velocity, stage conversion rates, and ARR attribution by channel. If they start with “here’s how we set up your dashboards,” that’s the wrong answer.
- What does the engagement look like six months after launch? This is the simplest tell. A project-based RevOps agency has a defined end date. An infrastructure partner doesn’t. Ask what the team is doing in month six. Are they still running the system? Are they iterating on it based on pipeline data? Or have they wrapped up and invoiced out?
What a Real RevOps Build Looks Like in Practice
When Phi built AtoB’s revenue system, the work wasn’t limited to CRM architecture. The RevOps layer connected to their outbound motion, their CS onboarding workflows, and their attribution tracking. Every signal fed back into the same operating layer. Sales knew which channels were producing qualified pipeline. CS knew which customer segments were churning. The system iterated because the team running it stayed embedded.
That’s the difference between a RevOps firm that builds and one that operates. The build is maybe 20% of the value. The other 80% is what happens when the system needs to respond to real pipeline data over the following months.
The Table: What You’re Actually Buying
| What they promise | What it usually means | What you actually need |
|---|---|---|
| CRM implementation | Salesforce rebuild, hand-off, goodbye | CRM architecture connected to live pipeline data |
| Revenue reporting | Activity dashboards nobody acts on | Stage conversion and ACV attribution by channel |
| Process documentation | A 40-page playbook your team ignores | Workflows embedded in the tools your team already uses |
| RevOps strategy | A deck with recommendations and no execution | An operator who runs the system after the strategy is set |
| Automation setup | One-time workflow build with no iteration | A running automation layer that adjusts when the process changes |
One Red Flag Worth Calling Out Directly
If a revops consultants team’s first deliverable is a discovery report, that’s a signal. Discovery is fine. A 20-page summary of what they found is not a deliverable. It’s a way of appearing to move without actually moving.
The right engagement starts with a system design, names the specific tools being connected, and puts an operator on the work within the first two weeks. Not a strategist. An operator.
You can read more about how we think about this at why Phi is different from a typical revenue operations agency. The short version: we build the system and we run it. Those are not the same thing, and most firms only do one.
The RevOps category is full of smart people who are very good at designing systems and very bad at running them. Before you sign, find out which one you’re hiring.
