Insight / SaaS / 22 July 2026

UK SaaS sales is over-tooled, and what should come out of the stack

The 2018-2024 UK SaaS sales tech stack accreted tooling at a rate that exceeded the value the tooling produced. Stacks of 12-20 tools at 100-300 person scale are common; per-tool usage rates of 20-40 percent are common; the per-tool cost compounds. This Insight argues for a structural rebalancing: most UK SaaS sales operations should be running 5-7 tools, not 12-20, and the tools that come out are predictable.

Three categories should come out of most UK SaaS sales tech stacks in 2026: redundant prospecting data tools (one is enough); standalone sequence-management tools where the CRM has caught up; and forecast-tooling overlap where one tool serves the function. The 5-7 tool stack is achievable and produces no measurable degradation in sales outcomes.

The 2018-2024 UK SaaS sales tech stack accreted tooling at a rate that exceeded the value the tooling produced. Stacks of 12-20 tools at 100-300 person scale are common; per-tool usage rates of 20-40 percent are common; the per-tool cost compounds. By 2026 the structural cost is meaningful: 5-20 percent of total sales operating cost is going to a stack where most components are under-used.

This Insight argues for a structural rebalancing. Most UK SaaS sales operations should be running 5-7 tools, not 12-20, and the tools that come out are predictable.

How the over-tooling happened

Three forces compounded.

Vendor-led category creation. Through 2018-2022, sales-tech vendors created adjacent categories at a rate that produced new tooling roughly every 12 months: conversation intelligence, sales engagement, ABM platforms, intent data, AI prospecting assistants, deal-room collaboration, mutual action plans. Each category had genuine merit; few teams resisted adding tools as the categories appeared.

RevOps capacity to evaluate. Most UK SaaS RevOps teams in 2020-2023 were small relative to the procurement decisions they were making. New tools were added on quick evaluation; few were ever audited post-purchase. The accretion compounded.

Comp-plan-misaligned procurement decisions. Some sales-leadership decisions to add tools were driven by signalling rather than need ('our competitors run this, we should too'). Tools added for signalling rarely produced measurable lift; few were removed.

The combined effect: stacks where 60-70 percent of seats are licensed but only 30-40 percent are actively used.

What should come out

Three categories, in order of how cleanly they cut.

Redundant prospecting data tools. Most UK SaaS sales teams are running two or three prospecting data sources concurrently (Cognism + ZoomInfo, or Apollo + Cognism, or all three). The marginal data uplift from the second/third tool is typically small; the cost is not. One prospecting data tool is enough for most use cases. Cutting the second saves 30-100k pounds annually at mid-market scale; cutting the third saves another 30-80k.

Standalone sequence-management tools where the CRM has caught up. Salesforce and HubSpot both shipped meaningful sequence-management capability in 2024-2025. Teams running Outreach or Salesloft alongside Salesforce or HubSpot for sequencing should evaluate whether the standalone tool still earns its keep against the now-mature CRM-native capability. For many mid-market teams the answer is no.

Forecast-tooling overlap. Some teams run Clari + Salesforce-native forecasting + a BI dashboard for forecast analytics. The three overlap substantially; one should be the source of truth, not three. Picking the source-of-truth tool and cutting the others reduces forecast-call confusion and saves licence cost.

What should stay

The 5-7 tool stack that produces no measurable degradation in sales outcomes:

  1. CRM (Salesforce or HubSpot)
  2. One prospecting data source (the strongest fit for the team's ICP)
  3. Conversation intelligence (Gong, Chorus, or Clari Copilot)
  4. Forecasting (Clari or BoostUp, or CRM-native at smaller scale)
  5. Compensation operationalisation (Spiff, CaptivateIQ, or Everstage)
  6. Document collaboration / proposal (Pandadoc or Docusign for signature; Loom or Vidyard for async demo)
  7. One platform for everything else (Salesforce or HubSpot covers most of the long tail; resist adding seventh-eighth-ninth tools to fill specific feature gaps)

What the resistance to cutting looks like

Three patterns visible across UK SaaS RevOps teams trying to rationalise stacks:

The 'this team uses it' defence. A sub-team somewhere in the org is using a tool the rest of the org isn't. The defence is real: cutting the tool harms that sub-team. The structural answer: cut the licence count to fit the actual users; don't keep org-wide licensing for 30 percent active usage.

The 'we already paid' sunk-cost framing. Multi-year contracts with usage commitments. The framing is psychologically real but economically wrong: the sunk cost is sunk. The decision is whether the next contract cycle pays back; existing licence is irrelevant.

The 'vendor will offer a discount' anchor. Vendors offer 30-50 percent discounts to retain accounts that are about to churn. The discount makes the math look better; it doesn't change the underlying value-vs-cost calculation. If the tool wasn't producing lift at full price, it isn't producing lift at half price.

The macro context

UK SaaS sales operations are operating under cost-discipline pressure that didn't exist in 2018-2022. CFOs are scrutinising sales-tech spend; per-seat cost is being compared across categories; tools that don't pay back are visible to finance. The window for unaudited tool accretion has closed.

The teams that have rationalised stacks in 2024-2026 (and there are several visible cases in Pavilion / RevPilots community discussion) report no measurable degradation in sales outcomes. The teams holding 12-20 tool stacks are spending 30-50 percent more on sales tech than the rationalised teams without measurable outcome lift to show for it.

What to operationalise

Three structural steps:

  1. Audit every tool against the four-metric framework (active usage, workflow integration, outcome lift, switching cost). Document. Make decisions portfolio-level, not tool-level.
  2. Move to one source-of-truth per category. One prospecting data source. One conversation intelligence. One forecasting tool. Consolidate; don't accept overlap.
  3. Decline new-tool conversations until current stack is rationalised. New tools are accretive by default; resisting accretion is the harder discipline.

This is editorial coverage of a contested topic, taking a position. Practitioners running larger stacks may disagree; the disagreement is welcome. The rationalisation thesis is salespeople.co.uk's view.

Source: Editorial synthesis from UK SaaS RevOps practice and Pavilion / RevPilots community discussion 2024-2026.