The problem
Most personal-property claims begin with reconstruction from memory
- Receipts and serial numbers are often incomplete or unavailable.
- Evidence gets assembled after the loss, when confidence is lowest.
- Claims teams receive screenshots, emails, notes, and PDFs with no clean structure.
The approach
ItemRecover helps policyholders prepare before the loss
- Digital Item Passport: one structured record per item.
- Proof Pack PDF: a clean document with receipts, serials, timestamps, and photos.
- Claim Mode: a guided flow for the panic moment when something goes wrong.
Separate insurance track
Do not start with "onboard every policyholder"
A realistic insurer conversation starts smaller: prove that better pre-loss records create cleaner claim evidence, then decide whether a policyholder pilot or portal workflow is worth expanding.
Insurance portal preview
The partner portal already has the shape of the pilot
42
Policyholder items imported
Batch upload and item list views for partner-side review.
9
Possible match alerts
The portal can surface matches and mark review status.
API
Keys and webhooks
Useful after the PDF-first pilot proves enough value.
Claim evidence board
The handoff should look reviewable before integration work starts
Insurers do not need a big systems project to understand the value. The first useful artifact is a clean packet that shows what the customer owned, what proof exists, and what a handler should ask for next.
Policyholder packet
Production camera kit
Completeness signal
What is ready, partial, or missing
The claim handler sees receipt status, photo coverage, serial notes, and export readiness before asking the customer to resend evidence.
Pilot proof
PDF first, data later
A partner can review Proof Pack PDFs during a pilot, then move to structured exports once the workflow proves useful.
Review artifact
Give claims and product teams something they can circulate
The insurer flow now has a visible queue and a shareable one-pager, so a partner can move from "interesting" to "I can show this internally" without waiting for a custom deck.
| Claim packet | Customer proof | Handler view |
|---|---|---|
| High-value camera kit Theft reported May 2026 | Receipt, serial, lens photos, IR Tag lookup | Ready to review |
| Home office laptop Water damage | Receipt, incident photo, repair quote | Needs valuation |
| Site equipment loss Tagged work vacuum | Receipt, tag photo, assignment note | Partial proof |
What your team receives
Evidence your claims team can review faster
Start with Proof Pack PDFs and exports. Move to structured data only when the partnership is ready.
Proof Pack PDF
A structured item summary with receipt, purchase date, serial number, photos, and supporting evidence.
Inventory export
A customer-level overview when multiple items are affected in the same event.
Signed JSON feed
A machine-readable handoff for future integrations when the pilot proves real value.
Pilot model
A simple way to test the partnership
- 1. Invite 50-100 policyholders into a co-branded pilot.
- 2. Let them document belongings before they need to claim.
- 3. Use Proof Pack PDFs as the first operational workflow.
- 4. Review documentation completeness, customer feedback, and claim-prep efficiency.
Why ItemRecover
- Before loss, not only after: evidence is created in advance.
- Consumer-simple, insurer-useful: easy enough to adopt, structured enough to review.
- Realistic to pilot: no rip-and-replace project required.
Let’s talk
Start with a practical insurer conversation
Tell us a little about your team, portfolio, or pilot idea. We will follow up with a focused conversation about fit, not a generic sales pitch.
Best use cases
Home contents, valuables, equipment, and personal-property claims where proof quality matters.
Lowest-friction pilot
Co-branded onboarding, Proof Pack PDFs first, structured exports later if the pilot proves value.
Response expectation
We aim to reply within one business day for insurer partnership requests.