Price Range Instead of Price List
The most common first message of all is “what does it cost?”. A number ends the conversation, and so does a dodge. Three questions about scope, timing and starting condition turn that question into an assessment: at the end there is a range with a reason behind it, and anyone who finds it too high says so instead of quietly disappearing.
Why “what does it cost?” is so often the last message
The first message in your inbox is rarely “tell me about your offer”. It is “what does it cost?”. You have two options at that point and both are bad. Name a number and it sits there without context, your contact measures it against a figure they invented for themselves, and they never write back. Dodge, with “that really depends” or “let’s get on a call first”, and they read it as expensive and as something you would rather not say out loud.
The dodge feels safer because you give nothing away. It still costs you. Gong analysed 11,331 sales opportunities: when price comes up in the first conversation, the close rate is 42 percent; when it waits for the second, 32 percent; the third, 15 percent; and with no pricing conversation at all, 5 percent are left. That is a correlation from platform data rather than proof, but the direction is hard to miss. Postponing the number does not make the deal more likely.
On top of that, your contact already expects an answer. In the TrustRadius buyer survey of 1,862 technology buyers, transparent pricing has been the number one thing buyers want from vendors for the fourth year running, named by 45 percent. When people do not get that orientation, they build it themselves, and they build it too low almost every time. Every number that arrives later then lands as a surprise. How expensive surprises are has been measured in online retail: at the Baymard Institute, the single most common reason for abandoning a checkout is extra costs coming in higher than expected, named by 40 percent, with another 12 percent leaving because the total was not visible upfront.
The way out sits between the two bad answers. Instead of a number and instead of a dodge, three questions come first: how big is the job, by when does it need to be done, what are you starting from. What follows those three answers is not a quote, it is a range, with a short reason for what pulls it up and what pulls it down. Underneath it sit two buttons: works for me, or higher than I thought. The second button is the real win. Whoever presses it stays in the conversation instead of silently closing the app.
You do not find the three questions at your desk, you find them in your last ten quotes. Lay them side by side and look for the variables that moved the price the most. In almost every project-based business it is the same three: scope, because it sets the volume; timing, because urgency gets paid for; and the starting condition, because it decides how much work sits in front of the actual work. Anything that moves the price by less than a tenth belongs in the call, not in the chat. And the range itself belongs in a message of its own. A number tucked behind an explanation gets skimmed past or read as fine print. A number standing alone is a statement you are prepared to defend.
How the sequence is built
The price question itself is the entry point
The trigger is the chat button on your pricing page, the link under an ad, or a message that starts with “what does it cost”. The first reply is an approved template with an opt-in, and it carries a promise: you will tell them the range, and for that you need three details. Without that promise, any question back reads as evasion, and that is exactly where you lose the people who have asked three suppliers for a price and never got one. With the promise, the first question is no longer a hurdle, it is the condition for something your contact actually wants.
Three questions that really drive the price
Scope comes first, because it is factual and asks nothing of anyone: how many square metres, how many rooms, how many dates, how many pages. Timing next, because urgency carries a premium in almost any business and because the answer also tells you whether this person is planning or acting. The starting condition comes last: the state of whatever you are building on. It has the biggest leverage, because it exposes the work that sits in front of the work, and it goes last because it is the one most likely to feel like an inspection. One question per message, at most three answer options. That format carries: across 2.6 million forms analysed by Typeform, one question per step averaged a 47.3 percent completion rate against 21.5 percent for classic forms.
The range comes from combinations, not from a formula
There is no calculator here, and that is the actual simplification. Three questions with three fixed options each produce a manageable number of combinations, and you set a range for every one of them in advance. A condition node reads the stored answers and picks the matching one. The advantage over calculation logic: you decide each range individually, with what you know about that kind of job, instead of trusting a formula that produces nonsense at the edges. The width of the range is a statement about you. If the top end is more than double the bottom end, your three questions are cut too coarsely.
The range arrives as its own message, with a reason
The range stands alone, with no preamble and nothing appended. Below it, in a second message, comes what pulls it up, what pulls it down and what is not included. The second part matters more. A number without a reason is a claim; a number with a reason is an assessment, and only an assessment can be applied by your contact to their own situation. The line about what is not included spares you exactly the argument that costs jobs that had already been won.
Two buttons, and the second one is the important one
Underneath the reasoning sit two options: works for me, and higher than I thought. Without the second button the objection has nowhere to go, and an objection with nowhere to go turns into silence. With it, you get the piece of information you normally never receive: that it was the price, and not the timing, the trust or a competitor. Both answers set a tag, so that after forty contacts you can see how your ranges are landing and whether they need moving.
The objection branch does not discount, it explains
There is no discount here. There are three things: what is genuinely included at the bottom end of the range, which of the three answers pushed the price up in this case, and what a smaller first step looks like. The middle one is the strongest, because it moves the price away from you and attaches it to the job. After that the path splits once more: whoever takes the smaller step heads for the same booking as everyone else, and whoever leaves gets a tag and a scheduled follow-up instead of dropping off the list.
The call starts at the scope, not at the price
The booking link only appears behind an accepted range, and there it is the single action button. In front of the goal of type “call_booked” sits the handover to your CRM: the three answers, the range you quoted and the reaction to it. That removes half the agenda from the call. Your contact has seen the price and came anyway, so “does this fit the budget” is answered before anyone asks it. You talk about the scope and about where in the range their job sits. Where your booking link belongs is marked, and so is the signal your booking tool sends back.
Example scenario: a bathroom renovation firm with a chat entry point
A trade business renovates bathrooms and interiors. Inquiries arrive through the chat button on the website and through ads. Almost every first message is some version of “what does a new bathroom cost?”.
Depending on the day, the answer is either “there is no flat figure for that” or “from around X”. The first version is usually the end of the conversation; the second one leads to a site visit where, twenty minutes in, it turns out the customer had half that number in mind. Anyone who finds the firm too expensive does not say so, they simply stop replying. The calendar fills with visits for jobs that were never going to happen, and the driving time is missing from the ones that would have.
Three questions now sit in front of the number: size of the bathroom, desired timeframe, condition of what is there. Then the range arrives as its own message, followed by the reasoning for what pushes it up, old pipework or a tight deadline for instance, and what is not included. Anyone who answers “works for me” sees the booking link for the site visit, and the three details are already in the CRM. Anyone who presses “higher than I thought” reads what is included at the bottom end and which detail drove the price, then decides from there. The calendar is emptier afterwards, and every site visit starts at the question of where in the range this bathroom sits, rather than at whether both sides are even thinking in the same order of magnitude.
What you get
The blueprint for the pricing sequence
The whole sequence laid out visually: the entry with its promise, the three questions, the condition node, the range message, the fork with its two buttons, both branches and the goal. Each node is annotated with what it is for and which detail it takes in or returns. The phrasing comes from you, the structure stands.
The three questions with their answer options
Which variable each question covers, what order it comes in, and how the three options need to be cut so every combination lands in exactly one range. Plus the reasoning for why those three drive the price in your business, and which obvious fourth question belongs in the call rather than in the chat.
The range matrix
For every combination of the three answers, the blueprint records which range gets sent and what the reasoning underneath it says: what pulls it up, what pulls it down and what is not included. You fill in the figures; the structure and the width of the spans are drawn out for you, along with a note on where your questions start getting too coarse.
The objection branch, fully drawn
What happens behind “higher than I thought”: the smaller scope at the bottom end, the pointer to the driver in that specific case, the smaller first step. Plus the point where this branch leads back to a booking, and the point where the tag is set so the contact runs into follow-up instead of off the list.
Buyer persona and starting list
A persona with over 50 data points on buying motives, objections and how decisions get made in your market. That tells you which range is even conceivable for the person reading it and which objection comes first. Along with the list of what needs to be ready before you build: booking link, CRM fields, a short video or a PDF explaining how your pricing works, and the smaller first step as a real offer.
More funnel blueprints
Discovery Call Pre-Qualification
Four questions in chat decide who gets a slot, who comes back later and who gets a friendly no.
View blueprintFrom Need to Recommendation
Two or three questions pin down the need and end at exactly one recommendation instead of a list that leaves your customer choosing alone.
View blueprintAnswer the price question before it ends the conversation
The pricing sequence comes drawn out: the three questions, the range matrix, the fork with both branches, buyer persona and asset list. You write the messages yourself, and the core takes under six hours to rebuild in your messenger tool. One-time payment, no subscription.
Build my funnel blueprintOne-time payment, no subscription. You get the complete strategy and overview first.