The base product is the fit — nothing else required

PaxExact Estimate doesn't assume a claim, an approval gate built for adversarial review, or a carrier reading the output. It's rooms, line items, quantities and units, and a total the platform computes rather than one assembled by hand — the same job a general contractor already does when scoping a repair for a homeowner directly. Evidence-linked scope, measurement, and server-computed totals are live today, and none of it requires anything beyond the base product.

That's a deliberate fit, not a workaround. A contractor who just needs estimating software gets exactly that — rooms, a photo tied to a room, a measurement a reviewer accepts or rejects, a total that admits when it's incomplete — without being sold a claim workflow they don't need. Organization-scoped data isolation is also live, so your estimates and your clients' information stay separated from every other organization on the platform by default, not by configuration you have to set up yourself.

Claim Adjustment adds an enforced approval gate and a case file built for an estimate that a carrier, an appraiser, or a court will examine. If you're scoping a repair job directly for the property owner, with no insurance claim in the picture, that module adds cost without adding value — the base product's own review states already cover ordinary estimate review. Add Claim Adjustment only if your work shifts into claims — for instance, if you start doing restoration work tied to insurance claims, at which point see the roofing and restoration page instead.

Two things a contractor workflow would plausibly want are both planned, not built, for any PaxExact audience today. Mobile capture with LiDAR-based room scanning — useful for a contractor scoping from the field rather than a desk — doesn't exist yet; capture happens in a web browser. Integrations, including CRM and claim-system connectors, are also planned, not built; there's no committed timeline for either.

This is a future audience in one specific sense: field-first mobile capture and connectors to the tools contractors already run aren't there yet, and it's fair to plan around that gap today rather than assume it closes on a particular date.

Nothing about using PaxExact Estimate requires replacing the CRM or job-management tool you already run. Structured connectors are planned, not built, so today PaxExact sits alongside your existing system rather than syncing with it — a REST API is in beta, with keys issued by arrangement, as the integration path.

In practice that means running PaxExact for the estimate itself — the scope, the evidence, the total — while your existing tools keep handling scheduling, invoicing, and client communication exactly as they do now. There's no migration required to start, and no assumption that PaxExact becomes your only system of record.