Product
Capability matrix
8 capabilities live · 7 in beta · 10 coming soon · 11 planned. Every status below is backed by evidence a reviewer can check — never promoted without it.
Most recent verification pass 2026-09-25. Each entry shows the date its own evidence was last checked.
- LIVE
- Deployed and usable end to end, for the scope its description states.
- BETA
- Deployed and usable, with limited validation or scope; the description says what the limit is.
- COMING SOON
- Partially built; not yet usable by a customer.
- PLANNED
- On the roadmap; not built.
Capture & evidence
Photo evidence capture (web)
LIVEPhotos are attached to specific rooms and damage records on a claim, from a web browser.
Capture sessions and photo attachment to rooms/line items are in production. Capture happens in the browser today; there is no dedicated mobile app.
Verified 2026-09-13
Learn more →Room measurement with accept/reject review
LIVERoom and floor measurements are recorded as server-computed records that a reviewer accepts or rejects.
Room dimensions and floor area are computed server-side and carry an accept/reject state. An uploaded LiDAR room scan can propose dimensions (see LiDAR room-scan upload), and those go through the same accept step. Net wall area with opening deductions is in development.
Verified 2026-09-25
Learn more →AI-assisted damage observations from photos
BETAA photo can be analyzed into a proposed, evidence-linked damage observation that always requires human review.
Proposals are tied to the specific photo and fail safely (no photo, no proposal). They never count toward an estimate until a professional accepts them. Limits: analysis depends on a configured vision provider and is unavailable if none is configured, in which case nothing is proposed or written.
Verified 2026-09-25
Learn more →Native mobile capture app (built-in LiDAR scanning and video)
PLANNEDA dedicated mobile app that scans rooms with the device's LiDAR sensor and records photos and video straight into a case is on the roadmap.
Not built: there is no native capture app. A scan made in another scanning app can already be uploaded from the web (see LiDAR room-scan upload, BETA).
Verified 2026-09-25
Learn more →LiDAR room-scan upload (RoomPlan JSON, or text-layer USDZ)
BETAA LiDAR room scan made in another app can be uploaded to a room on a case; PaxExact derives proposed dimensions from it that a reviewer accepts before they reach the estimate.
Limited validation: Apple RoomPlan JSON import is built to Apple's published format but has not yet been proven on a real device export. USDZ is accepted only when its root layer is text (.usda), as in the one real export tested end to end; binary USDZ is rejected. Only the RoomPlan JSON export is read as a room model: any USDZ yields just the overall bounding dimensions of the capture, not a detected room, openings or a confidence score. A RoomPlan export proposes length, width and height only for a simple rectangular room. Upload is from the web capture panel; there is no native capture app.
Verified 2026-09-25
Learn more →Video evidence
COMING SOONVideo attached to rooms and damage records alongside photos, and used as evidence.
Partially built: a video file can be uploaded as evidence on a captured room from the web capture panel and is stored with it. Nothing is done with it yet — video is not processed, AI analysis is photo-only, and there is no in-app video recording.
Verified 2026-09-25
Learn more →Net wall area with opening deductions
COMING SOONDoors and windows recorded as openings and deducted from wall area server-side.
In development: the quantity pipeline subtracts opening square footage when a measurement carries it, but nothing records that figure yet. An uploaded RoomPlan scan does record each door, window and opening's width and height as proposed measurements; they are not yet deducted from wall area.
Verified 2026-09-25
Learn more →
Scope & estimate
Evidence-linked scope records
LIVELine items, measurements and photos are separate, linked records — a line item can be traced to the evidence behind it.
The data model and the links are in production. Line items are entered by the estimator, or suggested from an accepted damage observation (see suggested line items, BETA); either way a line item keeps any link it has to the evidence behind it, and a hand-entered line may have none.
Verified 2026-09-25
Learn more →Suggested line items from accepted damage observations
BETAAn accepted damage observation — AI-proposed from a photo or recorded by hand — can be turned into suggested line items with quantities, which count toward nothing until a professional approves each one.
Limited scope: specific repair operations are suggested only for water damage to walls, ceilings, floors and baseboards, and smoke, soot or mold damage to walls, ceilings and floors, and water damage to a floor does not include replacing the floor covering; other observations produce a line with no code or price unless exactly one code fits. The room needs an accepted measurement first. Nothing is added to a total until a professional approves each suggested line.
Verified 2026-09-25
Learn more →Professional approval gate before pricing and reporting
LIVEA scope cannot become a priced, reportable estimate without an explicit approval step by a professional.
Enforced in code, not policy: unapproved scope items are excluded from totals and reports.
Verified 2026-09-13
Learn more →Estimate review, revisions and line-item approve/reject
LIVEEstimates carry revisions; each line item has a review state and stale lines are blocked from silent edits.
Approve/reject per line item and revision tracking are in production.
Verified 2026-09-13
Learn more →Server-computed totals with completeness and RCV state
LIVETotals are computed by the platform in cents (ROUND_HALF_UP) and report whether they are complete or partial, and whether they are RCV-only.
A missing price is never shown as $0. Overhead & profit is the percentage saved on the estimate (the web app pre-fills 20%), applied server-side. Sales tax is a single rate the professional enters, applied to the subtotal only (tax_state APPLIED, or NOT_APPLIED when no rate is entered); there is no taxable-base split, rate lookup or jurisdiction model.
Verified 2026-09-25
Learn more →
Pricing
Source-tracked, confidence-scored pricing
COMING SOONEvery unit price carries a source class (catalog, your own data, manual, unverified), a reason code and a confidence — but no production pricing catalog is loaded yet.
The architecture is built and in production; the data is not. The one connected pricing source is an explicitly sandboxed vendor feed guarded so it can never be mistaken for production data. Treat pricing as not yet a source of real numbers.
Verified 2026-09-13
Learn more →Pricing suggestions from your organization's own observed prices
COMING SOONPaxExact can suggest a unit price from your own prior priced lines once enough independent projects support it; a human price always wins.
Mechanism exists (minimum 2 distinct projects); depends on accumulated customer data. Your prices stay private to your organization unless you opt in.
Verified 2026-09-13
Learn more →
Commercial
Commercial coverage records and co-insurance calculation
BETACommercial coverages are recorded per estimate and a co-insurance calculation can be run, accepted or overridden with a documented reason.
Released to production in September 2026. Limits: one versioned co-insurance formula is applied, subtracting the deductible after the co-insurance ratio and before the policy limit, so policy forms that apply the deductible differently are not modeled; inputs are entered by the professional. Calculations are explicit about readiness — if a required input is missing, the calculation says so instead of guessing.
Verified 2026-09-25
Learn more →Business income / business interruption calculation
COMING SOONA business-income calculation is attached to the case, with accept and override steps recorded.
Partially built: the platform can record financial inputs, compute a business-income calculation, and record its accept or override, but there is no screen for it in the application yet and it is not included in the case report. The loss period is entered by the professional; there is no period-of-restoration logic.
Verified 2026-09-25
Learn more →
Contents & valuation
Contents inventory (itemization by room)
COMING SOONContents items can be recorded per room on an estimate.
Partially built: the platform can store contents items per room and includes them in the case report, but there is no screen for entering them in the application yet, and they do not count toward estimate totals. Valuation of contents is not built (see below).
Verified 2026-09-25
Learn more →Contents valuation, depreciation, RCV/ACV
PLANNEDReplacement-cost and actual-cash-value valuation with documented depreciation is designed but not in production.
Totals today are RCV-only and say so (valuation_state RCV_ONLY_NOT_DEPRECIATED). Depreciation and ACV are not computed.
Verified 2026-09-13
Learn more →
Case file & review
Claim / case-file workflow
LIVEEstimates, evidence and calculations live on a case, and a computed case report is generated after approval.
In production for early-access users. The case report is generated only after the professional approval step.
Verified 2026-09-13
Learn more →Defensible case-file export (PDF)
BETAThe approved case file exports as a PDF that carries evidence, scope and pricing state together.
The workflow is real and the PDF downloads from the case. Limits: it can be generated only after the professional approval step, it does not include business-income calculations, and it is not yet filed into the claim's document records; the output format is still being extended.
Verified 2026-09-25
Learn more →
Integrations
Caller-supplied external reference on estimates
BETAEstimates created through the API carry your own claim or job reference for reconciliation.
Available on the developer API (BETA; keys issued by arrangement). Limits: the reference is free text only, stored with the estimate for your own reconciliation; structured two-way synchronization is planned, not built.
Verified 2026-09-25
Learn more →Outbound webhooks
PLANNEDSigned event notifications (estimate created, approved, exported; case status changed) to your systems.
Not built. Today's webhook infrastructure only receives events from vendors; nothing notifies customers.
Verified 2026-09-13
Learn more →Salesforce connector
PLANNEDCases, accounts, contacts, properties and estimate status kept in step with Salesforce.
Not built. No Salesforce code exists; the connector is a roadmap item designed on the same API and webhook foundation.
Verified 2026-09-13
Learn more →Other CRM and claim-system connectors
PLANNEDConnectors for other CRMs and operational platforms, built on the same API and webhook foundation.
Not built. No connector code for any named CRM, claim system or accounting product exists.
Verified 2026-09-13
Learn more →Import and export of estimates, contacts and properties
PLANNEDBulk import and export in open formats so your data is never trapped.
Not built for PaxExact data. Existing import/export tooling in the platform serves internal pricing-catalog and lead workflows only; the approved case file exports as PDF (see Case file).
Verified 2026-09-13
Learn more →Organization data export
PLANNEDExport of an organization's complete estimate, evidence and case data on request.
Not built.
Verified 2026-09-13
Learn more →
Back office & portal
Organization roles and access controls for customer teams
COMING SOONPer-user roles and permissions inside a customer organization, on top of today's organization-scoped API key scopes.
Organization-scoped isolation and scoped API keys exist; a per-user role system for customer organizations is not yet exposed.
Verified 2026-09-13
Learn more →Intake, client and property records
PLANNEDLead and client intake, client records and property/claim records as the system of record.
Not available as a PaxExact module. Internal intake and records tooling exists for the operation PaxExact was built in, with that operation's business rules; a general-purpose module is a roadmap item.
Verified 2026-09-13
Learn more →Assignments and communications
PLANNEDAssigning cases to staff and communicating with clients from the case.
Not available as a PaxExact module (see Intake, client and property records).
Verified 2026-09-13
Learn more →Reporting
PLANNEDOperational reporting across cases, estimates and approvals.
Not built as a customer-facing module.
Verified 2026-09-13
Learn more →Case-file audit log
COMING SOONA chronological, exportable log of every change to a case and its estimate.
Partially built: a case records five lifecycle events (created, step advanced, estimate linked, professional approval, report generated) and the platform can return them in order. It does not yet record every change, cannot be exported, and is not shown in the application. Revision history on estimates is live; the agreement-signing engine has its own audit trail.
Verified 2026-09-25
Learn more →Client portal
COMING SOONA client-facing view of claim status, messages and documents for the cases you choose to share.
A claimant portal (status, timeline, messages, documents, and requests from the adjuster that the client answers) runs in production for the operation PaxExact was built in, and per-organization branding and domains are built. Not done: it reads only that operation's claim records, not PaxExact cases or estimates; it can be switched on for an organization only by PaxExact staff, with no PaxExact module entitlement or purchase path; and it has no client approval step.
Verified 2026-09-25
Learn more →
Platform
Organization-scoped data isolation
LIVEEstimates, evidence and prices are scoped to your organization; cross-organization access returns not-found, never a hint that data exists.
Enforced at the API layer.
Verified 2026-09-13
Learn more →Developer API (organization API keys, sandbox and live)
BETAA REST API with scoped organization keys, separate sandbox and live environments, rate limits and a versioned estimate contract.
Deployed and answering in production. Limits: keys are issued by PaxExact staff by arrangement — there is no self-serve key signup — and the scope is estimates, rooms, line items and pricing lookup, which has no production price catalog behind it yet (see source-tracked pricing). There are no webhooks, connectors or usage quotas yet.
Verified 2026-09-25
Learn more →Client agreements & e-signature add-on
COMING SOONA separately branded add-on for client agreements and electronic signature, integrated with the PaxExact case file.
The signing engine exists; commercial packaging, branding and templates are not final. Name to be announced.
Verified 2026-09-13
Learn more →Self-serve subscription checkout
PLANNEDPaxExact will be sold as a monthly subscription; self-serve checkout is not enabled and early access is by invitation.
Not built: there is no PaxExact checkout or subscription code. No public pricing has been published. Early-access terms are arranged directly with each organization.
Verified 2026-09-25
Learn more →