The handoff leak: the most expensive two metres in your business

Ask a service business owner where they lose money and you will hear about pricing, about clients who pay late, about a market that got more competitive. Almost nobody points at the two metres between the sales team and the delivery team. That is where the real leak usually is, and the reason nobody points at it is the reason it exists: no report anywhere in a normal business describes what happens in a handoff.

This article is an anatomy of that leak, why it happens structurally rather than through anyone's fault, what it costs, and a checklist you can steal today that works on paper before it works in any software.

The moment everything changes hands

Every project business has the moment. Sales closes a deal. There is a small celebration, a PO number, maybe a kickoff call, and then a transfer of responsibility: delivery now owns the promise that sales made.

The question that decides your margin is what, exactly, transfers with it.

Think about what the promise actually consists of by the time a deal closes. There is the written scope, in whatever state the proposal left it. There are the commitments made verbally across four or five calls, the "yes, we can include that" and the "we'll have someone senior on this" that never made it into a document. There is the commercial fine print: the VAT treatment, the payment milestones, the assumptions the price was built on. There are the risks sales already knows about, the stakeholder who was lukewarm, the deadline that is tighter than the client admits. And there is the relationship context: who the real decision-maker is, what they care about, what was promised about communication.

In most firms, that entire bundle has no single home. It exists as fragments: some in the proposal, some in an email thread, some in a spreadsheet, and a decisive amount in the head of the salesperson, who has already turned toward the next deal, because that is what salespeople are paid to do.

The reconstruction, and the drift

Delivery, receiving fragments, does the only thing it can do: it reconstructs the deal. A project plan gets written from the proposal, plus whatever the kickoff call surfaces, plus reasonable assumptions where information is missing.

Here is the structural problem: the reconstructed version is never quite the sold version. It cannot be. Reconstruction from fragments loses information by definition, and the information it loses is precisely the informal, verbal, relationship-level material that never got written down, which is also precisely the material the client remembers most vividly, because it was said to them directly, in conversation, by someone they were deciding whether to trust.

So the drift begins. The client asks about the thing they were told on a call. Delivery has never heard of it. Now there is a choice between two bad options: push back on something the client was genuinely promised, which reads as your company going back on its word, or absorb the work silently, which reads as nothing at all, because absorbed work is invisible. Most teams, most of the time, absorb. It feels professional. It keeps the relationship warm. And it is precisely how the margin leaves the building.

The cruel part is the accounting. Absorbed scope never appears as a cost, because nobody prices it. The project simply lands thinner than the quote promised, and at the retrospective, if there is one, the explanations are all plausible and all wrong: the estimate was optimistic, the client was difficult, the team was slow. The estimate was fine. The handoff leaked.

What it costs, beyond the obvious

The direct cost, free work, is the visible part. The secondary costs are usually larger.

There is the variation you could have billed. Scope changes are normal and healthy in project work; clients expect to pay for genuine additions, when the addition is visible against a baseline. With no clean baseline, every change is arguable, so teams stop arguing and stop billing.

There is the rework from wrong assumptions. When delivery guesses at missing information and guesses wrong, the work gets done twice, and the second time is at your expense and under time pressure.

There is the client-experience cost, which compounds quietly. From the client's side, a leaky handoff feels like being handed from someone who knew everything to someone who knows nothing. They repeat themselves. Things they were promised evaporate. Fairly or not, they conclude that your company forgets things, and that conclusion prices itself into the renewal conversation.

And there is the internal cost: the sales-versus-delivery blame cycle. Delivery believes sales promises the impossible and vanishes. Sales believes delivery squanders what they close. Both are describing the same missing structure from opposite ends of it.

The fix is structural, and smaller than you think

Because the failure is structural, the fix is too, and it is not heroics, more meetings, or better memories. It is one principle: the handoff must be a record, not a conversation.

A conversation transfers whatever the participants remember to say, and evaporates. A record transfers everything it contains, and persists. The moment a deal is won, what delivery should receive is not a briefing but the deal itself: its scope as sold, its email trail, its call notes, its documents, its commercial terms, its known risks, as one object with one history.

Here is the checklist we use, and the one we would suggest stealing whatever tools you run. Before delivery accepts a handoff, it should hold, in writing:

1. The signed scope, the actual document the client agreed to, not a summary of it.
2. Approved commercials, including the VAT treatment, inclusive or exclusive, decided and recorded, because that single word is worth 5% of the deal.
3. The PO reference, so invoicing never waits on an email hunt.
4. Named client contacts, who decides, who approves, who receives the invoices.
5. Everything promised verbally, written down at last, however awkward the writing down feels. This is the item that prevents the most grief.
6. The payment milestones, so delivery knows what triggers billing.
7. The risks sales already knew about, because delivery discovering them in week three costs triple.

The rule that makes the checklist work: if delivery has to ask for any of these, the handoff has already failed. They just don't know it yet.

Where Trazer fits, and where it doesn't need to

We built Trazer around exactly this principle. In it, winning a deal creates the project automatically, and the project is the deal, same record, same history, nothing retyped and nothing transferred, because nothing needs to transfer when both teams are looking at the same object. Scope changes become priced change requests against a written baseline, which turns the awkward absorb-or-argue choice into a routine commercial step. The client, through a read-only portal, sees the same plain-language status the team sees, which ends the where-are-we emails.

But the honest advice is that the checklist needs no software. Run it on paper for one quarter. Print it, staple it to every kickoff, and refuse the handoff until every line is filled. It will feel bureaucratic for two weeks, and then it will save you a variation argument, and after that nobody will give it back.

If, after a quarter, you find the paper version keeps failing in the same place, work scattered across too many inboxes for anyone to staple together, that is not a discipline problem either. That is the moment the work has outgrown the tools, and we would be glad to show you what the structural version looks like. Bring the deal where the handoff hurt most. Thirty minutes.

A note on culture, because structure is not quite the whole story

One objection deserves an honest answer: does formalising the handoff make a business feel bureaucratic, especially in a region where deals are built on relationships and a great deal is legitimately agreed in conversation?

Our experience is the opposite, and the reason is worth stating carefully. What corrodes relationships is not paperwork; it is broken promises, and the informal handoff breaks promises mechanically, without anyone intending it. The client who was told something on a call and later finds delivery has never heard of it does not experience your firm as pleasantly informal. They experience it as forgetful. Writing the verbal commitments down at handoff is not a retreat from the relationship; it is the act of taking the relationship's content seriously enough to protect it from attrition.

There is also a personnel dimension. In firms with leaky handoffs, institutional memory lives in individuals, which means every resignation is a small data loss and every holiday is a degraded service week. When the record carries the deal, people can actually hand things over, go on leave, change roles, or leave the company without taking a slice of the client relationship with them. That is not bureaucracy. That is the difference between a business and a group of individually heroic people, and it is precisely the property that makes a services firm sellable, scalable, or even just restful to run.

Start with the checklist. The structure can come later; the habit of writing the promise down cannot start soon enough.