Kevin.

A Faster Workflow for XactContents-Style Contents Claims

Kevin builds, prices, classifies and depreciates the contents lines, then exports a worksheet in the XactContents template. It is not a replacement for everything XactContents does.

Kevin Godfrey, KevinLast updated 3 October 2026

Is Kevin an XactContents alternative?

For the part of the job that is building contents line items, yes — Kevin does that work from photographs instead of by hand. For estimating and the carrier ecosystem, no, and we would not claim otherwise.

The useful comparison is not product against product but workflow against workflow. The slow part of a contents claim is producing the lines: identifying each item, finding what it costs to replace, keeping the evidence, choosing a class, applying depreciation. Kevin automates that and hands you a reviewed worksheet. Where it ends is also clear: it writes a file you send, and it has no carrier-facing review surface.

Kevin is not affiliated with, endorsed by or certified by Verisk. XactContents and Xactimate are Verisk products. Kevin writes a worksheet in a format their importer reads.

What Kevin does

The contents-line workflow, by step
StepWhat Kevin does
Photo evidenceHundreds of photographs ingest at once — a folder, a phone dump or a .zip, expanded in the browser.
GroupingShots of one item taken seconds apart become one proposed set, which you merge, split or exclude.
IdentificationRead from the photographs; several independent signals are weighed together and no single one is trusted on its own.
PricingOne query per item, priced from a single listing — a single representative listing.
SourceThat listing is stored on the row and prints into the export.
Content classEach line carries a class, which drives its depreciation and its place in the template.
DepreciationClassified to XactContents categories and sub-categories — 31 categories, 87 sub-lines, age-based, computed server-side and running to 100%.
RCV and ACVUnit cost × quantity, plus sales tax, less depreciation — footed left to right on the row.
ExportXactimate (Excel) · .xlsx · XactContents template, plus a room-by-room PDF.

What Kevin does not do

Out of scope, deliberately
Not KevinWhy it matters
Structural estimatingKevin values personal property. Dwelling and structure estimating is a different discipline and a different tool.
Restoration CRMNo job management, scheduling or crew tracking.
Warehouse and pack-out managementKevin records what the property was and what it costs to replace, not where the boxes went.
Carrier claim managementKevin exports a file you send. It does not submit into carrier systems and has no carrier-facing review surface.

By hand versus through Kevin

The same 400-item pack-out, two ways
By handThrough Kevin
Describing itemsTyped per item from the photographIdentified from the photograph, edited where wrong
Replacement priceSearched per item across several retailersOne query per item, priced from a single listing
EvidenceURL copied into a column, if there is timeStored on the row automatically and printed in the export
Content classChosen per line from memoryCarried on the line and used for its schedule
DepreciationLooked up per category and ageServer-computed from class and age, to 100%
The spreadsheetTyped, then re-typed when a price changesRecalculated in the app; the export is a snapshot
Your partAll of itReview, exceptions and judgment

The export

kevin.co/claims/…/export
Kevin's export dialog offering the Xactimate Excel worksheet in the XactContents template and a room-by-room PDF inventory
Xactimate (Excel) · .xlsx · XactContents template. Static values in every derived cell, because the importer rejects formulas.

Kevin never blocks an export on editorial readiness. The dialog tells you what needs attention — unpriced lines, missing model numbers, special-limits classes — and the download stays live. Whether to send it is your call, not the software's.

Interoperability, stated as it stands

Today the interchange is a file: Kevin writes the .xlsx and you import it. Xactimate uses Excel templates for contents and .ESX archives for whole estimates; programmatic integration in that ecosystem goes through XactAnalysis. Kevin has no integration with Verisk products and none is announced. If that changes, this page will say so on the day it is true and not before.

Common questions

Does Kevin replace XactContents?
No. Kevin removes the manual work of building contents lines — identifying items, pricing them from a listing, classifying them, applying depreciation and documenting the source — and exports a worksheet in the XactContents template. Estimating, the carrier ecosystem and everything XactContents does beyond contents valuation are not Kevin.
Does the export import without reformatting?
That is the intent and the reason for a constraint you can see in the file: every derived cell is written as a computed number rather than a formula, because the importer breaks on formulas. The export is a snapshot of what the web app produced, and recalculation happens in Kevin, not in the spreadsheet.
Does Kevin use XactContents depreciation classes?
Yes — that is what the schedule is built on. Each line is classified to an XactContents category and sub-category, and the depreciation follows from that class and the age of the item: 31 categories, 87 sub-lines, age-based, running to 100%. A carrier profile can select a bracketed schedule instead of straight-line where that is what the carrier uses. Using the taxonomy is not a relationship with its owner — see below.
Is Kevin a fit for public adjusters specifically?
Yes, and that is who it was built around: independent and public adjusters, content inventory specialists and estate professionals. Pricing is flat monthly rather than per claim or per seat, which is how adjusters already pay for the tools they use.
What about total losses with no usable photographs?
There is a separate route for that: a typed or exported inventory — PDF, CSV or XLSX — is parsed and each described row is priced like a photographed one, without brand and model precision. It is a different workflow from the photo-based engine and we do not present it as equivalent.
Is Kevin affiliated with Verisk?
No. Kevin is not affiliated with, endorsed by or certified by Verisk. XactContents and Xactimate are their products; Kevin writes a worksheet in a format their importer reads.

Build contents claims faster with Kevin.

Your first 250 line items are free, with no clock running. $249/mo after that, unlimited claims.

Start for FreeSee how it works

Related