A proposal software launch review should separate claims from evidence

What to take away

What a launch review can and cannot cover

A launch review of proposal software works from what a vendor publishes: release notes, help pages, pricing, security statements and roadmap material. That set is enough to judge positioning and scope. It is not enough to judge reliability.

The method below travels across the market. Whether you are reading a launch from Proposify, PandaDoc, Qwilr or Better Proposals, the same three questions decide the score: what the vendor has published, what it will put in writing, and what only your own trial can show.

A launch review can assess public vendor documentation, pricing pages and product announcements, and nothing more. It cannot include hands-on testing, a paid pilot, reference calls or a security audit. Listing those gaps is what lets you price the risk yourself.

Buyers meet launch news through paid channels before they read any documentation. Vendors place launch messaging using LinkedIn audience targeting, which reaches defined job titles rather than a general readership. Treat the first thing you see as advertising.

Scope also decides what you compare. Ask what migration from your current tool involves: which content, templates and pricing rules transfer, who does the work, and whether the old system stays readable while you run both. A review that ignores migration from your current tool leaves you to price the switch yourself.

Timing matters too. A launch that lands three months before renewal gives you room to trial. One that lands after you sign is a change request, so check your notice period and whether the new version changes the modules you already pay for.

If you need to connect the launch to your own process, our guide to proposal operations and delivery sets out where quoting, review and signature sit.

Score the launch against your own workflow

A rubric beats a feature checklist when you are judging proposal software, because it forces a weighting. Choose the criteria your team actually feels each week. Then score the vendor from 1 to 5 on each one, using only evidence you can point to.

Criterion	What you check	Weight

Score each of these criteria from 1 to 5 against the evidence you can point to, and add your own where your team feels the pain each week:

Weight the criteria to your deal size

A team sending forty quotes a month should weight approval speed above template variety. A team selling to procurement should weight audit trail and version history higher. Write the weights down before you look at the vendor's demo.

Turn the scores into a decision

Total the weighted scores and set a threshold in advance, expressed as a share of the maximum total your weights allow. A product that fails on exit terms should not pass because it scores well elsewhere. Where a claim carries no evidence, score it at the midpoint rather than the top, and note it for a trial. A single reviewer's total is a starting point, not a verdict.

Work through one claim

Take a typical launch line: 'our customers send proposals far faster'. It is a claim about speed, not a measurement. The evidence is the method behind it, the team size measured, the period covered and the baseline used, and whether the figure covers drafting, approval or signature. Until you have that, score the claim at the midpoint and note what a trial would have to show before the score moves up.

Where independent evidence still matters

Vendor claims about artificial intelligence deserve separate scrutiny. Providers that sell into the European Union face the EU AI Act, which places transparency duties on certain AI features and shapes how a product may be described. Article 50 of the Act sets the transparency obligations that apply to AI systems people interact with or that generate content, and Annex III lists the high-risk uses that carry heavier duties, with the Act's own penalty provisions behind them. Ask which obligations apply to the version you would buy, and what the vendor will state in writing.

Advertising copy in the UK must be evidenced. The CAP Code — the UK Code of Non-broadcast Advertising and Direct & Promotional Marketing, written by the Committee of Advertising Practice and enforced by the Advertising Standards Authority — requires a marketer to hold documentary evidence for a claim before it is published. If a launch page promises a percentage saving, ask for the basis.

Editorial judgement sits between those two poles. A clear roadmap and a thin help centre is a signal. Run your own proposal software checklist before you sign — security statement, references, exit terms, support hours — and treat any unanswered item as open.

Independent evidence rarely comes from one source. Price a claim against your own support tickets and cycle times once you run a trial. Keep the vendor's published numbers separate from your measured ones.

Common questions

Short answers to the questions buyers ask most often about a launch review.

Should a launch review include pricing?

Yes, where the vendor publishes it. Public pricing shows packaging and seat logic, which matters more than feature lists for most teams. Where pricing is hidden, ask for a written quote before you shortlist — in pounds, stating whether VAT is included and how seats are counted.

How much weight should a launch announcement carry?

Little on its own. Use it to decide whether a demo is worth your time. Weight instead the evidence behind each claim and the fit with your quoting workflow.

What if the review covers a feature you need?

Ask the vendor for a sandbox or a pilot with your own templates. A short trial with real pricing rules will tell you more than any published material.