Execution · 2026-04-10 · 5 min
Talking Price on the First Call Without Losing the Deal
Avoiding the price question on a first call does not protect the deal, it just delays the moment the prospect finds a reason to disqualify you. Here is how to raise price early without sounding like you are trying to filter people out.
The advice we hear most often from agency founders is to avoid talking about price until the second or third call, once "value has been established." In practice this usually just delays a disqualification that should have happened in the first ten minutes, and it wastes both sides' time doing it.
If a prospect cannot afford what you charge, no amount of discovery call rapport changes that. What the delay actually protects is the seller's discomfort with the conversation, not the deal.
Why avoiding it backfires
When price comes up late, it arrives after the prospect has already built a mental picture of the project and, often, a budget number that has nothing to do with your reality. Correcting that number after they have invested time imagining the work feels like a bait and switch even when nobody intended it that way. The relationship starts on the back foot exactly when it should be starting on solid ground.
Raising the range early does the opposite. It filters out the accounts where the fit was never there, and for the accounts where it is a fit, it builds trust because you did not waste their time getting to the number.
How to actually say it
The trick is not to announce a price. It is to state a range as a fact, tied to the type of project, and then move straight back into the conversation rather than pausing for a reaction.
Weak version: "So, before we go further, I should mention our projects usually start around €40,000, is that going to be a problem?"
This reads as an apology. It invites a negotiation before any value has been discussed at all.
Better version: "Projects like this typically run somewhere between €35,000 and €60,000 depending on scope, so let's talk through what you actually need and I can tell you roughly where you'd land in that range."
This version states the range as ordinary information, not a test, and immediately pivots to scoping, which is the actual point of the call. It also gives the prospect room to self-select without forcing a yes or no on the spot.
What to do with the reaction
There are three reactions worth planning for.
- Silence or a neutral acknowledgement. Keep going. This is the good outcome. Most qualified prospects react this way because the number matched what they expected.
- "That's higher than we budgeted." Ask what the actual budget is before assuming the deal is dead. Sometimes it is a real mismatch. Often it means the budget was a guess and there is room, particularly if the scope can flex.
- A visible flinch or a fast change of subject. This is useful information. It usually means the account is not qualified at the price point you sell at, and it is better to know in minute ten than in week three of a proposal process.
A short worked example
A prospect asks for "a full rebuild of our platform" with no further detail. Instead of scoping first and pricing later, try:
"Full rebuilds we've done recently have ranged from about €50,000 for a scoped MVP-style rebuild to well over €150,000 for something with the full feature set migrated. Where do you think this sits, and what's driving the timeline?"
This does two jobs at once. It anchors a realistic range immediately, and it turns the next question into a scoping question rather than a pricing negotiation, because the number has already been said out loud.
The exception
If you sell a genuinely custom, high-variance service where the range is so wide that stating it early would be meaningless, for example anything from €10,000 to €300,000 depending on scope discovered later, it is fairer to say that plainly: "the range on projects like this is wide enough that I'd rather scope with you first and give you a real number, but I want to be upfront that this isn't a five-figure-and-done category of work." That still signals seriousness without inventing a false precision.
Delaying the price conversation feels safer in the moment because it avoids an uncomfortable few seconds. It is not actually safer. It just moves the discomfort later, attaches it to a proposal you already spent hours writing, and makes it look like the number changed when really it was just finally said out loud.
Next: on your next first call, say the price range before the prospect asks for it, and watch how much faster the rest of the call moves.