> ## Content Index > Fetch the complete content index at: https://www.revenueoperationsalliance.com/llms.txt > Use this file to discover other available public pages before exploring further. # Why your next revenue tool should be harder to buy - URL: https://www.revenueoperationsalliance.com/why-your-next-revenue-tool-should-be-harder-to-buy/ - Published: 2026-09-29T13:37:00.000Z - Updated: 2026-10-06T13:46:24.000Z - Description: Sprawl gets built at the point of purchase. One signed order form at a time, each backed by a business case that looked fine on its own. - Author: Marisa Garanhel - Tags: Tech & tools, Articles Most conversations about [tech sprawl](https://www.revenueoperationsalliance.com/the-hidden-costs-of-revenue-tech-sprawl/) start with the stack you already have: the overlapping tools, the syncs that fail quietly, the seats nobody logs into. By the time you're counting those, the expensive decisions have already been made. Sprawl gets built at the point of purchase. One signed order form at a time, each backed by a business case that looked fine on its own. That makes the next contract the cheapest place to stop it. Once a tool is live, wired into the [CRM](https://www.revenueoperationsalliance.com/your-crm-data-isnt-accurate/) and part of someone's daily routine, removing it costs far more than declining it would have. [The hidden costs of revenue tech sprawlAn actionable eBook breaking down the true cost of disconnected sales tools, featuring expert insights and proven consolidation strategies from revenue leaders.![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/icon/android-chrome-192x192-33cfc3ff-4ec9-4db0-8925-d7bb8fc9b8d5.png)Revenue Operations AllianceRevenue Operations Alliance![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/thumbnail/ROA_Revenue_Tech_Sprawl_Sponsored_eBook-Supporting-Assets_Meta-d8118db7-9c4e-4a36-9abb-3179e1635088.png)](https://www.revenueoperationsalliance.com/the-hidden-costs-of-revenue-tech-sprawl/) ## How revenue tools get bought Very few [revenue tools](https://www.revenueoperationsalliance.com/the-top-5-tools-of-the-ai-revenue-revolution/) arrive through a planned evaluation. Most come in one of three ways. - **The vendor pitch.** A rep shows up with a demo and a "best-in-class" claim, and the gap it fills is real enough to say yes. - **The top-down ask.** A CEO or CRO saw a tool at their last company, or at a conference, and wants it here. - **The local fix.** One team hits a problem, finds a tool that solves it, and puts it on a card. Nobody outside that team is asked. None of these routes includes a step where someone checks how the tool fits what's already running. Michelle Hulse, Director of Revenue Operations EMEA at Pax8, described the pattern to an ROA London audience: > "There is a pressure to keep up. There are vendors out there telling us they are best in class, so we believe them and go, yes, we need that. Decision-making is driven from the top. A CEO will come to you wanting to implement a tool. We don't have a shared blueprint across marketing ops, sales ops, and customer success ops." That missing blueprint is where the cost starts. Marketing ops, sales ops and CS ops each buy for their own part of the funnel, and RevOps inherits the joins. Ross Brown, Director of Revenue Operations at Zafran, put the RevOps view plainly at ROA New York: every tool you add is "a different place to handle the logic." Each one is another set of rules for routing, scoring, or syncing, owned by a different team, and RevOps has less control over how data moves between them. [4% of deals close when sellers say they willIf close dates in your CRM are almost always wrong, what is your pipeline actually telling you?![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/icon/android-chrome-192x192-c0124754-bb31-4dbc-af35-99f9e88f2b79.png)Revenue Operations AllianceMarisa Garanhel![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/thumbnail/10-account-based-marketing-email-examples-to-level-up-your-campaign--1--094f6ee7-b91f-48ce-8713-97da658f6913.png)](https://www.revenueoperationsalliance.com/4-of-deals-close-when-sellers-say-they-will/) ## The line missing from the business case A typical business case for a new revenue tool has 2 numbers in it: the annual licence cost and the hours it promises to save. It almost never has a line for getting people to use it. That line covers training, rewriting processes, admin time, building and maintaining the integration, and often a middleware tool when the native connector can't do what you need. It also covers the months where reps run the old workaround and the new tool side by side. When nobody budgets for adoption, adoption doesn't happen. Jared Barol, VP GTM Strategy & Operations, told ROA Silicon Valley he'd looked at datasets across 40 companies: > "I can't name a single one that was actually using the systems they bought for the intents and purposes they bought them, across the majority of those systems." Thorsten Reichenberger, Head of Revenue Operations at Siemens Digital Industries, puts the order of work this way: process first, then tools, and "don't forget about people, because the change management exercise is an even bigger challenge." If the business case can't name who will drive adoption and how many hours it will take, it's missing its highest cost. ## 5 questions to ask before you sign RevOps rarely gets to veto a purchase. It can ask questions early enough that the answers change the decision. These 5 work whether the request came from a vendor, an exec, or a single team. 1. **What will this replace?** If the answer is "nothing", ask why. Hulse's test is blunt: "Have you already got two black dresses? Do you need another one?" If 2 tools would do 80% of the same job, the new one has to retire the old one. 2. **Where will the customer record live?** Name the system that holds the master record, and decide which one wins when the two disagree on a field. If nobody can answer, you're about to create a second version of the truth. 3. **Can we see the sync working on our own data?** Ask for a demo with your CRM fields, your lead definition, and your volumes. Find out whether the connector syncs in real time or on a schedule, and what happens when it fails. 4. **Who owns adoption, and what does success look like at 90 days?** Get a named owner, a training plan with hours attached, and a usage target you'll check before the first renewal. 5. **What does leaving look like?** Check contract length, auto-renewal dates, and how you get your data out. A 3-year term signed before anyone has measured usage is how shelfware gets locked in. If a request can't get through these 5, it isn't ready to buy yet. Most good tools pass easily. The ones that stall usually duplicate something you already own. [Why simplifying your revenue stack comes before everything elseHow Siemens Digital Industries is simplifying RevOps across 4,000 sellers.![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/icon/android-chrome-192x192-d25a35ed-8191-4413-b8d0-65cc6aa8a355.png)Revenue Operations AllianceFabrice Buron![](https://storage.ghost.io/c/62/19/6219f8f5-5d35-43bc-82c3-ce0aeb6b2cc9/content/images/thumbnail/Emily-Hartzell--2--ac340146-6ae1-4f4c-8435-415e82abd3bc.png)](https://www.revenueoperationsalliance.com/why-simplifying-your-revenue-stack-comes-before-everything-else/) ## Why AI raises the stakes Almost every revenue tool pitched this year comes with an AI feature, and plenty of new tools are nothing else. Each one wants access to your customer data, and each one adds another place where logic lives. Hulse's warning on this was short: "all AI is going to do to this problem is complicate it." An AI assistant that sees only the engagement platform knows about emails and calls. One inside the CRM knows about deal stages. Neither sees the full account. Barol's view is that AI output is only as relevant as the context behind it, and that context breaks down when the data comes from systems with no links between them. So the 5 questions matter more for AI tools. Question 2 matters most of all: if an AI tool needs its own copy of the customer record to work, you're buying a new silo with a chat box on it. ## The tools you've already bought These questions stop new sprawl. They don't fix the stack you're running today, and for most teams that's where the money is going. Untangling an existing stack takes a different process: auditing usage against spend, mapping how revenue moves from lead to renewal, deciding what the CRM should own, and rolling changes out in an order that pays for itself as you go. Our eBook with monday.com, *The hidden costs of revenue tech sprawl*, walks through that playbook step by step. It also has 5 teams that consolidated and the numbers they got back, including one that went live in 3 months on a project most companies expect to take 6 to 12 months. [Get the eBook](https://www.revenueoperationsalliance.com/the-hidden-costs-of-revenue-tech-sprawl/) Want the cost side first? Read [The revenue tech sprawl costing you 42% of the week](https://www.revenueoperationsalliance.com/the-revenue-tech-sprawl-costing-you-42-of-the-week/).