GM! Let’s talk about…
The Hiring Trap
You've been running the RevOps rhythm yourself.
Forecast accuracy improves.
Coaching becomes sharper.
Pipeline quality strengthens.
The system works.
But eventually, you hit a limit.
And this is where many companies make expensive mistakes.
They hire someone to "own the CRM."
Three months later:
reports nobody reads
processes reps avoid
data standards that create friction instead of clarity
Or they hire someone to build dashboards.
The dashboards look great.
Nobody changes their behaviour.
The forecast stays unreliable.
Or they hire a Salesforce specialist who optimises the system into unusability.
Everything becomes slower.
Reps disengage.
All three failures share the same root cause:
They hired for tools instead of judgment.
When to Hire RevOps
You do not hire RevOps based on ARR alone.
You hire when the cost of operating without RevOps exceeds the cost of building the function.
$2M–$5M ARR
Run the rhythm yourself.
If RevOps requires more than 8–10 hours weekly, investigate the process before expanding headcount.
$5M–$10M ARR
Introduce analyst support.
Focus areas:
reporting
CRM administration
data maintenance
repetitive operational tasks
Protect leadership time for strategic thinking.
$10M–$20M ARR
Build a dedicated RevOps function.
Complexity increases:
multiple managers
territory planning
compensation modelling
coaching infrastructure
forecast governance
Operational leadership becomes necessary.
$20M–$50M ARR
Expand capacity thoughtfully.
Typical structure:
1 RevOps manager
1–2 analysts
Managers drive decisions.
Analysts support execution.
$50M+
Specialisation becomes valuable.
Forecasting.
Systems.
Territories.
Analytics.
The function evolves alongside organisational complexity.
The 3 Levels of RevOps
Many companies hire one person and expect them to do everything.
That rarely works.
Level 1: RevOps Analyst
Focus:
reporting
CRM administration
data quality
onboarding support
Judgment requirement: Low
Success profile:
detail-oriented
organised
process-driven
Level 2: RevOps Manager
Focus:
territory design
forecasting process
compensation modelling
coaching operations
bottleneck diagnosis
Judgment requirement: High
Success profile:
commercially minded
comfortable with ambiguity
able to influence stakeholders
Level 3: RevOps Director
Focus:
system architecture
team leadership
annual planning
executive communication
revenue accountability
Judgment requirement: Very high
Success profile:
systems thinker
strategic operator
trusted leadership partner
Most hiring mistakes occur because organisations hire the wrong level for the problems they actually have.
The One Hiring Rule
Hire for judgment.
Not certifications.
Not tool proficiency.
Not platform expertise.
Tools change.
Judgment compounds.
Bad hiring question:
"Can they build Salesforce flows?"
Better hiring question:
"How would they diagnose a Proposal-stage bottleneck?"
Can they:
identify multiple causes?
challenge assumptions?
design experiments?
prioritise interventions?
If they can think clearly through ambiguity, the tools can be learned.
The First 90 Days
Strong RevOps hires do not arrive making changes.
They arrive learning.
Weeks 1–2: Observe
attend coaching sessions
observe forecast reviews
study pipeline movement
understand decision-making patterns
No optimisation yet.
Weeks 3–4: Investigate
Ask:
what creates friction?
where do deals stall?
what slows managers down?
what frustrates reps?
Map problems before proposing solutions.
Weeks 5–8: Experiment
Test one improvement.
Measure impact.
If it works:
standardise it
If it fails:
remove it
Small wins build credibility.
Weeks 9–12: Expand Ownership
Begin owning:
reporting cadence
territory recommendations
compensation support
forecast processes
By now, context has caught up with responsibility.
Your Move
Ask yourself:
Is RevOps consuming more than 10 hours weekly?
Is forecast accuracy no longer improving?
Is operational complexity outgrowing your current structure?
If the answer is yes, the question may not be whether to hire.
It may be whether you've waited too long.
And when you do hire:
Hire for judgment first.
The tools are just how the thinking gets executed.
→ Next week: The hidden failure points that quietly break otherwise healthy RevOps systems.
— Pipeline Playbook