5d (edited) • General discussion
Case Study Discussion: $20M Construction Company
We recently worked with a company doing over $20M a year. From the outside, they looked like a large, established operation. But once we stepped inside, it became clear they were still running the business the same way they did in the early days — through back of napkin systems, scattered notes, memory, long lost threads, and whatever someone happened to remember that day.
As we analyzed how work actually flowed, the pattern was obvious: revenue had scaled, but their internal systems hadn’t. Nothing was consistent, repeatable, or easy for the team to follow. The business looked strong, but it functioned like a small shop that had never updated how it operated.
The biggest takeaway was simple: growth will expose whatever systems you didn’t build. And if everything still relies on people remembering things, the business ends up operating with stress, confusion, and unnecessary inefficiency.
Case Study Question: When transforming back-of-napkin style businesses, what are the main systems you think every business should have in place before scaling?
Extra questions: Have you seen this before? Maybe in your own company or someone you know?How often do you think big businesses are still running on small-business systems behind the scenes?
2
0 comments
Case Study Discussion: $20M Construction Company
powered by
skool.com/business-systems-engineering-2058
Business leaders learn to diagnose, design, operate, sell, and scale systems through expert-led courses, strategy sessions, and a powerful community.
Suggested communities
Powered by