How it works
Verinode reads what you already have.
Your inbox holds the running story of a job. Your tools hold the numbers. Verinode reads both and turns them into peer benchmarks and decisions. Nothing to install. Nothing to switch.
You don’t connect to Verinode.
Verinode reads what you already use.
Start here
It begins in your inbox.
The carrier threads, the adjuster back-and-forth, the field updates, the invoices. The running story of a job lives in email, and no software tool captures it. Connect your mailbox, or forward what matters to your Verinode address. There is nothing to install and nothing to learn.
Forward it
Send any thread to your Verinode address. You get an instant acknowledgment, then a reply grounded in your own history.
Or connect it
Link your mailbox once, read-only. Verinode reads the threads that matter and ignores the rest.
Stays yours
Your raw email never leaves your side in a form anyone else can read. Only anonymized aggregates cross out.
The tools you already use
Already using these? We read their exports too.
If your tool can export a file, Verinode can read it. You export, Verinode reads. No API to wire up, no connector to wait for, no system to replace. The numbers land next to your email so the whole picture of a job sits in one place.
Accounting & books
QuickBooks, Xero, Sage, or any P&L export
Gross margin, AR aging, and expenses mapped to the restoration chart of accounts.
Estimating
Xactimate, Symbility, or any estimate export
Line items, scope, and the supplements you did, and didn't, get approved.
Field documentation & photos
Encircle, CompanyCam, DASH, and the field apps your crews run
Scope, photos, moisture readings, and equipment-on-site logs.
Job & project management
DASH, Albi, JobNimbus, iRestore, or your CRM export
Status, timestamps, and the timeline a job actually moved through.
Time & payroll
ADP, Gusto, ClockShark, busybusy, or a timesheet export
Field hours that become fully burdened labor cost, per job and per crew.
Equipment & fleet
Your asset tracker, maintenance log, or a spreadsheet
Utilization, runtime, and what your equipment and trucks really cost per job.
Examples, not a complete list. Naming a tool means we can read its export, not that we are affiliated with it. If your tool exports a file, Verinode can read it, and new ones are added as operators bring them. See where the numbers come from in the methodology, or read The Data You Already Own.
One pipeline
Many ways in. One path.
Email, documents, photos, voice, pasted text, and tool exports all converge on a single extraction path. However it arrives, it is read the same way, structured into operating data, and carries a receipt of exactly what was read, kept, dropped, or corrected. The quality of ingestion is measured, not assumed.
One extraction pipeline
Read, structured, receipted.
Structured operating data
Yours, then compared
Held in your vault. Compared so no one can be named.
Your structured data lands in a vault encrypted with a key only you hold, walled off in its own boundary. The only thing that ever crosses out of your side is an anonymized number, and even that is built so no single business can be picked out of it. That is what becomes the peer benchmarks, and what comes back to you as the few decisions worth your week.
Your data stays yours
Encrypted with your key
Your vault is encrypted with a key tied to your login and held by you. Without your authenticated session it cannot be decrypted, not by a vendor, a carrier, or Verinode staff.
Walled-off tenancy
Your records live in an isolated boundary with row-level security on every table. No other operator, no vendor, and no carrier can read them.
Logged and revocable
Every action taken on your data is written to your own security log. Reviewable, auditable, and revocable at any time.
Why the benchmark is safe to feed
Hashed before it pools
Before anything contributes to a benchmark, your identity is replaced with a one-way hash that cannot be reversed. Your raw records never leave your side.
A floor of three
A benchmark only appears once at least three separate operators are in the cohort, so no single business's number can be worked back out of it.
Never shared with anyone
Anonymized aggregates build peer benchmarks for operators, and only for operators. They are never shared with anyone.
The deeper technical shape of the trust boundary is in the architecture. More on how aggregation protects you: Anonymized Before It’s Pooled.
Point it at what you already have.
Forward one email or drop in one export. See your first benchmark, and the first decision, from data that was already sitting in your business.