Welcome to issue 99! Did someone forward this to you? If so, Subscribe here!
⚡ Today’s Skill In A Sentence ⚡
Before you follow up on a deal, make sure you know why they’d want to hear from you.
Today’s Skill: Ghosting Is A Discovery Problem
For eight years I sold permitting software to building and planning departments at local and state governments.
Of the thousands of potential client calls I had, one city in northeast Illinois still sticks with me. A couple of great calls, a really solid demo, and tons of alignment.
I was very confident that I knew what they were trying to accomplish and that we could definitely help them achieve those goals.
At the end they told me they were putting together an evaluation matrix and would get back to me in a few weeks.
I followed up two or three times. I’m not one to pepper people, and I can take a hint.
After those attempts, I never heard back.
Five months later I was curious if they ever did anything and happened to come across their council meeting minutes.
They had picked another vendor, and they had filled in our part of the matrix themselves.
Here’s what bothered me the most. A few features were marked as things we didn’t do, but not only did we offer those, I know for an absolute fact we showed them in the demo.
Nobody ever sent me the matrix and asked, “Brian, here are the 10 items we’re scoring on. Did we miss anything?”
Reading it, the matrix almost seemed written for the vendor they picked.
So not only did we lose out on $90k, we lost out on working with a growing city who I knew could benefit from the partnership.
It stung that they never told me they’d gone in another direction.
But that one’s on me.
→ What I should have done instead was offered to help them build the matrix.
Since they did this behind the scenes, I couldn’t offer my perspective from my experience doing this for several years.
→ At worst, I should have locked in a meeting on the calendar to go over their matrix once it was completed. This would’ve given me an opportunity to make sure our section was filled out properly and I could ask any additional questions about their process.
I could have done both. But, I got “happy ears” and took them for their word when they said, “we’ll get back to you in a few weeks.”
That, of course, never happened.
Why do you think you got ghosted
When a founder tells me a deal ghosted them, that’s my first question…”Why do you think you got ghosted?”
I want to hear whether they think it’s on them or on the buyer.
Usually it’s, “Well, they said they’d get back to me and they never did.”
So I keep asking.
When did they say it?
How did they say it?
What did that sound like?
This is why I tell everyone to record their calls. What founders think was said and what was actually said are two different things.
I hear “we covered all that” constantly. Then I listen back, and they asked a couple of questions and never dug into why it matters to the buyer.
On a good call the excitement is always there, especially when the idea is new and the buyer gets to talk about their own problems.
Then the call ends. The buyer is back at their desk working through their day, asking themselves, “Is this really a priority?” and “Do I really want to do this?”
→ That’s if they liked it.
There are many times they didn’t jam well on the call but said a polite “Let me look at things further and get back to you.”
Your ghosting problem
…is really a discovery problem.
They may not get back to you because:
They’re not interested
They’re interested but busy
They’re interested but it’s not a priority
They’re interested but waiting on others to chime in.
So we call it ghosting, but we don’t actually know which one it is.
But if we’d understood their situation, priorities and problems on the last call, we could’ve proposed another call right then to keep it moving.
And, at worst, if they push back on that and say “We’ll get back to you”, you could try to clarify when or what they need to discuss before they do.
Those “circling back” and “just following up” emails only happen when we didn’t set up where things stand and where they’re going while we had them on the call.
So remove the ambiguity on the call, and it’ll save you a lot of headaches later.
Before you hang up
The best follow-up is one already scheduled on the calendar or clearly laid out with mutual next steps.
On every discovery call and demo, do four things before the call ends.
Uncover one to three massive, specific problems that they’ve called out and the impact it’s having on their business.
Confirm the priority. Is solving this urgent in the next month, three months, six months or longer? (And why is it urgent!)
Know where this is going. Propose a clear next step before you hang up, and know why that step exists.
Send a control email with their problems, action items and the next step you agreed on.
ICYMI: Issue #54 goes deeper on getting clear on the problem, the reason to change and the decision process → Read Issue #54
Final Thoughts
Most of the time, the silence you’re getting through email was something already decided on your prior call.
When you know what matters to the buyer, your follow-up is about solving their problem. You’re no longer chasing their attention.
Get real good at understanding what they need solved, when they need it solved and why they need it solved.
You do that, buyers who ghost you start to go away pretty fast.
Your Action Item
Pick one deal that hasn’t gotten back to you.
Before you follow up, write down the problem they told you, in their words, and whether they said it was a priority.
If you can, make that the whole follow-up. Short and to the point.
If you can’t, you’ll have that top of mind the next time you get on a call.
Reply and tell me what you found. I read every one.
Need more help with sales?
Let’s explore your options on a call.
Find a time that’s convenient for you here.

That’s all for today! If you wanted to say hello, reply to this email or catch me over on Linkedin
The best way you can support me is by passing this newsletter to a fellow founder or shout it from the rooftops on your socials!
until next week!
just get started,
Brian


