The buyer asks, "How much does it cost?" The salesperson responds, "It depends," then guards the number like the final episode of a television show.
Price does depend on things. The buyer still deserves useful commercial information before donating thirty minutes to discovery.
Understand what the buyer is trying to decide
An early price question can mean several things: Can we afford the category? Is this enterprise pricing? Should I bring Finance? Is this worth another meeting? How does it compare with what we spend now?
Ask one direct question:
I can give you the useful range. Before I do, are you trying to check general fit, build a budget or compare a specific option?
The answer shapes how much detail is needed. It should not become an excuse to delay the number again.
Give the most accurate number you can defend
Use one of three forms:
Fixed price: "The program is $X per month with [included scope]."
Starting point: "Programs begin at $X when [minimum conditions] apply."
Range: "Most work of this type falls between $X and $Y, mainly depending on [two or three variables]."
If the company publishes pricing, know it. Making the buyer wait for a discovery call to hear the number already sitting on the website is an impressive way to fail an open-book test.
Explain why the number can move
Name only the variables that materially change the estimate. These may include users, locations, transaction volume, integrations, implementation work, support level, geography, contract term or service scope.
Use plain language:
The range moves mainly with the number of locations, whether historical data must be migrated and the support model. I can narrow it with three questions.
The buyer now understands both the range and the reason for discovery.
Ask the minimum discovery required
Do not hold the price hostage until the buyer completes a twenty-question intake form. Ask the few facts that change the commercial answer:
- What scope or volume should the estimate assume?
- Which requirement is likely to add implementation work?
- Is the buyer evaluating software, service or both?
- What decision must the estimate support?
The broader cold call discovery questions guide can support later stages. The early pricing response should stay small.
Use a script for complex B2B pricing
Based on what you have described, the credible range is [X to Y]. The number changes with [variable one], [variable two] and [variable three]. I do not want to pretend I can quote the final amount without those details. If the range is workable, we can spend fifteen minutes narrowing the scope and decide whether a formal estimate is worth preparing.
That response answers the buyer, protects the seller and gives the next conversation one job.
Handle “that sounds expensive”
Do not discount. Clarify the comparison:
Fair. Is it high compared with the current provider, an internal budget, another quote or the value you can see so far?
Each answer leads somewhere different. A budget gap may disqualify. A scope mismatch may need a smaller option. A weak value case needs evidence, not a surprise coupon.
Use the answer that matches the pricing model
For a subscription, state the unit, minimum commitment, included service and major implementation cost. For professional services, give a project or monthly range and explain which scope decisions move it. For usage pricing, name the unit and a realistic volume example without presenting an estimate as a guaranteed bill.
For a mixed software-and-service offer, separate the components:
The platform is typically [range] annually. Implementation is normally [range], depending on data migration and integrations. Ongoing managed support is optional and priced separately.
Separating the pieces helps the buyer understand what can change. A single giant range without structure often creates more confusion than no number.
If no credible range exists, say why and offer a bounded scoping step. "We need to map the locations and migration work before we can defend a number" is useful. "Every client is unique" is a decorative way to say nothing.
The B2B sales business-case guide helps connect investment to the current baseline and decision consequence without inventing ROI.
Know what an SDR can and cannot say
An SDR should know the approved fixed price, starting point, range, variables and hard floor. The caller should also know when to bring in Finance, sales leadership or a solutions specialist.
SDRs should never create a custom quote, promise a discount, waive a requirement or imply an estimate is binding. "I think we can probably do something" is how innocent small talk becomes a contractual ghost story.
Decide the right next step
Continue to discovery when the range is plausible and missing facts matter. Prepare a scoped estimate when enough requirements are known. Send pricing information when the buyer needs internal context. Disqualify when the gap is real and cannot be solved honestly.
Do not book a generic demo because a buyer asked for a number. Price may be the only question that needs answering.
CallTeam field card: early price question
Keep this structure beside the phone:
- What decision is the buyer trying to make?
- Fixed price, starting point or range?
- Which variables move it?
- What facts are missing?
- Discovery, estimate, resource or close?
The caller should be able to use the card without consulting a pricing oracle in another department.
How CallTeam handles early pricing inside appointment setting
CallTeam turns the client's approved prices, ranges, variables and hard limits into language a human caller can use without bluffing. The caller answers what can be answered, identifies the minimum missing facts and records exactly what the buyer heard. Sales receives the commercial context, assumptions and remaining decision question before accepting a meeting. If the budget and honest floor cannot meet, the opportunity is closed. If only a quote or document is needed, we do not manufacture a discovery call.
CallTeam field observation: In campaign conversations, “How much?” is often a routing question, not proof of buying intent. Buyers may be testing basic plausibility. A clear range earns more credibility than hiding the number behind a meeting request.
Put the commercial truth in the CRM
Record the number or range shared, assumptions, variables, buyer comparison, budget context, approved next step and anything explicitly not promised. Sales should know what the buyer heard before entering the meeting.
Pricing notes should include the date and version of the commercial guidance. If packages or rates change, the account executive needs to know whether the buyer heard the current offer or an older range that must be addressed directly.
CallTeam builds approved pricing language into the script, qualifies the commercial question and books meetings only when another conversation has a job. Want CallTeam to run the campaign? Book a B2B strategy call to define the pricing boundaries and handoff.