I joined Owen Gagne on The Intelligent Builder podcast for a conversation about the operating system underneath Capital City Roofing, how it became good enough to license, and why the technology layer is what makes the entire model work at scale.

The episode is titled "This Roofing Operator Built a System So Good He Licensed It." That is the thesis. Not that we built a good company. That we built a system underneath the company that someone else could operate and get the same results. Here is the full conversation.

Why Owen's show is different

The Intelligent Builder is not a show about motivational hustle culture. Owen Gagne built it around a specific thesis: residential contractors fail because they lack systems, not because they lack talent. The show brings on operators who have actually built the systems and asks them to break those systems down for an audience of contractors trying to do the same thing.

That framing is exactly why this conversation worked. Owen was not interested in revenue numbers or growth hacks. He wanted to understand the mechanics. What workflows exist inside Capital City Roofing? How do handoffs work between sales and production? What data gets captured on every job? How does the technology enforce the system instead of just documenting it? Those are the right questions.

If you run a contracting business of any kind and you are not already subscribed to The Intelligent Builder, fix that.

The operating system that became licensable

Owen's central question was simple: What does the operating system actually consist of? Not the marketing version. The real one.

Here is what I walked him through.

Lead flow and first response

Every lead that enters Capital City Roofing gets captured, scored, routed, and responded to within sixty seconds. Not sixty minutes. Sixty seconds. The system does not depend on a sales rep checking their phone. BuilderLync handles the capture and initial response automatically, and the lead routes to the right person based on geography, service type, and availability.

For a longer treatment of the first-response system and what it means for close rates, see How I Use a 10-Agent AI System to Close More Deals Without More Leads.

Standardized estimation and proposal generation

Every proposal that leaves Capital City Roofing uses the same pricing logic, the same scope language, the same terms, and the same presentation format. There is no "senior rep discount" or "rookie upcharge." The system produces consistent proposals regardless of who runs the appointment. That consistency is what protects the brand when you have multiple operators running under the same name in different markets.

BuilderLync generates the proposal from the inspection data. The rep fills in the measurements and damage findings, and the system produces a branded, itemized proposal that the homeowner can review immediately. For the deeper dive on why CRM-generated proposals are the only way multi-operator models survive, see The CRM Question Every Franchisor Gets Wrong.

Production workflow and quality control

Every job moves through the same stages: sold, scheduled, materials ordered, crew assigned, production complete, final inspection, customer sign-off, financial close. No stage can advance without the required data fields being populated. That is the enforcement piece that most companies miss. They document the workflow but do not enforce it.

I built the production workflow inside Capital City Roofing over two years of running jobs myself. Then I codified it inside BuilderLync so that the workflow runs whether I am in the building or not.

Financial close and reconciliation

Every job reconciles at close. Revenue, material costs, labor costs, subcontractor costs, permit costs, supplement recovery. The system produces a job-level P&L that tells you exactly what your margin was on every single project. Most roofing companies only see margin at the quarterly level, which means they are averaging their winners and their losers and hoping the average is good. Job-level reconciliation tells you which crews, which reps, and which service types are actually making money.

Why licensing instead of franchising

Owen asked the question every contractor asks when they hear the word "licensing": Why not just franchise?

The honest answer is that traditional franchising imposes structural constraints that hurt the operator and benefit the franchisor. A franchise model typically requires the franchisee to use the franchisor's technology (which is usually a white-labeled generic CRM), follow rigid operational playbooks that may not fit the local market, and pay escalating royalty fees on gross revenue regardless of profitability.

The Capital City Roofing Licensing Platform is structurally different. A licensed operator gets the brand, the operating system, the technology stack on BuilderLync, and the training through Capital City University. But the operator retains operational flexibility on local hiring, local marketing, and local relationship building. They run the playbook. They do not report to a district manager.

For the full comparison of licensing versus franchising from the operator's perspective, see 5 Questions I Wish I'd Asked Before Signing a Roofing Franchise. For the company-side breakdown of what a licensed operator actually inherits, see What Roofing Operators Inherit on the Capital City Licensing Platform.

BuilderLync as the infrastructure layer

Owen spent a significant portion of the conversation on BuilderLync specifically, because the technology layer is what separates this licensing model from every other brand-license arrangement in home services.

Most licensing and franchise models hand you a subscription to Salesforce or HubSpot or a GoHighLevel white-label and call it "technology support." That is not technology support. That is a software subscription. The operator still has to configure it, customize it, maintain it, and train their team on it.

BuilderLync was built inside Capital City Roofing by people who had to live with what they shipped. The CRM, the AI agents, the proposal engine, the dispatch system, the financial reconciliation, the customer communication sequences, the supplement tracker, the voice AI for after-hours calls. All of it was designed for roofing contractors by roofing operators. V1 trial is open as of June 1, 2026.

For the technical walkthrough of what BuilderLync does and how it differs from generic contractor CRMs, see BuilderLync Launches June 1: The Roofing Operating System I Co-Founded. For the AI-specific architecture, see What I Taught at Jack's AI Automations Masterclass.

The mission layer

The last part of the conversation went where it always goes in long-form interviews: the mission. Capital City Roofing is the engine. The Feeding the Future Project is the destination. Every roof we install contributes to a 501(c)(3) nonprofit working to feed one million children in ten years. Every licensed operator on the Capital City Roofing Licensing Platform participates in that mission structurally.

Owen made the point on the show that mission-driven businesses tend to attract better talent and retain them longer. I agree. The mission is not a recruitment tactic, but it functions as one because people want to work for something that matters beyond this quarter's revenue target.

For more on why the mission is structural and not cosmetic, see Why Community Impact Must Be Part of Every Business.

What contractors should take from this conversation

If you watched the episode or read this far, here are the three things that matter most:

  1. Document your operating system before you try to scale. If you cannot write down every workflow in your business and hand it to someone who has never worked for you, you do not have a system. You have habits. Habits break at scale.
  1. Enforce your system with technology, not with willpower. A documented process in a binder does not prevent anyone from skipping steps. A CRM that will not let you advance a job stage without the required fields prevents everyone from skipping steps. That is the difference between BuilderLync and a spreadsheet.
  1. Connect the work to something larger than revenue. The operators who last are the operators who have a reason to keep going when the market gets hard. Revenue is not a reason. Revenue is a scorecard. Mission is a reason.

Where to go from here

If you are a roofing operator who wants the full operating system, technology stack, and brand on day one, the Capital City Roofing Licensing Platform is the structure. The conversation starts at licensing@capitalcityroofing.net. I read every one of those personally.

If you want the technology layer alone for an existing roofing or home services operation, BuilderLync is available standalone.

If you want to talk about advisory, speaking, or any of the topics covered in this episode, reach out directly.

Thank you to Owen Gagne and The Intelligent Builder team for the conversation. This is the kind of show that makes the industry better because it asks the right questions.

Keep Exploring

Related reads on operating systems, licensing, and scaling with discipline:

About Brad Strawbridge

Brad Strawbridge is the Founder and CEO of Capital City Roofing, a GAF Master Elite, GAF Commercial Certified, and CertainTeed ShingleMaster Premier roofing company serving Greater Atlanta and Nashville with residential, multifamily, and commercial roofing. He is also Co-Founder and CEO of BuilderLync, an AI-driven CRM and operating platform built for contractors, and Founder of the Feeding the Future Project, a 501(c)(3) nonprofit working to feed one million children in ten years. Brad is an active member of the Forbes Business Council, RT3 (Roofing Technology Think Tank), NRCA, and The Roofing Alliance.

bradstrawbridge.com | LinkedIn | capitalcityroofing.net

Tags: The Intelligent Builder, Owen Gagne, Brad Strawbridge, Capital City Roofing, Capital City Roofing Licensing Platform, BuilderLync, roofing licensing, roofing franchise alternative, contractor operating system, AI roofing business, roofing CRM, home services scaling, Feeding the Future Project, roofing business systems, roofing company automation