“Too expensive” can mean several things in a pitch. The client may lack budget, doubt the outcome, worry about delivery risk, or compare offers with different scopes. A discount is premature until we know which concern is driving the response.
A useful response to a price objection begins by learning what the client is comparing. The budget may truly be short, the difference may be unclear, or the approver may fear delivery risk. A precise question creates room for an option that respects value and delivery cost.
Begin Selling by Asking Better Questions
Before opening the proposal, ask why the issue must be solved now, what happens if nothing changes, and who will use the result. Speak to users, approvers, and budget owners where possible; each may define value differently.
Agree on inspectable success criteria and constraints such as timing, internal capacity, and approval steps. If an outcome cannot yet be promised on the available evidence, state the assumption and what must be tested. Winning a pitch by creating unsupported expectations is a poor start to the relationship.
Before the pitch, ask why action is needed now, what has already been tried, and how approval will be judged. Listen to users, budget owners, and decision-makers, who may define value differently. Restate the problem before writing a detailed proposal.
Practical Takeaways
- Ask why action is needed now
- Ask how success will be measured
- Ask who is affected by the decision
Sell the Outcome, Not the Task List
A list of deliverables says what we will hand over, but not why that method fits the problem. Connect each activity to the decision or outcome it supports. Research may reduce uncertainty before content production; measurement may help reallocate spend away from ineffective work.
Distinguish what the team can deliver from results affected by the market, budget, and client decisions. Explain the sequence of reasoning, interim indicators, and exclusions. A transparent proposal lets the client compare offers on a common basis.
Connect the problem, method, measures, and resources to explain the price. Separate what the team can deliver from results influenced by the market and client. State assumptions, scope, and exclusions. An intended outcome should not become an unsupported guarantee.
Practical Takeaways
- Connect work to relevant KPIs
- Explain the logic behind the plan
- Clarify what is not included
Translate “Too Expensive” into the Real Question
When the client says the price is high, acknowledge the concern and ask whether it is high against the available budget, the expected result, or another offer. Each answer leads somewhere different. A budget gap calls for a scope discussion; unclear value calls for better reasoning or evidence.
If the comparison is between unlike offers, examine scope, revision rounds, responsibilities, and reporting. Do not disparage competitors or promise a return you cannot substantiate. Offer meaningful choices, such as a smaller first phase with a decision point before expansion.
Ask whether “expensive” refers to budget, expected value, or another offer. If scopes differ, compare responsibilities, revision rounds, and reporting. For a real budget limit, offer a narrower trial with explicit omissions. Do not quietly remove essential work or promise a standard the price cannot support.
Practical Takeaways
- Reflect the concern before responding
- Ask which comparison criteria matter
- Offer options with different scopes
Close with a Clear Next Step
End the conversation by stating the agreed problem and criteria, remaining concerns, who must provide information or approve, and when the next discussion will happen. Sending a proposal and waiting in silence leaves the reason for delay unknown.
If the client is not ready to buy, agree on what would enable a decision: a scope comparison, short plan, or answer about delivery risk. Avoid producing extensive unpaid work without a shared process. A good close makes the next step clear to both sides.
End with agreed objectives, remaining concerns, approvers, required information, and a review date. Send a summary understandable to people absent from the room and follow up as agreed. Distinguish a delayed budget cycle from a proposal that needs revision.
Practical Takeaways
- Summarise what is agreed
- Identify missing information
- Schedule the next step before ending
The next time you hear “too expensive,” pause before offering a discount. Find out what the client is comparing, then respond with evidence or a transparent scope change. Price should move with the work and economics, not just with discomfort in the room.
“Do not reduce the price before you understand what the client is uncertain about.”
Follow Ai Aiyaphat Wankawisant:
อัยย์ อัยพัชรAi Aiyaphat 
