TL;DR: Search "roof restoration software" and you get storm-and-insurance CRMs. Search "roof coating software" and you get coating manufacturers. Neither one knows what a test cut is. My ClickWerxs was built around a commercial contractor whose core business is silicone restoration, so the moisture diagnosis, the mil-thickness warranty tier, and the wet-insulation contingency are first-class objects in the software.
A coatings contractor and a storm-chaser run different businesses that happen to share a roof.
The storm contractor's job starts with a claim. There is an adjuster, a scope sheet, a supplement, and a fight about line items. The software that serves that business is built around the claim.
The coatings contractor's job starts with a question: is this roof still a candidate? Everything downstream depends on the answer. What the deck is doing under the membrane decides whether there is a job at all, what it costs, and how long the warranty runs.
That question has almost no representation in roofing software. We know because we went looking, then built the missing part around a real commercial operation.
What do you actually get when you search for roof coating software?
Two categories of result, neither of which is coatings-operations software. Searches run 2026-07-27 for "roof coating software" return manufacturer system pages and contractor service pages. Searches for "roof restoration software" return roofing CRMs whose restoration vocabulary means storm and insurance work.
The closest fit is QuoteIQ, which markets a CRM for roof restoration and explicitly lists "roof coatings—silicone, acrylic, elastomeric, polyurethane systems for flat and low-slope roofs" among the work types it serves. Its feature list on that page (checked 2026-07-27) covers satellite roof measurement, before/after photo documentation, inspection forms, job costing, invoicing, self-quoting, and review generation.
What that page does not list: mil thickness, infrared moisture scanning, or test cuts.
That is not a knock on the product. It is a description of where the category's attention goes. Roofing software has spent a decade getting very good at lead-to-close and at insurance workflow. The diagnostic layer that decides whether a coatings job exists never got built, because the tools were aimed at a different buyer.
Why doesn't a storm restoration CRM fit a coatings operation?
Because the unit of work is different, and every screen inherits that difference.
An insurance-restoration platform organizes around a claim number, an adjuster, and a scope. A coatings platform has to organize around a substrate, a condition assessment, a manufacturer specification, and a warranty term. Those are not the same fields with different labels. They produce different documents and different arguments with the customer.
Here is the concession, and it matters: for the business those tools were built for, they are better than what we shipped. JobNimbus and AccuLynx have a decade of insurance workflow, integrations, and field maturity behind them. If your revenue comes from hail season, buy one of those and stop reading. We keep an honest roundup of the alternatives for exactly that reason.
The mismatch only shows up when the job is a recoat on a 200,000 square foot warehouse, the customer is a facility manager with a capital budget, and the entire sale turns on whether the insulation is dry.
How does the software decide whether a roof is a restoration candidate?
By making the test cut a record instead of a note.
In My ClickWerxs, a test cut is its own object on the inspection. It carries the cut depth, the number of layers found, the deck type actually observed, a photo, and free-text notes, and it is tied to both the roof zone and the specific building it came from. Ten cuts across four buildings stay attached to the buildings they came from, which is the only way the data survives into a proposal that prices those buildings separately.
This matters because the industry process says it does. Per West Roofing Systems, the silicone restoration process begins with "inspection with core samples to verify roof eligibility and identify wet insulation areas," and wet insulation removal and replacement is a distinct step before the coating goes down.
Alongside the cuts, each building carries condition ratings by category. The system computes a grade, the inspector can override it, and the override travels with a comment explaining why. An estimator reading the file three weeks later can see both the computed grade and the human disagreement with it.
What happens to the infrared scan after the drone lands?
It becomes part of the report instead of a link you send someone.
The aerial scan module imports thermal survey output from WebODM Lightning, the processing service behind a DJI H20T flight. Each imported annotation keeps its area in square feet, its perimeter in linear feet, and its temperature reading when one exists. The report renders the temperature column only when at least one annotation actually carries a reading, so a survey without thermal values does not print an empty column.
The original polygon geometry is stored verbatim. Thermal and standard photos are paired per annotation, with a scan-level overview image of the full annotated map and zoomed crops beneath it.
That last part came out of watching the actual workflow. The contractor was finishing a thermal survey and then handing the building owner a WebODM share link, which is a fine engineering artifact and a poor sales document. The scan now renders inside the same themed report as the rest of the inspection, with the wet areas labeled in language the owner reads rather than the language the processing software exported.
How do you bid a job where the warranty term is the product?
By making the warranty a property of the tier rather than a sentence in the cover letter.
Two things set the warranty: how much coating goes down, and which warranty the owner actually buys.
Momentive, which manufactures the Enduris silicone line, issues Limited Product Warranties in "ten (10), fifteen (15) or twenty (20) year terms," a Product Plus warranty in ten, twenty, or thirty year terms, and a Labor and Material warranty in ten, fifteen, and twenty year terms. The three are not the same product. The product warranties carry "no fees and no inspection." The Labor and Material warranty requires "pre-approval, a fee and third-party inspection."
Thickness is the other lever. Per West Roofing Systems, terms are "determined by coating thickness applied," typically 20, 25, and 30 mils for 10, 15, and 20 years. That schedule is not universal. Published schedules from other manufacturers run 30, 35, and 40 mils for the same three terms, and some price warranty length in five-year increments off a 20-mil base.
That variation is the whole reason the software does not ship a built-in warranty table. A tier stores a reference to the specific manufacturer specification it was bid against, with a link to that document, plus its own warranty fee and term. Change manufacturers and the numbers change; the structure does not.
The customer choosing between tiers is not choosing a discount. They are choosing how long the roof is covered and who stands behind the labor, and the price difference is the additional material plus, where it applies, the warranty fee the manufacturer charges to inspect and back the install.
The proposal composer treats that literally. A pricing option group holds tiers, and each tier carries its own heading, manufacturer specification reference with a link to the spec, optional warranty fee, and warranty term in years. The optional warranty fee exists as a field because manufacturers charge one: Momentive's Labor and Material warranty is the documented case, and it is a real line on a real bid. Tier line items break out labor and material separately, with labor rendered the way estimators actually write it: four men times eighty hours equals a number. Option totals and estimated tax are computed on the server on every change, so the arithmetic on a signed document is never something a browser produced.
Groups can be set to pick-one or to à-la-carte, where each option carries its own "initial here to choose this option" line. Option groups can also be assigned per building, which is how one document prices a five-building campus without becoming five documents.
What happens when the crew opens the roof and finds wet insulation?
The contingency was already signed, with its own initials next to it.
A restoration bid is conditional by nature. You priced the job off cuts and a thermal survey, both of which sample rather than reveal. When the crew tears in and finds saturated board beyond what the survey showed, somebody is about to have a conversation about money.
The proposal carries contingency clauses as structured objects, wet-board fee and change-order rate among them, each with a flag marking whether it requires the customer's initials. When it does, the initial is captured separately from the main signature, with its own image and its own timestamp, and it appears on the signed render next to the clause it applies to.
The point is not the fee. It is that six months later the answer to "we never agreed to that" is a document showing the customer initialed that specific clause on a specific date.
Why is the quote module switched off for roofing tenants?
Because we tried it the other way and it did not survive contact with the work.
Most of the platform's trades get a quote object: fast, line items, send it. When we configured the roofing pack, we turned quotes off entirely and routed every job through the proposal flow instead, including small repairs. That decision is dated in the code, April 29, and the reasoning is one line: a repair still needs photos and an explanation.
A facility manager who receives a bare number for a $4,000 leak repair has no way to approve it. They need the picture of the split seam and the sentence about what happens if it waits. The fast path was faster for us and worse for the close, so it is gone.
What does the field paperwork look like on a coatings job?
Five system form templates ship with the pack, and the hazard analysis is the one that gets used every morning.
The roofing job hazard analysis opens by capturing the conditions that determine the day's risk: crew members on site, work type, roof system, building height in feet, roof slope, and site conditions. Then it walks the foreman through fall protection specifically. The plan identifier and the primary fall protection method are recorded, followed by confirmations that anchor points were inspected and rated for at least 5,000 pounds, that harnesses were visually inspected with current date stamps, that lanyards and self-retracting lifelines were checked, that skylights and roof openings were covered or guarded, that the ladder was secured at the top and extends three feet above the eave, and that the warning line was set at least six feet from the edge where required.
That level of specificity is the difference between a form that documents the work and a form that gets clicked through. A generic checklist item reading "fall protection in place" tells an investigator nothing. A record showing which anchor points were inspected, on which building, at which height, on the morning of the incident, is evidence.
The other four templates cover the pre-job roof inspection, the daily field report, equipment inspection, and a material delivery and tear-off manifest. Inspectors can also add ad-hoc checklist items during a specific inspection without altering the company's global template, which is how a one-off condition on one building gets documented without permanently changing the form every crew sees.
Jobs also carry roofing-native fields rather than repurposed generic ones: roof system as a picklist across TPO, EPDM, PVC, built-up, modified bitumen, standing seam metal, shingle, and slate or tile; squares; and the fall protection plan identifier. Warranty term is a field on the estimate itself, with options from ten to thirty years.
What does the building owner actually receive?
A document that looks like it came from the contractor, and a signature record that holds up.
The PDF renders through a theme system with eleven bespoke themes currently live across two roofing tenants, on top of the universal set. The proposal a customer opens carries the contractor's colors and layout, not ours.
The signing engine stamps the evidence that gives an e-signature its forensic value. A SHA-256 hash of the signed content proves the executed copy matches what was sent. The signer's IP address, user agent, and electronic consent are captured server-side rather than accepted from the browser, and the consent text is stored word for word, so the record shows the exact wording the signer agreed to.
What does this pack not do yet?
Three things worth saying out loud before anyone books a demo.
The seeded price book is replacement-shaped. It ships with tear-off, TPO, EPDM, PVC, modified bitumen, standing seam metal, polyiso, cover board, and drain line items. It does not ship coating line items. Those seeds exist to make the first quote work on day one, and tenants overwrite them immediately with real numbers.
The job type list is likewise replacement-shaped: tear-off, new install, repair, leak investigation, hail inspection, gutters, ventilation. There is no "coating" job type in the default set. The coatings shape of the platform lives in the inspection and proposal layers, which is where it does the work, and in the per-tenant configuration on top.
Automatic cropping of thermal annotations is deferred. The georeferenced source file is retained specifically so that work can happen later, but today the crops are made by hand.
Everything above is verifiable in the codebase. That is the standard we hold this kind of post to, because a demo that contradicts the blog post is worse than no blog post. The same approach produced the concrete cutting configuration, which tracks blade life by the foot for the same reason this one tracks test cuts by the building.
If you want the wider category view rather than the coatings-specific one, we maintain a comparison of all-in-one roofing software covering the platforms most commercial shops evaluate.
Frequently Asked Questions
We do both replacement and coatings. Does that break the setup?
No. The pack ships replacement-oriented job types and price book seeds by default and adds the coatings layer through the inspection and proposal modules, so a shop doing both works out of one configuration. The split shows up in how a job is documented, not in whether the software supports it.
Does this handle a portfolio, or one building at a time?
Buildings are first-class throughout. Test cuts, condition ratings, thermal scans, and proposal option groups all attach to a specific building, and one proposal can price several buildings with different scopes. That structure exists because campus and portfolio work was the original use case.
Do we need a drone and a WebODM subscription to use the inspections module?
No. The thermal import is one feature inside a module that also covers checklists, zones, photos, test cuts, and condition ratings. Contractors who subcontract their thermal surveys or skip them entirely use everything else without it.
Can we get our data out?
Yes. Documents render to PDF, and record data is exportable. Ask about the specifics for your situation during setup rather than taking a blog post's word for it.
Is this ClickWerxs Command Center, or something different?
Different products. Command Center is the CRM and marketing platform. My ClickWerxs is the field operations platform, which is what this post describes. They are sold separately and a contractor can run either one alone.
If you run a commercial coatings operation and your current software makes you keep the moisture survey in one place, the tier pricing in another, and the signed contingency in a filing cabinet, the demo is the fastest way to see whether this fits. We will show you the actual test cut record and the actual signed contingency clause, on a real configured tenant, not a slide.
See My ClickWerxs or get in touch.
Sources
- Momentive Performance Materials, "Roof Coating Warranty Program" — Enduris silicone warranty terms, warranty types, and the fee, pre-approval, and third-party inspection required for Labor and Material coverage. siliconeforbuilding.com (manufacturer, retrieved 2026-07-27)
- West Roofing Systems, "What Is the Process, Warranty, and Cost of Silicone Roof Coating Systems?" — warranty term by applied mil thickness; core samples for eligibility and wet insulation identification. westroofingsystems.com (contractor, retrieved 2026-07-27)
- QuoteIQ, "CRM For Roof Restoration" — coating work types served and advertised feature set. myquoteiq.com (retrieved 2026-07-27)
ClickWerxs provides CRM software through the ClickWerxs Command Center platform. We earn revenue from businesses that subscribe. This post reflects our direct experience onboarding clients onto our platform and is not independent third-party research. Pricing and features cited are current as of publication — see clickwerxs.com/crm/features for current details.
Competitor information cited in this post is based on publicly available sources as of the publication date and is subject to change. ClickWerxs is not affiliated with the companies mentioned. All comparative claims are sourced, see source links. This post reflects operator opinion and is not legal, financial, or professional advice.
Kaleb Dickhaut is the founder of ClickWerxs and built ClickWerxs Command Center. He earns revenue from businesses that subscribe to the platform. This post reflects his direct operational experience, not independent third-party research.
Kaleb Dickhaut — Founder, ClickWerxs. Kaleb built ClickWerxs from the ground up, from payment processing ISO to the Command Center platform to the AI SEO methodology the blog runs on. He has onboarded hundreds of small businesses onto payment and CRM systems. linkedin.com/in/kaleb-dickhaut