Every founder I know has felt the pull. A prospect is interested. The budget exists. Someone on your team says "we could have ink this week if we push." So you push. You compress the demo. You skip the pilot. You paper over the question marks with confidence.
Sometimes it works. Often it produces a customer who churns at month four because nobody paused long enough to check fit.
This post is about a deal where we did the opposite. We deliberately slowed down. The result was a larger contract, a customer who stayed, and a reference that opened three doors we hadn't knocked on.
A mid-market company came inbound. They had a clear pain, a clear budget, and a deadline. Everything pointed toward a fast close. Our sales instinct was to match their urgency — get an agreement signed before the quarter ended.
But during the first technical call, something felt off. Their requirements were real, but their assumptions about their own readiness were optimistic. They described an integration path that would have taken twice as long as they expected. If we had signed them that week, the first ninety days would have been frustration on both sides.
So we said something founders hate saying: "You're not ready yet. Here's what we think you need to do first."
We proposed three changes to the sales process:
A design review. Before signing anything, we spent a session mapping their existing architecture against what they actually needed. This surfaced two gaps they hadn't identified. It cost us a week.
A scoped pilot. Instead of a full deployment, we suggested they run a narrow pilot against one workload. This added three weeks to the timeline.
An honest conversation about scope. We told them that two of the five things they wanted to buy from us were things they could do themselves, cheaper. We recommended they not buy those from us.
Each of these steps made the deal take longer. Each of them also made the deal more real.
The design review changed their requirements. Not dramatically — but enough. They realized one of their assumptions about data residency was wrong. Catching that before signing meant we never had to renegotiate scope mid-contract. Anyone who has renegotiated scope mid-contract knows that conversation erodes trust at exactly the moment you need it most.
The pilot did what pilots do: it gave their engineering team direct experience with the product. When the internal champion went to their CFO for final approval, she wasn't presenting a vendor pitch. She was presenting her team's own results. That is a different conversation.
The honest scope reduction — telling them to keep two capabilities in-house — did something counterintuitive. It made the remaining three line items easier to approve. When a vendor says "don't buy this from us," the buyer starts trusting the things the vendor does recommend. The final contract value was higher than our original quote, because they added a workload we hadn't proposed. They added it because they trusted our judgment enough to expand scope on their own terms.
Six months in, the customer was healthy. Not perfect — no customer relationship is — but genuinely productive. When we asked if they'd take a reference call, they didn't hesitate.
That single reference opened conversations with three companies in adjacent industries. Two became customers. The third didn't — but they told us exactly why, which was its own kind of value.
Here is the math that founders miss when they optimize for closing speed: one high-trust reference is worth more than three lukewarm ones. Prospects can hear the difference on a call. A customer who says "they told us we weren't ready and helped us get ready" is more persuasive than a customer who says "implementation was fine."
I won't pretend this approach has no cost. Slowing down a sales cycle ties up your team. It delays revenue. It requires you to trust that the deal will actually close after you've introduced friction. Sometimes it won't. We have slowed deals down and lost them. That is the risk.
The question is whether the alternative risk is worse. A customer who signs before they're ready will consume disproportionate support hours, churn before renewal, and never become a reference. That outcome costs more than a lost deal. It just costs you later, so it's easier to ignore.
The lesson was not "slow is always better." It was narrower and more useful: the speed of a sales cycle should be set by the customer's readiness, not by your revenue calendar.
When a prospect is genuinely ready — architecture understood, internal alignment in place, use case validated — close fast. Speed is appropriate when it matches reality.
When a prospect is excited but unready, the best thing you can do is name the gap. Add the design review. Run the pilot. Tell them what not to buy. These moves feel like anti-selling. They are actually the highest-leverage selling you can do, because they build the kind of trust that compounds.
Trust compounds faster when you stop optimizing for speed. And compounding is the only game worth playing.
Be the first to comment.
0 comments
Loading comments...