The operating platform, if you don't already have one

Back Office is intended for firms that don't already run an operating platform — a growing public-adjusting practice tracking intake on a spreadsheet, or an estimating organization with no system connecting a lead to a case to an assignment. If that's your situation, Back Office is meant to become the place all of that lives, instead of PaxExact being one more disconnected tool alongside the spreadsheet.

If you already run a CRM or a claim platform, you don't need this — see Integrations instead. Back Office is built to replace a gap, not to compete with a system you've already invested in.

Everything Back Office is meant to do is planned, not built, with one exception. Intake and client/property records, assignments and communications, and operational reporting are all roadmap items today — there is no customer-facing module for any of them yet. Internal tooling exists for the specific operation PaxExact was originally built inside, but it carries that operation's own business rules and isn't available as a general-purpose module.

The one piece further along is organization roles: PaxExact already enforces organization-scoped data isolation and scoped API keys in production today, live at the platform level. A per-user role system on top of that — different permissions for different people inside the same customer organization — is coming soon, meaning it's built or in active development but not yet in production use.

The intended shape is a single record that starts at intake — a lead or a referral becomes a client and property record — and carries through an assignment to a specific person on your team, communications tied to that case, and reporting that rolls all of it up across your operation. None of that requires you to give up the base estimating product; Back Office is designed to sit around it, not replace it.

Don't wait on Back Office if you already have an operating system that works. PaxExact's Integrations module is where a scoped API, and eventually webhooks and connectors, are meant to let your existing platform stay the system of record while PaxExact handles the estimate and, if you use it, the claim workflow. Back Office solves a different problem — the absence of any operating platform at all.

If you're unsure which describes you, the test is simple: do you already have one place where a lead becomes a client, an assignment goes to a specific person, and someone can pull a report across your whole caseload? If yes, that system stays your system of record, and Integrations is the module to watch. If no — if that's currently a spreadsheet, a shared inbox, and someone's memory — Back Office is the module meant to close that gap once it ships.

Because almost all of Back Office is planned rather than built, don't build a workflow around it today. A firm evaluating PaxExact now should treat the base Estimate product, and Claim Adjustment if it applies, as what's actually usable, and treat Back Office as a reason to keep watching rather than a reason to wait before starting. Organization roles are the one piece close enough to call coming soon; everything else described here has no committed date.