I joined Fletcher Wimbush on the People-First Builders podcast for a 37-minute conversation about the systems, the leadership model, and the people decisions that built Capital City Roofing from zero to a multi-market operation in under four years. The episode is titled "How Great Operators Build Better Roofing Teams with Brad Strawbridge," and it covers the territory that most roofing podcasts skip: what actually happens inside the company when you stop managing with fear and start building with clarity.

SOPs and EOS before you earn the right to scale

Fletcher's opening question cut straight to the foundation: what did we build before we started adding revenue? The answer is SOPs and EOS. Every single one. Before I hired a second sales rep. Before I opened a second market. Before I had the conversation with anyone about licensing.

Most contractors treat documentation as an afterthought. They grow first, then try to write down what they are doing. That is backwards. The time to document your operating system is when you are the one doing every job, because you are the only person who knows why things work the way they work. If you wait until you have fifteen people and four crews, you are not documenting a system. You are trying to reverse-engineer habits that are already drifting.

We implemented EOS (Entrepreneurial Operating System) at Capital City Roofing when it was still a small team. We did the V/TO. We set rocks. We ran L10 meetings every week. And we wrote SOPs for every workflow in the business: lead intake, estimation, proposal generation, production scheduling, quality control, financial close. Every single step got documented, tested, and then hardened inside the technology layer so that the system would enforce itself.

That is the foundation underneath everything else. The licensing model, BuilderLync, the multi-market expansion. None of it works without the operating system being written down and enforceable before scale creates the pressure that breaks undocumented processes.

For a deeper treatment of the EOS and systems-first approach, see On The Intelligent Builder: How I Built a Roofing System Good Enough to License.

The shift from fear-based to people-first leadership

This was the part of the conversation that gave the episode its weight. Fletcher builds his entire show around the idea that people-first leadership is not soft leadership. It is better leadership. And I had to tell him the honest version: I did not start there.

Early in my career, I managed the way most young operators manage. Pressure. Urgency. Volume. If someone was not performing, the fix was to push harder. If a crew missed a deadline, the response was consequence, not curiosity. That approach produces short-term compliance and long-term turnover. I learned that the expensive way.

The shift happened when I started asking a different question. Instead of "Why is this person not performing?" I started asking "Does this person have the tools, the training, and the clarity to perform?" The answer was almost always no. The problem was not the people. The problem was that I was asking them to execute a system that lived in my head and nowhere else.

People-first leadership, the way I define it now, means three things. First, you give people a documented system so they know exactly what success looks like in their role. Second, you give them the technology to execute that system without guessing. Third, you give them a mission that connects their daily work to something larger than a revenue target. If you do those three things, performance follows. If you skip them, no amount of pressure compensates.

I wrote about the operator-to-architect mental shift in more detail here: The Mental Model Shift From Operator to Architect. And the integrity piece of scaling, which is inseparable from people-first leadership, is covered in Brad Strawbridge on Scaling with Integrity.

Hiring through relationships and referrals

Fletcher asked how we hire at Capital City Roofing, and the answer surprised him. We do not run Indeed ads. We do not use staffing agencies. We hire almost exclusively through relationships and referrals.

Here is why that works. When you build a company that people want to work for, your existing team becomes your recruiting engine. Every good employee knows other good employees. When someone on your crew tells a friend, "You should come work here. The system is clear, the leadership is solid, and the mission is real," that referral carries more weight than any job posting you could write.

The prerequisite is that your company has to be worth referring people to. That circles back to the SOPs, the EOS structure, and the people-first culture. If your company is chaotic, your team will not bring their network into the chaos. If your company is organized, clear, and mission-driven, your team will actively recruit for you because they want to work alongside people they trust.

We also look for something specific in every hire: coachability. Skills can be taught. Systems can be trained. But the willingness to follow a documented process, take feedback without defensiveness, and improve week over week is either present or it is not. That filter has saved us from expensive mis-hires more times than I can count.

From Lowe's to entrepreneurship

Fletcher asked me to tell the origin story, and I gave him the unedited version. I drove trucks at Lowe's. I worked in sales at a roofing company. I learned the trade from the ground up, not from a business school classroom. Every operational decision I make at Capital City Roofing is informed by the years I spent doing the work myself before I had the right to ask anyone else to do it.

That matters because the roofing industry is full of people who want to own a company but have never installed a roof, never run an insurance supplement, never stood in a homeowner's kitchen and explained why their quote is higher than the storm chaser's. The credibility to lead comes from the work. It does not come from capital.

The longer version of the career journey, including the recovery story and the Walmart parking lot, is on the Roofing School Podcast episode. If you are a contractor who came up through the trades and you are trying to figure out the business side, that episode and this one are the two I would start with.

BuilderLync and the technology layer

The last segment of the conversation turned to BuilderLync and why the technology layer is non-negotiable for any contractor who wants to scale beyond one location or one owner-operator.

Here is the core problem. Most contractors try to run their operations on a generic CRM that was built for insurance agents or real estate teams. Those platforms do not understand roofing workflows. They do not enforce production stages. They do not reconcile job-level financials. They do not generate proposals from inspection data. They do not automate supplement follow-ups. They are contact databases with email sequences bolted on top, and they break the moment you try to run a real contracting operation through them.

BuilderLync was built inside Capital City Roofing by people who run roofing jobs. The CRM enforces the same workflows that our SOPs document. If a stage requires a photo, the system will not let you advance without the photo. If a job needs financial reconciliation before close, the system surfaces it. The technology does not just record what happened. It enforces what should happen.

That enforcement layer is what makes the Capital City Roofing Licensing Platform work. When a licensed operator in a different market runs a job through BuilderLync, they are running the same system, with the same guardrails, that we run in our own markets. Consistency at scale requires technology that enforces the standard, not technology that merely suggests it.

For the full breakdown of what BuilderLync does and why we built it, see BuilderLync Launches June 1: The Roofing Operating System I Co-Founded.

Where to go from here

If you are a roofing operator who wants the full operating system, the brand, the technology, and the training 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 support the mission, the Feeding the Future Project is the 501(c)(3) nonprofit working to feed one million children in ten years. Every roof we install contributes to that goal.

Thank you to Fletcher Wimbush and the People-First Builders team for the conversation. This is the kind of show that makes the industry better because it asks the questions that matter most: not how big your company is, but how well you treat the people inside it.

Keep Exploring

Related reads on leadership, systems, hiring, 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: People-First Builders, Fletcher Wimbush, Brad Strawbridge, Capital City Roofing, BuilderLync, EOS implementation, roofing leadership, people-first leadership, SOPs for contractors, contractor hiring, roofing team building, Capital City Roofing Licensing Platform, Feeding the Future Project, roofing business systems