If you want to find where a business loses money, don't look at the work. Look at the seams between the work. The sale closes — and then what? Someone has to tell delivery. Delivery finishes — and then what? Someone has to tell billing. The invoice goes out — and then what? Someone has to tell support who this customer is. Every "and then what" is a handoff, and handoffs are where work quietly dies.
Why boundaries are dangerous.
Inside a single function, work has momentum and an owner. At a handoff, both evaporate. Ownership becomes ambiguous — is it still the salesperson's, or the project manager's yet? Context has to be re-created — the new owner doesn't know what was promised, only what was recorded, and what was recorded is whatever fit in the other tool's fields. The thing that was alive and understood in one person's head becomes a thin artifact passed across a gap.
Now make it worse, the way real businesses do: put each side of the handoff in a different tool. The deal lives in the CRM. The project lives in the PM tool. Billing lives in the accounting app. The handoff isn't just a change of owner — it's a change of System, performed by a human copying fields from one screen to another, hoping nothing important lived in a field the next tool doesn't have.
Work doesn't fail in the doing. It fails in the passing.
The specific things that fall in the gap.
It's never the big stuff that drops. It's the texture. The discount the salesperson promised that never made it to the invoice. The scope note from the kickoff call that the project board never captured. The fact that this customer is sensitive about timelines, known to sales, invisible to support. Each loss is small. In aggregate they're the difference between a customer who feels handled and one who feels like a ticket — and they all happen at the seams, in the copy-paste between tools.
The fix isn't a better handoff. It's fewer of them.
You can invest in handoff hygiene — checklists, handoff meetings, mandatory fields. It helps a little, the way a better bridge helps you cross a river. But the structural move is to stop crossing rivers. When the deal, the project, the invoice, and the support history are the same record on the same platform, the handoff isn't smoother — it's gone. Closing the deal ist the thing that opens the project. The context doesn't transfer because it never left.
That's the quiet superpower of one data layer. The promise the salesperson made is on the record the project manager opens. The scope note is right there when billing generates the invoice. Support sees the entire relationship, not a fresh ticket. Nobody re-creates context at a boundary, because there's no boundary to re-create it at.
The payoff.
Teams that close their seams describe the same change, almost word for word: things stop falling through the cracks, because the cracks are gone. The billing disputes drop. The "wait, who owns this?" Slack threads stop. The customer experiences one company instead of a relay race between departments. None of that came from working harder. It came from removing the boundaries where the work was dying.