What gets delivered does not match what was sold. Somewhere between the signed deal and the first day of work, scope, expectations, and promises get lost.
Sales moves on to the next deal, delivery starts from a thin or inaccurate picture, and the client, who heard one thing in the sale, experiences another in delivery. The gap shows up as scope disputes, rework, and a client who feels misled before the work even gets going. This guide closes it with a clean handoff: capturing exactly what was sold, transferring it to delivery with a readiness check, and aligning the client on what to expect, so delivery starts from the truth.
Plan two to three hours to design the handoff, then a short handoff per engagement after that. It is not a fix for the sale itself. If the sale never captured scope in the first place, a handoff has nothing to transfer.
Establish a single source of truth for the engagement: exactly what was promised, scoped, and expected in the sale. Capture the deliverables promised, the scope boundaries of what is and is not included, the timeline and milestones committed, and the price and terms.
The most common failure is that the implicit promises, the things said in conversation but never written down, never reach the delivery team. Capture those explicitly. The unwritten promise is the one that becomes the mid-engagement dispute.
Open the Sold-Scope and Commitment Capture →Before delivery accepts the engagement, check whether it can actually deliver what was sold, on this timeline, at this price, with the team available. Where the answer is no, the gap is surfaced now, while it is still cheap to fix.
Gaps resolve one of three ways: renegotiate with the client before starting, adjust the delivery plan to meet the commitment, or escalate a mismatch that sales and delivery must reconcile. Surfacing the gap at handoff is the entire point.
Open the Handoff Protocol →Transfer the engagement from sales to delivery cleanly, so delivery owns a complete, accurate picture. Hold a structured handoff where sales transfers the captured scope, context, client relationship notes, and commitments, and delivery confirms it has what it needs to start.
The transfer is complete only when the delivery owner can restate the scope and expectations back accurately. A handoff is a confirmation, not a forwarded email.
Open the Handoff Protocol →Set the client expectations explicitly at the start, so the experience through delivery matches what they understand. Run a kickoff that confirms scope and deliverables, timeline and milestones, how and how often you will communicate, who their point of contact is, and what is expected of them.
Naming what is and is not in scope at kickoff, in the client hearing, is what prevents the "but I thought this was included" dispute later. The kickoff sets the tone: organized and proactive, or already behind.
Open the Client Kickoff and Expectation-Setting Template →Make the handoff a standard step every engagement passes through, not a one-time fix. Set it as a required gate between sale and delivery: no engagement starts delivery without the capture, the readiness check, the transfer, and the client kickoff all complete.
Define who is responsible for each part, and make it routine. The discipline holds only when the handoff is mandatory, not optional under deadline pressure.
Open the Handoff Protocol →Delivery starts every engagement with an accurate, complete picture of what was sold. Scope mismatches surface at handoff, not mid-engagement. Clients are not surprised at kickoff by what is or is not included. And sales and delivery stop blaming each other for misalignment (Systems and Relationships: Level 2 toward Level 3).
With a clean handoff, most teams move to Delivery Standardization and Quality Assurance, so the work that now starts from the truth is delivered consistently. If scope creep turns out to be an under-pricing problem, that is pricing strategy. Delivery Standardization and Quality Assurance →