Why Prospects Say 'Not Now' (And It Doesn't Mean No)
- Cormac Repman
- 4 days ago
- 3 min read
I was on a call last week with a founder who'd been saying "not now" for six months. When we finally dug into what was actually happening, the answer surprised me: they weren't uninterested. They were underwater.
Their business had hit a revenue plateau. They'd increased spending to scale, but the operation couldn't keep up. New hires were making mistakes. Systems were breaking. Instead of growth, they were firefighting. When I brought up our solution, their answer wasn't "we don't need this." It was "we can't onboard this right now." Two very different things.
This is the real story behind most "not now" objections, and it's nothing like what sales training teaches you.
The traditional wisdom says timing objections are brush-offs. They're not. They're signals that the prospect is dealing with an internal sequencing problem. They're rebuilding infrastructure. They're fixing broken conversion rates. They're recovering from a failed implementation of something else. Or they're in a hiring cycle, a system migration, or a post-merger integration. All of this is real work, and it comes before they can afford to think about anything new.
I watched this pattern repeat across different conversations. One prospect was mid-platform migration. Another was retraining their team after losing key people. A third had just realized their product-market fit was weaker than they thought, and they were pivoting their entire GTM. None of them said "we're not interested." All of them said "call us in Q4" or "let's revisit in a few months."
The reason this matters is that most salespeople respond to "not now" by either accepting it at face value or pushing harder. Both strategies miss the real opportunity.
If you accept "not now" literally, you assume they've genuinely deprioritized you. They haven't. They've temporarily deprioritized their own forward progress. There's a difference.
If you push harder, you're selling into someone who can't buy right now. You're adding noise to someone already drowning in work. You'll either burn the relationship or trap yourself in an endless loop of follow-ups that go nowhere.
What actually works is treating "not now" as a data point about their internal state, then re-engaging strategically after the stability window closes.
Here's how I do this: When I hear "not now," I ask one follow-up question: "What's the priority that's taking your bandwidth right now?" Usually they'll tell you. They're honest about it, because they're under stress. Now you know what problem they're actually solving. You know when they'll finish. You know what their mental state will be on the other side.
Then you vanish. Not forever. You set a calendar reminder for two weeks after their stated window closes. When you re-engage, you don't pitch. You reference what they told you. "I know you were in the middle of the platform migration. How'd that go?" Now you're not a vendor interrupting their chaos. You're someone checking in after a milestone.
At that point, one of two things happens. Either they're still in the fire and they ask for more time, which is fine. You've just built trust by respecting the boundary. Or they've emerged, their plate has space, and they remember you as the person who actually understood what they were dealing with. That's the moment they're ready to move.
I've had prospects move from "not now" to contract in two follow-up cycles using this approach. I've also had people ask me directly to reach back out, because the first re-engagement proved I was different from every other vendor hitting them while they were drowning.
The lesson is simple: "not now" isn't rejection. It's just bad timing. And bad timing becomes good timing when you know what you're actually waiting for.
Comments