How Many Times Should You Follow Up With a Prospect? My Answer: Once.

There's a strange conviction in sales that persistence is a virtue in itself.

Send the message. Follow up. Follow up again. Bump it. Try a new angle. Ask a different question. Keep touching the prospect, because the playbook says a deal takes X touches and you're only on touch four.

I want to offer a different reading of an unanswered message:

The person doesn't want to talk to you right now. And that's okay.

The fifth "just bumping this"

You know the experience. You open LinkedIn and there's a pitch in your inbox.

The first message is fine. Someone has something to sell, you run a business, that's commerce. No problem.

Then the follow-up. Still fair — messages get missed, people get busy.

Then another. And another.

"Just bumping this up."

"Wanted to make sure you saw this."

"Circling back."

"Thought I'd try you one more time."

At some point you realize you're not in a conversation. You're watching someone run a sales sequence at you.

I had one recently: three messages, three separate discovery questions, zero replies from me. And it struck me that the salesperson wasn't having a conversation with me anymore.

He was having a conversation with himself.

To be clear, I don't blame the guy. He was doing exactly what he'd been trained to do. The target here isn't the person sending the fifth message — it's the philosophy that taught him the fifth message was a good idea.

Silence is information

My rule is getting simpler the longer I run this business: one outreach, one reasonable follow-up, then leave people alone.

If someone tells me to circle back next month, that's different — they invited it. But absent that, silence is information. It might mean no. It might mean not now. It might mean you didn't catch them at the right time, or your message wasn't compelling enough, or they fully intend to reply and haven't gotten to it.

None of those readings entitles me to keep demanding someone's attention until they surrender it. The prospect knows where to find me. If what I offered was worth it, the door's open.

The counterargument, which I'll grant

Salespeople will point to the data: more touches, more responses. They're probably right. I'll likely lose some business by refusing to chase people as hard as conventional wisdom says I should.

I'm comfortable with that — because the number of people who eventually say yes isn't the only thing I'm optimizing for.

I want clients who want to work with OpsStack. Not someone nudged into a meeting they didn't really want, maneuvered into an uncomfortable call, or talked into starting before they were ready. That's not just a sales preference. It's a brand decision.

"Comfortable to work with" is a real principle

One of the things I want to separate OpsStack from the pack is deceptively plain: we're comfortable to work with.

That doesn't mean passive, and it doesn't mean I won't challenge a client — an operations consultant regularly has to tell people things they'd rather not hear. Comfortable means something else. It means you don't have to manage me. You don't have to dodge me. You don't have to decode my motives or wonder whether every conversation is a setup for the next upsell. And you don't have to say no five different ways before I respect it.

I can make a recommendation, tell you exactly why I believe in it, and still treat the decision as yours. That relationship should start before you're ever a client — because how I sell is a preview of how I work.

Your sales process is part of your brand

Companies pour enormous effort into defining their brand. Values, voice, visual identity, customer experience. Then they hand the first contact with a prospect to a process built on a completely different philosophy — and suddenly someone's first six impressions of the company are automated messages from a rep who won't go away.

That's branding too. For someone who's never worked with you, it might be the only real evidence of your brand they ever get.

If OpsStack ever has employees, contractors, agencies, or automated systems reaching out on its behalf, the same standard holds: nobody gets to make a person uncomfortable in this company's name because a dashboard suggested four more touches might lift conversion.

Where the line is

I'm not arguing follow-up is wrong. One good follow-up is enthusiasm, and enthusiasm is fine. I'm arguing there's a point where persistence stops signaling "I think I can help you" and starts signaling "my desire to close matters more than your desire to be left alone."

I don't want OpsStack on that side of the line.

The whole philosophy condenses to one sentence: I don't pressure people into working with OpsStack — I try to make it easy for the right people to choose it.

Maybe aggressive persistence would book me more calls. I'll accept that trade. Because there's a metric I care about more: when a client signs on, I want to know they're there because they believe I can actually help — not because they got worn down. They chose it.

I'll take that relationship over a better response rate every time.

---

No hard sell here — that would rather miss the point. If you ever want to talk through what's going sideways in your operation, you know where to find me.