When to keep, replace, or rip out a sales tool

The keep / replace / cut decision for any sales tool sits inside a 2x2 of usage and outcome lift, modulated by workflow integration and switching cost. This piece walks through the four quadrants.

High usage + high outcome lift = Keep

The clear keep. Don't second-guess this; renew on time, lock in price for two years if you can negotiate it. Don't add features the vendor pitches for upsell unless they survive the same audit on their own.

The trap in this quadrant is over-investment in adjacent capability from the same vendor. The tool earned its keep doing X; the vendor pitches Y as a natural extension; Y joins the stack at renewal; six months later Y is a low-usage line item the team forgot about.

High usage + low outcome lift = Investigate, don't cut

This is the trickiest quadrant. The tool is being used but you can't isolate the outcome it drove. Two scenarios:

Scenario 1: the tool is genuinely creating value but the value is diffuse. Examples: a CRM is hard to attribute outcome to specifically because it's structurally everywhere. A communication tool has team-effectiveness benefits that don't map to a sales metric.

Scenario 2: the tool is being used because it's there, not because it produces outcomes. AEs run a sequence in Outreach because the manager asks them to, not because it converts.

The defence: a controlled test. Pull a sub-team off the tool for 60 days. Measure their outcomes vs the rest. If outcomes degrade, you've confirmed scenario 1; if outcomes are flat, you have scenario 2. Few teams do this; the teams that do tend to cut the tool.

Low usage + high outcome lift = Improve, don't cut

The most common quadrant in mature UK SaaS sales stacks. A great tool, used by 30 percent of seats, producing measurable outcomes for that 30 percent. Cutting kills the outcomes; doing nothing wastes the licence cost.

Three improvement plays:

1. Reduce seats to fit actual users. Sometimes the answer is 'this tool is great for SEs and useless for AEs'. Cut the AE seats; expand SE seats.
2. Workflow-integrate harder. Pull the tool's output into Slack or CRM so users don't have to navigate to a separate dashboard.
3. Train. Sometimes the under-usage is a training gap. A 60-minute team session with the vendor's solutions engineer is cheap and often resolves the gap.

If none of three works, downgrade to cut.

Low usage + low outcome lift = Cut

The clear cut. Don't have the conversation with the vendor first; have it internally. Document the audit. Issue notice. Plan the migration.

The vendor will offer discounts, additional services, account management upgrades. None of these address the structural problem. If a 50 percent discount would make the tool keep-worthy, the tool was overpriced from the start.

The switching-cost overlay

Apply the keep / replace / cut decision against switching cost as a secondary axis:

• High switching cost + cut: budget the migration explicitly. A tool that was tightly integrated takes 3-6 months to remove cleanly.
• Low switching cost + cut: do it this quarter.
• High switching cost + replace: fold the migration into a structured procurement; replacement tool inherits the integration debt.
• Low switching cost + replace: try the replacement against a sub-team for 60 days before full migration.

The switching-cost variable is the one most often under-estimated in stack audits. Factor it in early.