You Grew. Your Systems Didn't.

A property management company in Chicago grew from 3 buildings to 12 in four years. Revenue tripled. Team doubled. The portfolio was thriving by every metric that makes it into a board meeting.

The maintenance director's tracking system? The same spreadsheet he'd built when they had 85 HVAC units. Now it had 340.

At 85 units, he could hold most of it in his head. The spreadsheet was a backup for his memory. At 340, the spreadsheet was the only system. And it couldn't keep up.

$4,200 spent on a compressor still under warranty. Forty-seven units with unknown warranty status. Thirty-four with overdue maintenance he didn't know about. Estimated annual cost of the gap between what the spreadsheet showed and reality: $38,000 to $52,000.

The business had grown. The system hadn't. And the distance between the two was widening every month.

This isn't a property management problem. It's a growth problem. Every SMB that's doubled in size in the past few years has a version of Dave's spreadsheet somewhere. A system designed for the old business, running badly in the new one, costing money nobody tracks because nobody realises the system stopped working three growth spurts ago.

When you grow faster than your systems, you accumulate what I think of as systems debt. It works like financial debt. It compounds quietly. And you don't feel the weight of it until something breaks.

At 3 buildings, Dave's spreadsheet worked. It was accurate enough because he could verify it against his memory. The debt was zero.

At 6 buildings, it was straining. He updated less frequently. Some data was stale. Debt was accumulating, but invisibly. Nothing had broken yet.

At 12 buildings, it was failing. $4,200 warranty mistakes. Unknown statuses across 47 units. Missed maintenance on 34 more. The debt was compounding. Every month he didn't address it, the gap between the spreadsheet and reality grew wider.

Systems debt shows up in predictable ways across every industry we've worked with.

The person who "holds it all together" becomes a bottleneck. Fiona at the Edinburgh physio clinic. Dave in Chicago. Karen in Portland. The system runs because they run. Their knowledge, their memory, their Friday updates are the only thing keeping the process alive.

Errors increase but nobody's measuring them. Portland's 5.6% engagement letter error rate. Nashville's missed conflicts buried in a spreadsheet. Edinburgh's 3-of-14 referrals that vanished. Each one invisible until something forced a count.

The team adds workarounds instead of fixing root causes. Calendar reminders on top of spreadsheets on top of email folders on top of "can you just check with Dave?" Three layers of manual intervention to accomplish one outcome. When the fix needs a fix, the system is long overdue for replacement.

New hires make the problem worse, not better. More people updating the same spreadsheet means more inconsistency, not less. More people running the same manual process means more variation, not less. You hired to add capacity. You added complexity.

The cruel part: systems debt is invisible during the growth phase. You're too busy growing to notice the systems lagging behind. Revenue is up. Clients are happy enough. Nobody's complained loudly enough. You only see the debt when something breaks: a chain collapse, a bar complaint, a lost patient, a voided warranty.

By then, it's been compounding for years.

These show up in every business that's outgrown its infrastructure. You'll recognise yours.

One person is the system. If removing one person would cause an entire process to stop, that's not a role. It's a single point of failure. Fiona was the referral system. Dave was the equipment tracking system. Karen was the engagement letter system. The process runs because they run. When they're sick, on holiday, or give notice, the system stops.

You've added people but not capacity. You hired to handle volume. But the new hires are doing the same manual work in the same manual way. Revenue per employee is flat or declining. You're scaling linearly. Every pound of new revenue costs roughly one pound of new expense. The headcount grew. The output per head didn't.

Your workarounds have workarounds. Calendar reminders to update the spreadsheet that tracks the data that gets copied into the report that goes to the Monday meeting. Three layers of manual intervention to produce one outcome. When the Charlotte brokerage was using a Google Sheet plus calendar reminders plus Monday reviews plus a part-time admin calling agents to ask "did you do the thing," that's four workarounds stacked on top of a system that stopped working at 15 deals. They had 45.

You can't answer basic questions without digging. "How many units have overdue maintenance?" "How many candidates haven't been contacted in 7 days?" "How many engagement letters are still unsigned?" If answering any of these requires someone to go search, count, and compile, you're running blind at scale. The information exists somewhere. It's just not accessible without a human excavation project.

Your error rate goes up with volume. During your busiest periods, tax season, Q4, summer maintenance, errors spike. Not because your team gets worse under pressure. Because the system can't handle the throughput. The process was designed for 85 units, not 340. For 200 clients, not 412. For 15 active deals, not 45. Volume didn't break the team. Volume broke the system.

Three questions for each of your major processes. Answer honestly.

How many units did this process handle when it was designed? And how many does it handle now? Dave's spreadsheet was built for 85 HVAC units. It now handles 340. That's a 4x increase on a system that was never redesigned. If the ratio is 2x or more, the process is almost certainly under-scaled. It might still be running. But "running" and "working" aren't the same thing.

Would this process survive if the person who runs it disappeared for a month? Not "could someone muddle through." Would it actually function? Would referrals still get tracked? Would milestones still get monitored? Would engagement letters still go out with the right fee structures? If the answer is no, the process isn't a system. It's a person. People get sick. People take holidays. People quit. Systems don't.

Does this process get worse during your busiest periods? If errors spike, deadlines slip, or things fall through cracks when volume increases, the process has hit its ceiling. It works at normal throughput. It fails at peak. And businesses don't grow at normal throughput. They grow through peaks.

Score each process. Three concerning answers means critical systems debt. Fix now. Two means significant debt. Plan the fix. One means early debt. Monitor it. Zero means the system scales. Protect it.

Apply this to your five highest-volume processes. The ones scoring worst are your Dave's-spreadsheet moments. Systems designed for a business that no longer exists, running on borrowed time.

The companies that grow without drowning share a few patterns.

They upgrade systems at growth thresholds, not after failures. When they double in size, they ask: "Which systems are still running on the old version?" They don't wait for a $4,200 warranty mistake or a bar complaint to force the conversation.

They automate before the ceiling hits. Dave's agent costs $280 per month. At 85 units, it would've been premature. At 340, it was overdue. The sweet spot was somewhere around 150 to 200 units, when the spreadsheet started straining but before mistakes forced the issue. The firms that get this right build the system during the strain, not after the break.

They separate the person from the system. Fiona, Dave, and Karen are all exceptional at their jobs. But their value isn't in updating spreadsheets. It's in judgment, relationships, and decisions that no system can make. Freeing them from manual tracking lets them do the work that actually grows the business. The Edinburgh clinic didn't grow by hiring another practice manager. It grew by giving Fiona her 10 hours a week back. Chicago didn't hire another maintenance coordinator. It gave Dave real-time visibility instead of a monthly spreadsheet marathon.

The pattern is consistent. Growth is good. But growth without system upgrades is just scaling your problems alongside your revenue. The businesses that thrive past the doubling point are the ones that recognise the difference between growing pains and systems debt, and stop treating the second as if it's the first.

Pick your highest-volume process. The one that's straining. The one where the person running it has been saying "I need to get better at this" for two years but never has time.

Ask the three questions. If the answer is "this was designed for a smaller business," it's time.

Not because the process is bad. Because the business it was built for doesn't exist anymore. And the gap between then and now is costing you more every month.

Want to find where the systems debt is highest? The AI Bottleneck Audit walks you through the scale audit for your specific business. Five minutes. No pitch.

Want to see how 33 businesses found the gap? Download Unstuck. Every one discovered a system designed for a business that no longer existed.

by SP, CEO - Connect on LinkedIn
for the AdAI Ed. Team