The Person Who Understood the Deal Is Never on the Kickoff Call

content/blog/2026-04-27-person-who-understood-deal-never-on-kickoff.md

@@ -0,0 +1,92 @@
+---
+title: "The Person Who Understood the Deal Is Never on the Kickoff Call"
+date: 2026-04-27
+pillar: "The Optimism Cascade"
+tags: [sales-to-delivery, handoff, mid-market, commerce, scope]
+linkedin_copy: |
+  The person who sold the deal understood something about the client that never made it into the spec.
+
+  I have seen this pattern on enough mid-market commerce projects to call it structural. Sales closes the deal. A Statement of Work transfers to delivery. Architecture diagrams, discovery decks, maybe a recorded call or two. Delivery reads everything. They build exactly what the document describes.
+
+  Three sprints later, the client raises something that sounds like scope creep. Delivery pushes back. The client says, "We discussed this during the sales process."
+
+  They did. With someone who is no longer in the room.
+
+  This is not a communication failure in the usual sense. Nobody forgot to send an email. The problem is that selling and transferring context are fundamentally different activities. Sales conversations optimize for momentum. They respond to objections in real time. They read tone and emphasis. None of that transfers through a summary document.
+
+  The fix is simple and boring: a fifteen-minute pre-recorded handoff video from the sales lead, made before kickoff, covering three things. Why this client bought. What almost killed the deal. What the client said once that matters more than anything in the SOW.
+
+  It does not require new tooling. It requires one person to spend fifteen minutes doing work that benefits someone else's timeline. That is why it almost never happens. The sales lead's job is done at close. The handoff artifact lives in nobody's incentive structure.
+
+  The cost of the missing handoff does not appear as a line item. It appears as friction: scope conversations that take two meetings instead of one, a client who feels unheard by week three, a prioritization call that is technically correct and contextually wrong.
+
+  Organizations that close this gap run better projects. Not because they have better engineers. Because their delivery teams start with context, not just specs.
+
+  Full post: {{url}}
+---
+
+The person who sold the deal understood something about the client that never made it into the spec.
+
+Maybe it was the real reason the client left their last platform. Maybe it was the line item that almost killed the deal before it closed. Maybe it was the executive sponsor's actual priority, the one they said out loud exactly once in the third meeting and never repeated.
+
+That context lives in someone's head. And that someone is not on the kickoff call.
+
+This is the most expensive process failure in mid-market commerce, and it is not a technology problem. It is a handoff problem. The spec transfers. The context does not.
+
+## What delivery gets
+
+Delivery gets a Statement of Work, an architecture diagram, maybe a discovery deck. If the organization is disciplined, they get a recorded meeting or two.
+
+What they do not get is the signal layer: why this client said yes, what they were afraid of, which features were table stakes and which were concessions to close. They do not get the politics. They do not get the unstated priority.
+
+So delivery reads the spec and builds the project. And they are right, technically. The work matches the document.
+
+But the document was never the full picture.
+
+## Where it breaks
+
+Three sprints in, the client raises something that sounds like a scope change. Delivery pushes back. The client gets frustrated. They say, "We talked about this in the sales process."
+
+They did. They talked about it with the person who is no longer in the room.
+
+This is not a communication failure in the way most people mean when they say "communication failure." Nobody dropped a ball. Nobody forgot to send an email. The information lived in a conversation that was never designed to be transferred. It was designed to close a deal.
+
+Selling and transferring context are two different skills. Sales conversations optimize for momentum. They move fast. They respond to objections in real time. They read the room. None of that is captured by a transcript or a summary document.
+
+The signal that matters most, the thing the client cares about but did not put in the RFP, is almost always communicated through emphasis, repetition, and tone. Those are exactly the things a document cannot carry.
+
+## The fix is boring
+
+The fix is a pre-recorded handoff video from the sales lead, made before the kickoff, covering three things:
+
+1. Why this client bought. Not the business case. The actual reason they said yes to this vendor and not the other one.
+2. What almost killed the deal. The objection, the concern, the competing priority.
+3. What the client said once that matters more than anything in the SOW.
+
+Fifteen minutes. Recorded asynchronously. Watched by the delivery lead and the technical architect before the first standup.
+
+This does not require a new tool. It does not require a process overhaul. It requires one person to spend fifteen minutes doing something that is not in their incentive structure.
+
+That is why it does not happen.
+
+The sales lead's job is done when the deal closes. The handoff artifact is work that benefits someone else's timeline. In most organizations, nobody measures whether it was made, and nobody notices when it was not. The absence is invisible until it is expensive.
+
+## The cost is not obvious
+
+The cost of a missing handoff does not show up as a line item. It shows up as friction. A scope conversation that takes two meetings instead of one. A client who feels unheard three weeks in. A delivery lead who makes a prioritization call that is technically correct and contextually wrong.
+
+Over a six-month engagement, that friction compounds. The project does not fail. It just runs slightly sideways from what the client expected, and nobody can point to the moment it drifted.
+
+The moment it drifted was the kickoff. The person who could have prevented the drift was not in the room. They had already moved on to the next deal.
+
+## The pattern underneath
+
+This is a specific instance of a broader pattern in mid-market commerce: the people who shape the project and the people who deliver the project occupy different incentive structures, different timelines, and different accountability windows.
+
+Sales is measured on closed revenue. Delivery is measured on margin and client satisfaction. The handoff sits between those two measurement systems, owned by neither.
+
+Every organization knows this gap exists. Almost none of them close it, because closing it requires someone in sales to do post-close work that does not count toward their next quarter.
+
+The organizations that do close it, the ones where the delivery lead walks into kickoff already understanding the deal, not just the spec, run better projects. Not because they have better developers. Because they started with better context.
+
+Context is not a deliverable. That is why it keeps getting lost.