# “How much is it?” on the first call: answer it, then write down what you said

https://salesbond.app/blog/first-call-price-question-pipedrive/
Published: 2026-10-06 · Updated: 2026-10-26

When a prospect asks for price on the first call, answer it. Give a range, say what moves it, and ask what job the buyer is trying to get done. Then, before the next call starts, add the range, the assumptions behind it and the buyer’s reaction to the deal. The price question is not the trap. The trap is naming a number, forgetting the conditions you attached to it, and sending a proposal two weeks later that argues with your own words.

## He asked at minute two

A made-up call, but the shape is real. Elspeth sells for a six-person team. Ruairi runs operations at a regional logistics firm and booked the call himself. She hasn’t finished saying what the call is for when he cuts in: “Before we go on, roughly what does this cost?”

It’s an honest question, and most reps are trained to hear it as a hostile one. Ruairi has a budget line, a director who will ask, or two other vendors booked this week. For him, price is a filter. He wants to know whether the next 28 minutes are worth having.

The classic dodge, “let’s come back to that once I understand your needs”, tells him that you decide when he gets to know what his own purchase costs. He hears a tactic, because it is one. Not a great way to open a [first call with a small team](https://salesbond.app/blog/discovery-call-small-team-pipedrive/).

## What the data says, and what it does not prove

HubSpot Research, as quoted in [HubSpot’s piece on the first-call conundrum](https://blog.hubspot.com/sales/the-first-sales-call-conundrum), found that 58% of buyers want to discuss pricing on the first call, while 23% of salespeople are prepared to. Gong Labs looked at 11,331 opportunities: win rates were highest when pricing came up on the first call, 10% higher, and it made no difference whether the buyer or the seller raised it. Their top reps tended to raise price in the 38 to 46 minute window, and first-call budget talk went together with longer relationships, four calls instead of two ( [Gong, “Data reveals the best time to talk price and budget”](https://www.gong.io/blog/data-reveals-the-best-time-to-talk-price-and-budget)).

Read that as correlation. Deals where price comes up early may simply be deals where the buyer already has money and a reason. Nothing here shows that answering caused a win or that stalling caused a loss. The usual advice is to hold price until value lands. This data doesn’t back the wait, and nothing in it penalizes a rep for talking about price early.

## What to say when a prospect asks for price: three moves

A range isn’t a dodge if the conditions come attached. We teach it as three sentences, in this order.

1. **Acknowledge, and say the true useful thing.** “Fair question. I can give you a range right now, and a firm number once I know two things about your setup.”
2. **Give the range with its assumptions.** “For a team like yours, between $1,800 and $2,600 a month. The low end assumes one region and standard integrations; the high end assumes two regions or a custom connection. User count moves it most.”
3. **Ask back about the job, not the budget.** “What made you look at this now?”

The second sentence is the one teams get wrong. A range that spans three times its own floor isn’t a price, it’s a shrug, and the buyer will remember only the floor. Keep the low end at or above the smallest deal you actually want; the reasoning is in our note on [minimum deal size for a small team](https://salesbond.app/blog/minimum-deal-size-small-sales-team-pipedrive/). And never let the range rest on a volume you guessed from their website. “You look like about 12 users” becomes “you quoted us for 12 users” by the time the proposal lands, and now you are the one who moved.

Sometimes the price question is the only question. You give the range, ask what prompted the call, and get back only “just checking.” Write it down exactly like that: asked for price, described no job. That line tells the the next person who opens the deal more than any stage label. If the prospect asks for an NDA before they will talk numbers or see the product, log that request on the deal too; here is our rule for [an NDA before the demo](https://salesbond.app/blog/nda-before-demo-sales-team-pipedrive/).

## The price line in your call note

You already write a [short call note](https://salesbond.app/blog/sales-call-notes-minimum/) after the call. When price came up, add a price block to it. Elspeth adds this before she opens the next tab:

```
Range named (8 Sep call): $1,800–2,600/mo
Assumptions: 12 users, one region, standard integrations, annual billing
Reaction: "that's in the zone"; comparing two other vendors; no budget figure offered
```

The range is the promise. The assumptions are what you will check the proposal against, and that line only protects you if its written the day you said it, not rebuilt from memory a fortnight later.

The reaction is the line most reps skip, and it’s where the deal’s real state lives. “In the zone” with [two competitors named](https://salesbond.app/blog/price-match-quote-lines-pipedrive/) is a different deal from silence and a quick goodbye, and Sindre, her sales manager, reading the pipeline on Monday, can’t tell them apart from the value field. If the reaction was “that’s too much”, treat it as an objection and log it the same way you [log objections in Pipedrive](https://salesbond.app/blog/objection-handling-pipedrive-log-coach/).

For a team of six a note is enough. A field helps Sindre filter only if the team keeps it filled, and an [empty field is worse than a good note](https://salesbond.app/blog/pipedrive-custom-fields-cleanup-data-fields/).

## When your proposal comes out above your own range

Two weeks later Elspeth has done the scoping. Ruairi’s firm turns out to run two regions and wants a NetSuite connection. The proposal lands at $3,400 a month. His reply is one line: “You said 2,600.”

Without the note she argues from memory against his, and his is written down. With the note, she opens with the assumption that changed: “I quoted 1,800 to 2,600 on 12 users, one region, standard integrations. Since then we’ve added the second region and the NetSuite link. Here is what each one adds.” The range didn’t break. The assumptions did, and she can show which.

![Quoted range next to the later proposal: a second region and a NetSuite link are the two assumptions that changed](https://salesbond.app/wp-content/uploads/2026/10/first-call-price-question-pipedrive-2.png)

What she must not do is shave the proposal back to 2,600 because she feels caught. That is how discounts stop being policy and start being apology; the [discount policy piece](https://salesbond.app/blog/discount-policy-sales-teams/) is about exactly this leak. If the gap matters to him, show the one-region option at the old range as a [good-better-best tier](https://salesbond.app/blog/good-better-best-proposal-pipedrive/) beside the full scope, or [trade scope for price](https://salesbond.app/blog/sales-negotiation-trade-concessions-pipedrive/) rather than give price away. Either way, put a validity date on it, or week one’s number will be quoted back to you in month three ( [quote expiry dates](https://salesbond.app/blog/quote-expiry-validity-date-pipedrive/)).

A disclosure: we build SalesBond, and its Deal Health checks every deal against the rules a team switches on. Whether a proposal matches what was said on call one is still a person’s job, and only possible when the price line exists.

## The thing to say tomorrow

If a buyer asks for price in the first ten minutes, answer with a range, name the assumptions out loud, and put both in the deal before you do anything else. The number you say on a first call rarely loses a deal; the number you can’t explain two weeks later sometimes does.