A customer asks for a feature, and the easy answers are both bad. Saying yes adds something to the product that only one account wanted. Saying nothing teaches the customer that requests disappear.

The useful move is to separate the need from the solution. Customers describe the feature they imagine. Your job is to find the problem underneath it.

Ask what they are trying to finish

Start with the last time the problem occurred. What were they doing, what did they do instead, and what did it cost them? Often the stated feature is a workaround for something simpler.

Decide with a fixed set of questions

Before answering, check four things:

  • Would at least a few other customers benefit, or only this one?
  • Does it fit what the product is for?
  • What does it cost to maintain after it ships?
  • Is there an existing way to get most of the result?

If the answers point to no, say so plainly and give the reason. Customers usually accept a clear boundary more easily than a vague maybe.

Offer something real

A refusal is stronger when it comes with an alternative: a different workflow, an export, a manual step you can help with, or an honest pointer to a tool that does the job better. Do not promise a roadmap slot you are not prepared to defend.

The need is usually negotiable even when the feature is not.

Close the loop

Write the request down with the customer’s reason. When similar requests accumulate, the pattern becomes evidence. One loud request is an anecdote; five quiet ones are a direction.

Should paying a premium change the answer? It can change the conversation, but it should not change the product by accident. If custom work is a service you offer, price and scope it as one.