They Have the Problem: So Why Won't They Give You Feedback?

You send out invitation after invitation, asking potential customers for feedback. Not a single reply.

You need answers before spending another month on the product. Do you change how you reach people, or go back and change the product?

"Could you take a look and give me some feedback?"

A small favor. At least, that's how it sounds when you're asking.

There's work hiding inside "take a look"

A useful answer can mean learning an unfamiliar tool, explaining how they work today, then figuring out what you should change. You're asking them to help shape a product you hope to sell them.

That is a lot to pack into "take a look."

Your product might save them time later. Giving you feedback costs them time now.

Someone can be drowning in admin and still have no appetite for another tool to evaluate. Their problem is urgent. Helping you doesn't automatically join the queue.

From your side, the request makes sense. You want to stop guessing. You want to build something useful. You would rather hear an awkward truth now than spend another month building the wrong thing.

But none of that explains why they should spend their afternoon helping you find the answer.

In Founding Sales, Pete Kazanjy separates winning a conversation from selling a product. That distinction matters even when you're asking for research rather than a sale: the conversation needs a reason of its own.

Give them something worth thinking about.

Suppose you're building a tool for agencies that spend too long chasing client approvals.

You can see how a portal could help. Comments in one place. Less searching through email. A clearer record of what was approved.

So you ask an agency owner to try it and tell you what they think.

To give you a useful answer, they may have to compare it with a live project, think through how their clients would use it, and explain the awkward parts of their current process. Your invitation has handed them a small research project.

Come prepared to discuss a tradeoff instead. Reviews can stay in email, where clients already work, but comments can get scattered. A portal can collect those comments, while giving clients another place to check.

Perhaps keeping approvals in email is a compromise the owner has already thought hard about. Perhaps the scattered comments are exactly what they want to escape. Either way, there is something here to discuss about running the agency.

The owner can consider that tradeoff without first learning your interface. You can bring a view, hear where it falls short, and learn something about the work your product is supposed to help with.

That gives the conversation a use beyond helping you improve your software. The owner has a reason to think it through even if they never buy your tool.

And yes, you still want to learn from them. Say so. Do some of the thinking before asking them to do theirs. You don't need to pretend you have already solved their problem to bring something worth discussing.

Before you build another feature.

A worthwhile discussion doesn't guarantee a reply. People can miss your message or have more pressing things to do. Silence won't tell you why.

But it should make you look at the request before treating it as a verdict on the product.

You can build another feature and return with the same invitation: learn my tool, explain your work, and help me decide what to change. The product has moved forward. The work you're asking them to do may be much the same.

That is why "talk to customers" can be sound advice and still leave you stuck. The advice tells you where learning happens. It doesn't give anyone a reason to join you there.

Your need for answers is real. It isn't their reason to say yes.