DEV Community

Dan Liang
Dan Liang

Posted on

Why Aren't Potential Customers Replying to Your Emails?

You've sent ten emails. Maybe more. No replies.

We hear this often when helping founders rethink a business that's stalled.

These people look like a good fit for your product. The company size is right, the work they do matches, and they seem to face the very problem you're trying to solve.

But the messages go out, and nothing comes back.

Send another, and you might become a nuisance. Walk away, and you wonder whether you're giving up too soon. Wait long enough, and even the product you believed in starts to look doubtful. Does anyone actually need it?

The hard part is wanting to change something without knowing what to change.

Hunter's 2026 report analyzed 31 million emails sent by its users in 2025. The average reply rate for initial emails in that sample was about 3%. Ten unanswered emails aren't enough to conclude that something is wrong with the product.

A message can go unseen. An address can be wrong. Bounces and messages sent to the wrong person are worth checking first. But even if the email arrived and they read it, the question remains: they have this problem, so why aren't they responding?

The same problem can mean different work

Say you've built a tool that automatically follows up on overdue invoices for independent consultants. Fewer payment dates to remember. Fewer reminders to write. It sounds useful.

Contacting consultants who've been paid late makes sense.

But "chasing payment" can mean very different things in someone's working day.

One consultant occasionally gets paid late. An email usually sorts it out. It's annoying, but not annoying enough to justify setting up another tool. A spreadsheet, calendar and inbox do the job well enough.

Another can't collect the final payment because the client says the last round of revisions isn't finished. They need to agree on whether the work is complete. An automated reminder can arrive right on time without bringing the money any closer.

A third is short on cash. They need to find whoever can authorize payment and establish whether it will arrive this week. "Spend less time chasing invoices in future" and "Will this money arrive by Friday?" carry very different weight right now.

All three might agree that chasing payment is a pain. The same invoice tool would be useful to them in very different ways, if at all.

This is where the mismatch can begin. We describe their need as "late payment." They are dealing with forgotten invoices, disputed work or a payment waiting for approval.

We haven't invented the need. We've treated several different problems as one.

Even knowing that someone is under pressure doesn't close that gap. Urgency can push someone to look for a new approach. It can also leave them with no room to evaluate one while they deal with the immediate problem. What matters is which piece of work we can actually help move forward.

So an unanswered email may have more behind it than unconvincing copy. The recipient may not see how this conversation connects to what they're trying to get done.

What can the next email say?

If all we know is that they're an independent consultant, we don't yet know which payment, if any, they're worried about. We can keep exploring. The next conversation could be about where payments tend to get stuck, without assuming that automated reminders are what they need most.

If they've recently written publicly about checking invoices one by one and sending reminders every month, we have a specific use for automation to discuss. The next message can pick up that piece of work without introducing the whole product again.

If we've already spoken, they asked for a proposal and we agreed to talk on Friday, silence on Monday is different again. We can follow up on that agreement. They may have missed the message, or their plans may have changed. A reminder can serve a purpose without a new feature or discovery attached.

We don't know who will reply in any of these situations. But what we already know does change what the next message can reasonably say.

And having something relevant to say still doesn't guarantee an answer. A clear no means we stop. Repeated silence, with nothing specific left to pursue, can be a reason to put our time into other conversations. A reply or a change in circumstances can give us a reason to return.

Putting one conversation aside doesn't require us to write off the product.

We've spent a lot of time building something. Of course we want people with the problem to hear us out. That urgency is understandable.

But they may be trying to collect a disputed final payment while we keep explaining how to send fewer reminder emails. Both sides are taking their work seriously. We just haven't found the same thing to talk about yet.

Before sending another email, I'd want to understand where that payment is stuck.

Top comments (0)