Spencer breaks down why RevOps implementations take twice as long as expected. The main culprit: poor upfront planning and lack of systems thinking, which causes scope creep. Large builds involving ERP migrations and complex data integration can stretch 6-12 months, while tools like Clay and Cargo can help but require strategic expertise.
Chapters
How long does a revenue operations implementation actually take? This is a doozy because a lot of sales professionals, a lot of marketing professionals might argue that the best CRM in the world might be HubSpot or Salesforce. But depending on the size of your business, like we work with established businesses as well as emerging businesses, it can take as little as a month up to 6 months. If we're migrating from a private hosted application or we're moving over from an ERP layer and we're building a whole application to support the service hub as well as service operations and professional services, It can take anywhere from 2 to 6 months. Larger builds can take anywhere from 6 to 12 months. But the way that I always see it in revenue operations is that the peak build should always be listed on an engineering spec. When you work with an engineering consultancy or you work with a HubSpot engineering consultancy or a Platinum Partner or Salesforce consultancy, even it makes a lot more sense to understand what is the value and what does the outcome look like and what does it feel like on the enablement plan. What does that actually mean for your team is it's just another tool that they're going to be using on the HubSpot or the Salesforce or on the Adyen or any of the large CRMs that a revenue operations team is going to be using. But the revenue operations team is not always just centered inside of the CRM. Revenue operations at its core takes care of all of the interconnected systems. It comes back, looks at the ERP, it looks at the user database. It should look at finances. It should look at ads attribution. You should be able to calculate your cost of acquisition. Right? These all add up to one thing for revenue operations. It's revenue back to the business, or ROI, return on interest, right? So the largest scope for a revenue operations implementation usually covers the implementation of a CRM. In my instance, we love to use HubSpot. We dabble in some Salesforce. We are knowing our way around Adio quite well with the VCs in California. But most of these builds can be done if there's nothing to rip out. It can take anywhere from 2 to 3 weeks to scope out perfectly what it's going to look like. But at the larger end, it can take all the way up until 6 months just to be able to implement the large-term and the long-term solution. For instance, if you are a German company, you're probably going to have certain security requirements. And I will laugh behind the scenes because we've done business with large businesses in Europe as well as North America. But if you are trying to onboard 100 sales professionals, it is a much bigger task than it is to onboard a VP of sales at an emerging tech product startup in Silicon Valley where you have a founder, maybe a VP of sales, maybe one for deploy engineer. You probably only need 3 seats and maybe 5 or 10 capabilities inside of your CRM. And you might believe that you can actually just do it yourself and wing it and kind of, you know, vibe code your way. There are benefits to vibe coding your way into a CRM and vibe coding your way into a solution. And this is the kind of the pinnacle of the industry right now. It's build versus buy. Are you going to build your own solution and waste all of your time to build this yourself when you should really just be doing your job leading the company as a CEO or a founder? Or maybe you're really good on the technical side and you want to invest all of your time to build this for yourself so you make sure it's done really right. Well, that time that you're going to invest in doing this, it could— it completely depends on your technical ability and your strategic knowledge in revenue operations. Alternatively, another solution is to actually hire a team to be able to sprint a project like this. Take about 1 to 6 months to do it if it's a smaller implementation, anywhere from 3 to 12 months depending on the size of your team. The end outcome for revenue operations implementation though is usability. It's not just the fact it's another shiny tool. It is an enablement platform for you to do your jobs better and for the sales and the marketing professionals to be able to do their jobs better. Revenue operations is the pinnacle of the industry because it connects all of the different systems and all of the different teams. So it really, really depends on how much of a systems thinker you are. That is the lay of the land right now. There are some really great tools that you could implement for building on a CRM, including tools like Clay, Cargo, Claude, to do massive data orchestration at scale and moving records from one database to another. These are current 2026 trends, and anybody can open up an account on any of these different tools to be able to manipulate their own data. It does take a strategic professional to be able to organize that data in a comprehensive way that will scale with you, though. And that is probably the, the biggest red flag that I can flag right now to anybody that's watching this video to figure out exactly how you want to interact with the data in the future. Not just you, but anybody on your potential team within the next 3 months. This is the number one pitfall that I see when I do the implementations for large businesses, is that their failure to plan ahead ends up costing them implementation time that slows it down when you should be able to just scope it out at the beginning, figure out what the end outcome and the shape of the data and the orchestration looks like at first, and gradually build into the revenue operations implementation. implementation plan little by little. This would be the pitfall to look out for when you are doing a revenue operations implementation. And when you're going to hire an implementation party or an agency or a consultancy like mine, then you should really start to think about, is it worth your time to build it and losing your own time on task? Or is it worth your time and budget to be able to buy capacity and buy an accelerated demand to be able to up with your growth. My name is Spencer. You can find me on LinkedIn, and I can help you out with all of your revenue operations as well as your growth needs.
