FAQ

Questions, by who's asking.

Firms, carriers, and adjusters all want different answers. Pick your tab.

For IA firm owners and ops — pricing, onboarding, configuration, volume, and what the platform does and doesn't replace in your stack.

How does per-file pricing actually work?

Every submitted file counts as one file. Volume tier is set monthly based on your trailing 30-day claim volume — so you pay the right rate as you grow, without renegotiating a contract.

Do I have to commit to a minimum volume?

No. Entry tier has no minimum. Growth and Scale are triggered by your actual volume — not a committed forecast. Enterprise terms may include a volume floor in exchange for custom SLA.

What's included in the per-file price?

The full inspection workflow, auto-assembled GLR, photo report, parties log, audit trail, and carrier-ready deliverable. Add-ons (INSPEKTstudio and INSPEKTaps) are separate monthly subscriptions.

Does the platform do measurements?

No. The platform covers the inspection workflow around the measurement — documentation, interview, GLR, photo report, parties. Your measurement provider (EagleView, Hover, etc.) stays where it is.

How does carrier configuration work?

Standard carrier configurations are included as part of onboarding. For carrier-specific customization — photo lists, interview templates, report formats — use the INSPEKTstudio add-on to tune them yourself, or we'll do it for you on Enterprise terms.

Can individual adjusters sign up?

No. The platform is firm-first — adjusters access it through their firm. The firm is the unit of accountability for carrier relationships.

What does onboarding look like?

Typical onboarding is a short kickoff, per-carrier configuration review, and adjuster orientation. Growth tier gets priority onboarding; Scale gets a dedicated success manager. Draft — final details reviewed before sign.

For carrier leadership, InfoSec, and compliance — auditability, AI posture, data handling, and how the platform fits into carrier SLAs and vendor review.

How is AI used in a live claim file?

Narrowly. The only place AI touches a live claim is the GLR narrative — generated from adjuster-verified structured inputs. No classifications, no decisions, no inventions. Every other decision on the file runs on deterministic ITTT (if-this-then-that) logic. See the AI Posture one-pager for the full story.

How are outputs auditable?

Same inputs produce the same outputs. Every rule can be traced, tested, and reproduced. Every entry is timestamped, geolocated, and attributed. The audit trail is built into the product, not generated at the end.

Can the platform be configured to our specific requirements?

Yes. INSPEKTstudio provides per-carrier configuration: photo lists, interview templates, report formats, workflow gates. Enterprise tier includes carrier-direct integration options.

How do you ensure quality across multiple IA firms?

Firm-level scoring, carrier-verified inspection workflows, and gating at the CHECKiT completeness check before GLR generation. Every file signed by adjuster, firm, and the platform before submission.

What data does the platform handle and where does it live?

Claim documentation, photos, interview responses, and structured inspection capture. Data handling, retention, and access controls are detailed in the security brief — available on request until the public version ships.

Does the platform replace our measurement provider?

No. The platform wraps around the measurement — it does not measure. Your measurement vendor (EagleView, Hover, etc.) stays in place; the platform handles the workflow, documentation, interview, GLR, and audit trail.

What SLA and integration options are available?

Enterprise terms include custom SLA, carrier-direct integration options, and a dedicated technical contact. Standard tiers include audit trail, real-time status, and the carrier-ready deliverable on every submission.

How does the platform defend against model drift or silent updates?

By design: the runtime system is deterministic ITTT. The AI layer was used at design time to engineer the workflow — a one-time job. No live model, no drift, no "the AI got updated." What worked last quarter works this quarter.

For adjusters in the field — access, measurement tools, time savings, and what changes about your day.

Do I have to pay for this myself?

No. The platform is firm-first — the firm provides access as part of their carrier-facing operation. You don't buy it individually.

Can I use the platform as a solo adjuster?

No. Access is through firm enrollment. The firm is the unit of accountability for the carrier relationship, and the platform is built around that structure on purpose.

Do I still need EagleView, Hover, or another measurement app?

Yes. The platform doesn't do measurements. It covers everything around the measurement — workflow, photo capture, interview, documentation, parties, GLR. Use your measurement provider for dimensions; use the platform for the inspection itself.

What does "40%+ less desk time" actually mean?

Post-inspection workflow time — GLR assembly, photo sorting, interview notes reconciliation, file cleanup — cut by 40%+ per claim. Verified in the field, not projected. Because the file is carrier-ready before you leave the property.

What if I don't have cell coverage at a property?

Draft: offline capture with sync on reconnect. Specific coverage details being reviewed before the public answer ships.

Who configures the carrier-specific photo lists and templates?

Firm ops. Your firm uses INSPEKTstudio (or we configure it on Enterprise terms) to match each carrier's requirements. On the claim, you just follow the prompts — the carrier-specific logic is already loaded.

How does the platform affect my file quality signal to the carrier?

Firm-level scoring is baked in — your firm sees how your files measure up on thoroughness, quality, and cycle time. The carrier sees a uniform, auditable deliverable. Your file quality signal is visible, not a guess.

Can I use my own phone or tablet?

Draft: device requirements being finalized. The short version is it's designed to work on mobile in the field — not pinned to a specific device. Final answer reviewed before sign.

Next steps