Nine Reasons Reps Give for a Slipped Deal, Ranked From Plausible to Career-Limiting

"Procurement is slow" is the sentence I hear more than any other when a deal slips a quarter. It's also the one managers wave through fastest, because it sounds like weather — nobody's fault, nothing to be done, wait it out. Most of the time it isn't weather. It's the tell that the rep never found out who signs, when, or what has to happen before they will. Reps don't lie about slipped deals, usually. They give you a compressed cover story, and if you know how to read it, every one of the nine you'll hear this quarter points at a specific competency that wasn't in the room when it mattered. Ranked below from "sometimes genuinely true" to "there's no reading of this that isn't a qualification failure."

What "ranked" means here

I'm not ranking these by how often reps say them. I'm ranking by how much of the excuse is real versus how much is a polished stand-in for one nameable gap: a stakeholder never identified, a criterion never confirmed, a question never asked. The excuses near the top are sometimes exactly what they say on the tin. The ones near the bottom never are — by the time a rep reaches for excuse nine, they've told you, without meaning to, that they don't actually know why the deal isn't moving.

The nine

1. "Procurement is slow." Sometimes true — some organisations run an eight-week vendor onboarding process and there's genuinely nothing to be done about week six. But ask two questions: who is the procurement contact, and what date did procurement themselves commit to. A shrug means the deal was never actually in procurement — the rep just stopped hearing back and reached for the nearest respectable-sounding cover. The gap is decision-process mapping, and it should have happened in month one, not been discovered in month three.

1. "Legal's redlining the contract." Also sometimes literally true. The tell is timing: if legal picked up the paper before the economic buyer had confirmed value and budget, the rep sent the deal to contract on hope, not evidence. Redlines that drag for weeks are usually a symptom of a deal that went to paper early because the rep wanted a milestone to report, not because the buying process actually called for it.

1. "A new stakeholder joined and wants to restart discovery." Almost always true and almost always avoidable. It means the rep built the case with one person and never asked who else touches the decision. A properly multi-threaded deal survives a personnel change because three other people already know the story. A single-threaded one resets to zero the moment your one contact goes on leave, changes roles, or gets outranked.

1. "Budget got reallocated." Sounds like bad luck at head office. Usually means the rep never had a real conversation with whoever actually owns the budget line — they had a conversation with someone who wanted the thing to happen and quietly assumed that was the same as funding it. Budget doesn't get reallocated out from under a deal where the economic buyer personally sponsored the number.

1. "They're evaluating a competitor we didn't know about." A straightforward discovery miss. Somewhere in the first two calls, nobody asked who else they're looking at and what would make them choose it instead. Competitors don't appear in week nine. They were in the room in week one; the rep just didn't ask.

1. "The champion's gone quiet." By the time you hear this, you should already suspect the champion was never a champion — just a friendly coach with no internal capital. A real champion, someone with a personal stake in this deal happening, doesn't go quiet during a live evaluation. They chase you, because your silence is their problem too.

1. "The champion left the company / moved teams." Structurally the same failure as #6, ranked worse because it was foreseeable. Champions move jobs constantly — that's not the risk, that's the baseline. A rep who was multi-threaded from month one has three other relationships to fall back on. A rep who wasn't just watched the whole deal walk out the building attached to one person.

1. "They want to wait until next financial year." Translation: there was never a compelling event. Nobody established why doing this now beats doing it in eleven months, so "next financial year" isn't a decision the buyer made under this rep's influence — it's simply what happens by default when nothing is pushing the other way.

1. "They're still deciding internally." The worst one, because it's the vaguest, and vagueness this late means total qualification failure. This rep cannot tell you who's deciding, what they're deciding between, or when they'll be done deciding. Every other excuse on this list at least names a specific missing piece. This one names nothing, which tells you the rep never had answers to the basic questions — they've been running on hope since discovery.

What to do with this as a manager

Don't argue with the excuse. Ask the question behind it. "Procurement is slow" gets answered with "who's your contact there, and what did they commit to." "Still deciding internally" gets answered with "who specifically, deciding between what, by when." If the rep has a crisp answer, the deal is probably fine and the timeline is real. If they don't, you've just found next week's actual coaching priority, and it's rarely "close harder." It's usually one missing conversation from months ago that nobody went back to have.

Run this against your open pipeline with a proper Deal Review Checklist rather than a gut-feel call, and use the MEDDPICC Scorecard to check whether the deal actually has a confirmed economic buyer and a validated champion attached to it, not just a stage in the CRM. If champion strength keeps coming up as the recurring gap, the Champion Identification Checklist is the fastest way to teach reps the difference between a coach and a champion before the excuse ever gets said out loud.

None of this is about catching reps lying. Most of them believe their own excuse by the time they say it to you. The job is noticing that belief is doing the work qualification should have done three months earlier.