Read a sample: 1. The Work Between Yes and Start
The buyer has signed. The sales team has shared the good news, and someone has asked when the project can begin.
It is tempting to treat that moment as the finish line. The agreement is in place, the relationship is established, and the delivery team can take it from here. Yet the people responsible for the work may know only the title of the engagement, the price, and a rough start date. They may not know why the buyer chose the service, what the salesperson said would happen first, or which details were left for later discussion.
A signed agreement is essential, but it is not always a complete operating brief. It establishes important terms; it does not necessarily explain every conversation, working assumption, stakeholder concern, or practical dependency that will shape delivery.
The work between “yes” and “start” closes that gap. It turns the information gathered during sales into a useful internal picture of what the delivery team is expected to do, what remains uncertain, and what must happen before work begins.
A good handoff is not a transfer of ownership by disappearance. It is a coordinated transition. Sales contributes its knowledge of the buyer and the commitments made. Delivery tests that information against the work ahead. Together, they identify questions, involve the right people, and prepare for a clear conversation with the buyer.
Consider a fictional service firm called Harbor & Pine, which helps organizations improve their customer onboarding process. Its salesperson, Maya, has just closed an engagement with a regional software company called Northstar.
Northstar wants new customers to move through onboarding with less confusion. The signed agreement calls for Harbor & Pine to review the current process, recommend improvements, and facilitate a working session with Northstar’s team. It describes the principal deliverables and identifies a target period for the engagement.
Maya knows more than the agreement says. During the sales conversations, Northstar’s operations director explained that customer-facing teams use different versions of the onboarding checklist. A sales manager also expressed concern that any new process might slow down account launches. In a later call, Maya said Harbor & Pine could look at the existing checklists early in the engagement. The buyer mentioned an upcoming internal planning meeting and hoped to have preliminary findings in time for it.
None of this means the agreement is defective. The document may do exactly what it was intended to do. But if Maya sends only the agreement to Jordan, Harbor & Pine’s delivery lead, Jordan will need to reconstruct much of the situation while trying to start the work.
Several questions are already visible. Did Maya commit to preliminary findings before Northstar’s planning meeting, or did she say the team would explore whether that was possible? Who at Northstar can provide the current checklists? Does the sales manager need to participate in the working session? Does the target period in the agreement allow enough time for the review, especially if the materials arrive late?
The answers may be straightforward. The risk lies in assuming they are already known.
This fictional engagement will follow us through the book. It is not an example of a careless salesperson or an unusually complicated buyer. It is an ordinary service engagement with the usual mixture of written terms, useful context, hopeful expectations, and details that still need decisions.
An internal handoff is the organized transfer and review of deal information between the people who developed the opportunity and the people who will prepare and perform the work.
That definition contains two important ideas: transfer and review. Sending a folder is a transfer. A handoff also gives the receiving team an opportunity to understand the information, question it, and identify what is missing. It produces a shared working picture rather than a collection of files.
In practical terms, the handoff should help delivery answer:
- What has the organization agreed to provide?
- What has been said that could reasonably shape the buyer’s expectations?
- What is the buyer trying to accomplish, based on what the buyer has actually told us?
- What timing, resources, or buyer inputs does the work depend on?
- Who is involved, and what roles do they play?
- Which questions need answers before work begins?
The handoff does not need to resolve every detail immediately. It does need to make important uncertainty visible. “We do not yet know who will approve the final recommendations” is more useful than an unexplained blank, especially when it is paired with an owner and a plan to ask.
For Harbor & Pine, a useful handoff would give Jordan the signed agreement and a concise explanation of the Northstar conversations. It would distinguish the agreed deliverables from the hoped-for preliminary findings. It would identify the people Maya has met, note the concern about slowing account launches, and assign someone to confirm who can supply the checklists.
That is enough to move the conversation forward without pretending the team has answers it does not have.
The internal handoff sits between the sales process and the beginning of delivery. It can start before an agreement is signed, particularly when a delivery lead needs to assess feasibility or help shape a proposal. After signature, it becomes the process for confirming what was sold and preparing the people who will carry it out.
It is not a substitute for the agreement. The handoff brief should help the team…