What Should You Do With a Lead That Is Not Ready to Buy?

What should you do with a lead that is not ready to buy?

Find out whether the problem is timing or fit, then treat those two completely differently. A timing objection is a real opportunity with a date on it. A fit objection is a no wearing a polite coat. Most pipelines fail because everyone treats both the same way and calls it nurture.

The difference is worth money. A buyer who cannot start until their next budget cycle needs one thing from you: to still be there, credible and unchanged, when the cycle opens. A buyer who does not have the problem you solve needs nothing from you, and every email you send them costs you attention you could spend elsewhere.

Across six years and seventy plus projects, the single most common pipeline problem I see is not a shortage of leads. It is a folder full of people who said not right now, and nobody knows which of them meant it.

How do you tell not now from not you?

By asking one more question before you let them go. What would have to be true for this to be worth doing? The answer sorts people instantly. Timing answers name an event: a funding round, a contract ending, a hire, a quarter. Fit answers name a condition that will never arrive.

If someone says we would need to be twice the size, that is a fit answer dressed as timing. They are telling you their company is not the company you sell to, and the honest response is to say so warmly and stop.

If someone says we are locked into a contract until March, that is a date. Write it down. That single field is worth more than any lead score, because it tells you exactly when to reappear and gives you a reason that is about them rather than about your quarter.

The answers also teach you something about who you are attracting. If most of your not nows are actually fit problems, the issue is upstream of sales, which is the situation I described in the signs your ideal customer profile is too broad.

Why does your CRM make this worse?

Because most pipeline models offer two endings, won and lost, and this person is neither. So they get marked lost, which is untrue, or left in an open stage forever, which corrupts every forecast you produce. The category is missing, so the data lies.

The fix is a third state with a date attached. Call it whatever you like. What matters is that it is not open pipeline, not a loss, and that it carries the trigger and the date in structured fields rather than in a note somebody wrote at the end of a call.

Notes are where this information goes to die. Six months later nobody reads the note, and the person who wrote it has moved on. A date field can be filtered, and anything that can be filtered can be acted on without anyone remembering to.

Whatever you use, HubSpot, Salesforce, Pipedrive or a table you maintain yourself, the requirement is the same. If your system cannot answer which deferred deals come due this month, it is not helping you with the largest segment of your pipeline.

What should you actually send someone who is waiting?

Things that are useful whether or not they ever buy. Not check ins. A check in asks the recipient to do emotional labour on your behalf and offers them nothing, which is why they go unanswered and why people dread sending them.

The version that works is specific and short: something that changed in their world, something you published that answers a question they raised, an introduction to someone unrelated to your product. Each one is a reason to write that does not require them to reply.

I keep this concrete. When a buyer tells me their constraint, I note the constraint, and when I write something about that exact constraint I send it to them with one line explaining why. That is not a sequence. It is remembering what somebody said, which is rarer than it should be.

The test I apply before sending anything is simple. If they never buy from me, was this still worth their time to open? If the answer is no, it is a check in with better formatting.

How often is too often?

Any cadence you cannot sustain with genuinely useful material is too often. If you have committed to monthly and month four is a newsletter round up nobody asked for, you have trained them to ignore you and you will still be ignored in March when the budget opens.

Quarterly is enough for most deferred deals, with an exception for anything tied to a known date. For those, one contact a few weeks before the date and nothing in between beats a steady drip, because the timing itself carries the relevance.

Volume is the wrong lever here anyway. The thing that determines whether they come back is whether you were useful and whether you were still there, not how many touches a system recorded. Ten thoughtful contacts over a year will outperform fifty automated ones, and they cost less to produce than people assume.

Who should own a lead that has gone quiet?

One person, by name, with the date in their calendar. Handing dormant deals to a shared inbox or a marketing automation is how they become nobody's job. The person who had the original conversation holds context that no sequence can reproduce, and that context is the whole asset.

In a small company that person is the founder, and the answer is to accept it rather than build a system to avoid it. The founder who remembers a constraint from eight months ago and writes one specific sentence about it will reopen deals that no nurture track would have touched.

In a larger team the risk is a handover that loses the thread. If a deferred deal changes owner, the trigger, the date and the constraint have to move with it in writing, or the next contact will read as a cold approach to someone who already spoke to you. That handover discipline is the same one I argued for in who should get a lead the moment it arrives.

When should you close the file for good?

When the trigger passes and nothing happens, twice. One missed date is life. Two missed dates means the constraint they named was not the real one, and continuing to wait is a decision to keep a fiction in your pipeline.

Close it honestly and say so. A short message that says I am going to stop following up, do reach out if this changes, is the most under used sentence in sales. It is respectful, it frees you, and a meaningful number of people reply to it with the real objection, which is information you could not otherwise buy.

Closing the file is also what keeps your forecast usable. A pipeline that only ever grows is not a pipeline, it is a list, and the difference becomes obvious the first time somebody asks you to commit to a number.

What does getting this wrong actually cost?

Two things. The obvious cost is the deals that come due and nobody notices, which is pure waste because the work of winning them was already done. The subtler cost is that your forecast becomes fiction, and you start making hiring and spending decisions against it.

There is a third cost that is easy to miss. Chasing people who were never a fit consumes the exact hours you would otherwise spend on people who are. For a solo consultant or a small team, that is the entire constraint. I price on fixed fees precisely because it forces me to be honest about where my time goes.

And a deal that is genuinely deferred can still die of neglect at the end, which is a different failure from the one at the start. Late stage stalls have their own causes, and I went through those separately in why B2B deals keep stalling at procurement.

What should you do next?

Open your pipeline and find every deal sitting in a stage nobody has touched in sixty days. For each one, answer two questions: is this timing or fit, and if it is timing, what is the date. Anything you cannot answer, you do not have a deal, you have a hope.

Then add the date field, move the fit problems out honestly, and put one calendar reminder against each real trigger. That is an hour of work and it will surface deals you had already written off.

If your pipeline is full of people who said not right now and you cannot tell which of them meant it, that is a solvable problem and usually a fast one. Reach out if you want to talk it through. Let's chat.