The customer says it is too expensive. Compared with what?

You present the proposal and explain what is included. The reply is: “That is a little expensive.” You have put work into it and believe the price is fair. The instinct may be to explain the quality again or offer a discount before the conversation ends.

But that sentence does not tell you enough yet. The client may have a smaller budget. They may be comparing a different offer. Maybe they understand the price but do not see why they should invest now. Or they may simply prefer another solution.

A price objection is a point of clarification. The right answer depends on what you find.

Same words, different questions

In a real conversation, several reasons may exist at the same time. The table below is a discussion tool, not a psychological classification of the person.

You do not need to ask every question. Start with one and listen. If the person does not want to continue, respect that answer.

Two offers for the same website

Suppose a client compares two fictional proposals for a brochure website. Option A costs EUR 3,000 and option B EUR 5,000. All amounts exclude VAT; the comparison does not represent NOT MORE. prices.

Option A includes a template-based design, implementation and uploading supplied content. The client prepares the copy, structure and assets. Option B also includes organizing the information, writing the copy and checking the inquiry journey. Neither automatically includes new photography, ongoing maintenance or paid traffic.

For this demonstration, we assume both options can meet the final requirements once the missing activities are covered. The price difference buys specific activities and responsibilities. It does not, on its own, prove a better commercial result.

How to compare time without inventing savings

The client might assign an indicative value of EUR 50 to an internal working hour. In our example, the 30 hours represent EUR 1,500 as a value of time; the 12 hours represent EUR 600.

So the price plus the assumed value of time is EUR 4,500 for A and EUR 5,600 for B. The difference shrinks from EUR 2,000 to EUR 1,100, but option B remains more expensive in this scenario.

The 18 hours freed up do not automatically become revenue. Their value depends on what the client can actually do with them. If the team has the time and skills, A may be the right choice. If the work needs external coordination, B may fit better.

Do not arbitrarily add rework costs to the cheaper proposal. An estimate needs a concrete reason and an explicit assumption. Otherwise, the comparison simply favors the option we want to sell.

What marketing can clarify before the price conversation

A page can explain what is included, who it suits and what the collaboration involves. Demonstrations make differences visible. Clear terms help people compare before completing a form.

“Premium website” says little. “Structure, copy and implementation for the eight agreed pages, including form checks and access handover” gives the client something to assess. Describe the actual deliverable and its limits.

Google and The Behavioural Architects’ 2020 research describes people moving between exploration and evaluation before purchasing. That gives us a reason to make comparison information accessible. It does not establish a phrase that will persuade every customer. Google: research on purchase decisions

How might that conversation sound?

In a fictional example, a customer says: “Another proposal is EUR 3,000. Yours is EUR 5,000.” A useful reply might be: “Let’s compare what is included. We also provide the structure and copy. If you already have those ready, we can work out what is still needed.”

You have explained the difference and opened the possibility of a meaningful adjustment. You have neither promised a discount before understanding the project nor assumed the alternative is inadequate.

If EUR 3,000 is the maximum budget, the question becomes what can responsibly be delivered within it. Perhaps fewer pages, or copy supplied by the customer. Perhaps the requested project is not feasible. Those conclusions are more useful than a reduced price attached to promises that cannot be kept.

The offer has to be explainable beyond the first conversation

The person you are talking to may need to present the proposal to a partner, a manager or the team that will work on the project. If the explanation of value exists only in your conversation with them, it can get lost when the document reaches the others.

A usable proposal lets them identify which problem it addresses, which deliverables it includes, what contributions it requires and how each stage will be checked. Where there are options, we show what changes between them. If monitoring or later support is contracted separately, we say so next to the relevant components.

In the website example, the difference between the options can be explained by who prepares the structure, who writes the copy and who checks the form’s journey. “More strategy” or “better design” does not say, on its own, what responsibility is being taken on. An anonymized example of a deliverable, when it can be shown, makes the discussion more concrete.

Clarity does not guarantee that the proposal will be accepted. It does give the client a better basis for comparison and helps us identify which component needs to be discussed.

When the difference is understood but not needed

A client may fully understand the advantages of an option and decide they do not need them right now. They may already have an in-house specialist, a clear enough strategy or materials prepared by another partner. In that case, we check which contribution is still missing and build the offer around it.

For consulting or strategy contracted separately, we clarify what the team carrying the project forward will receive. For execution, we agree on the brief, the dependencies and the acceptance criteria. For a broader collaboration, we define the stages and the decisions about continuing. That way, the price describes the work and responsibilities taken on in the specific case.

The timeline matters too. If urgency requires reorganizing resources and involves an extra cost, we explain that condition before the work is accepted. We do not present every request as urgent, and we do not use an artificial deadline to rush a decision.

When the budget cannot support a responsible delivery, we can discuss a smaller but useful stage or a different time. Explaining the value does not cancel the budget limit or the client’s right to choose another solution.

How we approach this discussion at NOT MORE.

We explain the problem each part of the proposal addresses, what the client receives and what we need from their team. If budget and scope do not align, we discuss priorities and the implications of a smaller project.

We can demonstrate our process and explain how delivery will be checked. For outcomes that also depend on the offer, market or sales team, we state assumptions and responsibilities. A client should be able to discuss price without feeling judged for their budget.

What is worth checking in your offer

• Can a client explain what they receive and what remains their responsibility?
• Are price differences supported by visible components or evidence?
• Do you know whether conversations stall because of budget, timing or missing information?

Do you often hear “it is too expensive”?

We’ll start with your offer and the questions that come up in sales conversations, and see what needs explaining more clearly and whether the presentation reflects what you deliver. You can give an anonymous example; you don’t need to prepare a full analysis before the first discussion.