Cersosimo — Decision Science & Engineering
Field Note · Jun 17, 2026 · Thought Engineering · 6 min read

How to get a deal unstuck when procurement freezes your contract

When a deal stalls in procurement, the buyer isn't the enemy — the process is. Move around the process by mapping the temperament of the stalled stakeholder, speaking to their decision speed, and engineering a micro-yes that unfreezes the contract.

When a deal freezes in procurement, the buyer isn't ghosting you — they're trapped inside a system that punishes forward motion. The contract sits on a desk. The stakeholder goes quiet. You send another email. Nothing moves. The problem isn't price, and it isn't interest. The problem is that you're speaking to the person as if the process doesn't exist, and the person is speaking to the process as if you don't exist. To unstick the deal, you stop pitching and start engineering a micro-yes that gives the stakeholder permission to move.

Most advisors treat a stalled contract as a negotiation problem. It isn't. The deal already closed in the room. The stakeholder said yes. Then procurement asked for three more signatures, two committees weighed in, and the whole apparatus ground to a halt. The stakeholder who bought in Week 1 is now paralyzed in Week 9 — not because they changed their mind, but because the system introduced friction they didn't predict.

The move isn't to push harder. The move is to map the stakeholder's temperament, speak to their decision speed, and design a micro-yes that bypasses the apparatus.

The fork in the stalled deal

Every stalled procurement situation reveals a fork. The buyer can move forward — if you give them the smallest possible step that satisfies the process without requiring a full committee vote. Or they can stay frozen — because the next move feels too large, too public, or too uncertain.

Your job is to collapse the size of the ask until it fits inside their authority and their pace.

A litigation partner calls. His firm closed a corporate client six weeks ago. The GC said yes. The retainer went to procurement. Silence. The partner sends a follow-up. The GC replies: "Still working through approvals." Two more weeks pass. The partner asks what I'd do.

I ask: what's the GC's temperament?

He doesn't know. I walk him through the map. The GC is methodical, evidence-first, slow to commit but loyal once in. Melancholic type — the data-driven operator who won't move without proof the process is airtight.

The partner's instinct was to call and ask, "What's the holdup?" That question reads as pressure. Pressure makes a Melancholic go quieter.

The engineered move: send a one-line email that gives the GC a micro-yes.

"Would it help if I sent you a one-page summary of how we handled approvals for [comparable client]?"

The GC replies in four minutes. Yes. The partner sends the page. The retainer clears procurement in nine days.

The buyer isn't the enemy — the process is. Your move is to make the next step smaller than the friction.

Where the greats left it

Cialdini opened the science of commitment and consistency — once someone says yes, they'll move toward behavior that aligns with that yes. He stopped at the initial commitment. The discipline now in practice picks up where he set the tool down: you engineer a sequence of micro-yeses so small that each one feels like process hygiene, not risk.

The insight Cialdini named but didn't operationalize for stuck deals: the second yes is harder than the first, because now the stakeholder has to defend the original yes to a new audience. Procurement is that audience. The committee is that audience. The CFO who "just wants to take a look" is that audience.

If your next move after the handshake is to wait for the contract to flow through, you're assuming the system is frictionless. It isn't. The system is designed to slow things down.

Skinner's operant conditioning mapped this from the other side: behavior that gets rewarded gets repeated. The problem in procurement isn't that the stakeholder doesn't want to move — it's that every time they try to move, the system punishes them with more steps, more signatures, more questions. You're asking them to repeat a behavior that has only ever produced friction.

The engineered path: reward the smallest motion. Give them a yes they can execute in thirty seconds. Then another. Then another. Each one builds momentum.

Mapping the stalled stakeholder

Before you unstick the deal, you map the person holding it.

The Choleric type — fast, outcome-driven, impatient with process — stalls when they hit a roadblock they can't bulldoze. They said yes in the room because the deal made sense. Now procurement is asking for three more approvals, and they're furious. They won't tell you they're furious. They'll just stop answering.

The move: give them a way to win without waiting. Send a one-liner that lets them delegate.

"If it's helpful, I can walk your procurement lead through the contract directly."

You're not asking them to do more work. You're offering to take the work off their plate. They forward your email in sixty seconds.

The Sanguine type — expressive, energy-driven, consensus-focused — stalls when the deal loses its story. They sold the room on your firm because it felt exciting. Now it's a contract negotiation, and no one's excited anymore. They're not ghosting you — they're waiting for someone else to re-energize the room, because they don't want to be the only one pushing.

The move: give them a story they can tell.

"I just helped [comparable client] close a similar deal in two weeks — want me to send you the one-page case study so you can share it with the team?"

You're handing them the narrative. They forward it to the group thread. The deal unsticks.

The Phlegmatic type — patient, trust-driven, deliberate — stalls when the process feels rushed or unsafe. They said yes because they trust you. But procurement is moving faster than they're comfortable with, and now they're second-guessing. They won't say they're second-guessing. They'll say, "Still reviewing."

The move: slow down and ask about the process, not the decision.

"What's the internal approval process look like on your end? I want to make sure we're not missing a step."

You're not pushing. You're giving them room to walk you through their system. They explain. You adjust. The deal unfreezes because you made it feel safe again.

The Melancholic type — evidence-first, data-driven, methodical — stalls when they don't have enough proof to defend the decision to the next layer. They believe the deal is right. But if procurement asks, "Why this firm?" they need an answer that holds up under scrutiny.

The move: give them the evidence.

"Would it help if I sent you a one-page breakdown of how we've handled [specific issue] for three comparable clients?"

They say yes. You send it. They forward it to procurement with a note: "This addresses the question." The contract moves.

Three moves you can run this week

Move 1: Diagnose the stall by mapping the stakeholder's pace.

Go back through your last three emails or calls with the stalled contact. Are they asking for more data? That's a Melancholic stall — they need evidence. Are they going quiet after an enthusiastic start? That's a Sanguine stall — the energy left the room. Are they frustrated with process? That's a Choleric stall — they're blocked and they hate it. Are they saying "Still reviewing" without urgency? That's a Phlegmatic stall — they need reassurance the process is sound.

Move 2: Design a micro-yes that takes thirty seconds to execute.

Write a one-line email that gives the stakeholder a single, tiny step forward. Not "Can we get this finalized?" — that's a big ask. Instead: "Would it help if I [did this specific small thing]?" or "Can I send you [one specific document]?" The yes has to be smaller than the friction.

Move 3: Reward the first motion, then queue the next.

When they say yes to the micro-yes, execute immediately. Send the document in under an hour. Then wait forty-eight hours and offer the next small step. You're not pushing the whole contract through in one email. You're engineering a sequence. Each yes builds momentum. Momentum unsticks deals.

FAQ

Q1: What if the stakeholder won't even reply to the micro-yes email?

A1: Then the stall isn't process — it's interest. A true procurement stall still has a live buyer on the other end; they're just stuck. If they won't reply to a low-friction, high-value offer, the deal is dead and you're chasing a ghost. Move on.

Q2: How do I know which temperament the stakeholder is if I've only met them once?

A2: Listen to their first question when you met. Choleric types ask, "What's the bottom line?" Sanguine types ask, "What's the vision here?" Phlegmatic types ask, "How does the process work?" Melancholic types ask, "Can I see the data?" That first question tells you their predisposition. Map it and speak to their pace.

Q3: Can I use this same approach if the deal is stalled with a committee, not one person?

A3: Yes, but you pick one person in the committee and engineer the micro-yes for them. Committees don't move — people in committees do. Find the stakeholder who has the most to gain from the deal closing, map their temperament, and design the smallest yes that gives them something they can bring back to the group. Let them unstick it from the inside.

Apply the discipline

See the read and the move running inside your practice.

The 60-minute briefing walks Decision Science, Temporal Predisposition Mapping, and Thought Engineering through one of the three practices — financial advisory, medical, or legal. The first conversation is short and honest about fit.

← All Field Notes