Building a RevOps Layer on Top of a HubSpot You Didn't Set Up
Almost nobody starts with a clean HubSpot instance. Most founder-led businesses inherit one — set up by a previous hire, an agency, or a well-meaning founder three years ago — with pipeline stages that don't match how sales actually happens, properties nobody remembers the purpose of, and workflows that fire for reasons lost to history. The instinct is to rip it out and start over. Usually the better move is a structured audit and a focused fix.
Diagnosing what's actually there, before touching anything
Before changing a single workflow, map what exists: every pipeline and its stages, every custom property and whether it's actually used, every active workflow and what it triggers. This takes a day, not a week, and it prevents the single most common mistake — deleting or 'fixing' something that a different part of the business quietly depends on.
The 80/20 of RevOps fixes
- Lifecycle stage hygiene — decide what 'lead,' 'MQL,' 'SQL,' and 'customer' actually mean in your business, and fix the records that don't match
- One source of truth for pipeline stages — if sales reports pipeline differently than what's in HubSpot, the CRM has already lost, fix the gap in one direction
- Kill dead automations — workflows nobody remembers building, firing on old logic, quietly sending the wrong emails to the wrong people
- Reporting that matches how the business actually talks about revenue — not HubSpot's default reports, the specific numbers your leadership team already reviews
What to leave alone vs. what to rebuild
Not everything inherited is broken. Custom properties that are actually populated and used should stay. Integrations that work should stay. The instinct to rebuild everything from scratch usually comes from not trusting what's there rather than from evidence it's actually failing — the audit step exists specifically to tell the difference.
Signs the RevOps layer is working
Sales and leadership are looking at the same pipeline number in the same meeting without a reconciliation conversation first. Lifecycle stage changes happen automatically instead of being manually updated (or not updated) by whoever remembers to. And the CRM stops being 'the thing sales complains about' and starts being the thing that answers questions faster than asking a person would.
Related reading
Inherited a HubSpot instance nobody trusts?
Thirty minutes to look at what's actually in there and what the fastest fix would be.
Book a call