What the business looked like in February 2020
I joined Beehive Plumbing as Operations Manager at the start of COVID. The timing made me nervous. The business was doing about $4M a year, serving around 500 homes annually, with roughly 30 employees. Matt, the owner, had been working with a Theory-of-Constraints coach for years — reading the books, attending the workshops, understanding the ideas — but he hadn't been able to make the transition from knowing TOC to running his business on it. The gap between the methodology and the daily execution was the work I was hired to close.
I showed up with an MBA, a decade of business coaching at Rich Dad Poor Dad where I'd worked with more than a thousand small business owners, and zero practical exposure to TOC. I had never read The Goal. I thought I knew how businesses worked.
Two weeks in, I realized what Matt already knew: most of what I'd been trained to think about business — the Lean frameworks, the Six Sigma thinking, the conventional ops-manager playbook — was structured around optimizing every part of the system at once. TOC says the opposite. There's one constraint. Everything else either supports it or gets in its way. You don't fix ten things. You find the one thing and you fix that, relentlessly, until it stops being the constraint — and then you find the new one.
The constraint we actually had
Residential plumbing at our scale looks simple from the outside. A new housing development needs plumbing. You schedule your crews. They go do the work. You bill. Next development.
The reality is different. The work comes in phases — rough-in, top-out, trim — and each phase has its own preconditions. The walls have to be open for rough-in. The drywall has to be up for top-out. The house has to be close to finished for trim. Miss a precondition and the crew rolls to a jobsite that isn't ready, loses a day, burns fuel, and has to be rescheduled — which cascades into every other job they were supposed to hit that week.
The constraint was not crew capacity. It was not materials. It was not sales. The constraint was scheduling accuracy. Specifically: the gap between what the office thought was ready and what was actually ready on the jobsite.
Every time a crew rolled to a not-ready site, we lost a full crew-day. At our volume, we were burning several crew-days per week. The math: those lost days were the ceiling of the business.
What we did about it
TOC gives you five steps: Identify the constraint. Exploit it. Subordinate everything else to it. Elevate it. Then find the new one.
Identify
We instrumented every crew dispatch. Every not-ready rollout got logged with a reason code. Within three weeks we had enough data to see the pattern: three categories of readiness (information, materials, labor) accounted for nearly every failure, in roughly that order of frequency.
Exploit
We built a release gate. A job couldn't go to the crew until all three categories were confirmed — not assumed, not "probably fine," confirmed. The office kept full visibility of every job, at every stage, at all times. But the crew-facing schedule only showed work that had cleared the gate. This meant crews spent their time doing work, not discovering half-ready jobsites.
Subordinate
Every other function in the business had to align around that release gate. Sales couldn't promise start dates that weren't achievable given material lead times. Purchasing had to own readiness on a per-job basis, not a per-PO basis. Supers had to sign off on site readiness the day before, not the morning of. The gate was the constraint, and everything else worked in service of it.
Elevate
Once the gate was running clean, we raised throughput. More crews, same discipline. The material cost savings came from being able to forecast demand accurately once jobs stopped getting rescheduled — procurement went from reactive to planned. Productivity climbed because crews stopped losing days.
Find the new constraint
Three years in, the constraint was no longer scheduling. It was customer acquisition. So we moved there.
The numbers
Between 2020 and 2023:
Revenue: $4M → $40M (10x in three years)
Homes served per year: ~500 → 1,750 (3.5x)
Employees at time of sale: ~30 → 155 (5x peak)
Material cost savings: ~$2.5M per year at peak — from being able to procure against real schedules rather than reactive ones
Productivity gain: 150% — measured as jobs completed per crew-day
Sale price in January 2023: $40M, acquired by Intermountain Home Services
These are not claims made in isolation. Beehive Plumbing is a real, operating company in Utah. The acquisition by Intermountain Home Services on January 18, 2023 is on public record — see the verification section below.
Want to see the architecture running in your shop?
Sub Structure is the same release-gate system, rebuilt as software you can use on day one.
Start Free →Why I built Sub Structure
After Beehive, I started a cabinet manufacturing and install company of my own — Cabinets Express, a smaller shop doing about $5M a year with 25 employees. I wanted to apply everything I had learned at Beehive to a new trade.
I bought BuilderTrend. On paper it had everything: project management, scheduling, communication, document storage. In practice it failed for our team on every dimension that actually mattered.
Salesmen hated it — every minute spent updating BuilderTrend was a minute not spent selling. Purchasing used it but it was reactive, not proactive — we found out about problems instead of preventing them. Real communication happened on Slack and got manually translated into BuilderTrend by a single employee whose entire job became "BT translator." That role was a full FTE whose whole function was to keep two systems agreeing with each other. If anyone on the team stepped away from the tool for a week they came back completely lost.
I tried patching it with N8N automation between Slack and BuilderTrend. I built connectors. I built pipelines. I got it partially working. And sitting there looking at my half-glued Rube Goldberg machine, I realized: it would be less work to build a system designed around the release gate from the beginning than to keep retrofitting one that was fighting me.
That's Sub Structure. It is the operational architecture from Beehive, rebuilt as software that any trade team can run on day one, without hiring a TOC coach and without me standing in their ops manager's office.
What this means for your business
You probably don't need to scale 10x in three years. Most of the teams we talk to want something more immediate: a week where no crew rolls to a not-ready jobsite. A Monday morning where the office and the field agree on what's happening. A quarter where reschedules don't eat the margin you just sold.
Sub Structure is built around that. Three gates — Information, Materials, Labor. A release mechanism that makes the gate the system of record, not a post-hoc dashboard. A field view that only shows ready work. An office view that shows everything, always.
It is the same architecture that took Beehive from $4M to $40M. You get it in software, on day one, without the three years of trial and error that built it.
Independent verification
- PitchBook company profile: pitchbook.com/profiles/company/266727-34 — confirms acquisition by Intermountain Home Services on January 18, 2023.
- Beehive Plumbing website: beehiveplumbing.com — the operating business, headquartered in Salt Lake City, UT.
- Parent company: Intermountain Home Services — Beehive operates as a subsidiary since the 2023 sale.
Will Marsh served as Director of Operations at Beehive Plumbing from 2020 through 2023. This case study is his firsthand account of that period. The acquisition and timing are verifiable through the PitchBook profile linked above and other public records; the revenue, headcount, homes-served, material-cost-savings and productivity figures reflect business performance during his tenure. Sub Structure has no ongoing commercial relationship with Beehive Plumbing or Intermountain Home Services, and this case study is not an endorsement by either company. Individual results in any operational system depend on execution — this describes what happened at one company with the sustained commitment of a full ops team.