The offer that priced 12 years at 4× profit
One install, 30 days, nothing a buyer prices touched. The founder left the support desk 2 months before he left the business, with the ledger to prove it.
Illustrative example, not a client. Figures are modeled.
- Shop
- Fulfillment platform, 12+ years old, about 30 people, Central Europe, founder-led: warehouse software plus pick-pack-ship for about 140 online brands
- Surface
- Support. The inbox where brands and their customers ask where an order is
- The constraint
- Listed for sale. A 5% margin, a founder who answers the hardest tickets himself, and a buyer clock already running
- What triggered it
- The first offer came in at roughly 4× profit, a quarter of the asking price, with a 12-month earnout tied to the founder staying at the support desk
- What we built
- The Handoff Install: an order-status copilot with the founder’s exceptions written as rules, a named escalation path that isn’t him, an access map, and a dated founder-hours ledger. 30 days, 3 recorded hours of his time, nothing a buyer prices changed. Paid at close
Founder hours in the support inbox, before and after, from the dated ledger: the order-status copilot answering 58% of tickets on its own and every exception routed to a named support lead.
The support-transition term in the buyer’s second offer: a 12-month earnout tied to the founder became 90 days of part-time advisory. The price stayed where the first offer put it.
A fulfillment platform in Central Europe, 12+ years old, about 30 people. It runs warehouse software and the warehouses behind it for about 140 online brands. Revenue is real: about $3.4M a year. Profit is not: about $170K, a 5% margin.
The founder listed it at $2.4M. The first serious offer came in at $700K, priced on profit, with an earnout that kept the founder at the support desk for another year.
The business makes money on volume and gives it back in people. The biggest line after warehouse labor is support: 6 people and a contractor answering about 4,200 tickets a month. Brands ask where a shipment is. Their customers ask where a parcel is. More than half of those tickets are answered the same way: open the warehouse system, find the order, open the carrier’s tracking page, type what you see.
The founder knows every exception by heart. Which carrier lies about “delivered.” Which brand’s SLA promises a reply in 2 hours. Which customer has threatened a chargeback twice. None of it is written down. So the hardest 10% of tickets still go to him, and the buyer noticed.
The buyer’s diligence questions were short. Why is margin 5%? Who answers the escalations when you leave? The founder’s honest answers were “support” and “me.” That is how a $2.4M ask becomes a $700K offer with an earnout.
He had tried the obvious fix: a help-center article titled “Where is my order?” Ticket volume didn’t move. The people asking had already tried the tracking link. They wanted someone to read 2 systems and tell them the truth.
We started with the Handoff Map, the free one. A website address and an email, and 48 hours later a written read of what a buyer’s first pass would price into his transition, split the way a seller has to split it: what can be fixed before close without touching anything a buyer prices, and what belongs to the buyer’s first quarter.
| What a buyer’s first pass flags | Priced as | Fix | Install | Lands |
|---|---|---|---|---|
| The founder is the escalation paththe hardest 10% of tickets go to him; nothing is written down | 12-mo earnout | copilot + exception rules + named lead | 30 days | Before sale |
| Carrier and brand knowledge in one headwhich carrier lies, which brand has a 2-hour SLA, who owns which login | longer transition | runbooks + access map | 30 days | Before sale |
| Support runs at 6.5 FTE for the volumea cost line the buyer will want to re-size once the copilot is proven | buyer’s upside | staffing decision, theirs | 90 days to prove | Buyer’s Q1 |
| Carrier invoice auditevery invoice line checked against contracted rate and scanned weight | buyer’s upside | audit install | 90 days to prove | Buyer’s Q1 |
Rows 1 and 2 are the install: 30 days, the product untouched, the staff untouched, the spend untouched.
Read-only
The agent drafts an answer to every order-status ticket. A person still sends every reply. Drafts are compared to what was actually sent.
The founder’s head
3 recorded walkthroughs, 60 minutes each. Every exception he handles by memory becomes a rule checked before any answer, and a page in the runbook.
Live, with a gate
Clean cases send on their own. Exceptions, angry tone, refunds route to the support lead with the reason printed. The founder is no longer in the routing. Deflection: 46%.
The ledger
No new features. Founder hours in the inbox, tickets he touched, time to first reply, reopen rate, where every exception went. Dated, exported, and handed over.
Week 2 is the part that kills most installs, and the part that matters most to a buyer. The rules came straight from the founder: carriers whose “delivered” scan needs a 48-hour wait, brands with 2-hour SLAs, customers flagged for chargeback risk. Any ticket that trips a rule goes to a person. The founder’s judgment stops living in the founder.
| Measure, 30 days live | Before | After |
|---|---|---|
| Founder hours in the support inbox, per week | 14 | 2 |
| Tickets the founder touched, per week | 95 | 6 |
| Exceptions routed to the named support lead | by memory | 100%, with the rule printed |
| Order-status tickets answered by the copilot | 0% | 58% |
| Median time to first reply | 5h 40m | 4 min |
| Reopen rate, copilot-answered tickets | n/a | 3.1% |
| Support headcount, spend, pricing, product | unchanged |
On day 9 of live running, the agent told a customer their parcel was delivered, because the carrier said so. It wasn’t. It had been left at the wrong address, and the customer was already angry. The rule existed, the 48-hour wait on that carrier’s “delivered” scan, but it only fired on tickets that used the word “missing.” This one said “not here.” We widened the rule to any delivered-but-disputed case, and that type of ticket now always goes to a person.
The second wobble was the buyer’s, not ours. Their diligence team wanted 6 months of ledger, not 30 days, before they would call the business founder-independent. They were right to. 30 days proves the routing works, not that it holds through peak season. So the second offer moved the terms, not the price: the 12-month earnout tied to the founder became 90 days of part-time advisory, and the number stayed where the first offer had put it. We wrote the 6-month gap into the transition plan before the buyer could find it themselves.
And deflection settled at 58%, not the 70% the map had modeled. The founder’s exceptions were a bigger share of the inbox than anyone guessed, including him.
Modeled, not measured, in the ledger’s own terms. The founder’s hours in the inbox went from about 14 a week to about 2, and the tickets he touched from about 95 a week to 6, all of them exceptions the rules sent to him on purpose. The handoff kit puts every exception in a file the buyer owns, the access map names who holds every login, and an internal copilot answers the team’s questions with the founder’s own rules. The support-transition term in the second offer shrank from 12 months full-time to 90 days part-time. The price did not move. The install never claimed it would.
The margin is the buyer’s to take. At 58% deflection, the support line can run leaner once the copilot has a peak season behind it: about $95K a year, modeled, and about $380K at the 4× they paid. That decision sits in the handoff kit as the new owner’s first quarter, not in the seller’s numbers, because a cost cut made while the business is for sale is the first thing a diligence team prices back out.
What we haven’t measured matters as much. Deflection through peak season: not measured, because 30 days in spring is not December. Whether the reopen rate holds once the founder is gone: not measured, because he hadn’t left yet. The carrier invoice audit: nothing until the buyer runs it.
The texture is where the change lives. The question “who answers the escalations?” has an answer that isn’t a person’s name. The founder stops being the support desk 2 months before he stops being the owner. And the buyer is looking at 30 days of dated tickets, not at a founder saying it’ll be fine.
A real flag, not a wish. The Handoff Map is free so we can say “list as-is” when there is nothing a buyer would price. Here there was.
The founder on a recorded screen, 3 times, for an hour. The exceptions lived in 1 head, so 1 head had to be walked through.
Read access to the warehouse system and the carrier APIs, and a support lead willing to be the gate for the first 2 weeks and the named escalation path after them.
The broker agreeing to put the ledger and the transition plan in the data room as exhibits, not footnotes. Brokers are paid on closing, so this one said yes in a single email.
And the patience to let the buyer ask for more months than we had. The ledger only works if a skeptic can re-run it and land somewhere close.
Find out what a buyer will price into your handoff before the buyer does.
If the read finds nothing a buyer would price into your transition, we say so in writing: list as-is. The map is still yours.