When a client says your price is too high, do not defend it before you know what “too high” means. They may have a fixed budget, be comparing a different scope, be unclear about a deliverable, or simply need approval from someone else.
Ask one question, identify the constraint, and then choose among three honest responses: clarify the existing scope, reduce the scope, or decline the project. A discount is only one option, and it should come with a clear reason rather than panic.
Start by clarifying the objection
Useful questions include:
- “Is the constraint the total budget, the timing of payments, or the scope itself?”
- “Which part of the proposal feels out of proportion to what you need?”
- “Are you comparing this with another proposal that includes the same deliverables and terms?”
- “Is there a budget ceiling I should use if I prepare a smaller version?”
Do not interrogate the client. One neutral question is usually enough to reveal whether a revised proposal would help.
Response example
Thanks for being direct. Before I change the proposal, can I check whether the issue is the total budget or whether some of the deliverables are not essential? If you have a firm ceiling, I can show what a smaller scope would include and what it would leave out.
This keeps the conversation factual and avoids promising the same work for less.
Make the price comparable
A line such as “website design: EUR 4,000” is difficult to assess because the boundary is missing. State what the fee covers:
- number and type of pages;
- copy, design, development, or strategy included;
- responsive and accessibility work;
- number of review rounds;
- handover, training, and post-launch support;
- third-party costs and exclusions.
Describe outcomes you can reasonably connect to the work, but do not promise business results you cannot control. “Editable CMS and recorded handover” is concrete. “A website guaranteed to double leads” is not.
If the client is comparing proposals, ask them to compare scope, assumptions, timeline, and rights as well as the total. A lower quote may simply contain less work.
Reduce scope without hiding the trade-off
When the budget is firm, offer a version that still works on its own. Show exactly what moves out.
We can bring the project to EUR 3,200 by launching the five core pages first. The case-study template, analytics dashboard, and second revision round would move to a later phase. The launch date remains 30 April.
This is a new offer, not a disguised discount. Update the proposal so the accepted document matches the work you will deliver.
Possible scope changes include:
- fewer deliverables;
- a later or longer timeline;
- client-supplied copy, research, or assets;
- fewer review rounds;
- a shorter support period;
- a paid discovery phase before the full build.
Do not remove work that makes the result unusable or unsafe. If the budget cannot fund a viable version, say so.
Show scope and price clearly
Start from proven proposal templates
Save writing time and use layouts built to make scope, value, and pricing immediately clear.
Use packages only when the choices are real
Two or three packages can help when clients regularly choose between meaningful service levels. For example:
| Package | Suitable for | Main trade-off |
|---|---|---|
| Core | A team that can supply final copy and assets | Less support from you |
| Complete | A team that needs design, build, and handover | Higher project fee |
| Ongoing | A team that also needs monthly optimisation | Longer commitment |
Each option should be deliverable at the stated price and appropriate for a real client. Avoid a deliberately weak package or an inflated option whose only purpose is to manipulate the comparison.
If every client needs the same scope, one well-explained proposal may be clearer than three packages.
Consider payment timing separately from price
Sometimes the total fits but the first payment does not. If your cash flow and project risk allow it, milestones can solve that without reducing the fee.
For example:
- 40% on acceptance;
- 30% on approval of the first milestone;
- 30% on delivery.
Tie payments to objective events and state due dates. More instalments also mean more administration and collection risk, so use the simplest schedule that fits the engagement.
Treat proposal opens as a limited signal
Tracking can show that a proposal link was accessed. It cannot prove that the client objects to price or intends to buy. Multiple opens may reflect several stakeholders, a forwarded link, repeat reading, or something else entirely.
Use the information to improve the next question:
- no recorded open: confirm delivery;
- opens but no reply: ask whether scope, timing, or approval needs clarification;
- a client message about budget: respond to that stated constraint.
With Proposa proposal tracking, opens, messages, and the client's recorded decision stay together. The data can reduce guesswork, but the client still has to tell you what the obstacle is.
When a discount can make sense
A discount is not automatically wrong. It can be reasonable when there is a real exchange, such as:
- a smaller scope;
- a longer delivery window that lowers your cost;
- a volume commitment;
- a case study or other right whose value and consent are written down;
- an early-payment arrangement that genuinely improves cash flow.
Name the condition and show the original and revised terms. Avoid permanent “special” pricing or a deadline you do not intend to enforce.
When to walk away
Decline when the requested budget cannot cover a responsible version of the work, the client insists on hidden extras, or the terms move unacceptable risk onto you.
A short response is enough:
I cannot deliver the agreed scope responsibly within that budget. The smallest version I can offer is the Core scope at EUR 3,200. If that does not fit, I understand and would rather be clear before either of us commits.
Checklist for the budget conversation
- Have I asked what “too high” refers to?
- Are the compared scopes actually equivalent?
- Can I explain the fee using concrete deliverables and boundaries?
- If I reduce the price, have I shown what changes in return?
- Is the revised scope still useful and deliverable?
- Have I updated the proposal before asking for approval?
The strongest response is usually the most precise one. Clarify the constraint, offer a viable trade-off if one exists, and let the client decide without inventing urgency or reading intent into analytics.
Built for freelancers
Want to send professional proposals in less time?
Try Proposa for free and reuse templates designed to speed up prep and increase approvals.