Five things every supply chain needs before it hits $100M.

There's a pattern I've watched play out across more growing operations than I can count. The shape is identical even though the industries differ wildly — chemicals, CPG, healthcare, pharma. Every time, the operation walks confidently from $20M to $50M on the same infrastructure that got it to $5M. Then between $50M and $100M, things start breaking.

Not all at once. Not loudly. Quietly, on a Wednesday afternoon, when nobody can find an answer to a customer's question about an order they placed last Friday. Or when the third-party logistics provider sends an invoice 22% higher than the previous month and nobody can explain why. Or when finance closes the month and the inventory number on the balance sheet doesn't match what's on the shelf — and the gap has six zeros.

The fix for each of these problems individually isn't hard. But by the time three or four of them are happening simultaneously, the operation is in firefighting mode and the leadership team is too busy putting out fires to install the infrastructure that would have prevented them.

The five things below are what should be installed before you cross $50M. Some of them feel premature at $30M. They aren't. They're what makes the next $50M survivable.

1. A single demand signal

At $15M, sales calls demand. At $30M, sales calls demand and operations argues with it. At $60M, sales and operations and finance all have their own version of demand, none of them agree, and the company makes decisions based on whichever one was loudest in the most recent meeting.

The fix isn't a sophisticated forecasting tool. It's an agreement — in writing, with leadership sign-off — about which number is the demand signal, who owns updating it, how often, and what happens when reality diverges from it. That's a governance artifact, not a technology project.

The most common mistake is to skip this and buy a planning tool first. The tool can't fix an organization that doesn't agree on what the inputs are.

2. Cycle-count discipline

This is the unglamorous one. Every operation between $10M and $200M has the same conversation about cycle counts every twelve months: "we should really start doing those." Then they don't, because the warehouse is busy.

The cost of not doing it grows exponentially. At $10M, inventory variance is a rounding error. At $60M, it's seven figures of trapped working capital and an audit risk. The companies that install cycle-count discipline at $30M never have the seven-figure conversation. The companies that wait until $80M spend a year unwinding the cumulative drift.

Start with the 20% of SKUs that hold 80% of the inventory dollars. Count them monthly. The other 80% can be quarterly or annual depending on velocity. Two warehouse staff can run this. It doesn't require a system.

3. A real KPI cadence

"We look at the numbers every month" is not a KPI cadence. A real cadence has four properties:

• The same KPIs every month, defined the same way, calculated the same way
• An owner per KPI who's accountable for the result and prepared to explain variance
• A standing meeting where they're reviewed — not buried in a deck for another meeting
• An escalation path when one moves outside tolerance

At $30M, you can probably get away with five KPIs reviewed monthly: in-stock rate, OTD, forecast accuracy, inventory turns, freight cost as a percentage of revenue. At $80M the list will be longer and the cadence may go weekly for some of them. The number that matters most isn't the count — it's whether the team uses the cadence to make decisions, or whether it's just a report-out that happens before the real conversations.

The test: when a KPI moves outside tolerance, does something happen within a week? If no, you don't have a cadence — you have a meeting series.

4. Strategic supplier relationships (not just contracts)

At $15M, you have suppliers because you needed inputs. At $80M, the difference between operations that scale cleanly and operations that hit a wall is which suppliers got promoted to strategic relationships — and which ones are still transactional five years after they should have been upgraded.

Strategic means: annual reviews with the supplier's leadership, joint planning, pricing tied to volume commitments, agreed-upon escalation paths when something goes wrong, and (the hard part) a real conversation about who their next-tier customer is and how to make sure that isn't you. Companies that scale to $100M on transactional supplier relationships pay a tax in working capital, lead times, and crisis pricing.

The work to upgrade a supplier from transactional to strategic is six to twelve months of effort per relationship. You can only do it with two or three at a time. At $30M you should know which two or three. At $60M you should be halfway through the upgrade. At $80M the strategic ones should be in place and you should be working on the next tier.

5. A network/footprint that's not still on a serviette

Most operations at $30M have a footprint that was designed when revenue was $5M. One warehouse, maybe a 3PL, maybe a co-packer relationship. The footprint worked because the volume was small enough that any decent layout was good enough.

By $80M, that footprint is either constraining the operation or quietly subsidizing inefficiency. Maybe you're paying for premium freight because the single warehouse can't serve coastal customers on time. Maybe the 3PL pricing structure that worked at $10M volume is now hilariously bad on the new volume. Maybe the warehouse you have can't scale and a second one isn't planned.

You don't need a perfect network design at $30M. You need a real conversation about it. What's the demand mix going to look like at $60M, $100M? What lanes will be expensive? What capacity ceilings exist in the current footprint? At what revenue do they become binding constraints?

The answer doesn't have to be a five-year capex plan. It has to be a written set of triggers — "when X happens, we open Y conversation." That's enough to keep you from being surprised.

The order to install them

Sequencing matters. The instinct is to do everything at once. Don't. Each of these depends on something earlier being in place. The order I'd recommend, with rough timeframes for an operation at $30M–$50M:

Items 1–3 are sequential. Item 4 can run in parallel with item 3 if you have the bandwidth. Item 5 can start once items 1–2 are giving you reliable data on where the constraints actually are.

What happens if you skip them

You don't fail. You just spend three years between $60M and $100M firefighting the consequences. The operation grows, but slowly and painfully. Working capital builds up. Customer-service complaints rise. Hires that should have been impact players get consumed by remediation work. The board starts asking pointed questions about why margins keep compressing.

By the time leadership commits to fixing it, the operation has scar tissue that's harder to address than the original problem would have been. The fix takes longer. The team is more tired. The cost is bigger.

The operators who scale cleanly through $100M aren't smarter than the ones who don't. They committed earlier — usually around $25M–$35M — to building infrastructure they didn't yet need.

The headline

Nothing on this list is brilliant. Nothing here is new. Every one of these is the kind of thing a competent operator would write on a whiteboard if asked.

The difference between the operations that scale cleanly and the ones that crack isn't strategy or insight. It's the willingness to commit to governance work that doesn't look exciting on a quarterly review but is what makes the exciting things possible.

Build the boring things first. The rest gets a lot easier.