I. The $5M Account My Company Marked Dead
I was inheriting a territory at an AWS partner. One of the accounts on the list had a status that made every other rep skip past it. No response in 90 days. Flagged dead.
My colleague had been working it for three months. She is one of the best reps I have ever sat next to. The account had gone quiet on her, and the pipeline tag had quietly become a verdict.
Six weeks after I touched that account, they committed to $5 million. Biggest logo of my career to that point. The lesson cost me weeks to make peace with, because the deal was never the hard part. The dead-lead tag was.
This week I want to break down the research method that turned the longest silence in our CRM into the biggest close of my year, the question I should have asked younger Ivan, and the system you can run on your own pipeline this Tuesday afternoon.
If you’d rather watch this, I turned it into a video:
II. Open Your CRM This Tuesday
Open your CRM. Sort it by “Last Contact Date, oldest first.” Look at the top ten rows.
Most of those accounts are marked something like “no response in 90 days” or “going dark” or “pursue later.” The collective name for them, in your head and in your tooling, is the same. Dead. The list itself is the artifact you need. Most reps will not look at it because looking at it feels like admitting they failed at follow-up. Walking past it feels productive because the next thing on the calendar is a fresh prospecting block where the leads are clean and the inbox is empty.
That walk-past is the most expensive minute of your week. The contacts on that list have already been paid for. Your team spent ad budget, content effort, conference fees, or referral favors to get those names into the database. Then someone got busy, the timing slipped, and the row went silent. The cost of acquisition has already been paid. The cost of walking past that row is the entire deal value sitting inside it.
Before you do anything else this week, copy that list of ten into a separate tab. That tab is what you will rebuild in the next four sections.
III. The Generic Check-In Trap
The default move on a dead-lead list is the generic check-in. Every sales course teaches a version of it. Most CRMs ship with a template that looks something like this:
Hi [name], just checking in to see if anything has changed since we last spoke. Let me know when’s a good time to reconnect. Best, [you].
That message has a 1.4% reply rate in most B2B environments. It does not get answered because it puts the work on the person who has already gone silent. It asks them to dredge up context about you, recall the previous conversation, evaluate their current priorities, and write a thoughtful response. It is a free favor request from a stranger, and the reader owes you nothing.
The deeper problem is that the message contains zero new information. You knew everything in it before you sent it. Your colleague knew everything in it. The reader is not pulled into a new context, given a new reason, or shown that anything has changed on your end. The message itself proves you have not done any work since the last touch. That is what the silence is responding to. The silence is not about the product. The silence is about the absence of a reason to reply.
IV. Three Sentences That Reopen Anything
What I sent the day I went back to that account was three sentences. The math of those three sentences is what unlocked the next six weeks.
Paragraph one: the public signal. I started with something the customer had said publicly that I had read carefully. In my case it was a discussion in their engineering team’s GitHub repo where one of their senior architects had described a constraint they had hit with their current tooling. That constraint mattered. Nobody on my team had referenced it in any prior outreach. By naming it in the first sentence, I proved I had done the work the previous messages had skipped.
Paragraph two: the specific gap. I named the gap in their current stack that the constraint pointed to, and I named it in their language, not mine. I did not say “we can solve this for you.” I said “here is what I think the next six months of this constraint looks like for a team your size.” That sentence is the hardest to write because it requires understanding their roadmap better than they assume an outside vendor would.
Paragraph three: the peer question. I asked them a question a peer would ask, not a question a salesperson would ask. The peer question is the diagnostic version. It assumes the reader has already evaluated the obvious solutions and treats them as someone who has thought about this longer than I have. The salesperson question assumes the reader is naive and needs to be guided to a conclusion. The peer question gets answered. The salesperson question gets ignored.
This is the same shift my parents have been running on hotel guests for thirty years. The bad concierge asks “Is everything okay with your room?” The good concierge says “I noticed you ordered the same espresso the last two mornings, so I had it ready for you at 7.” The first is a generic favor request. The second proves the work has been done. The hospitality move is the same in B2B sales. Prove the work in the first three sentences and the conversation reopens itself.
The customer replied in 18 hours. On the discovery call, two things came out that I could not have predicted from the outside. Their current provider had blockers they could not work around. They were running AWS direct without the partner support they actually needed. Six weeks later, $5M committed.
V. The Weekly Research Rhythm
The research-note method works on one account at a time, but the value compounds when you turn it into a weekly rhythm. Here is the cadence I run on dormant pipeline now.
Day 1, Identify (15 min). Pull the top five “no response in 90 days” accounts from your CRM. Drop them into a spreadsheet with five columns: company, contact name, last touch date, last topic, public signal source. The public signal source is the URL or document where you will dig for the research note.
Day 2, Research (60 min, 12 min per account). For each account, find one specific public artifact: a GitHub issue, a job posting that hints at strategy, a conference talk by someone on the team, a recent blog post about the problem space. Write one sentence describing what the artifact reveals about their priorities. If you cannot find anything in 12 minutes, the account is genuinely dead and you mark it for full archive. That is the audit.
Day 3, Send (45 min). Send five three-sentence research notes following the framework in Section IV. No templates. Each note is hand-built around the artifact. Track replies in the spreadsheet.
Day 4 to 7, Advance. Reply rates on this method run between 35 and 50% in my experience compared to the 1 to 2% on generic check-ins. Every reply gets a 30-minute discovery call slot. Every discovery call gets a follow-up note within 4 hours of ending.
The math: five research notes per week, two replies on average, one becomes a real opportunity, four to six weeks to a commit. Repeat for 12 weeks and your dormant pipeline becomes the highest-converting source you have.
VI. Run It Yourself in 2 Hours and 15 Minutes
Run this on your own pipeline this week. Total time commitment: about 2 hours and 15 minutes spread across three days.
Tuesday afternoon (15 min). The Audit.
Open your CRM. Sort by Last Contact Date oldest first. Pick the top 5. Drop them into a spreadsheet. Note the last topic of conversation for each.
Wednesday morning (60 min). The Research.
For each of the 5, find one public artifact that reveals their current priorities. GitHub, blog, conference, job posting, podcast. Write one sentence per account on what the artifact tells you.
Thursday morning (45 min). The Send.
Write 5 three-sentence research notes. One artifact, one named gap, one peer question. Send them. Log them in the spreadsheet.
Following week (15 min/day, ongoing). The Track.
Read replies. Book discovery calls. Follow up within 4 hours. Track which research artifact pattern produced which reply rate.
If you do this once a week for a month, you will have evidence about what works for your specific pipeline. If you do it once a week for a quarter, you will have a rebuilt CRM where the “no response” tab is no longer a graveyard but a queue.
A new episode every Friday, and this letter is the written version.
VII. Go Find Your $5M
An account is not dead because nobody replied. An account is dead because nobody asked the right question yet. The most expensive sentence in sales is “they’re not interested.” Three months and $5 million almost paid the price. The next time you read it on a CRM row, treat it as a question you have not finished asking, not a verdict you have to accept.
The money you are not making is already in the database you have already paid to build. Go look.
If this issue gave you something to run on this week, forward it to one rep on your team who has a “no response in 90 days” tab they have not opened in a while. That forward is how The Lobby grows.
Humano, hasta la proxima semana.
Welcome to The Lobby.
Ivan
Watch the full episode →