“We invested in RevOps too soon.” - said no one ever But I’ve been speaking with lots of folks who didn’t bring in RevOps early enough. Now they’re dealing with: - Dirty data + messy reporting - Complete misalignment across teams - A bloated Frankenstack cobbled together by random employees over the years - Loads of other scaling pains And here’s the thing - you don’t have to hire a 5-person team to do RevOps. You can start with one of these options 1. One full-time RevOps hire who’s comfortable with your systems but can think strategically as well 2. An operationally-minded sales/marketing/CS leader who can get things started in a basic way and bring in help as needed 3. A fractional RevOps resource who can bring in best practices and implement them from the start, allowing you to build on that solid foundation and scale as you grow With one of these options, even super small start-ups can get RevOps going. It’s easier to build things right the first time 😉
Well said, Heather! From my experience, I've found even organizations who have fallen victim to all of scaling pains you listed, are STILL hesitant about making the investment in RevOps. I'm curious how you, and others, are building the business case for RevOps and helping organizations understand the ROI?
I mean, you could invest in RevOps too soon. You should at least have revenue first.* *There may be exceptions where RevOps before revenue also makes sense.
Ok but like I’m totally stealing “Frankenstack”
Number 1 is the ideal solution if you ask me 😀
Leading driven companies to transform, scale, and succeed! 📈 | Revenue + RevOps friendship advocate | Extreme foodie 🥘 | Obsessive tinkerer
5moThat first line made me laugh, because it's so true, but consistently such a low priority for a lot of early stage, high growth founders