Adding People to Broken Systems Just Scales the Chaos
Most contractors get this backward. They hire first, then scramble to build systems once the chaos hits.
I've watched company after company push for big growth, jumping from $100K to millions in annual revenue, only to stumble because there was nothing underneath to hold the weight.
When an owner brings me in to help scale, they're usually surprised by my first move. I don't start hiring. I build systems.
And some of those systems look almost insultingly small.
Small systems, outsized impact
Take file folder management. Seems trivial, right?
But when you're standing on a jobsite and a GC asks about a specific document, and you can't put your hands on it in seconds, three things happen at once:
You look flustered
You look uninformed
You look disorganized
That undermines confidence in your ability to manage the daily chaos of a growing company. And on a jobsite, confidence is currency.
Meanwhile, hiring costs you thousands before anyone swings a hammer: the posting, the interviewing, your time, the onboarding, and the months before they're fully productive. Replacing someone who leaves costs a multiple of that. And they will leave if they can't succeed in the seat you put them in.
Even substantial companies lose traction when the underlying organization is a mess. Can yours afford that kind of waste while you're trying to grow?
The real obstacle isn't technical
Here's what most business advice won't tell you: the hardest part of implementing systems isn't the system. It's the people.
When I introduce something new, especially something small like a folder structure or a file naming convention, I get two kinds of responses.
Some people recognize why it matters and get on board. We structure it, explain the benefit, roll it out.
Others resist. And not passively. They'll deliberately misuse the new system to prove they were right all along, that structure is unnecessary and their way works fine.
My strategy with those folks? Let the explosion happen.
Sounds dumb and impractical. Let me tell you something. I've spent 30 years raising daughters who are a lot like me and boys masquerading as grown men. I've tried every tactic I can imagine, and the one that works best is this:
Let them.
Let them muck it up.
Let them prove me right.
Then, when somebody's standing there fumbling for an answer in front of a sub or a GC, I've got it in seconds. I've pulled more people out of that fire than I can count with nothing but decent information management and document control. They usually take the credit. Fine. The system is what saved them.
Reality is the most persuasive thing in the room.
Measure something
Most small companies have no way to tell whether a system is working, which creates blind spots that make smart scaling impossible.
Start with productivity from your timecards. How long does each phase actually take?
Rough-in
Panel wiring
Room completion
Trim and fixtures
Break the job into pieces and track how long each piece takes. That works in any trade. Then, as you roll out changes (file structure, coordination protocols, communication standards, RFI process), watch those numbers.
Implement one change every two weeks. Not five at once. One. That gives you time to work out the kinks and actually see the impact.
Comprehensive metrics take months to build. Trend lines show up within weeks, and the trend is what tells you whether you're on the right road.
Not everyone needs every piece of information
Effective systems recognize that information should flow to the people who act on it, and not much further.
In construction there's already a chain of command. A first-year apprentice doesn't need access to the RFI log or a direct line to the PM.
Superintendents and foremen make sure the crews are working from the latest drawings
Project managers maintain the current contract documents, including RFIs and ASIs
PMs keep vendors and subs informed of changes, and update purchase orders and contracts to match
I use logs and folders and share selectively. Copying everyone on every email creates so much noise that people start ignoring the messages that actually matter.
Project management software handles this automatically, which is great when you can afford it. When you're small, those subscriptions get expensive fast, and a disciplined folder structure with a couple of maintained logs will carry you a long way.
Either way, the goal is the same: free your PM to manage obstacles instead of managing information.
The $100K-to-millions reality check
When I walk into a company trying to make that jump, here's what I usually find.
A shared drive with some folders. A log or two nobody has updated in months. The only consistently maintained records are accounts payable and receivable, and even there the supporting documentation is often missing.
That becomes a real problem the first time there's a dispute and finding the backup means hours of hunting.
And these companies are usually hoping to hire an admin who magically arrives knowing how to build all of this.
Some admins genuinely can. But it's bad business to pay someone very little for work that's this load-bearing, and it's worse business to expect it from someone you hired to answer phones.
Systems aren't administrative overhead. They're a strategic asset.
Make it survive after the consultant leaves
Sustainability needs a human champion.
I always train one person, usually an office manager or a project coordinator, to keep adjusting things after I'm gone. That builds internal ownership while I stay available for the occasional question.
Good onboarding and clear processes also keep people longer. Employees who can actually find what they need and understand what's expected don't quit in month four.
The growth paradox
Here's the uncomfortable part most growth advice skips.
Adding people to broken systems amplifies the dysfunction.
When you hire before you have systems, you're institutionalizing the chaos. New people learn the broken process, invent workarounds, and pass both along. Before long you've got tribal knowledge and no institutional knowledge, and the whole thing lives in three people's heads.
The answer isn't hiring better people. It's building something better for people to work inside.
Where to start
Start with information management. How documents get stored, named, shared, and updated. It's the least glamorous and highest-leverage thing on this list.
Implement one change every two weeks. Not a transformation. One change.
Turn tribal knowledge into written process. If it only lives in somebody's head, you don't own it.
Watch your productivity numbers for trends, not perfection.
Adapt to the people you actually have. Cookie-cutter rollouts fail because they ignore human dynamics. Sometimes the fix is changing an email subject line or moving a field on a form.
Train a champion before you need one.
Only accelerate hiring once the systems hold.
The companies that thrive aren't the ones that grow fastest. They're the ones with a foundation strong enough to hold the weight.
Systems before scaling isn't just good practice. It's the difference between growth that builds something and growth that implodes.
FAQs
Should I hire or build systems first? Systems first, at least for information management. New hires learn whatever process exists when they arrive, so hiring into chaos means you've now got more people doing it wrong. And, no. It’s not your admin’s job to get this right for you. This is your business and she doesn’t get paid enough to manage the stuff you’re already handling her.
What's the first system a small contractor should build? Document and file management. Where drawings, submittals, RFIs, change orders, and billing backup live, how they're named, and who updates them. Everything else depends on being able to find things within seconds when you’re on the phone in the middle of a stern negotiation.
Do I need project management software to scale? Eventually it helps a lot. Early on it's often an expense you can't justify, and a disciplined folder structure with maintained logs will get you further than most people expect.
How do I get my crew to actually use a new system? Roll out one change at a time, show the win, and train one internal champion to own it. Expect resistance. Some people only believe it after the old way fails in front of somebody who matters.
Frankie Allen spent 30 years in construction, from drafter to journeyman electrician to project manager on residential, commercial, hospital, and federal jobs. Rippling Roots provides fractional assistant project management to contractors in Alaska, Hawaii, and the Western U.S.
