
Operations
Part of Running prospecting software operations: workflow, data quality and compliance
How to assess prospecting software launch claims
A practical framework for separating verifiable facts, vendor claims and editorial judgement when assessing prospecting software launch announcements.
What to take away
For example, a sales operations lead in Leeds reads a prospecting software launch announcement on Tuesday, books a demo for Friday, and by Monday three colleagues are building pipeline in a tool nobody has finished assessing.
- An assessment should say what it checked, such as published pricing, help-centre articles, release notes and security pages.
- Vendor figures on match rates or reply rates remain marketing claims until supported by a named source and date.
- For personal data used in direct marketing, check the UK GDPR lawful basis and objection handling, and assess electronic marketing against PECR and the ICO's direct marketing guidance.
- Editorial judgement, such as whether an interface suits a six-person team, is an opinion and should be labelled as one.
If you want the wider operating model before you sit through another demo, the prospecting software operations and delivery guide sets out ownership and handover in more detail.
What an assessment can cover
A desk-based assessment can examine a vendor's public pricing page, product documentation, sub-processor and security pages, any published release notes, and the launch announcement itself. It can report what those materials say, but it is not a review of a named product unless the reviewer identifies the vendor and the materials assessed.
Two things follow from that scope. First, the assessment is repeatable: a second reader can check the same pages on the same date. Second, it is limited to what the vendor chose to publish, which is never the whole picture.
Limits of a desk-based assessment
A desk-based assessment cannot establish how a product performs in use. Unless the reviewer opens a trial account, runs a sequence or measures inbox placement, the piece should not claim to have tested those things. It should also state whether it draws on customer interviews, paid pilots or reference calls.
Where a review describes how a feature behaves, it should say whether that account comes from the vendor's own documentation. That distinction matters when the same feature appears in a competitor's comparison table.
Separating vendor claims from independent evidence
Launch material mixes three things: verifiable facts, vendor claims and the reviewer's own judgement. A price shown on a vendor's published pricing page is verifiable as at the date checked. A claim that the tool doubles reply rates remains a vendor claim unless the vendor names the study and its date.
Verifiable vs Vendor Claim
Verifiable fact
- Pricing tier
- £325 a month
- Reply rate
- Needs named study
- Interface clarity
- Not applicable
- Lawful basis
- ICO guidance
Vendor claim
- Pricing tier
- Not applicable
- Reply rate
- Doubles reply rates
- Interface clarity
- Not applicable
- Lawful basis
- Vendor explanation
Editorial judgement
- Pricing tier
- Not applicable
- Reply rate
- Not applicable
- Interface clarity
- Reviewer's own view
- Lawful basis
- Risk assessment
For personal data, ask which UK GDPR lawful basis the vendor relies on; legitimate interests may be available for direct marketing, depending on the circumstances. For electronic marketing, check which rules in the Privacy and Electronic Communications Regulations 2003 (PECR) apply to the channel and recipient, alongside the ICO's direct marketing guidance. Ask how objections and opt-outs are handled: screening or enrichment alone does not establish compliance.
The UK digital strategy sets out national priorities for software adoption and digital skills. Treat it as policy context, not independent evidence of a particular product's capabilities or claims.
If launch material uses public-sector demand, government spending or tax-related figures, identify the underlying dataset, publisher and publication date. Without those details, do not treat the figures as independent evidence of market size or buyer demand.
Claims that need a named source
Any percentage attached to pipeline, reply rates, match accuracy or time saved needs a named study, a sample and a date. Without those, treat the figure as an illustration of what the vendor hopes happens.
Claims that are editorial judgement
Interface clarity, onboarding effort and documentation quality are opinions. They are still useful, provided the review says who formed them and on what basis.
Worked example: separating subscription and admin costs
Illustrative figures only. A six-person sales team in Birmingham adopts two tools at £325 a month each, so £650 a month, or £7,800 a year. List cleaning and admin take eight hours a month at an internal cost of £35 an hour, adding £280 a month, or £3,360 a year. The first-year commitment is £11,160.
If usage data at month three shows one tool carrying every sequence, the team can ask whether the second subscription is justified. An assessment that surfaces that question early may help avoid an unexamined renewal.
Common questions
Is a launch review the same as a product review?
No. A product review judges how software performs in use. A launch review judges what a vendor published at launch and how well the claims hold up. The second is quicker and narrower, and it should say so.
Who should own the assessment?
Someone who will not use the tool daily can own the assessment. Sales operations is often a practical choice because the team carries the admin cost when a licence goes unused. The prospecting software service standards in England page offers an operational reference point, not a regulatory standard.
What should trigger a re-review?
A pricing change, a new data source, an ownership change at the vendor, or a shift in the rules covering outreach. Otherwise, review on the same cycle as your budget.



