MyCo, built from the roof down
The operating system I built to run a residential roofing business, end to end.
The action moves the job, not a status field
Status: Ready to verify. Do that one thing and the job advances itself.
The problem
I learned this business by working in it, and it ran on a stack of spreadsheets and scattered message threads. Leads, permits, material orders, collections, and crew coordination each lived somewhere different, so nobody had one true picture of a job. The pain was not theoretical. It started with a late-night call and water coming into a customer’s home.
The idea
Build the software from the inside, for the way the work actually happens. A few principles held the whole thing together: actions move a job forward instead of editing a status field, the order is the single source of truth for what gets built, and every conversation lives on the job rather than in someone’s phone.
What I built
- One app I built from scratch, spanning the whole lifecycle: CRM and estimating, job movement, customer comms, invoicing, and collections.
- A work-order-driven production workflow, so the exact materials, colors, and quantities flow from sale to crew to supplier.
- Job-centered communication that pulled customer, supplier, and crew threads out of chat and onto the record.
- An installable field app so project managers and crews worked the same system from a phone on the roof.
Impact
- Built from scratch and run as the sole developer, across three major versions over eight years.
- Revenue grew from about $9M to $30M a year on nearly flat headcount, close to twice the revenue per employee, and the system was a big part of why.
- In a group of 25 brands, it was named the leanest, generating more revenue and EBITDA per head than any other.