What the delivery team inherits
The deal closes and the work of winning it disappears — so the buyer answers discovery twice. A commercial-side failure that starts long before signature.
Kickoff. The first real call after signature. A dozen people on the line, half of whom have never spoken to each other. The project lead — the person who now owns delivering this thing — opens with a version of the same question every time:
“So, walk me through what you’re trying to accomplish.”
And the buyer answers. Patiently. Again.
They answered that question in discovery. A sharper version during the security review. A third version when the business case went to their finance team. Every time, someone on the selling side wrote it down. Every time, the answer got better. None of it is in the room now.
Four things that break between the verbal yes and the work
The deal is effectively won and then it stalls, and the reasons are unglamorous. Four recur.
Scope described imprecisely
Not wrong — vague. Two readers form two different pictures of what is being bought, and neither finds out until delivery.
Service specificity missing
What is included, what is not, what is optional, and the point at which additional work becomes a change. Left implicit at proposal stage, it becomes an argument later, usually with the customer you just won.
Redlined clauses arriving late
On terms nobody on the commercial side had read until after the verbal yes.
Partnership language that lives only at the top
The overarching commitments agreed in the master agreement never get carried down into the project-level documents people actually work from. What was agreed at the top never reaches the work.
Let me be exact about the boundary before going further: contracts and redlines are not what I do. That is a lawyer’s job and I will not pretend otherwise. But look at that list again. Three of those four are commercial-side failures with commercial-side fixes, and the fourth is a handoff problem wearing a legal problem’s clothes. The clause arrives late because nobody built a moment for it to arrive early.
The second discovery call
What the project lead inherited is a contract and a statement of work. Both are legal documents. They record what was agreed, not what was learned — and the gap between those two things is most of the deal.
The rep who learned it is on next quarter’s number. The solutions engineer who scoped the integration is on someone else’s opportunity. The forty security answers that took three internal reviewers a week are sitting in whatever file they were pasted into. The champion’s real reason for buying — the one they would never put in an RFP — was said out loud on a call and lives in one person’s memory.
So the buyer becomes the archive. They are the only person in the room who was present for the entire process, which is why they end up narrating their own deal back to the vendor they just bought from.
That is a strange thing to ask of a customer in their first week. They paid you. Their first experience of being a client is doing your onboarding for you. And they notice — not as a complaint they will file, but as a small recalibration of how organised they think you are. Buyers who just spent months evaluating your competence are unusually alert to the first evidence of what you are actually like to work with.
It gets harder as the buying group grows. Healthcare IT purchases commonly run 12–18 months with roughly 8–10 stakeholders (Salesmotion / MarketBetter). In the mid-market I would put the number of genuinely load-bearing stakeholders lower — four to eight is closer to what I have seen, and that is my estimate rather than a sourced figure. Either way it is more people than any one person’s memory can carry across a signature.
Why this is a commercial-side failure
Delivery teams take the blame for this and it is not theirs. They are handed a project with the reasoning removed and asked to reconstruct it under a start date.
The mechanism is simple. The answers, decisions and approvals generated while winning a deal get treated as exhaust — byproduct, disposable once signed. And every one of them was expensive. A subject-matter expert’s afternoon. A security lead’s review. A champion’s political capital. A finance approval that took four people. Then the deal closes and that entire body of work scatters across a CRM field, a shared drive, three inboxes and somebody’s laptop.
Nobody decides to throw it away. That is exactly the problem — it is a default, not a decision.
It stays invisible because nothing measures it. The opportunity is marked Closed Won and the record stops moving. The rep’s compensation event is complete. The cost lands weeks later, on a different team, in a different system, and gets logged as a slow start or a scoping problem.
A failure that pays out on one team’s ledger and bills to another’s is a failure nobody fixes.
What actually closed the gap
I have built against these, and two things moved the needle more than anything else.
Integrating the systems and the information. Not a new platform — connecting the ones already in use so the proposal, the quote and the scoping document draw from the same source rather than from three people’s separate understanding. Most of the imprecision above is not carelessness. It is three documents assembled independently by people who never compared them.
A standing cross-functional deal conversation, running the length of the sale. Not a stage gate and not a committee. A working group with the commercial, technical, delivery and finance sides represented, in contact continuously through live chat and asynchronous threads, and meeting live several times over the course of a deal.
What matters is less the meeting than the agenda. It covers the whole deal, not one function’s slice of it — strategy, pricing, how well the solution actually fits, the complexity and resourcing the work would demand, timelines, the contracting path, and where the account could go afterward. Anything to do with strategising a deal, executing its mechanics, or planning the future of the account.
That is what stops scope drifting and clauses arriving late. Not a template. A room where the people who will have to live with a commitment are present while it is still being made.
Templates matter too — scope and service definition written the same way every time, so the gaps are visible before a buyer finds them. But templates without that conversation just produce consistent documents describing something nobody validated.
What it looks like when it carries
An illustration, not a case study — a state built from parts I have run, not a client I can name.
- The project lead inherits a contract and a statement of work — both record what was agreed, not what was learned
- Requirements are re-gathered from the person who already answered them
- The reason this buyer bought lives in one person’s memory
- The commitments at the top of the agreement never reach the working documents
- The delivery owner sat in on scoping before signature — not to sell, but to check the read
- Requirements are not re-gathered. They are confirmed
- The security and compliance answers are current, dated and owned
- The reason this buyer bought, in their own words, is written down somewhere other than a person’s head
Somebody asked whether the timeline in the proposal was real, and said what they thought on the record, while there was still room to change it. That is the whole difference: a confirmation, not an excavation.
Where my work stops
My contracted work ends at signature. I do not run projects, manage implementations, govern delivery, review contracts or redlines, or grade the quality of the work after the ink is dry. I would be the least experienced person in that room and I am not going to pretend otherwise to widen a scope.
What I build is the commercial system that runs up to signature: how you decide what is worth pursuing, how you survive someone else’s evaluation, how you document and approve and get to a clean close. In B2B SaaS and life sciences since 2011, running Deal Desk and Sales Operations since 2018 — a Deal Desk built from scratch governing a $25M+ pipeline, a 2,000+ vetted Q&A library behind 5,000+ responses built and audited, and around a thousand proposals for buyers in clinical research, health systems, insurance and financial services.
But scope and value are two different measurements, and conflating them is how consultants end up selling things they cannot do. My scope ends at signature. The value of what I build is measured downstream — by what the next team inherits.
The work of winning a deal should accumulate, not evaporate. That is a standard applied while the deal is still open, by people already in the conversation, so the answers, decisions and approvals are still there on the far side of the signature. What the delivery team does with them is their craft, not mine.
The reframe
Your commercial process is the single largest act of research your company will ever perform on that customer. Months of it. Dozens of people. Their words, their constraints, their politics, their reasons.
Treat it as exhaust and it is gone the day you win. Treat it as an asset and it is still there a year later — in the kickoff, in the QBR, in the renewal, in the second deal.
Same work. Same people. Same conversations.
The only difference is whether anybody decided in advance that it should last.
If you handed your last closed-won deal to a project lead tomorrow with nothing but the contract, how much of what you actually learned would reach them?
Rob Roberts is the founder of Widenine Solutions. In B2B SaaS and life sciences since 2011, running Deal Desk and Sales Operations since 2018 — including a Deal Desk built from scratch governing a $25M+ pipeline, and a 2,000+ vetted Q&A library behind 5,000+ responses built and audited.