Ask a D2C founder what their support costs and you’ll usually hear a tool subscription and maybe a salary. Ask what a single resolved ticket costs and you’ll get silence — support is the one part of the P&L that most brands have never unit-priced. Which is odd, because post-purchase is volume-dependent: every ticket has a marginal cost, and that cost quietly scales with every order you win.
Here’s the full calculation, the honest benchmarks, and the levers that actually move the number.
The formula
Cost per resolved ticket = (people + tools + outsourcing) ÷ tickets actually resolved, over the same period. Three rules keep the number honest:
- Count people at fully loaded cost — salary plus employer contributions, or the founder’s time at what an ops hire would cost. “The founder does it, so it’s free” is how the most expensive support setups stay invisible.
- Count every tool that exists because of support — helpdesk seats, the returns portal, the warranty spreadsheet’s fancier successor, tracking add-ons. Not just the one labeled “helpdesk.”
- Divide by resolved tickets, not received ones. A ticket that bounced through three replies before the actual answer is one resolution, not three touches of progress.
A worked example
A brand doing 2,000 orders a month, ~500 tickets, one support person plus a founder covering evenings and peaks:
| Position | Monthly cost |
|---|---|
| Support employee (fully loaded) | €3,200 |
| Founder overflow, ~15h at ops-hire rate | €450 |
| Helpdesk, 2 seats | €120 |
| Returns portal | €150 |
| Tracking / notifications add-on | €80 |
| Total | €4,000 |
€4,000 ÷ 500 resolved tickets = €8 per ticket — squarely inside the €5–15 range we see across D2C brands, before a single hidden cost is counted. One of our beta customers, a beauty brand, did this exact exercise and landed at around €7 — and that number is what made the problem real for them.
The hidden costs the formula misses
The divisor math is the floor. Four costs sit on top and rarely get attributed to support:
- Context switching. When resolving one case means touching five tools — inbox, shop backend, carrier portal, shipping tool, spreadsheet — the per-ticket minutes balloon, and so does the error rate. (This was us, at our own brands: the full story here.)
- The goodwill leak. Tired support buys ticket closure with money: a refund that a tracking lookup would have avoided, a replacement where a repair was due. This never shows up as “support cost.” It shows up as shrinking margin.
- Slow answers compound. Every unanswered day breeds follow-up tickets (now you’re paying twice for one question), chargebacks, and reviews that cost future revenue. Weekend response gaps are the classic version — the WISMO playbook covers that mechanism.
- Founder opportunity cost. We valued founder time at ops-hire rates above to be conservative. The real cost of a founder answering tickets is the product and marketing work not happening.
What good looks like
Rough benchmarks from the brands we work with:
- €5–15 per ticket — normal for manual support with a standard tool stack. Not a scandal; simply the cost of resolving cases by hand.
- €3–5 — a tight manual operation: consolidated tools, good self-service, templates that actually fit.
- €1–2 — only reachable when a large share of cases resolve end-to-end without a human touch, and the humans handle only genuine judgment calls. The beauty brand above went from ~€7 to ~€1.50 this way.
The step from €5 to €3 is optimization. The step to €1.50 is structural: it requires automation that doesn’t just draft replies but executes the resolution — the tracking lookup, the refund, the return label. Drafting tools cap out quickly, because typing was never the expensive part of a ticket; per-seat and per-ticket pricing also has a way of eating the savings it promises.
How to cut the number, in order
- Measure it first. One month of data, the formula above. Without the baseline you can’t tell optimization from theater.
- Prevent tickets upstream. Realistic delivery promises, honest dispatch emails, proactive delay notices. The cheapest ticket is the one never opened.
- Consolidate the tool stack. Every extra tool adds minutes to every case that touches it — and its own subscription.
- Automate resolution, not typing. Judge any automation by one question: did a human still have to look something up or click something? If yes, you’ve bought faster typing at the old cost structure.
- Re-measure and expand category by category. WISMO first, then standard returns, then the harder categories — with an approval mode until each one has earned trust.
We went through this exact curve with our own two hardware brands — the numbers, including what we’d tell other founders, are in the ONNOA & LOVETALES case study. If you’d rather see your own numbers than ours: the live demo analyzes your store and estimates your cases and savings — no signup required.