One client asked for it. Does the market want it?

A request is not a market

One client’s need is real, but it is shaped by that client’s history, systems, people and quirks. What looks like a general problem may be a very local one. Build a product around it and you may find that the next ten clients don’t have the same problem, or have it in a different form, or simply solve it another way. The feature that felt like market demand becomes a custom project that everyone else has to carry.

Check that the problem repeats

Before anything becomes a product, I look for the same problem elsewhere. I talk to other clients, look at support requests, check how competitors approach it and ask the sales team whether it comes up in conversations. The question is not whether other clients would like the feature. People always like features. The question is whether they experience the same problem, often enough and painfully enough to change how they work.

Serve the client, protect the product

None of this means turning the client away. Their need can still be met, as a configuration, an integration or a clearly separated custom module. What it means is keeping the core product clean until the evidence is there. If the problem turns out to be common, the custom solution becomes a tested prototype for the general one. If it doesn’t, the product hasn’t been bent out of shape for a single customer.

Patience pays

It takes some nerve to slow down when a large client is excited and money is on the table. But products built on one voice tend to serve that voice and nobody else. Products built on a problem that repeats across many clients are the ones that grow, and the extra few weeks of checking are the cheapest insurance a product team can buy.