Delivery Leak · The Sales-to-Crew Gap
The Guy Who Sold It Wasn't the Guy Who Showed Up — and the Customer Noticed.
In This Article
The crew wraps up. The work is clean — on-spec, on-time, nothing to complain about. And the customer is standing there polite, nodding, paying... and something's off. Not about the work. About whether this is even the company they talked to on the phone.
Here's the promise up front: this isn't a quality problem, and you don't fix it by working harder. It's a handoff problem, and it has a one-page fix. What got said on the sales call and what showed up in the truck are two different memories of the same job — and right now, nothing carries one into the other.
The leak: two people, two memories
Somebody took that call. They heard the specific thing this customer cared about — the color that had to match the trim, the gate that had to stay closed for the dog, the "can you be done by Friday, we have people coming." They said yes to all of it, meant it, and hung up. Then the job went on the board as a job type, an address, and a time slot. The specific promise stayed exactly where it was made: in one person's head.
The crew that shows up knows the job type and the address. They don't know the promise, because nothing ever asked them to. So they do it right — by the only version of "right" they were handed — and the customer hears themselves saying "that's not what I was told," even though nobody on your team did anything wrong on purpose.
This is a different leak from a few close neighbors, worth naming so you can tell which one you actually have. The Delivery Leak is about going quiet after the customer already said yes — no handoff problem, just silence. The Callback Leak is about redo visits after the job is finished and paid for. The Silent Job is about the crew going quiet during the work itself. This one is earlier than all three — it's what got promised before the crew ever showed up, and whether it made the trip.
Why it happens (nobody's lying)
Don't reach for blame here, because it doesn't fit. The salesperson didn't lie — they meant every word of what they promised. The crew didn't ignore anything — nobody handed them the details to ignore. This is a systems gap, not a people problem: there's no object whose job is to carry the promise from the call to the job site. Without that object, the promise simply doesn't travel. It relies on someone remembering to mention it, on the right day, to the right person — and busy days don't run on "someone remembered."
What the gap actually costs
As an illustration, not a claim about your numbers — swap in your own: imagine 1 in every 15 jobs has a detail that never made it from the call to the crew — a color, a request, a date someone was counting on. If even a third of those customers quietly downgrade from "I'd refer this business" to "I wouldn't bother," that's a steady trickle of people who were never angry enough to complain, just unimpressed enough to stay quiet next time someone asks who they'd recommend.
That trickle matters more than one awkward afternoon, because keeping a customer is the cheap side of the ledger next to replacing one — Harvard Business Review put the cost of replacing a customer at 5 to 25 times more than keeping one, citing research on customer retention economics. A gap this small doesn't cost you the job in front of you. It costs you the next several jobs that customer would have quietly sent your way.
The One-Page Handoff Sheet
The fix isn't a CRM, a new hire, or a "let's communicate better" pep talk. It's one page that travels with the job, filled out by whoever took the call, read by whoever's about to knock on the door.
The promise, in the customer's words
Not the internal job code — what the customer actually said mattered to them. "Match the trim color." "Keep the side gate shut, there's a dog." Write it the way they said it, not the way it got filed.
Anything nonstandard about the request
The one thing about this job that's different from the last twenty like it. If it's not written down, the crew will treat this job exactly like the last twenty — reasonably, since nothing told them otherwise.
Any timeline commitment made on the call
If a date got promised — even a soft one — write it down. A crew that doesn't know a date was promised can't be blamed for missing it, and the customer won't care whose fault it was.
One person, every time — whoever takes the last look before the job goes out. Not a committee, not "whoever has a minute." One name on the sheet is what keeps it from becoming everyone's job, which in practice means nobody's.
The rule that makes it work
The sheet gets written the same call, or the same day — not recalled from memory later, once the details have already gone soft. A handoff sheet filled out three days later, from memory, is just a second version of the same leak wearing a form.
This is the quiet, internal cousin of the guarantee that wins the job before the estimate — that's the formal promise you say out loud to close the sale; this is the informal habit of making sure that promise actually survives the trip to the job site, whether or not you've ever put a guarantee in writing. And if the promise does survive the trip, it's worth protecting: run the numbers on what one customer relationship is worth over years, not one job, and a single frayed handoff looks a lot more expensive.
Imagine the version where the sheet exists. The crew knocks already knowing what was promised — the color, the gate, the Friday deadline — and the customer's first feeling is being heard, not explaining themselves twice. Now imagine the version without it, a year from now: same leak, same "picky customers," same story you're still telling yourself about why this one keeps happening. One page changes which of those two years you get.
Frequently Asked Questions
Because the promise only ever lived in one person's memory — whoever took the call. Nothing carried it from that conversation to the person actually showing up to do the work, so the crew arrives knowing the job type and the address, but not the specific thing that made this customer say yes. It's not a communication failure by any one person; it's that there was never a piece of paper whose job was to carry it.
Write down what was promised the same day it was promised, on one page, and make sure it travels with the job — not a CRM overhaul, one sheet. Capture the promise in the customer's own words, any nonstandard request, and any timeline commitment made on the call. One person gives it a last look before the crew rolls. That's the whole system.
Three things, at minimum: the promise in the customer's words (not the internal job code), anything nonstandard about the request, and any date or time commitment made on the sales call. Keep it to one page. The goal isn't paperwork — it's making sure the person doing the job knows what the person who sold it actually said.
Because good work and a kept promise aren't the same thing to the customer. They're not grading the craftsmanship against a textbook — they're comparing what happened to what they were told would happen. If those two things don't match, quality doesn't cancel it out. The fix isn't better work; it's making sure what was said on the call is what shows up on-site.
Use one page, filled out the same day as the sales call, owned by one person. Software helps at scale, but the mechanism that actually closes the gap is simpler than any tool: write the promise down while it's fresh, and make sure it physically travels with the job instead of staying in someone's head.
