The standards body has a conflict problem
The episode's core complaint about the IICRC is structural. A nonprofit that sets the standards also sells the training and certification against those standards, and the hosts question why board members are allowed to run consulting businesses on the side while shaping the rules everyone else pays to follow.
The sharpest example raised: an S500 chairman who also serves as director of mitigation services at ITEL Laboratories. In the hosts' view, those two roles should not belong to the same person. Add carriers telling contractors they need the certification to receive carrier work, and the episode's conclusion is that the organization's objectivity cannot be taken on faith.
The practical position both hosts land on is simpler than any standard: if material is wet, dry it until it is no longer wet. Certifications tell you less about a technician than the industry pretends.
If material is wet, dry it until it is no longer wet.
Software that stores data is running out of road
The second argument: most restoration software charges monthly to store your data and never touches the work that eats your week. Now that operators can point AI directly at estimates, carrier communications, and admin, the hosts argue those companies are in a race to the bottom, because building your own workflow in-house is becoming cheaper than renting theirs.
The window they put on it is about 18 months. Operators who implement real AI for job performance and AR tracking pull ahead. Bolting a chat feature onto an existing app does not count; the episode's point is that a wrapper around a general model adds nothing you could not do yourself.
There is also a data warning worth taking seriously: read the user license agreement on your CRM. The hosts' claim is that many of them reserve the right to use and sell your data, and that operators rarely check where it goes.
The customer gets the invoice, every time
On getting paid, the episode is blunt: you do not have a contract with the insurance company, so it does not owe you money. The invoice goes to the customer. One host describes building his company on deposits, sometimes equal to the deductible amount but never called a deductible, because the wording changes what you can enforce.
The strategy is to arm the client. A paid-in-full or owed invoice gives the homeowner standing to tell their carrier this is a cost incurred, reimburse me. Coach them on what to say, because an uncoached policyholder gets worn down by carrier scare tactics about what was and was not needed.
And use discretion on the back end. If the client is actively fighting to get your bill paid, give the carrier reasonable time to reimburse before adding interest. The goal is carrier money, not squeezing a homeowner who does not have nine grand sitting in checking.
If you run TPA work, stop doing the admin by hand
The hosts agree the TPA admin burden is where margin dies: reviewer responses, comparative estimates matched line by line, timeline forms. None of it is billable on a TPA program, and all of it is exactly the kind of structured, repetitive writing AI already handles well.
The math in the episode: five to ten hours saved per project manager today, and for a midsize shop running 260 to 300 TPA jobs a year, thousands of admin hours annually. The hosts' position is that a contractor who automates that layer succeeds on TPA work where others burn out, because the burden shrinks from hours to minutes.
