I have been appointed to the Board of Directors of RT3, the Roofing Technology Think Tank. RT3 is the industry body that exists to push roofing forward through technology, software, AI, and the operational practices that connect them. The appointment is for 2026 and sits alongside my recent Forbes Business Council membership and my appointment to the National Roofing Apprenticeship Program Board.
This piece is the longer version of why the seat matters, what I plan to do with it, and how it connects to the rest of what we are building.
What RT3 actually does
RT3 brings together contractor leaders, manufacturers, technology builders, and consultants who care about the same question: how does roofing modernize without losing the operating discipline that makes a great contractor a great contractor in the first place. The Think Tank publishes research, hosts working sessions, and runs events that pull the industry forward on practical technology adoption.
It is not a vendor showcase. It is a working room where operators and builders work through what is actually changing in the field, what tools are worth adopting, and what the standards should be for everything from data integrity to AI deployment in customer-facing workflows.
Why this appointment matters
Three reasons.
First, the roofing industry is in the middle of a real technology transition. AI, voice systems, autonomous coordination, and standardized data pipelines are no longer optional for operators who want to scale without breaking. Most of the industry is unprepared. The Think Tank is one of the few rooms where this conversation is happening with the seriousness it deserves, and I want to help shape the outcome.
Second, Capital City Roofing and BuilderLync sit at the leading edge of this transition. CCR runs a 10-agent AI workforce in daily operations. BuilderLync is an AI-first CRM and operating platform built from the ground up around the workflows that contractors actually run. The lessons from operating these systems in production at a real roofing company are the lessons RT3 needs in the boardroom.
Third, the Capital City Roofing Licensing Platform is built on the thesis that the right operating system, supported by the right technology, is what separates contractors who scale durably from contractors who burn out. A seat at the RT3 board lets me advocate for that thesis at the level where industry standards are set.
What I plan to bring to the board table
A working operator's perspective. RT3's strength is that it includes builders who actually run companies, not just analysts and consultants. I plan to bring the daily reality of running a Georgia roofing company with 10-plus AI agents in production, a licensing platform, and a co-founded technology company. The conversations I want to push on the board:
- What operational discipline has to exist before AI gets layered on. Most failed AI implementations in roofing are not technology failures, they are operating-system failures. The Think Tank should publish a clear standard.
- What contractor-friendly technology actually looks like. Too much of what gets sold to roofers is general-purpose software with a roofing logo on it. I want to push for purpose-built standards that respect how roofing actually works.
- What the next decade of training looks like. This connects to my parallel appointment to the National Roofing Apprenticeship Program Board. The workforce question and the technology question are the same question.
How this fits the broader arc
I have written before about the mental model shift from operator to architect and the discipline of scaling with integrity. Board service belongs in that arc. The strongest founders are the ones who eventually serve the industry that made them, not just their own company.
That is what I intend the RT3 appointment to be. Service to the trade, with the operator's perspective in the room.
If you operate a roofing company and want to talk through what AI-first operations actually look like in practice, the contact page is the place to start.