When Clients Ask for the Wrong Thing

Imagine an ordinary chat. A business owner writes: “I need a new website.” You name a price, promise a timeline, collect materials, and honestly build the website. After launch, they look at it and say: “I thought I would get more enquiries.” No one seems to have lied. The client ordered pages but hoped for more enquiries.

In stories like this, the problem is often not the quality of the work. The process itself is broken: it obediently races to the finish line even though no one checked whether this was the right stop. The client names a familiar solution, and the provider treats it as a complete task definition.

You do not need to guess hidden motives, become a psychologist, or persuade someone to buy something more expensive. You need to slow the conversation down a little before making an offer: understand the situation, the desired change, and the limits of the choice. Then the client remains the author of the decision, and you stop selling at random.

When someone asks for a specific product or service, they usually describe their task through something they have already seen, heard about, or tried. That is a normal starting point. A cafe owner may have seen a competitor’s ads and ask you to “set up advertising.” A craft maker may hear advice about having a website and ask for exactly that. They are not required to know every option - that is your professional part of the conversation.

At the same time, a specific name does not answer the more important questions: what is not working now, what needs to become different, and what the client is not willing to sacrifice. Without this, you may complete the order literally and leave the main headache exactly where it was.

The real task is not necessarily hidden or complicated. It often sounds very human: “I want less chaos in bookings,” “I need enquiries for this specific service,” “I do not want people to confuse the prices,” “I need to explain the offer to partners.” Once you have a phrase like that, you can discuss options.

GOV.UK’s discovery guidance recommends examining a predefined solution, reframing it as a problem, agreeing what falls outside that problem, and investigating constraints before building. It also allows for simpler alternatives, including better information instead of a new service. This is guidance for government service design. The conversation prompts, scripts and two-option offers below are GrandMa editorial methods; the guidance does not prove that they increase enquiries or sales. The examples of Olena and Serhii are hypothetical illustrations, not reported client results.

From a service to a way of working

For example, Olena sells custom cakes and asks for an online store. If you immediately talk only about a catalogue, basket, and payment, you may miss something important: most of her orders are individual, clients first send photos, and the production calendar has limits. She may need not a conventional store, but a clear page with examples, a form for order details, and rules for booking a date. This is not a “better” option by itself. It may be more suitable specifically when the goal is to collect clear custom enquiries rather than sell ready-made items from stock. An online store can also support custom orders if that workflow is included in its scope. Compare what the proposed options actually include and require, rather than assuming that the label “store” determines how orders must work.

Do not replace the request with your own assumption. Say: “You are asking for a store. I want to understand how orders work for you now, so I do not suggest something unnecessary.” This acknowledges the client’s logic and invites them to clarify.

If you notice recurring questions about your business, write down not only the names of services but also how people describe their problems. Over time, these can grow into clearer offers and materials: content marketing can explain a client’s situation before the first call.

You do not need to turn the first conversation into an interrogation. These three questions in ordinary language are our editorial starting point, not a validated questionnaire or a rule that three answers are enough for every project. Their goal is not to collect every detail in the world, but to avoid quoting for something the person did not actually choose. Before a fixed quote, also clarify the deliverables, dependencies and unresolved questions that could change the work.

First: “What needs to change after this?” It moves the conversation from the thing itself to the outcome. If the answer is vague, help with an example without pushing: “Is it more important for you to get more enquiries, explain less over the phone, or have a clear order inside the team?” Then repeat the answer in your own words: “So you want people to understand which service to choose before they contact you.” This lets the client correct you before you begin suggesting anything.

Second: “What have you already tried, and what did not work about it?” This question protects you from repeating an unsuccessful attempt in new packaging. Maybe advertising brought the wrong people. Maybe the previous page was clear, but it did not contain current terms. Or perhaps the solution was fine, but no one on the team had time to use it. Do not look for someone to blame. Clarify the sequence: what they did, where they stopped, and what exactly disappointed them.

When you need to choose a priority

Third: “What matters more to you if you have to choose?” This question is about a trade-off - a conscious choice between two desirable things that you cannot always get at the same time. For example, a client may care more about launching quickly than adding every possible feature. Or preserving personal communication may matter more than removing all manual work. Do not invent the trade-off for them: suggest the ones you genuinely see in this situation and ask whether they are relevant.

Serhii asks you to “make nice posts” because sales of corporate gifts are uneven. After a conversation, it turns out that he does not lack ideas for posts. He repeatedly explains to company managers which sets fit different budgets and when they need to place an order. Then, instead of an abstract package of posts, you can discuss a series of materials with examples of sets and clear ordering terms. But first check whether this is really what gets in the way, whether Serhii has materials that can be shown, and whether he is ready to confirm the information. If not, it is more honest not to promise that content will solve the issue by itself.

These three answers form a short brief - a simple record of the situation, the outcome, and the limits of the work. A brief does not have to be a large document. At this stage, you need the client’s words, not polished guesses of your own.

Keep a distinction between what the client reports and what you have checked. A business owner can explain their workload, but their account alone does not establish what customers find difficult. GOV.UK’s guidance on learning about user needs recommends reviewing existing evidence, interviewing or observing actual or likely users, and treating opinions that do not come from users as assumptions to investigate. For this conversation, ask to walk through a recent enquiry or order: where did clarification become necessary, and what information was missing? Compare that account with available enquiries and, where needed, ask customers to explain or try the current process. Record any unanswered question instead of turning it into a confident diagnosis.

An unpleasant mistake is answering a specific request with: “You do not need this.” Even if you are right, the person may hear that their experience has been dismissed. They may become defensive or agree with distrust. Neither response helps make the work clear.

It is better to move in three steps. First, confirm: “Yes, a website can be one of the options.” Then show the connection to what you heard: “But you said the key thing is getting enquiries for custom cakes, not selling ready-made items.” Only then explain the difference: “That is why I would consider a page with an enquiry form and a calendar of available dates rather than a large catalogue. It fits how you work now better.”

You do not take away choice when you name limits. You bring it back into the conversation. If the new option has an inconvenience, say so directly: “With this solution, some orders will still need to be confirmed manually.” This matters more than trying to look flawless.

An offer with two clear options can make the comparison easier, but the number of options does not guarantee that someone feels no pressure. Each option should honestly explain which situation it suits.

Do not create an artificial “cheap bad” option to push someone toward a more expensive one. Each option should also honestly describe what it solves, what it does not do, and what it requires from the client. It is important that both options remain real, rather than becoming scenery for an answer chosen in advance.

For example: “We can build a catalogue with payment if you want to sell standardised sets without extra confirmation. Or we can make a page with set selection and an enquiry form if orders often change. In the second option, you keep control over the details, but you answer every enquiry manually.” This is not a presentation for the sake of a presentation. It is a way to give the person a clear decision criterion: what matters more right now.

When clients’ real needs repeat, it is worth reflecting them on the website too. Pages about websites and e-commerce should help a visitor recognise their situation, not only list your tools.

Sometimes, after all the explanations, the client still wants exactly what they came for. That does not mean the conversation was pointless. You have already checked understanding, named the consequences, and did not pretend that no other path exists.

Say calmly: “We can go with the catalogue. I only want to note that it will not solve manual approval of custom orders without a separate process.” Do not scare them, argue, or punish the “wrong” choice with an inflated price. Leave the choice with the client if they understand the limits.

Another situation is when you are asked to do something you are not ready to take responsibility for or that conflicts with your rules. Then an honest refusal is better than silent agreement. Briefly explain what exactly you do not take on, and, if appropriate, offer a safer format. You do not need to prove that the client is wrong. It is enough to define your boundary.

Before starting, send the client a short written confirmation. Do not hide it in a long email after the estimate. Write separately what you chose, why you are doing it, what limits the solution has, and who gave approval - explicit confirmation that the client accepted this specific option.

The text can sound like this: “Please confirm: we are making a page for custom cake orders. Its task is to collect enquiry details and show available dates. We are not adding payment to this version because the final price depends on the decoration. You will provide current examples of your work and the terms. Does this match the option you want us to proceed with?” This shows not only the list of work, but also the reason for the decision and the proposed trade-off. Sending the summary does not itself establish approval: record the client’s explicit reply, who can confirm the decision, and any outstanding dependencies. In this example, also agree who updates the available dates and make clear that an enquiry does not reserve a date until Olena confirms it.

A hypothetical check of the result

Continue Olena’s hypothetical example. Suppose that, among 20 recent enquiries, 12 required a follow-up just to learn the requested date or number of servings. These numbers are invented for illustration. The working hypothesis is that asking for those details clearly will reduce this particular clarification work. Before building more, let likely customers try a draft form and check whether they understand what to enter. If they cannot yet name a date or quantity, find out why rather than forcing an inaccurate answer.

Agree separately how to check delivery and the desired change. For delivery, test that the form passes the entered details to Olena and explains the confirmation process. For the outcome, Olena could review the next 20 enquiries from the page and count how many still need those same basic clarifications; also check for signs that people cannot complete the form. Twenty is only this example’s review point, not a research standard. GOV.UK’s discovery guidance recommends deciding what performance data to collect and how to measure success. A small before-and-after comparison can guide the next revision, but it does not prove that the page caused a change: the types of orders, traffic and season may differ. It also says nothing by itself about increased sales.

If the main task changes during the process, do not disguise the change as a small edit. Return to the three questions and agree on the direction again. Usually, this is the moment when you can see whether only the details changed or the client is already asking for a different outcome.

The first step is simple: in your next conversation, ask “What needs to change for you after this solution?” before committing to a fixed price for an unclear request. Then wait for the answer. If the client needs an early budget range, you can give a provisional estimate with its assumptions and explain what still needs checking before you confirm the scope and price.