Kevin vs XactContents

They overlap in part of the personal-property valuation workflow and are not the same product. This is what each one does, row by row, without a declared winner.

Kevin Godfrey, KevinLast updated 3 October 2026

How do Kevin and XactContents compare?

XactContents is contents valuation inside Verisk's estimating ecosystem; Kevin is automation for building contents lines from photographs, which exports into that ecosystem as a worksheet.

The honest comparison is narrow. Both deal in personal property, but one is part of an estimating platform with a carrier network behind it, and the other turns a folder of pack-out photographs into priced, documented lines. Most people asking this question are not choosing between them so much as deciding what builds the lines before the estimate is assembled.

Kevin is not affiliated with, endorsed by or certified by Verisk.

Row by row

What each one is for — not a scorecard
	Kevin	XactContents
Primary purpose	Build, price, classify and document contents lines from evidence	Contents valuation within an estimating platform
Photo intake	Hundreds at once: folder, phone dump or .zip expanded in the browser	Not its focus
Multi-photo grouping	Shots of one item become one proposed set, confirmed by a person	Not its focus
Item identification	Read from the photographs, with several independent signals weighed together	Entered by the estimator
Replacement research	One query per item; priced from a single listing	Price list and catalogue driven
Source URL on the line	Stored on the row and printed in the export	Not in this form
Content classification	On every line, driving its depreciation	Native to the platform
Depreciation	XactContents classes — 31 categories, 87 sub-lines, age-based, to 100%	Platform and carrier schedules
RCV and ACV	Computed server-side, footed on the row	Yes
Structural estimating	No	Yes, with Xactimate
Carrier ecosystem	No. Kevin exports a file you send	Yes, including assignment flow
Export formats	Xactimate (Excel) · .xlsx · XactContents template, plus PDF	Platform formats including .ESX archives
Pricing model	$249/mo flat, unlimited claims, 2,000 items included	Licensing through Verisk
Best fit	Large contents inventories built from photographs	Estimating inside the carrier workflow

When XactContents is the better fit

Your work is structural as well as contents, and lives in one estimate.
Assignments arrive through the carrier ecosystem and are expected back the same way.
A carrier requires their platform and their price lists, which is not a preference you get to override.
Contents on your claims are a short schedule rather than several hundred lines.

When Kevin is the better workflow

The bottleneck is volume: hundreds of photographs becoming hundreds of documented lines.
You want the listing behind every price kept automatically rather than when time allows.
You are a public or independent adjuster paying for your own tools, and flat monthly beats per-claim.
The loss is total and the inventory is a typed list rather than photographs.

How they fit together

In practice Kevin runs first and the estimate second: the photographs become a reviewed, priced worksheet, and that worksheet imports where the rest of the claim is assembled. Nothing is pushed anywhere — Kevin writes a file and you decide where it goes, which is also why it has no carrier-facing review surface.

Common questions

Which one should I use?

They answer different questions. If your work is structural estimating inside the carrier ecosystem, that is Xactimate and XactContents, and Kevin does not replace them. If the slow part of your week is building, pricing and documenting hundreds of contents lines, that is what Kevin automates — and its output is a worksheet in the XactContents template.

Can they be used together?

That is the common case. Kevin produces the priced, classified, depreciated contents worksheet and you import it where your estimate lives.

Does Kevin do structural estimating?

No. Kevin values personal property. Dwelling and structure estimating is a different discipline with different price lists, and we do not pretend to cover it.

Is the export really importable?

It is written to the XactContents template with static values in every derived cell, because the importer breaks on formulas. Recalculation lives in the web app; the file is a snapshot of what the app produced.

Is Kevin integrated with Verisk products?

No. Kevin is not affiliated with, endorsed by or certified by Verisk, and no integration is announced. The interchange today is a file: Kevin writes the .xlsx and you import it.

What about pricing models?

Kevin is flat monthly — $249, unlimited claims, 2,000 line items a month included and $0.20 an item after that, with the first 250 free and no deadline on them. There is no per-seat or per-claim fee.

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 Free See how it works