Broken handovers

Broken handovers are one of the largest and least examined reasons professional services firms underperform.

They are hard to see because nothing fails at the moment they occur. A proposal is signed, a project is opened, a delivery team is briefed, and everyone leaves the room believing the same thing. The cost arrives weeks later, in a form that gets attributed to something else.

The misdiagnosis

When the consequences appear — scope shifts, lost assumptions, time and cost data arriving late, invoices rebuilt at the end of the month — they are read as delivery problems or finance problems, depending on which function is holding them at the time.

They are transfer problems. Sales, delivery and finance are working from different versions of the truth, and each version was created honestly at the point the work moved between them.

The reason this matters is that transfer problems do not respond to effort inside the functions. A better project manager cannot recover an assumption that was never written down. A better finance lead cannot reconstruct an approval that was never recorded. Each function can only be as good as what it was handed.

What gets lost in the gap

The losses are specific, and they repeat across firms.

The assumptions behind the estimate — how many revision rounds, which client resource was expected to be available, what counts as complete — usually exist only in the head of whoever priced the work.

The concessions made to win. A discount, a rate exception, an extra deliverable added in the final negotiation. These reach the contract and frequently do not reach the billing rules.

The acceptance criteria. Written in a proposal paragraph, read once, and then not consulted again until a milestone is disputed.

Each omission is small. Collectively they mean delivery begins by interpreting what was sold, and finance ends by reconstructing what was delivered — which is the same document being written twice by people who were not present when it was agreed.

Why a new platform does not fix it

This is worth saying plainly, because it is the mistake we watched firms make repeatedly before we built anything.

A new platform does not fix a broken handover. It makes the ambiguity move faster. If what passes between sales and delivery is a document plus a conversation, digitising the document produces a faster route for the same gap. The tooling improves and the reconstruction work does not change, which is why implementations of this kind are so often described afterwards as successful and disappointing at once.

That belief sits at the core of how DAY ONE was built. We came out of consulting, transformation and operational improvement rather than out of software, and before DAY ONE we ran a Salesforce consultancy of around fifty people using an operating system we had built for ourselves inside Salesforce. It was, honestly, not elegant — assembled over about seven years, piecemeal, fragile in places. What it did do was keep sales, delivery and finance on one record, and the administrative overhead of that firm was a few hours a week rather than a function.

The mechanism

A governed handover means the transfer is data rather than a briefing.

The engagement that delivery works to is the same record that was quoted, carrying its commercial terms, its rate card, its assumptions and its acceptance criteria as fields rather than as prose. Delivery structure is created against it, so the plan inherits the commercial basis instead of restating it. Time and costs are captured against that record and inherit the rules that decide whether they are billable. Change attaches to it as a priced, approved variation. Each WIP entry links back to work, approval and contract term.

The test of whether the handover held is not whether the kick-off meeting went well. It is whether anyone had to ask what was agreed after the work started. Where those terms are set is covered on our scoping and quoting page; where they have to survive contact with the work is our delivery and time capture page.

On Salesforce; works with your Salesforce org, or available as a bundled edition if you don’t use Salesforce.

What this costs, and what has to be true first

Making the handover data means the selling side has to record things it currently carries in its head, at the point of sale, when the incentive is to close and move on. That is a real cost and it lands on the people least inclined to absorb it. A firm that cannot get its commercial leads to do this will not get the benefit, and the software will not persuade them — that is a management problem, and it should be settled before an implementation rather than during one.

It is also worth naming what a governed handover does not do. It does not make a bad estimate good. If the assumptions were wrong, recording them faithfully means the firm discovers they were wrong sooner, which is valuable but is not the same as being right. Some of the discipline’s early value is unpleasant information delivered promptly.

And there is a scale below which it is unnecessary. If the person who sold the work is also delivering it, the handover is internal to one head and the ceremony adds nothing.

A test worth running

Pick the last engagement that produced an awkward invoice conversation. Ask the delivery lead what they understood the scope to include, ask whoever sold it the same question, and compare the answers without either of them conferring first.

The gap between those two answers is the handover debt on that job. It is usually larger than either party expects, and it was created before anybody did anything wrong. What the Rowland case study sets out is what rebuilding that chain took in practice, including the parts that were not straightforward.