Key takeaways
  • The 8–12 point margin gap between TPA and direct work is structural and will not close through relationship-building.
  • Closing part of the gap takes operational efficiency, documentation automation and capacity discipline.
  • Program-heavy companies that hold margin cap their share at a target and protect direct-margin work.
  • Worth modeling the right mix annually based on geography, ownership goals and balance sheet capacity.

The job profitability split between TPA work and direct work in restoration sits around 8 to 12 points of gross margin, and that gap has not closed in five years. Operators who run TPA-heavy mixes either accept the lower margin or build the operational discipline that closes part of the gap. The latter is the harder path and the more durable one.

Three sources of the margin gap

The gap between TPA and direct work has three structural sources. The first is pricing. TPA programs negotiate rates that sit below the regional market. The company accepts the lower rate in exchange for inbound volume. The second is the documentation overhead. Program submissions require more documentation than direct submissions, which means more labor per job. The third is the cycle time. Program work pays slower, which costs the company working capital.

None of these three sources will close through relationship building with the TPA. They are structural features of the program design. Operators who hope to close the gap by being a favored panel member are operating on a misread of how the programs work.

The moves that close part of the gap

The operational moves that close part of the gap fall into three buckets. Operational efficiency, documentation automation, and capacity discipline.

Operational efficiency means running TPA jobs with the same crew utilization and equipment efficiency as direct jobs. Most companies accept lower efficiency on TPA work because the program inbound is unpredictable and the response window is tight. The companies that close part of the gap have built dispatch discipline that treats program work as part of the same operational system, not as a separate workflow.

Documentation automation means the photo capture, moisture logging and dry-out tracking happen with the same tooling on every job, regardless of source. The companies that have built this with field-friendly tools see documentation labor drop by 30 to 40% on TPA jobs. The labor savings flow straight to margin.

Capacity discipline means the company has decided how much program work to take and does not chase volume past the line. The trap most operators fall into is taking every program call because the volume is there. The math says some of those calls are net negative once the documentation overhead and cash cycle are accounted for.

The mix question

The question worth asking is not "how do I get more TPA work" but "what is the right mix." The right mix depends on the company's direct demand, the carrier landscape and the balance sheet. A company with strong direct lead flow can run at 15-25% TPA mix and use the programs as a smoothing tool. A company in a market with weak direct demand can run at 40-50% and accept the margin profile.

The companies that have not made this decision deliberately tend to drift toward higher TPA share over time, because the program work is easier to acquire than direct work. The drift is a slow margin erosion that does not surface as a single event.

The relationship pays in volume. Margin gains come from operational discipline, not from being a favored panel member.

What the program-heavy companies do well

The program-heavy companies that maintain margin do three things. They run intake with high consistency, which keeps the documentation chain clean from the first call. They invest in tools that automate the documentation overhead, which removes the labor cost of the additional submission requirements. They cap their program share at a target and protect direct margin work as a strategic priority.

The companies that fail at program-heavy mixes usually fail at one of these three. Inconsistent intake creates documentation gaps that drive carrier review delays. No documentation automation means each program job costs an extra half-hour to two hours of labor over a direct job. No cap on program share means the operation gets entirely shaped by program work, and direct margin opportunities get squeezed out.

The carrier relationship

The relationship with the TPA matters but in a specific way. The TPA program manager has limited discretion on rates and terms. They have meaningful discretion on volume allocation within the panel. A company that runs above-average scorecards gets more inbound. A company that drops below average loses volume quickly. The relationship pays in volume, not in margin. Operators who go in expecting margin concessions from relationship-building are operating on a wrong model.

The decision to make this year

For an operator running an unmodeled TPA mix, the work this quarter is to model it. Pull the jobs by source, by margin, by cycle time. Build the explicit comparison between program and direct work at the company's specific scale. Decide what the right mix is and what operational changes would close part of the margin gap. The math usually surfaces 2 to 4 points of margin recovery within a quarter of focused work.

Want to hear what Stoa sounds like?

Book a 20-minute demo and we will call your company with the AI voice. Hear exactly what your homeowners would hear at 2am and decide for yourself.

Book a 20-min demo