Every SE team has a version of the same deal in their pipeline. It started with real energy, strong discovery, a tight POV, a champion who said all the right things. And then, somewhere around month three, it slowed down. Now it's month nine. The deal is still technically open. And nobody is quite sure what happened.
Enterprise deals routinely take two or three times longer than they should. Some of that is structural, budget cycles, procurement processes, security reviews that nobody can speed up. But a significant portion of it is self-inflicted. The deals that drift aren't drifting because of forces outside anyone's control. They're drifting because of a specific set of mistakes that happen early, compound slowly, and become very difficult to reverse.
The anatomy of a stalled deal
The pattern is almost always the same. A deal opens well. The champion is engaged, the technical team is enthusiastic, and the SE does real work connecting the product to a genuine problem. Then comes the POV, which goes fine. Results are positive. Everyone on the customer side says they're impressed.
And then the next step doesn't happen.
The champion goes into a planning cycle. A reorg creates uncertainty about who owns the budget. A competing priority gets elevated. One follow-up email goes unanswered, then another. The SE and AE send check-ins that produce polite responses with no concrete forward motion. Months pass. The deal ages. Everyone is still technically "engaged," but nothing is moving.
What happened is not mysterious, even if it feels that way. The deal lost its urgency, and urgency is not something that sustains itself. It has to be engineered, maintained, and reinforced throughout the sales process. When that work doesn't happen, deals drift by default.
The urgency problem is set up in discovery
Most urgency problems are created before the POV even starts. During discovery, the SE asks about the customer's needs, their environment, their criteria. They don't ask enough about time, specifically, about what creates actual pressure for the customer to make a decision.
There's a meaningful difference between a customer who wants to solve a problem and a customer who needs to solve a problem by a specific date. Both will tell you the problem is real and the interest is genuine. Only one of them has a deal that closes on time.
The questions that reveal this aren't comfortable: What happens if you don't decide by end of quarter? Is there a contract renewal, a migration deadline, or a board commitment that this ties to? What does your leadership expect to see happen with this initiative this year? These questions feel presumptuous in the early warmth of a discovery call. They're necessary. Without the answers, you're flying blind on timeline, and you'll find out the hard way, usually around month five.
Champions degrade over time
Something SEs underestimate: the champion you had on day one is not the same champion you have on day ninety. Internal priorities shift. The pain that drove the initial evaluation gets addressed by a workaround. The champion gets promoted and hands off to someone who wasn't in the room for any of the early conversations. Or they just get tired of shepherding a process that hasn't produced a decision.
Long sales cycles kill champions through attrition. The faster a deal moves, the more likely your champion is still in place, still motivated, and still positioned to advocate internally. Every month of drift is a month in which the deal becomes incrementally more fragile.
This is one of the most underappreciated reasons to compress timelines aggressively. Speed isn't just about efficiency, it's about keeping the humans on the other side engaged and invested before their circumstances change.
The "still evaluating" trap
There is a polite phrase that means a deal is probably dead: we're still evaluating. It sounds like progress. It isn't. "Still evaluating" means no internal advocate has pushed for a decision, no business urgency is demanding one, and the path of least resistance is continued non-commitment.
The deals that say "still evaluating" for more than thirty days are almost never moving through a deliberate process. They're sitting in a queue. The customer hasn't said no, often because no one has asked them to decide, but they're also not moving toward yes.
The SE's job at this point is not to send another check-in email. It's to understand what it would take to get a decision, and then to help create the conditions for that decision to happen. Sometimes that means having a direct conversation about whether the evaluation is still a priority. Sometimes it means connecting back to the business outcome and asking what's changed. Sometimes it means acknowledging honestly that the deal has stalled and asking what would restart it.
What doesn't work is pretending that continued engagement is the same as forward motion.
Forcing functions that actually move deals
The most reliable tool for compressing enterprise timelines is a mutually agreed next step that has consequences. Not "we'll talk next week." A specific action, owned by a named person on the customer side, with a clear output and a date attached.
The second most reliable tool is connecting the evaluation to something the customer is already accountable for. If your champion has a leadership review in six weeks, the POV results need to be ready to present at that review. If there's a contract renewal coming in two months, the procurement process needs to start now. When the timeline is anchored to something external and real, it doesn't require constant renegotiation.
The third tool is the executive sponsor conversation, not to escalate a stalled deal, but to align on the business case before the deal stalls. When a senior leader on the customer side has personally connected the initiative to a business outcome they care about, there is organizational gravity pulling the deal forward. Without that, the champion is pushing a boulder uphill alone.
What the SE controls
A lot of deal velocity is outside the SE's hands. Procurement is procurement. Budget cycles don't move because an SE sent a well-crafted follow-up email. Security reviews take as long as they take.
But the SE shapes more of this than most SEs believe. The quality of the discovery determines whether urgency is understood early. The structure of the POV determines whether there's a concrete forcing function at the end. The success criteria process determines whether the customer owns the outcome or just watches it. The executive alignment determines whether there's gravity behind the deal or just interest.
None of these are things that happen to an SE. They're choices, about how to run discovery, how to structure the evaluation, how to frame success, when to ask hard questions. The deals that close in ninety days and the deals that drag into their ninth month often started from similar places. What separates them is mostly what happened in the first two conversations.
The nine-month problem is not a pipeline problem. It's not a champion problem or a timing problem, though both of those are symptoms. It's a structural problem that gets baked in early, before anyone realizes a deal is in trouble, and that's why fixing it requires changing how SEs approach the very beginning of an opportunity, not how they handle the rescue attempt nine months in.