Part one of this series was about capital — funding growth initiatives without mistaking early traction for proof. This one’s about what happens after the money is allocated: scale and the internal risks it exposes.
A company can look healthy right up until one request reveals how many scaling risks it’s actually carrying.
Sometimes the bigger risk is inside the building. Scaling up or down both expose it. Roadmaps need rebuilding. Supply agreements need renegotiating. It’s easy to miss how much of this happens below the surface, and a strong market won’t save a strategy that’s held back by its operations. Watching for it early is about paying attention before the numbers make it obvious.
Most folks understand that scaling up an operation brings challenges. However, even a highly scaled operation can face risks when scaling down. I remember a growth opportunity in which a customer who spends hundreds of millions of dollars with us requested a small amount of specialized compute capacity at a specific location. We do business there, but due to the high equipment failure rate for that type of compute, we had not expanded to that location. It was a simple request, but it triggered many actions that had to be executed to perfection to meet the timeline.
If I deploy such a small compute footprint, a single unit failure could reduce capacity by 25%, and we would make a large customer unhappy. If I added another unit as a spare, our margin would take a hit. The equipment lead time was 52 weeks, and the customer needed the capacity in 8 weeks. Since all my equipment was in the US, it was covered only by a US warranty, and we had no idle capacity.
To address the opportunity, we decided to get equipment from our own model factory to deliver service at the new location. That meant renegotiating warranty and support contracts while running the logistics of decommissioning, packing, transporting, unpacking, and commissioning — all in parallel with contract negotiations with the equipment supplier and the customer. While all of this was going on, we also had to figure out how we could make up for the model factory’s capacity shortfall. We did eventually grow the specialized compute business profitably, but managing the internal and contracting risks was essential to getting there.
Review leading indicators weekly, and they’ll show you where the business or an initiative is headed way before revenue shows you one way or the other. Watching only revenue, margin, and expense is watching the rearview mirror. The leading numbers are harder to find, sometimes impossible to quantify cleanly — but even a rough qualitative read beats waiting for the quarter to close.
Scale is where the capital from part one meets reality — not a review, but actual demand. Treat scaling up or down as an engineering problem, and you’ll usually catch the risk while there’s still time to do something about it. Skip that discipline, and you find out the hard way — after the initiative has already stalled.