Co-Founder & CEO, BuilderLync | Founder & CEO, Capital City Roofing | RT3 Board of Directors

Roofing Contractor asked the right question in The Race to Own Roofing's Operating System, its 2026 technology special section feature reported by Tanja Kern and Art Aisner, and then, correctly, left it open:

Should contractors trust a system owned by their supplier, their licensing brand, or a neutral vendor?

I am one of the interested parties. I co-founded BuilderLync and I run Capital City Roofing on it. So read this knowing exactly where I sit. But I have also been the guy on the other end of that decision, signing up for software because it was cheap and finding out later what cheap meant.

Here is how I actually think about it.

Software is never free, it is only funded

There is no such thing as free software at scale. There is only software somebody else is paying for, and the person paying decides what gets built.

Roofing Contractor put the number on it. Construct's white-label platform, the one behind Richards CRM and several other distributor-branded systems, now drives more than $10 million in monthly material sales, because every quote a contractor builds inside it links straight to that distributor's loading dock. The article's own framing: the CRM brings contractors in, but the real business is in the material orders.

That is not a scandal. It is a business model, and a smart one. But it settles the roadmap question before you ever file a feature request. Anything that increases material throughput gets built. Anything that reduces it does not.

So when a rep tells you the CRM is free, the honest translation is: the CRM is funded by your purchase orders, and it will keep being funded as long as you keep sending them.

Three owners, three different loyalties

Your supplier. They win when you buy more material from them specifically. Your quoting tool, and therefore your margin structure, sits inside a system owned by the party across the table from you on price. Some contractors are genuinely fine with that. Most have never framed it that way.

Your franchisor. They win when your revenue grows, because the royalty is a percentage of it. That is real alignment, and it is the best argument for the franchise model. The catch is that the software is usually mandated rather than chosen, and the royalty is usually uncapped. At $500,000 in revenue, a 10% royalty is a line item. At $5 million, it is half a million dollars a year for the privilege of using a name. I wrote about why I would not sign that in 5 Questions I Wish I'd Asked Before Signing a Roofing Franchise.

A neutral vendor. They win when you renew. Genuinely neutral, which is the model's real strength, and also its limit: neutrality means nobody at that company has ever had to live with the consequence of a bad workflow decision on a hot driveway in July.

A contractor-operator. They win when the platform actually works, because they are running their own company on it. That is the case I am making, and the reason I am making it is not philosophical. It is that we had no choice.

Why we built it instead of buying it

We did not set out to be a software company. We set out to fix a specific problem and could not buy the fix.

Every module that shipped in BuilderLync V1 got specced because someone on a Capital City Roofing crew or in a Capital City Roofing office hit a wall existing software could not get past. JobCam, the proposal engine, the AI workflows, the automations. All of it was in production inside working roofing companies before an outside customer ever logged in. Roofing Contractor reported that sequence, and it is the entire product philosophy.

Sean Richard, my co-founder and our Chief Product Officer and CISO, is also Capital City's CTO. Edward Oueilhe is COO of both. Blake Grissom runs Revive Roofing and Exteriors in Charleston. James Kuntz runs Tarrytown Roofing. That is not a cap table designed to look good in a press release. It is five people who have to use the thing on Monday.

I explained the founder-side reasoning at launch in BuilderLync Launches June 1: The Roofing Operating System I Co-Founded.

The part I will not oversell

Roofing Contractor was fair to us and also fair about us, and I want to repeat the criticism rather than bury it.

The article notes that BuilderLync creates its own kind of lock-in, one attached to your whole operation rather than just your purchase order. True. If you standardize your inspection, your proposal, your scheduling, and your job documentation inside any platform, leaving gets expensive. That is what a source of truth is. Anyone who tells you their platform has no switching cost is describing a tool nobody depends on.

The difference is what the owner does with that leverage. A distributor uses it to hold your material spend. A franchisor uses it to hold your brand. We use it to keep you subscribed, which means the only way we keep you is by continuing to be worth it. I prefer that trade. You may not. Evaluate it rather than accept it.

The other criticism, from ServiceTitan's Vishal Laddha, is that a contractor-built operating system has not proven it can scale across multiple locations, trades, and brands. That one is aimed at me and it is legitimate. We are four markets in. ServiceTitan is not wrong that this is the thing we have to prove, and I would rather say that out loud than pretend V1 settled it.

What I would actually ask a vendor

Not a feature checklist. Four questions.

Who funds this, and what do they get when I use it? If the answer is materials, you now know the roadmap.

Can I export everything, today, without asking? Customers, jobs, photos, quotes, financials, in a usable format. If export requires a support ticket, you do not own your data. You are renting access to it.

Who inside your company has waited on an adjuster? Ask it literally. The answer tells you whether the roadmap comes from customer interviews or from scar tissue.

Does it hold across every division I run? Retail residential, insurance restoration, commercial low-slope, and multifamily are four different businesses wearing the same logo. A platform that only fits the first one will fail you the week you win an apartment portfolio.

Standardize first, then automate

The mistake I see most is treating a platform purchase as the operations project. It is not. It is the enforcement layer for an operations project you still have to do.

AI makes this worse, not better, because AI is an amplifier. Point it at a documented process and it compounds. Point it at a process that produces a different answer depending on which inspector showed up and it compounds that instead. This is the whole argument in Why Standardized Operations Must Come Before AI in Roofing, and it is why the technology at Capital City Roofing sits on top of a standardized 27-point inspection rather than replacing one.

Write down how your company inspects a roof. Write down what data every job must carry at every handoff. Write down who is accountable at each step. Then go buy software to enforce it.

Where this leaves the question

Roofing Contractor's framing was that the established company wants to be the system that roll-ups use, while the newcomer wants to build the roll-up itself. That is a fair description of the difference between ServiceTitan's position and mine.

What I want is narrower than it sounds. I want roofing contractors to own their operating system instead of borrowing one from whoever has the most to gain from their purchase orders. If that means you buy BuilderLync, good. If it means you build your own like Garen Armstrong did at Shamrock, also good. If it means you keep your distributor's free CRM with your eyes open about what it is optimized for, that is a real choice too.

What I do not want is for another decade of contractors to hand over the most valuable asset in their business, the record of how the work actually gets done, without noticing they did it.

Related reading:

If you are an operator working through this, the conversation starts at licensing@capitalcityroofing.net. I read every one of those personally.