How to handle the 'send me pricing' email

'Send me pricing' is the most-received-and-most-fumbled email in UK SaaS sales. The instinct is to send a price list. The right answer is more nuanced and the difference is meaningful for win rates.

Why 'send pricing' deserves a structured response

Three signals are buried in 'send pricing':

• The buyer is far enough along to have a budget question (positive)
• The buyer doesn't yet have a value frame (the email is a request for cost, not for value)
• The buyer wants pricing to share with others (the email is rarely solo decision-making)

A response that just sends a list price answers the cost question and ignores the other two signals. A response that refuses to send pricing entirely insults the buyer's time. The middle is the right answer.

The structure that works

A response that addresses all three signals, in roughly 5-8 sentences:

1. Acknowledge the request directly. ('Happy to share pricing.')
2. State that pricing is straightforward and the band is X-Y for companies in their size and use-case range. (The soft anchor.)
3. Note that the specific number depends on two or three variables you'd want to clarify. ('Final pricing depends on user count, contract length, and whether premium support is needed - all things we can dial in once we know your specific situation.')
4. Offer two paths: a written proposal with a specific number (which requires a brief context conversation) OR a published list-price page (if you have one and you're comfortable directing the buyer there).
5. Suggest a specific next step. ('I'd want 20 minutes to confirm we can deliver the value at that price; can you do Tuesday or Thursday?')

This response gives the buyer enough to decide whether to continue. It surfaces the variables that would change the price. It moves to a structured next step without dragging the buyer into an unnecessary discovery call.

What not to send

Three patterns that fail predictably:

The list-price PDF. Confirms 'send me pricing' as a transactional request. The buyer takes the PDF, compares it to two competitor PDFs, and shortlists on price alone. You lose context.

The 'pricing depends' deflection without a band. 'Pricing depends on usage, support level, and contract terms' with no number is functionally a refusal. The buyer interprets it as 'they're hiding the price because it's high' and disqualifies you.

The 'let's set up a call before I share pricing' demand. Sometimes appropriate (for complex enterprise deals) but routinely overused for mid-market. The buyer who doesn't want a 30-minute call before getting a number drops you for a vendor who'll send the number.

When the band is genuinely impossible to give

Some product categories have such variable pricing that no useful band exists ('fully bespoke enterprise contract; price depends on custom development'). In these cases, the right answer is to acknowledge the limitation explicitly: 'We don't have list pricing because every deployment is bespoke. Customers in your size range have invested £X-Y total over a 24-month contract, but the specific number depends on scope. The next step would be a 30-minute scoping call.'

This is the rare case where the call-first response is honest. Don't use it when a band would be possible.

The metrics question

Sales operations teams that track 'send-pricing email response patterns' in their conversation-intelligence tooling find that AEs who use the structured response (band + variables + path) have 1.5-2x the close rate from price-request emails as AEs who send list-price PDFs. The data isn't published widely, but the pattern is consistent across multiple UK SaaS teams that have measured it.