The just send me pricing objection puts a rep in a bind that sales training makes worse. The prospect says 'just send me pricing,' the rep has been told never to quote without discovery, so they stall, and the prospect hears a vendor hiding a number, which is what a vendor with a bad number does. Refusing is the wrong move. So is sending a full quote to someone whose team size, use case, and current spend you do not know, because that quote goes into a spreadsheet next to four others and gets judged on the bottom line alone. The script below gives a real range in the first thirty seconds, then earns the two questions you need to make the number specific. The openers cover the email version, the cold-call version, and the late-stage version, and the smokescreen test tells you when 'send pricing' means 'I am done talking.'
What "Just send me pricing" is really telling you
Under 'just send me pricing' you usually find one of two things. The first is a filter: the prospect has a budget ceiling in their head and wants to know in ten seconds whether you clear it before they spend an hour on you, which is a perfectly rational way to buy. The second is an exit: pricing is the request that ends a call politely, because a rep who is refused a number will keep pitching, but a rep who sends a PDF will go away. The mistake reps make cuts both ways. Refusing to name any number reads as evasion and kills the filter case. Emailing a full quote with no context loses the exit case anyway and hands the filter case a number with no story around it. Give a range, out loud, then ask for the two facts that would move it.
Just send me pricing objection script: five beats, spoken
You need a real range you are allowed to say aloud before using this. If your company will not let you name one, fix that first; the script does not work with 'it depends.'
ACKNOWLEDGE: Happy to. I will give you a range right now, and then I want to ask you two things so the number I send is the one you actually pay rather than the one on the website.
CLARIFY: For a team your size it typically lands between {{low}} and {{high}} a year. The two things that move it are how many seats and whether you need the {{module}}. Roughly how many people would use it, and is {{module}} in the picture?
REFRAME: The reason I ask is that a number in an email gets compared with four other numbers in a spreadsheet, and the cheapest one wins on paper whether or not it does the job. If I know the two facts, I can send you the price and a line on what it replaces, so the spreadsheet compares like with like.
PROOF: Northwind Freight asked me the same question in the first five minutes. The range I gave them was right, the final quote landed in the middle of it, and the twenty minutes we spent first meant they cut a tool they were already paying for, which covered most of the cost.
ASK: Can I take those two answers now, and get you a one-page quote by end of day with the number and what it displaces?Direct: 'Sure. For teams like yours it runs between {{low}} and {{high}} a year. Two quick questions and I can make that exact.'
Curious: 'I can. What number would make this an easy no, so I do not waste your time?'
Dry: 'I will, and I will also tell you what it replaces, because a price with nothing next to it is just the most expensive line in the spreadsheet.'The test: give the range and ask 'Does that fit the budget you had in mind?' A real buyer reacts to the number, high, low, or fine, and tells you something. A smokescreen says 'just send it over' again without engaging with the range at all.
If it is not real, send it and release them: 'Will do. It sounds like this is a not-right-now; if that changes, the number will still be in your inbox.' Then log the range you gave so the next rep does not contradict it.Say the range out loud before you ask anything; a rep who asks two questions first has already confirmed the prospect's suspicion that the number is bad.
Rewrite the script for your product and this account
The script works with a real range and two qualifying facts specific to your pricing model, and the one-page quote it promises has to show what your product displaces at this account. Give Claude your pricing structure and what you know about their stack with the prompt below and let it draft both.
I am handling 'just send me pricing' from {{prospect title}} at {{company}} ({{company URL}}). My product: {{one-line description}}. Pricing structure: {{seats, tiers, modules, typical range for a team of their size}}. The two facts that move the price most: {{fact 1}}, {{fact 2}}.
What I know about them: {{team size, tools they currently pay for that overlap with mine, any budget signal}}.
Rewrite the five-beat script below with a real range in CLARIFY and my two qualifying questions asked in plain language. In REFRAME, name the specific tool or manual process at {{company}} my product would displace, if you can infer one from their site or stack. PROOF should use: {{customer who asked for pricing early, what they displaced}}. Under 200 words, spoken. Then draft the one-page quote email: price, what it replaces, one line on next step. Mark inferences.
SCRIPT:
{{paste the script above}}Handle any objection with Claude
- Objection handling script prompt →The copy-paste prompt that drafts a response to any objection in your voice, with the proof point pulled from your own wins.
- Competitive battlecard skill →For the competitor-shaped objections: a rep-ready battlecard built from live competitor intel.
- Discovery call prep skill →Most objections are discovery you skipped. The skill preps the questions that surface them before the pitch.
Frequently asked questions
How do you handle the just send me pricing objection without losing the deal?
Give a real range in the first thirty seconds, then ask the two questions that make the number exact. Refusing to name a figure sounds like you are hiding a bad one, and a full quote sent blind gets compared on price alone against vendors who solve a different problem. The range keeps you honest, the questions buy you a few minutes of discovery, and the quote you send afterward can show what your product displaces, so the comparison is on cost of the outcome rather than on the sticker.
Should you ever refuse to send pricing?
Almost never. The cases where holding the number makes sense are enterprise deals with genuinely custom scoping, and even there you can give a floor. For everything else, a rep who will not say a number is telling the prospect that the number does not survive daylight. What you can refuse is the blind, context-free PDF. Offer the range, ask for the two facts that move it, and send a quote that names the outcome and what it replaces. That is a different document from a price list, and it gets read differently.
What if the range is above their budget?
Then you have saved both of you an hour, and you should say that. Ask what the ceiling was, because it tells you whether you are 20 percent over, which a smaller scope or a displaced tool can close, or three times over, which nothing closes this year. If it is the former, propose the smaller scope on the spot. If it is the latter, thank them, ask what would have to change for the budget to move, and note the date. Prospects remember the rep who took a quick no gracefully.