Discuss a price objection for product design services
The Prospecting Show with Dr. Connor Robertson · Editorial sales resource · October 12, 2026
Understand the comparison behind a pricing concern before responding. This guide applies the workflow to selling product design services, where a useful conversation may involve the product manager and design leader and a practical review of a user workflow remaining unclear after feature discussions.
The finished result is a pricing discussion note. Work from information the buyer confirms. The examples below are planning models; replace bracketed fields and unsupported assumptions before using them with an actual account.
Start with the buyer’s operating context
For this selling context, a possible reason to investigate involves a product release or workflow redesign. That event alone does not establish demand. Check whether the team experiences this issue: a user workflow remaining unclear after feature discussions. Confirm who owns the workflow and whether a change is worth evaluating.
| Question | Working hypothesis | Evidence to request |
|---|---|---|
| Who should participate? | product manager and design leader | The contact’s description of ownership and decision roles |
| What is happening? | a user workflow remaining unclear after feature discussions | A recent example from the actual workflow |
| What can be measured? | task completion, usability observations, and design decisions | A dated baseline with definitions and a named owner |
| What constrains a change? | user access, prototype scope, and engineering dependencies | Requirements confirmed by the people responsible |
A practical sequence
- Ask whether the concern is budget, value, timing, or an alternative.
- Restate the agreed scope.
- Explore a narrower option only if it remains useful.
- Record the tradeoff instead of offering an unexplained discount.
Apply these steps to the same account rather than changing the hypothesis halfway through the exercise. If new evidence contradicts your starting assumption, update the record and reconsider the next action. The objective is a useful decision, not a completed form.
Worked example: discuss a price objection
Illustrative example, not a report of a client result.
“When you say the price is too high, is the concern the available budget, the scope, or confidence that we can address a user workflow remaining unclear after feature discussions?” If a narrower review is sensible, define a review of one workflow before estimating design work as a separate scope with its own deliverables rather than discounting the original proposal without explanation.
Use a concrete artifact
A useful supporting resource in this context is a task-based usability brief. It should help the product manager and design leader assess the current situation without forcing them through a generic sales presentation. Keep the scope narrow enough that the buyer can correct it.
For example, connect the artifact to task completion, usability observations, and design decisions. Identify which inputs came from the buyer, which are public observations, and which remain assumptions. Do not request private operational records before the buyer has agreed an appropriate purpose and handling process.
Build the working record
Complete this worksheet during preparation, then revise it after the conversation. An unknown is a useful finding when it is recorded honestly.
| Field | What to write |
|---|---|
| Account and owner | [Account] · [Rep] · [Review date] |
| Confirmed problem | The buyer’s description of a user workflow remaining unclear after feature discussions, or “not confirmed” |
| Baseline | Available evidence for task completion, usability observations, and design decisions, with source and date |
| Deliverable | a pricing discussion note, including scope and the person who reviews it |
| Open questions | Unconfirmed assumptions, required participants, and unresolved constraints |
| Next decision | Advance, gather evidence, revisit by request, or close the record |
Evaluate the result
Track pricing concerns resolved with a clear scope decision. Define the numerator, denominator, and review window before comparing results. Use comparable accounts and channels; otherwise an apparent improvement may simply reflect a different list or buying context.
For product design services, pair the workflow measure with the quality of evidence about a user workflow remaining unclear after feature discussions. A reply or meeting is useful only if it helps establish relevance. Record declined and unsuitable opportunities so the team can improve targeting as well as messaging.
A common failure to avoid
Do not argue with a budget constraint or invent scarcity. A lower price without a scope change can obscure the real issue.
In this context, the practical consequence is spending time on a review of one workflow before estimating design work before the buyer has confirmed a reason to do it. Revisit user access, prototype scope, and engineering dependencies early enough to discover a genuine mismatch.
When to move forward
Proceed when both sides understand the economics and the remaining decision. A sensible next step may be a review of one workflow before estimating design work, but only when it follows from the evidence. If the buyer cannot identify a relevant problem or owner, close or reclassify the record instead of manufacturing urgency.
Continue the workflow
- Discuss an existing provider
- Write a clear sales proposal
- Discuss a price objection across selling contexts
- Product design services sales guides
For the wider collection, visit the prospecting and sales library. Learn about the host on the Dr. Connor Robertson profile or explore the published podcast interviews.