Proposal software pricing models: illustrative scenarios

What to take away

If your UK sales team still quotes from a shared inbox, proposal software pricing may first appear as per seat, with headcount determining the licence total.
A 12-person team on an illustrative £45 per user per month pays £540 a month, or £6,480 a year, whether it sends 40 documents or 400.
Volume and credit models follow output, which suits seasonal quoting but makes quarterly forecasting harder.
Platform fees with usage add-ons move implementation, e-signature and API costs onto separate lines.
The biggest effective discount usually comes from contract length and payment terms, not from a wider feature tier.

How does per-seat pricing work in practice?

Per-seat pricing bills named users. The invoice grows with the number of people who can draft, price or approve a quote. A 12-person sales team on an illustrative £45 per user per month pays £540 a month before VAT at the 20% standard rate. Annual prepay at an illustrative 15% discount brings that to £5,508 a year.

Per-seat pricing at a glance

£45per user per month
£540monthly for 12 users
15%annual prepay discount
£5,508annual prepay cost

This makes forecasting easier, but the friction sits elsewhere. Sales engineers, bid managers and finance approvers who only need to approve a document still take a licence, unless the vendor offers a view-only tier.

Why do volume and credit models change the maths?

Volume pricing charges per document, per envelope or per credit pack. A firm quoting through peaks and troughs pays for what it sends. Seasonal sectors often prefer this shape.

Volume vs seat model trade-off

Volume/credit model

Cost driver: Documents sent
Quiet months: Cheaper
Peak months: Can exceed seat cost
Best for: Seasonal senders
Key risk: Variance

Per-seat model

Cost driver: Named users
Quiet months: Same cost
Peak months: Predictable
Best for: Steady teams
Key risk: Idle licences

The risk is variance. Quiet months feel cheap, and one large tender month can cost more than a seat licence would have. Pull twelve months of send history from your CRM before you sign anything.

Where do implementation and add-on costs sit?

Onboarding is the line most often missed. Guided setup, template migration and CRM integration may be quoted as a one-off fee, sometimes waived on an annual contract. An illustrative £1,500 onboarding charge adds about £125 a month to a £6,480 first-year licence.

Add-ons stack up too: e-signature envelopes beyond the allowance, API calls, single sign-on and premium support. Ask for a written list of what sits outside the licence before you compare two quotes. For a broader budget view, see the proposal software costs and budget guide.

How do per-seat and platform-plus-usage models compare?

The figures below are illustrative planning scenarios, not published prices or quotes from a supplier. Assume a 12-person team sends 200 documents a month.

The illustrative per-seat model charges £45 per user per month with 15% off for annual prepay: £6,480 a year, discounted to £5,508.

The illustrative platform-plus-usage model charges a £250 monthly platform fee plus £1.20 per document. At 200 documents a month that is £490 a month, or £5,880 a year. At 320 documents it becomes £634 a month, or £7,608 a year.

At these illustrative rates, the platform-plus-usage model overtakes the per-seat model's undiscounted £540 a month once the team sends about 242 documents a month. Model your own peak month rather than your average.

Does inflation change which model you should pick?

Inflation can inform a budget assumption, but it does not show what a supplier will charge or whether an uplift is capped. The Bank of England's page on inflation and the 2% target provides monetary-policy context. The ONS inflation and price indices release provides price-index data; check the supplier's contract for its actual price-review terms.

As a planning scenario, a capped 5% annual increase on the illustrative £6,480 licence above adds £324 in the second year. Check whether a written cap covers add-ons as well as the base licence.

What should a like-for-like pricing comparison include?

Keep demand-generation spend separate from the proposal software licence. Compare the same user count, document volume, contract term and included services; otherwise, a lower headline fee may cover less.

Run each model against quiet, typical and peak months from your own send history. Keep the assumptions beside each calculated total so a planning scenario is not mistaken for a supplier quote.

Common questions

Here are the pricing questions UK teams ask most often when comparing per-seat and usage models.

Is per-seat pricing cheaper for a small team?

Not necessarily: compare the licence cost for each seat with usage fees at your expected volume. Usage pricing can suit a few people sending high volumes. Test both against your busiest month.

Can we negotiate at renewal?

Discount normally comes from a longer term, annual payment or fewer seats. Ask for the add-on rates to be held flat, not just the base licence.

Do UK vendors publish list prices?

Some do, many quote on request. Where no price is published, ask for a written quote separating the document allowance, overage rate and onboarding fee.

How long should we commit for?

Two or three years usually buys the best rate, but only when headcount is stable. A one-year term with a capped increase is safer while hiring.