TL;DR
- The operator’s first move is refusing the default answer. Whether the obvious solution is too big (the vendor everyone uses) or too cheap (the quick workaround), it is almost never sized to your actual constraint, and right-sizing the fix is the entire job.
- Ops Intel: Long-term 3PL storage fees are now standard, not the exception (nearly half of warehouses charge them, up from under a quarter a year ago), and they punish exactly the low-volume, slow-moving SKUs that a “save the rent” move creates.
- Do this week: Before you accept any “this is just how it’s done” solution, write down the one constraint that actually binds you (a date, a cash number, a risk). If the default answer isn’t sized to that number, it isn’t your answer.
On this week’s episode of the podcast, a founder told me how she saved an entire product line in seven days. She runs a Canada-wide food brand that packs every order fresh, and she had launched a chocolate category that grew into three-quarters of her orders. Then May turned hot, the first “my chocolate arrived melted” email landed, and she went looking for a fix. Everyone pointed her to the same packaging solution, the one the whole category uses. She called them. The answer: one-month lead time, one-truckload minimum. Her response, more or less, was “I can’t wait a month, I can’t use a truckload, thank you, goodbye.” She found a scrappier fix instead, validated it by leaving boxes in the sun outside her warehouse for a day, and shipped. She solved it herself. I just got to watch, and then to think about why the move she made is so rare.
I have spent years walking into operations and finding where they leak, and I have had to make that exact call more times than I can count. Not the chocolate. The move underneath it: looking at the answer everyone agrees on and saying “that is not sized for me.” It is the most valuable instinct an operator has, and it is the one founders most often talk themselves out of.
The default answer is provisioned for someone you’re not
Sometimes the default answer is too big. The industry-standard solution, the one the established players use, comes with a one-month lead time and a truckload minimum because it is built to serve big, predictable buyers. That is not a flaw in the vendor’s eyes. It is the whole point of their business. It is simply not sized for a lean brand that needs a working answer by the weekend.
Sometimes the default answer is too cheap. The obvious shortcut, the “let’s just throw something together for now,” is sized for a fantasy in which the shortcut stays temporary. It never does.
Either way, the mistake is the same: taking the constraints of the default answer as if they were the physics of your situation. The operator’s job is to know they are not, fast enough to go find the answer that actually fits. Two examples from my own work, one in each direction.
Too cheap: the stopgap I refused to build
A founder once asked me to stand up a makeshift fulfillment setup. It would have worked, sort of, for a while. It also carried real safety and liability exposure, and I was fairly sure it would be scrapped within months. The expedient answer was right there. Build the workaround, bill for the hours, move on.
I said no. I would not put my name behind a setup I knew was wrong, and I would not bill for it either. The line I used with the founder was, “you would be changing four quarters for a dollar.” It looks free because you are not counting the labor to build it, the risk it carries, and the cost to tear it out and do it properly later. The default felt cheap because nobody was pricing the parts that make it expensive.
That is the tell for a too-cheap default: it only looks like a bargain because the real costs are sitting off the invoice. The operator’s move is to put them back on.
Too big: the cost cut that quietly bleeds the business
The opposite direction is an obvious cost cut. You look at the bill from a third-party warehouse and the instinct is to pull fulfillment in-house to "save the rent." Everyone nods at "cut the overhead.
But the math usually runs the other way. A fulfillment warehouse tends to bill to receive each case, then again to pick each case, so every box gets touched, and billed, twice. And when a product is lot-controlled, many warehouses will not stack two lot codes on one pallet, so you pay monthly rent on several half-empty pallets of the same item. Cases sit in storage that may never clear. The "save the rent" default is not the fix. It is a wrong-sized answer to the wrong problem.
The fix is almost never leaving the warehouse. It is sizing the production runs and the sell-through to the pallet, so you never pay rent on a lot code that will not move. Smaller lever, right size.
Why defaults are almost always mis-sized
It is not random that the obvious answer so rarely fits. The standard, professional solution is priced and provisioned for companies operating at steady state, at volume, with quarters of planning runway. That is exactly what you do not have in the moment a problem actually bites. And the cheap, expedient answer is priced for a version of events where it stays temporary and nothing goes wrong, which is exactly not how operations behave under load.
So the bigger and more “standard” the solution, the more it assumes you are big and planning ahead. The cheaper and more “obvious” the shortcut, the more it assumes you are lucky. Your real constraint, the date, the cash, the risk that actually binds you, is the one thing neither default is measured against. Until you measure it yourself.
The right-sizing playbook
Pull the instinct out of the chocolate and the warehouse and it is a repeatable sequence. Four steps.
1. Name the one constraint that binds, first. Before you evaluate a single option, write down the real limit: the date it has to be working, the cash you actually have, the risk you cannot carry. Not “soon,” not “cheap.” A number. This is the spec everything else gets measured against, and it is the one thing that never survives the vendor call or the “let’s just” conversation unless you write it down before.
2. Disqualify by the constraint, not by prestige or by price. Any option whose lead time lands past your date is out, no matter who uses it. Any option that only looks cheap because the real costs are off the invoice is out, no matter how obvious it seems. “Everyone uses this” and “this is the cheap way” are both disqualified until they meet the number.
3. Widen the search past your category. The founder on this week’s episode got her answer from frozen-food shippers, not other snack brands. When the in-category default fails your constraint, the fix usually lives in an adjacent industry that solved a harder version of your problem for its own reasons.
4. Validate as cheaply as reality allows. You will not have time or budget for a perfect test. Design the smallest one that tells you the truth. Boxes in the sun for a day. One node, one week. One SKU, one run. The goal is not certainty. It is enough signal to commit without betting the season.
None of this is exotic. It is what good operators do under pressure and mostly cannot explain afterward, which is why it does not get taught, and why capable founders freeze in exactly these moments, negotiating inside the vendor’s month or talking themselves into the workaround, instead of throwing both defaults out and sizing the fix to the number that actually matters.
The founder with the melting chocolate did not have a big team or a cold-chain consultant. She had a constraint she refused to negotiate and a loading dock with good afternoon sun. On that week, that was not a smaller version of operational competence. It was the whole thing.
Next week’s episode goes inside a very different operation, an AI company, and what “forward deployed” means when the product itself is intelligence.
Share this with the COO or VP Ops you think would find this pattern familiar. The ones who have accepted a vendor’s lead time, or a too-cheap shortcut, as gospel at least once, and paid for it.
OPS INTEL
Europe’s heatwaves are slowing parcel delivery 👀
Carriers shorten shifts and sorting hubs slow down in the heat, and the brands running a single carrier feel it worst. Heat is a supply-chain constraint most DTC brands price in a season too late, which is the whole chocolate story.
Long-term 3PL storage fees are becoming the norm, not the exception ↑
Nearly half of warehouses now charge long-term storage fees, up from under a quarter a year ago, and they can double the rate on a slow-moving SKU. The per-touch and per-pallet math is sized for full-pallet movers and quietly eats small brands, which is the exact “save the rent” trap in this issue.
Enterprise AI agent pilots are still failing around 88% of the time 👀
Across McKinsey, Gartner, and cross-sector studies, the failure is not model quality, it is scoping and ownership: nobody owns the process the agent is supposed to run. AI does not fix a process that has no owner, which is exactly where next week’s episode goes.
For DTC brands, “retail-ready” is now an operational bar, not a milestone 👀
Retailers have tightened OTIF thresholds and chargeback enforcement, and a single non-compliant case can cost around 3% of a brand’s cost of goods. What kills small brands at the shelf is rarely the product, it is the default process accepted under pressure.
If your operation has a “we’ve just always done it this way” you can’t quite defend, reply to this email. I read every one.
This week’s episode: “My Chocolate Melted in Transit: We Fixed It in One Week,” with Mariela Katz of Nutterie. Watch or listen, the link is below.