Reviews
Part of Customer success software reviews or vendor demos, which one earns your trust?
Why a customer success software review methodology earns trust
How our customer success software review methodology separates vendor claims from independent evidence, with a scoring checklist for UK buyers.
What to take away
- As of 2022, the UK had 5.5 million private sector businesses, according to Business population estimates 2022, so review coverage has to be proportionate.
- We assess published documentation, pricing pages, regulatory filings and platform documentation. We do not claim hands-on testing.
- Vendor claims are labelled as claims. Independent evidence is cited with its source and date.
- Editorial judgement is stated as judgement, and scoring criteria are fixed before assessment begins.
- Buyers should verify anything material themselves before signing.
What our customer success software review methodology assesses
Our method looks at what a vendor publishes and what independent bodies confirm. That means help centre articles, release notes, security pages, pricing terms and contract language where available.
Evidence sources we assess
- Help centre articles
- Release notes
- Security pages
- Pricing terms
- Contract language
- ASA rulings database
- BSI digital risk standards
It also means checking marketing statements against rulings and codes. The ASA rulings database is a useful reference when a vendor makes strong retention or performance claims in advertising.
Security and data handling sit in scope because retention platforms hold customer records. We look for evidence that a vendor follows recognised practice, such as the digital risk and information security management standards set out by BSI.
A sub-processor list or data residency statement counts as a claim to verify, not as a confirmed control.
We record the date of each document we rely on. A pricing page captured in March may not describe terms renewed in September, so each review notes when its evidence was last checked.
What the methodology does not assess
We do not run the software, sit in a live customer environment, test integrations against production data or measure retention outcomes for real users.
We do not interview named customers, and we do not present vendor-supplied case studies as independent proof. A quoted percentage from a vendor deck is a vendor claim.
A demo is not evidence.
If a claim cannot be traced to a document, a regulator or a dated public statement, it stays out of the score.
Knowing what a review leaves out matters, which is why our guide to customer success software reviews and comparison methods explains how to read a score in context.
Scoring criteria and weightings
Each product is scored against fixed criteria so that comparisons stay consistent between reviews. The weighting below is illustrative of our approach, not a vendor benchmark.
Scoring criteria and weightings
- Documented capability25%
- Commercial transparency20%
- Security and data handling20%
- Contract terms20%
- Claim substantiation15%
| Criterion | What we look for | Weight |
|---|---|---|
| Documented capability | Feature descriptions with version or date | 25% |
| Commercial transparency | Published pricing or clear quote process | 20% |
| Security and data handling | Named standards, sub-processor lists | 20% |
| Contract terms | Renewal, exit and data portability clauses | 20% |
| Claim substantiation | Marketing claims traceable to evidence | 15% |
Scores are relative to the criteria, not to a market average. A low score means thin published evidence, not necessarily a poor product.
Each criterion is graded from 1 to 5 against the evidence available. A grade of 1 means no published evidence, while 5 means a dated primary document. Grades are combined using the weightings above, and the evidence behind each grade is listed in the review.
Checklist before you rely on any review
- Identify who wrote the review and whether they tested the product.
- Check whether vendor claims and independent evidence are separated.
- Confirm the date of every statistic and ruling cited.
- Look for the scoring criteria and weightings used.
- Check whether the vendor's own documentation is linked.
- Ask what the review explicitly did not assess.
- Verify security and contract claims against primary documents.
How to weigh editorial judgement
Editorial judgement is unavoidable in any review. The question is whether it is disclosed.
We state when a conclusion rests on our reading of public documents rather than on a measured test. We also state when a vendor has published nothing on a criterion, because silence is itself a finding.
Judgement should be revisable. If a vendor publishes new documentation, the assessment can change, and the review should carry a date so readers know which version they are reading.
Where two vendors score equally, we prefer the one with the clearer exit terms, because switching costs are real. That preference is judgement, and the review says so.
If you want to see how these criteria apply across products, our comparison of customer success software best providers shows the method in practice.
Common questions
Does this methodology include hands-on testing?
No. We assess published documentation, pricing, contract terms and independent evidence. Any hands-on testing would be stated explicitly in the relevant review.
How are vendor claims treated?
They are recorded as claims and labelled as such. Where possible, we check them against regulator rulings or published standards before they influence a score.
Can a vendor request a correction?
Yes, where a factual error is shown with a primary source. Scores based on editorial judgement are not changed on request alone.
How often are reviews updated?
Reviews carry a date and are revisited when a vendor changes pricing, contract terms or security documentation.
