Respond When a Prospect Wants Pricing Before a Call
Give a useful answer without pretending all technology pricing is identical.
The buyer moment
An inbound buyer asks for pricing and refuses a discovery meeting.
Some buyers need a quick range to decide whether a call is worth their time. Ask for the smallest inputs that make the range honest: intended team, likely workflow, and whether they are planning a pilot or a broader rollout. If the buyer cannot share those details, give a clearly labeled starting range and link it to the product scope it assumes. A useful price response lowers friction while making clear that exact terms depend on a decision the customer has not made yet. State whether the range includes implementation, support, and any usage assumption so the buyer can compare it responsibly.
A useful way to open
“I can give you a useful range. Which team size and workflow are you planning for?”
Move the decision forward
Buyers ask for pricing because they are planning, comparing, or protecting their time. Respect that request. Clarify the minimum inputs needed to avoid sending a number that misleads them.
Coach reps to be transparent about assumptions and to avoid forcing discovery as a toll gate.
Practice before the next call
Roleplay a buyer who says, “If you cannot send a price, we are done.” Practice offering a scoped range and one question that improves it.
Next step
Send a range with explicit assumptions and a brief invitation to validate the right package.
Practice these next
Frame a first conversation around an operating decision the CFO recognizes.
Carry forward the buyer’s language so the first AE call feels like progress.
Respect a buyer’s preferred channel while learning whether email is enough for the decision.
Earn a reply with a plausible operating question that relates to the buyer’s work.
Choose a next step that matches the uncertainty uncovered in the call.
Reach out about a visible incident without exploiting a difficult moment.