Scaling a trade business without losing what works

Execution: do the systems from earlier in this series still hold at double the volume?

Usually not, unless you deliberately checked — a process documented for one crew's worth of jobs tends to fail quietly, not loudly, once several crews are meant to be following it at once. This is exactly what Part 2 of this series and Part 9, on building a business that runs without you, were building toward: a documented quoting or job-handover process only counts as a real system if it survives being run by people you didn't personally train and can't personally check on every job. Growth is the moment that gets tested. A whiteboard or shared spreadsheet that worked when one person updated it becomes unreliable the moment three crews are meant to be updating it simultaneously — nobody trusts it's current, so everyone starts working around it instead of through it, and you're back to phone calls and guesswork with more people making the guesses.

Cash: why does growth make cash tighter, not easier?

Because more jobs running at once means more money tied up in materials and labour before a single invoice gets paid, and that gap — what Scaling Up calls the cash conversion cycle — widens with volume unless you actively manage it. One job running under water is annoying. Five jobs running under water at the same time, because nobody's tracking margin per job as volume climbs, is a genuine cash crisis, and it arrives quietly: the business looks busier and the bank balance looks fine right up until several invoices are overdue at once and several supplier bills land in the same week. The deposits, prompt invoicing, and active collections that were optional discipline with one crew become non-negotiable once you're carrying the cash exposure of several jobs running in parallel.

Why do crews and owners resist new systems even when the old way is visibly failing?

Because familiarity feels safer than change, even once the evidence says the old way isn't working anymore — which is the exact psychology Spencer Johnson's Who Moved My Cheese was written to explain. The book's core idea is that outcomes depend less on the change itself than on how people react to it: denial first ("nothing's wrong with how we do it"), then reluctant fear, then, eventually, adaptation — and both owners and crew move through that same arc, often at different speeds. An owner who built the original whiteboard-and-spreadsheet system has real identity attached to it; a crew member who's used the same paper docket for years has genuinely learned to work fast with it. Neither one is being lazy or difficult by resisting a new system. They're doing what people do when something familiar is taken away before something trusted replaces it.

Why would a business resist switching job management software even after outgrowing spreadsheets?

For the same reason described above, plus a very specific trade-business version of it: the "control freak" instinct to personally hold every quote, job, and decision, which feels like diligence but is actually what caps growth in the first place. Switching tools mid-growth feels risky precisely when the business is busiest — which is exactly the wrong moment to also be learning something new, or so the reasoning goes. In practice it's the opposite: the busier the business gets on the old system, the more expensive every gap in it becomes, and the switch only gets harder to make later, with more crew to retrain and more habits to undo. Who Moved My Cheese's advice here is practical rather than abstract: don't wait for certainty, and don't attempt the whole transformation in one go — take one small, low-commitment first step (one crew, one job type, one week) and let the results build the case for the rest.

How do you know your business has outgrown its own systems?

The clearest sign is the Part 2 symptoms turning up again, at a bigger, more expensive scale. Watch for: follow-ups slipping through again despite a "process" existing on paper somewhere; a job nobody's actually sure was profitable until the accountant flags it months later; you back to doing admin at 9pm despite having fixed exactly that once before; a new crew member asking the same question three different people gave three different answers to. None of these mean the earlier fixes in this series were wrong. They mean the business has grown past what those fixes were sized for, and it's time to check the Four Decisions again rather than assume what worked at five staff will hold at fifteen.

What does leadership have to do with keeping systems working as you scale?

Part 10 of this series covered owning outcomes instead of reflexively blaming the crew when something goes wrong — and that habit matters most exactly when growth is stress-testing your systems. When a process breaks at higher volume, the easy read is "the new guys aren't following the process." The accurate read, more often, is that the process wasn't actually documented well enough to survive being run by people who weren't there when you built it — which is a leadership and systems failure to fix, not a discipline failure to punish. A leader who owns that gap fixes the process. A leader who blames the crew just gets the same failure again with the next new hire.