Answer a Request for Pricing With Useful Context

A buyer may ask for pricing before a full discovery call because they need a budget screen. Avoid making them earn a number through an elaborate process.

Read the signal

At the same time, a bare price can mislead if the quote depends on users, usage, support, or implementation. The answer should separate known pricing from assumptions and help the buyer estimate the relevant configuration.

Make the next move

Share the published price or an honest range when you can. State the variables that could change it and ask for the smallest set of inputs needed for a useful estimate. If a custom quote is required, explain the process and timing plainly.

Language you can adapt

Illustrative wording:

Our price depends on the number of users and the support level. For the team size you mentioned, I can send an estimate with those assumptions shown. Are you budgeting for the whole team or an initial group?

The wording is a starting point. Replace the problem, evidence, and request with details the buyer actually gave you. If those details are missing, ask a question before sending a polished message. Specificity makes it easier for the buyer to correct your understanding and easier for you to see whether the opportunity is moving.

Decide what happens next

If the buyer only needs an initial budget check, do not force a full proposal. If the estimate rules you out, learn which constraint mattered. If it fits, agree on the next evaluation question.

Write the result in your deal notes as an observable fact: who responded, what they agreed to do, and when. A friendly reply is useful, but a decision, a named owner, or a scheduled review tells you more. If the next step remains vague, treat that as information about the deal rather than a reason to send the same follow-up again.

Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.