The Quote Behind the Quote: Turning a SaaS 'Contact Us' Into a Number You Can Compare

A pricing page is a shop window. The quote is the contract draft. Between the two sits a gap that UK teams often discover only after the first invoice, the first true-up or the first annual renewal. The fix is not to become cynical about software sales. It is to ask for a written cost breakdown that turns a vague 'contact us' figure into something you can compare, challenge and approve with a straight face.

Start with the number you can actually compare

Per-seat-per-month pricing is easy to read and easy to misapply. A quote that says £12 per user per month sounds tidy until you notice the minimum seat count, the annual billing requirement and the implementation fee sitting on page two. Ask for an annual total instead. Then ask for the same annual total under two or three realistic usage bands: a lean team, a likely team and a growth team. If the vendor cannot produce those figures in writing, you do not yet have a quote. You have a mood.

A useful quote should state the commercial model in plain terms: what is charged, when it is charged, what triggers a change and what happens if your usage moves. That last point matters more than the headline rate. Most budget surprises do not come from the per-seat price. They come from the assumptions underneath it.

The line items that hide in plain sight

Implementation and onboarding are the classic omissions. Some vendors include a basic setup call; others charge for configuration, data migration, sandbox environments, training, integrations or project management. None of those are inherently unreasonable, but they need to be on the page before approval. Ask specifically whether the quoted implementation is fixed-fee, time-and-materials or capped. If it is time-and-materials, ask for the estimated hours and the hourly rate in writing.

Support is another assumption trap. 'Standard support' can mean UK office hours, extended hours, a portal with a response target, or a phone line staffed by whoever is available. Ask what hours are covered, whether bank holidays count, what the response and resolution targets actually are, and what out-of-hours support costs. Premium support may be optional, but if the team will need it during month-end or a busy season, it belongs in the comparison.

Then there are the smaller charges that add up: API call overages, extra storage, additional environments, premium connectors, audit-log retention, training refreshes, and charges for paying by invoice rather than direct debit. None of these need to kill the deal. They just need to be visible.

Minimums, overages and the quiet maths

Minimum seat counts are common and not automatically unfair. They become a problem when the quote presents a per-seat rate without making the floor obvious. If the minimum is 25 seats and you need 18, the real per-user cost is higher than the page suggests. Ask for the quote to show both the minimum commitment and the cost at your expected seat count.

Overages deserve the same treatment. Find out what counts as usage, when the overage is measured, whether it is charged monthly or annually, and whether there is a grace band. A vendor that charges retrospectively at the end of a busy quarter is giving you a different cashflow risk from one that blocks usage at a threshold. Neither is wrong, but they are not the same product.

Annual uplifts are where three-year comparisons go to die. A fixed 5% uplift is easy to model. A CPI-linked uplift is less predictable, especially if the quote does not say which index, which month and whether there is a cap. Ask for the uplift clause in writing and model it over the contract term. If the vendor will not commit to a cap, treat the uncapped years as a risk rather than a rounding error.

VAT, payment terms and the cashflow question

Most UK software quotes are exclusive of VAT. That is normal, but it should be stated clearly, along with whether VAT is recoverable for your organisation. A quote that mixes VAT-inclusive and VAT-exclusive figures across pages is not a comparison; it is a puzzle. Ask for one table with the VAT treatment made explicit.

Payment terms matter too. Annual upfront, quarterly in advance and monthly billing all produce different cashflow profiles. If annual upfront unlocks a discount, ask for the discount as a separate line so you can see what you are buying. If the quote assumes a purchase order, a finance approval or a direct debit mandate, put that in the assumptions list.

Turn the quote into a table, not a PDF

A good next step is to ask the vendor to complete a simple cost schedule. Columns might be: item, trigger, assumed quantity, unit price, annual total and notes. Rows should include subscription, minimum commitment, implementation, data migration, training, support tier, overage rate, annual uplift, VAT and payment terms. It is a boring document. Boring documents are how you avoid exciting invoices.

Once the table is complete, compare vendors like for like: same seat bands, same contract length, same support assumption, same implementation scope. If one vendor includes migration and another does not, the lower number is not necessarily lower. It is just earlier in the story.

Document the assumptions before anyone approves

Before approval, write a one-page assumptions register. It should say what usage you have assumed, which seats are in scope, what implementation includes, what support hours you expect, how the uplift is calculated and who owns the renewal review. Give it a review date. When the first invoice arrives, you can check it against the assumptions rather than reconstructing the deal from memory.

This is not about squeezing every supplier or pretending that software pricing can be perfectly predictable. It is about making the commercial model legible before it becomes a commitment. A quote you can read is a quote you can compare. A quote you can compare is one you can approve without hoping the maths works out later.