Working insurance claims, not just repair jobs

For a roofer or restoration contractor working insurance claims, the base product alone isn't quite enough — the estimate isn't just a job scope, it's the document a carrier will scrutinize before approving payment. The typical configuration pairs PaxExact Estimate, for the rooms, line items, and server-computed total, with Claim Adjustment, for the approval gate and case file that make the estimate defensible once someone whose interests don't align with yours is reading it.

That combination is optional in the sense that nothing forces it — a contractor doing straightforward repair work for a homeowner directly, with no claim in the picture, is better served by the base product alone. It's typical because contractors working claims consistently need both pieces, not because the platform requires it.

A carrier reviewer doesn't take a line item's word for it. Evidence-linked scope is live today: a line item, a measurement, and a photo are separate, linked records, so a reviewer — yours, or the carrier's — can trace any number back to what was actually documented at the property, rather than relying on a narrative written afterward. That structure holds up under exactly the kind of scrutiny a contractor working claims has to expect.

The professional approval gate is enforced in code: unapproved scope is excluded from totals and reports, so what reaches a carrier reflects a deliberate decision, not a draft that got ahead of itself. Once approved, the case file carries evidence, scope, and pricing state together, and PDF export is in beta — the underlying workflow is real and in production, and the output format itself is still being extended, so expect it to keep changing.

That combination — traceable scope plus an enforced gate plus a case file — is what gives you something to hand back when a carrier disputes a line, instead of reconstructing the justification from memory weeks after the fact.

Nothing here requires you to give up the system you already use to run your business. A dedicated mobile capture app with LiDAR-based room scanning is planned but not built — capture happens in a browser today. Connectors for CRMs and claim platforms, including a general integrations layer, are also planned, not built. Until those ship, PaxExact is meant to sit alongside your existing CRM for estimating and claim documentation, not replace it.

That's a deliberate sequencing, not an oversight: the approval gate, the evidence linking, and the case file are the pieces that make an estimate defensible, and those are the pieces built first. Field capture and system integrations extend how you get evidence in and data out, but they don't change whether the record itself holds up — which is why they're optional add-ons rather than requirements to start using Estimate and Claim Adjustment on a real claim today.