What Sales Should Find Out Before Quoting a Price

A salesperson who quotes a price before understanding the customer's goal, situation, obstacle, timing and decision maker wastes the lead that marketing paid for. Five discovery questions recorded as CRM fields, together with a written response-time standard, turn a caller who repeats the price into an adviser.

Why is quoting the price first a mistake?

Because a price given without context is only a number, and the customer has nothing to compare it with except a cheaper number. When the first thing a salesperson says is the price, the conversation becomes a price comparison, and the salesperson has no reason to offer for choosing one option over another.

I call this pattern "the caller who repeats the price." The lead asks how much, the salesperson answers, the lead says "I'll think about it," and the record is closed as "not interested." Nobody learned why the person asked in the first place. The adviser does the opposite: understands what the customer wants to achieve, recommends the option that fits, and then states the price as part of that recommendation.

Discovery does not mean hiding the price or dodging the question. If a customer asks directly, give a range and then ask for two minutes to make sure you recommend the right thing.

What should a salesperson find out before quoting a price?

Five things: the goal, the current situation, the obstacle, the timing, and who makes the decision. With those five, the salesperson can recommend one option with a reason, and the manager can judge whether the lead was worth pursuing.

What to find out	A question that works	What the answer tells you
Goal	"What do you want to be able to do once this is done?"	Which product or level actually fits
Current situation	"Where are you today? What have you tried so far?"	The starting point, and what not to offer again
Obstacle	"What has stopped you until now?"	The real objection, before it shows up as "too expensive"
Timing	"When do you need to start, and is there a date driving that?"	How urgent the follow-up should be
Decision maker	"Is this your decision alone, or does someone else weigh in?"	Who needs to hear the recommendation

These are conversation prompts, not a questionnaire to read aloud. Listening matters more than the order.

How should the answers be recorded in the CRM?

As structured fields, not as a free-text note. A note that says "interested, will call back" cannot be counted, filtered or reported. A field that says "Timing: this month" can.

Most CRM systems let you add your own fields. HubSpot, for example, calls them custom properties and lets you choose the field type, such as a dropdown, a date or a number. I recommend five fields that mirror the five questions:

Goal: a dropdown with four to six options that match your offers
Current situation: a short dropdown, such as beginner, has tried before, already using an alternative
Obstacle: a dropdown with price, time, trust, needs approval, other
Timing: this week, this month, later, undefined
Decision maker: self, family, manager, committee

Keep one free-text field for the customer's own words, because those words are what your next ad should say. Then set one rule: no price quote is logged as sent until the five fields are filled. That rule turns discovery from advice into routine.

How fast should the first reply be?

Fast enough that the person is still thinking about the problem that made them write to you. A Harvard Business Review study of how companies respond to online sales inquiries concluded that most companies do not respond nearly fast enough.

The practical step is to write the standard down. In the sales procedure I helped write at CoderZ, the response standard for a new inquiry is under three minutes. That is a standard written into the procedure, not a measured result, and I mention it only as an example of how specific a standard should be. Choose a number your team can honestly keep, define what happens outside working hours, and measure the gap.

How does discovery protect the marketing budget?

It tells you which leads were worth paying for. Without discovery data, a marketing manager sees only the cost per lead, and the cheapest lead looks like the best one. With it, you can see which campaign brings people who have a clear goal, a near date and the authority to decide.

Here is a hypothetical example with round numbers. Campaign A brings 100 leads at 5 dinars each, and Campaign B brings 50 leads at 10 dinars each. On cost per lead, A wins. If the CRM fields show that 10 of A's leads had a defined goal and a start date this month, against 20 of B's, then B produced twice as many serious conversations for the same 500 dinars. Without the fields, the budget would have moved to A.

Discovery data also explains lost deals. If "needs approval" is the most common obstacle, the fix is material written for the person who approves, not a discount.

Where does this approach come from?

From shared work, not from me alone. At CoderZ, where I am the marketing manager, I worked on a sales system we call Discovery together with colleagues and management. I have no measured uplift to report from it yet, so I am not claiming one. What I can describe is the reasoning behind it.

What should you do this week?

Read or listen to ten recent sales conversations and count how many quoted a price before asking a single question.
Agree with the team on the five questions in their own words, in the language your customers use.
Add the five fields to your CRM as dropdowns, plus one free-text field for the customer's own words.
Write the response standard in one sentence and put it where the team can see it.
At the end of the week, review how many records have all five fields filled, before you look at any sales number.