Tools and providers
Part of How to buy customer success software with confidence
How to run customer success software selection without regret
A practical guide to customer success software selection for UK teams, covering written requirements, weighted scoring, data protection checks and exit terms.
What to take away
Customer success software selection is the process of matching a retention platform to written business requirements rather than to a supplier feature list.
- Write requirements before you see any demo, so the demo answers your questions instead of setting them.
- Score every supplier on the same weighted criteria, including data protection and exit terms.
- Test each shortlisted tool on one shared scenario rather than comparing interface tours.
- Treat the contract, not the product tour, as the real test of fit.
- Give each requirement a named owner so scoring rests on evidence.
Prepare the requirements before you shortlist
Turn retention goals into written requirements
Start with the outcome you already report on. If net revenue retention is the board measure, the software must show renewal and expansion history at account level. Write each requirement as a testable statement, ranked essential or desirable.
Turn retention goals into written requirements
- Start with the outcome you report
- Write each requirement as testable
- Rank essential or desirable
- Cap essentials at around twelve
- Give each requirement a named owner
- Avoid shared ownership
Use blunt wording: the system must export account-level renewal history for the last eight quarters without a support ticket.
CAP essentials at around twelve. More than that and every supplier passes. For example, a team paying £400 a month for a legacy tool may find half its essentials already met by the incumbent.
Separate must-haves from nice-to-haves with owners
Give each requirement a named owner and a written pass mark. Finance owns billing and invoice accuracy. Data protection owns retention periods and subject access handling. This stops the loudest voice in the room deciding the outcome.
Avoid shared ownership. Two names against one requirement is how gaps survive sign-off and reappear during implementation.
Where the decision touches revenue reporting, it helps to know how platforms treat retention revenue alongside new business, as set out in this explanation of revenue lifecycle management.
Score suppliers on evidence, not demonstrations
Build a weighted scorecard and test it
Weight each requirement by business impact, then score suppliers from 0 to 5 with a comment for every score. A score without a comment is an opinion. Let weightings total 100 and have the sponsor sign them off before any supplier is scored, so the maths cannot be tuned afterwards.
Score suppliers on evidence
- Weight each requirement by impact
- Score suppliers 0 to 5 with comments
- Let weightings total 100
- Get sponsor sign-off before scoring
- Insist on sandbox or trial data
- Run one scenario across shortlist
- Compare outputs, not interfaces
Insist on a sandbox or trial data set. A supplier that will not provide one has told you something. Run one scenario across every shortlisted tool: onboard a new account, trigger a health alert, produce a renewal forecast. Compare outputs, not interfaces, and note how long each task took.
Check data protection and security duties
If the platform sends marketing email, the rules on consent and soft opt-in apply. The ICO guide to PECR explains what counts as valid consent for electronic marketing, which matters when retention messages go to individuals.
Ask for the sub-processor list, the retention schedule and the breach notification window. Record where customer data is hosted and who can access it. The GOV.UK business innovation, protection and cyber security guidance sets out the security expectations UK buyers should apply when assessing suppliers.
Before you request pricing, work through a structured vendor due diligence checklist so security, references and contract terms are tested in the same round.
Compare the before and after
What changes when selection is run properly
The table shows the shifts once requirements lead the process.
What changes when selection is run properly
Before
- Requirements
- Gathered during demos
- Shortlist
- Six to ten suppliers
- Scoring
- Impression and price
- Security review
- After contract talks start
- Decision owner
- Whole committee
- Exit plan
- Not discussed
After
- Requirements
- Written and ranked first
- Shortlist
- Three, all passing essentials
- Scoring
- Weighted scorecard with comments
- Security review
- Before pricing is requested
- Decision owner
- One accountable sponsor
- Exit plan
- Export and notice terms agreed
Agree the exit before you sign
Ask what happens on termination. You need a full export in a usable format, a defined notice period and a clear deletion date. Put these in the contract, not a support article. Check whether the export covers historical health scores and account notes, because those are the parts teams rebuild by hand.
Set a review point at twelve months. If the platform has not moved the retention metric you bought it for, the review gives you a reason to renegotiate or leave.
Ask about uplift caps at renewal: a multi-year discount often hides a step-up in year two. The wider market context sits in our guide to customer success software tools and suppliers.
Common questions
How long should customer success software selection take?
For a mid-market UK team, eight to twelve weeks is a reasonable assumption. Most of that time goes on requirements, security checks and reference calls rather than demos.
How many suppliers should be shortlisted?
Three is usually enough. Each extra supplier adds scoring work and a security review, and rarely changes the outcome. Keep a reserve name in case one drops out.
Should price decide the shortlist?
Price should be scored, not used as a filter. A cheaper tool that fails an essential requirement costs more across the contract term.
Who should sign off the final choice?
One named sponsor should own the decision, with finance and data protection leads holding a veto on their own criteria. Committees that decide by consensus default to the safest brand, not the best fit.
