What we walked into
The company had a young, resourceful sales ops hire who'd done a solid job standing up HubSpot in the early days. Pipelines worked. Contacts were tracked. Deals moved. For a while, that was enough.
Then the company grew, and five departments all started building inside the same HubSpot account. No shared architecture. No naming conventions. No documentation. Each team created what they needed, when they needed it, with no coordination.
The result was predictable: properties duplicated across objects, workflows colliding, automations triggering things they shouldn't. HubSpot had become a warehouse where every team dumped everything.
Finance couldn't trust the numbers
Stripe was connected to HubSpot, but roughly one in three syncs failed. Custom integrations broke silently. Nobody could tell what had synced and what hadn't without checking manually.
The renewal pipeline was built on deal start dates. But billing actually started on the first payment date. Every renewal date in the system was wrong. Nobody had caught it because nobody had documented what "start date" was supposed to mean.
Subscriptions had no end dates. Clients who signed for a year would get billed into month thirteen and call to complain. At its worst, the company processed $60K in refunds in a single month. The renewal rate sat at 10%.
The CFO spent days closing each month. Not because the volume was high, but because nothing could be trusted without cross-checking it by hand.
What we managed to fix
Month-end revenue reconciliation went from days of manual cross-checking to roughly 3 hours, with reliable numbers the CFO could actually sign off on.
We set up a structured intake system as a single place to log, categorize, and route ops requests so the team could distinguish between product issues and ops tasks, prioritize properly, and manage their own time. The ops team recovered 6 to 8 hours a week.
We documented core RevOps workflows for the first time: billing logic and Stripe sync behavior, renewal triggers and pipeline stage definitions, lead routing and handoff criteria, request intake and escalation paths, source-of-truth mapping across systems.
The real lesson
This company didn't lack tools, budget, or talent. The original ops hire had built something real, and with the right support, the foundation was there to scale.
What was missing was leadership clarity. No org chart. No ownership model. No willingness to hold a decision long enough for it to take effect. When everything is everyone's job, nothing gets fixed.
RevOps can't succeed in a vacuum. It needs three things from leadership: defined ownership, stable structure, and enough patience to let the architecture set before remodeling again.
We don't see this as a success story. There was so much more to do. But sometimes a battle can't be won when you're pushing against the current of an organization's own culture. The problems weren't technical. They were structural. And structure starts at the top.