Before the claim
Create the record while photos, receipts, serial numbers, policies, and repairs are still easy to find.

Photos, policies, repairs, receipts, and source-attributed address context organized into private property records and evidence-ready packets.

Founder story
ClaimGuardian starts from a practical Florida reality: when the weather turns, the property file should already exist. The product is shaped around capture on glasses, confirmation on iPad, and web-based review or packet export.
Create the record while photos, receipts, serial numbers, policies, and repairs are still easy to find.
Keep the packet boundary clear so a claim, repair, sale, or review gets only the evidence it needs.
Preserve originals, provenance, and review notes so the property history stays usable.
How it works
The workflow keeps AI suggestions, human confirmation, source context, and packet boundaries separate so reviewers can understand what they are seeing.
Use Meta Ray-Ban Display glasses for hands-free evidence candidates, then bring the session to iPad.
Review, annotate, enrich, and approve evidence on iPad before anything becomes packet-ready truth.
Use the web surface for review, export, homeowner inventory, claim evidence, and admin workflows.
Value
ClaimGuardian does not collapse private evidence and public intelligence into one exposed feed. It keeps the boundary visible.
Rooms, items, receipts, warranties, policies, repairs, notes, and review decisions stay workspace-private.
Parcel, permit, flood, and public-place intelligence can explain the address without exposing private records.
Frozen snapshots preserve scope, redactions, manifest details, and the reason the packet was created.
Track what exists, where it lives, and what proof belongs with it.
Attach purchases, serials, coverage notes, replacement values, and service history.
Keep policies, invoices, scopes, contractor packets, and completion evidence together.
Review source-attributed parcel and public context around the private record.
Export evidence-ready packets with clear provenance and packet boundaries.
Share snapshots intentionally instead of exposing raw private tables or the full workspace.
Who we serve
Other lanes are scoped contributors or packet recipients. They do not receive raw private records unless a user explicitly shares a snapshot.
Build the property memory before a storm, loss, repair dispute, move, or sale.
Contribute before photos, scope, materials, invoices, warranties, and completion evidence.
Review parcel context, permits, flood exposure, site constraints, and due-diligence notes.
Review address-level readiness and public context without opening private resident records.
Review surface
Hands-free discovery and lightweight evidence candidates.
Final review, annotation, enrichment, and packet preparation.
Review, export, admin, homeowner inventory, and claim evidence.
Who we fight for
Pricing
Pricing is intentionally scoped around records, packets, and partner workflows. Pilot availability can vary by deployment profile.
Start
$0
Create a private property record and begin organizing existing evidence.
Property profile
Evidence imports
Readiness checklist
Property
Pilot
Build deeper inventory, repair, policy, and packet workflows around a property.
Room inventory
Document vault
Packet builder
Partner
Scoped
Coordinate contractor, developer, or public-sector packet workflows with explicit boundaries.
Contributor packets
Source context
Review exports
Start with one property, import existing evidence, and turn the strongest items into a reviewable packet when needed.
FAQ
ClaimGuardian is designed for evidence-ready property records and reviewable packets, not automatic outcomes.
No. ClaimGuardian helps create evidence-ready, source-attributed, reviewable packets. It does not guarantee claim approval, insurance coverage, eligibility, or legal admissibility.
No. The product is designed around the glasses-to-iPad loop for capture and review. The web app is for review, export, homeowner inventory, claim evidence, and admin workflows.
Workspace evidence, property records, originals, annotations, and packet drafts are private by default. Sharing happens through scoped snapshots and packets.
Public place context should carry source names, freshness, confidence, limitations, and safety scope so reviewers know what they are looking at.
A storm packet should start before the storm.
Field signal, not a claim outcome promise.
A repair handoff should not live only in text messages.
Field signal, not a claim outcome promise.
A property sale should not depend on a folder nobody can find.
Field signal, not a claim outcome promise.