How to handle pricing questions too early is a skill that separates founders who close from founders who get ghosted, because "what does it cost?" in the first two minutes is almost never really about the number. It is a test, a filter, or a reflex. Answer it like a literal question and you either anchor yourself low, scare them off before they see value, or lose control of the conversation. Dodge it clumsily and you look evasive and lose trust. There is a third move, and it is learnable.

For founders running their own sales this comes up constantly, because buyers know a founder can usually quote on the spot. The goal is not to hide the price. It is to make sure the price lands after the value, not instead of it, without making the buyer feel handled.

Key takeaways

• An early pricing question is usually a budget filter, an anchoring test, or nervousness, not real readiness to buy.

• Never quote a hard number before the buyer has connected your product to their problem.

• Acknowledge the question, give a range or anchor, then redirect to scope; do not dodge it.

• Use an anchor that frames value (their cost of the problem), not just your number.

• If they will not move past price first, that is qualifying data, treat it as a signal.

Why do buyers ask about price so early?

Mostly for three reasons, and none of them is "I'm ready to buy, just tell me the number." It is a budget filter ("is this a $50 or a $50k thing so I know whether to keep talking"), an anchoring move (they want to set the negotiation low), or simple nervousness (price is the concrete thing they know how to ask about). Treating all three as the same literal request is the core mistake.

According to B2B buying research from Gartner, buyers spend the majority of their journey doing independent evaluation, and early price probing is part of self-qualification, not late-stage negotiation. So the right response is not a number; it is a response that helps them qualify while keeping value in front. For where this sits in the call, see the 5-stage discovery call playbook.

What do you actually say when they ask too early?

You acknowledge it directly, give an honest range or anchor so you are not evasive, then redirect to scope so the real number lands in context. The move has three beats and takes about fifteen seconds. The structure below is the script.

The three-beat response

• Acknowledge: "Totally fair question, I'll give you a straight answer."

• Anchor with a range tied to value: "It runs roughly $X to $Y depending on scope, and teams usually weigh that against the [cost of the problem] they're spending now."

• Redirect: "So it lands in context, can I ask two quick things about your setup?"

This is honest (you gave a real range), confident (you did not flinch), and controlled (you moved to scope). Refusing to answer at all reads as a tell. For nearby objection scripts, see the outbound objection cheat sheet.

How do you anchor on value instead of just your number?

You anchor against the cost of their problem before you state your price, so your number is compared to a bigger one. "Most people in your spot are losing X hours a week or paying an agency $4,000 a month for this; we're a fraction of that" reframes the entire price conversation. The classic anchor: "An SDR agency runs about $4,000 a month. Doing it yourself by hand is hours a week you don't have." Now your price is the relief, not the expense.

The anchor is what stops an early number from killing the deal. For the comparison narrative behind the agency anchor, see AI sales rep vs SDR agency cost.

When should you just give the number immediately?

Give it straight when the price is low enough that the question is genuinely a filter, when the buyer is clearly senior and time-poor and will resent the dance, or when hiding it would damage trust more than an early number would cost you. Skilled handling means reading which situation you are in, not running the redirect on reflex. A founder who redirects a CEO who asked one direct question loses more than the anchor saves. For qualifying who you are dealing with first, see how to qualify B2B prospects before you DM.

Frequently asked questions

Isn't redirecting a price question just dodging?

Only if you refuse to answer. The technique gives an honest range immediately, then adds context; that is not a dodge, it is sequencing. Dodging is "we'll get to that." Acknowledging plus a real range plus a scope question is transparent and still controlled.

What if my pricing is public on my site anyway?

Then never pretend it is secret; that destroys trust instantly. Instead, acknowledge they have seen it and pivot to value: "You saw it's $X; the thing that actually matters is whether it pays back for your setup, can I show that?" Public price changes the script, not the principle.

They keep pushing for an exact number before anything else. Now what?

Give the real range confidently and read it as a signal. A buyer who cannot move off price before any value is often price-led and low-fit. That is useful qualification, not a failure. Do not lowball to keep a deal that was telling you what it is.

Does this apply to a low-priced self-serve product?

Less so. For a low self-serve price, just answer; the redirect overhead is not worth it and can feel evasive on a small number. The full technique pays off most on considered, higher-ticket or scoped deals where context genuinely changes how the price is received.

Bottom line

How to handle pricing questions too early comes down to reading the real reason behind the question, never quoting a bare number before value lands, acknowledging honestly with a range, and anchoring against the cost of their problem so your price is the relief. Know when to skip the dance and just answer. Done right, an early price question becomes a qualifying tool instead of a deal-killer. To keep filling the pipeline with buyers worth having this conversation with, see repco.ai.