The handoff nobody designs on purpose
Most agencies can describe their sales process and their delivery process separately, in detail. Fewer can describe what actually happens at the seam between them — the moment a signed proposal becomes a real project with real scope, a real budget, and real people assigned to do the work. That handoff usually isn't designed; it just happens, informally, through a Slack message or a forwarded email, and details get lost in the gap.
This matters more than it looks like it should, because the handoff is where scope gets defined for the team actually doing the work. If the proposal said one thing, the contract said something slightly different, and the kickoff call added a few more assumptions, the person tracking time against the project is now working from a version of the scope that exists only in their memory of that kickoff call.
Where the gap actually shows up
Scope drifts between proposal and delivery. A proposal is a sales document — written to close a deal, often generalized or aspirational about what's included. By the time delivery starts, the scope needs to be specific: which deliverables, by when, at what level of revision. If nothing formally converts the proposal's language into the delivery team's actual scope, the team ends up interpreting the proposal themselves, and interpretations vary.
Contract terms don't reach the people billing the work. Payment terms, retainer structure, cancellation clauses — these live in the contract, but the person generating invoices six months later often isn't the person who negotiated the deal. If the contract isn't a first-class object connected to the client record, its terms exist only in someone's memory or a filed PDF nobody re-reads at invoice time.
Nobody owns the moment scope becomes budget. A proposal might say "ongoing social media management" without translating that into a specific number of hours or a specific retainer cap. The team delivering the work needs a number, not a phrase — and if that translation doesn't happen deliberately, the first invoice becomes the moment scope gets defined, which is exactly the wrong moment for that conversation.
What a clean handoff actually requires
A pipeline that ends where delivery begins, not before. Sales-to-delivery handoff works best when the CRM pipeline and the delivery system are the same system, or at least share the same client and project record — so a deal moving to "won" naturally becomes a project instead of requiring someone to manually recreate everything the sales process already captured.
Contracts attached to the client record, not just filed. A signed contract should be something the team can reference when a scope question comes up months later — not an artifact sitting in a signature tool's dashboard, disconnected from the project it governs. When contract terms (retainer amount, cap, renewal date, cancellation notice) live next to the actual billing data, invoicing questions get answered by looking, not asking around.
Proposals that convert into scoped deliverables, not paragraphs. The most useful proposals are ones that translate cleanly into the units delivery will actually track against — hours, deliverables, a retainer cap — rather than staying in marketing language. That conversion is worth doing once, deliberately, at handoff, instead of being reconstructed by whoever gets the first "wait, was that included?" question.
The cost of skipping this
Agencies that don't formalize the proposal-to-delivery handoff tend to pay for it later, in two specific ways: scope disputes (the client remembers a broader promise than what delivery was told), and billing friction (the invoice doesn't match what the client thinks they agreed to, because the terms lived in a contract nobody connected to the invoicing process). Both are avoidable — not through more meetings, but through making the handoff a system behavior instead of a hope.