The 62% Proposal Stall
Northline Analytics sells a mid-market reporting platform at a $35k average contract value. The VP of Sales reviews 24 opportunities in late-stage pipeline and finds 15 have no quantified Impact and no documented Critical Event. Reps record Pain as 'needs better reporting' and move deals to Proposal once a champion asks for pricing. The quarter's commit is $1.9M; $1.1M has closed with two weeks left. One rep, Maya, has a $48k deal with a director who says, 'We need this before our fiscal year end,' but the CRM shows no date, no consequence of missing it, and no economic buyer. Maya wants to offer a 10% discount to 'create urgency.' The sales leader has one 45-minute deal review with Maya this week and cannot change CRM stages before next quarter.
1. Which SPICED elements are weakest in the pipeline review, and what evidence would you require before accepting a deal as late-stage?
Read the worked answer
The weakest elements are Impact, Critical Event, and Decision. Situation and Pain exist, but Pain is a symptom ('needs better reporting'), not a quantified business problem. Without Impact, the buyer has no business case; without a Critical Event, there is no dated consequence for inaction; without Decision, the rep does not know who signs, what criteria matter, or what procurement requires.
Evidence to require before late stage:
- A buyer-confirmed impact statement with a metric and owner, e.g. 'reduce reconciliation hours by 30% in finance; sponsor: controller.'
- A Critical Event with a date and consequence: 'if not live by 1 November, peak-season volume hits a manual backlog.'
- A decision map: economic buyer, technical approver, procurement steps, security and reference requirements.
- A next step with a buyer commitment, not a rep action.
The judgment is not 'fill all fields.' It is whether the buyer has said these things, not whether the rep typed them.
2. How should the sales leader use the 45-minute review with Maya to test the $48k deal without simply telling her to 'ask better questions'?
Read the worked answer
Use the 45 minutes to test the deal, not to lecture. First ask Maya to separate facts from assumptions: what did the director say, what was the exact date, who else was in the room, and what happens if the date slips? Then have her role-play the next call. Coach two questions: 'If nothing changes, what does that cost you by fiscal year end?' and 'What has to be true for you to sign before that date?' Listen for a named metric and a named approver. If the director cannot articulate either, the deal is not late stage.
Do not lead with the discount. A discount substitutes for a missing Critical Event and trains the buyer to negotiate. Instead, ask Maya to send a recap to the champion: 'Here is the impact we agreed, the date, and the approval path-correct?' That creates evidence. If the champion will not confirm, downgrade the deal and coach Maya on the cost of a false commit.
3. What one process change would reduce the recurrence, and what resistance should the leader expect?
Read the worked answer
Add a stage-exit requirement: Proposal requires a buyer-confirmed Impact statement and Critical Event in the CRM, plus a named economic buyer. Keep it to two required fields and one link to the call recording or email confirmation. Resistance will come from reps who see it as admin and from managers who want to protect the forecast.
The leader must inspect the evidence in deal reviews and refuse to accept 'the champion told me' without a date and consequence. Run a two-week audit of 10 deals, show the correlation between documented impact and close rate, and make the gate about forecast accuracy, not compliance. If the leader does not enforce it in reviews, the field will revert.