You did the work. The file gets a Submit, Hold, or Fix decision before it reaches the carrier.
Claims-to-Cash is a pre-submission file review for restoration contractors with 1–20 locations and $1M+ in annual revenue. Every enrolled file is checked against your carriers' actual denial and reduction patterns, and returns a decision before you send it, not a dispute after you don't.
Every file lands on one of three outcomes.
Not a vague "looks good." A specific decision, before the file goes out.
Scope, evidence, and pricing all support the work performed. The file is ready.
Critical information is missing. The file waits until it's resolved, not after the carrier finds it.
Specific scope, documentation, or pricing corrections are needed before this file goes out.
Water, fire, smoke, and mold restoration contractors: 1 to 20 locations, $1M+ in annual revenue.
If claim volume is still low enough that you personally read every file before it goes out, this earns its keep later, not yet. Claims-to-Cash matters the moment a reduction stops being one bad file and starts being a pattern across estimators, crews, or locations. And you can see the total on the P&L but not which file is causing it.
What usually forces the question.
- The controller flags a reduction pattern in the monthly numbers, but can't point to which files or which estimators are driving it.
- A carrier just cut equipment days or scope on a file your team thought was clean.
- You're opening a new location and don't want the same documentation habits to scale with it.
- A TPA review came back with findings your team had no answer for. Because the file never anticipated the question.
What NanoForce actually does. Two passes, every file, no exceptions.
This is the real sequence a file runs through. Not a simplified version of it.
Gap identification, before submission
Estimate header, equipment monitoring notation, psychrometric completeness, category and class, scope-to-estimate alignment, and cause-of-loss narrative. Checked against the denial patterns we've documented for each of your carriers, not a generic checklist.
Correction and defense language
We write the language that makes each correction hold up: the fact, the standard it's grounded in, the defensible action. Your team executes the specific fix. The file that goes out was built to survive a second look.
Carrier response support
If a carrier reduces or disputes after submission, we read the response, pull that carrier's known behavior, and build the rebuttal your team sends. Same business day.
Xactimate defaults every equipment line to "No Monitoring." Every time.
Your estimating software doesn't flag its own defaults. Encircle doesn't check itself against the estimate. Nobody's job is to confirm that what's in the field documentation, the psychrometric log, and the Xactimate line items all tell the same story. So a carrier finds the mismatch before you do.
What you actually receive on every file.
Exact location of every flag
Not "documentation could be stronger." The specific line item, the specific gap, the carrier pattern it maps to.
Correction language your estimator can paste in
Written to the standard, not generic filler. Your team executes. NanoForce never touches the file.
Carrier-specific documentation requirements, current for your state
Built from real claim files and denial patterns. Not a generic adjuster handbook.
A Submit, Hold, or Fix decision on every file
You always know exactly where a file stands and exactly what closes the gap, not a vague "documentation could be stronger."
With NanoForce vs. without it.
The same file, run two different ways.
| Where the file stands | Without NanoForce | With NanoForce |
|---|---|---|
| Carrier-specific denial patterns | Learned after a reduction lands | Checked against documented patterns before you submit |
| Missing scope or proof gaps | Found when the carrier flags them | Caught in Pass 1, while evidence is still easy to prove |
| Submission decision | A gut call | Submit, Hold, or Fix on every file |
| Correction language | Written under deadline pressure | Drafted in Pass 2, built to survive a second look |
What NanoForce is. And isn't.
Positioning matters more here than almost anywhere else in the business.
| Function | NanoForce | A public adjuster |
|---|---|---|
| Reviews documentation before submission | Yes | Not typically |
| Submits the claim to the carrier | No. You do | Sometimes |
| Negotiates directly with the carrier | No. You do | Yes |
| Keeps you in control of the relationship | Always | Varies |
NanoForce provides documentation audit and carrier intelligence only. You submit and manage your own claims at all times. Nothing here is legal advice.
One file, before and after.
Illustrative structural example. This is what a Submit decision looks like once Pass 1 and Pass 2 are done.
This file had three of the most common gaps NanoForce finds: equipment lines left on Xactimate's default "No Monitoring," no documented dry standard, and demolition scope with no signed addendum protecting against a spoliation defense.
All three were caught in Pass 1, corrected in Pass 2, and submitted clean. The file contained documented support for each of the three gaps before the carrier ever reviewed it.
See more file walkthroughsQuestions owners actually ask.
Is NanoForce a public adjuster?
No. NanoForce audits documentation before submission and provides carrier-specific intelligence. You submit and negotiate every claim yourself, at all times. We never contact a carrier or adjuster on your behalf.
Does this slow down submission?
No. Pass 1 runs on the file your team already builds. Most gaps are caught before your estimator would have submitted anyway; the correction happens in the same workflow, not as a separate delay.
What if our documentation is already pretty good?
Good. Pass 1 runs on every file regardless, so you'll see that reflected in a high audit score with minor corrections rather than a rework list. The value shows up the first time a carrier tries a reduction pattern you didn't know they used.
What does a Submit, Hold, or Fix decision actually mean?
Every enrolled file gets one of three outcomes before it's sent. Submit means scope, evidence, and pricing all support the work performed. Hold means critical information is missing and the file waits until it's resolved. Fix means specific corrections are needed first. It's a decision, not a vague opinion.
How is this priced?
A flat $2,000/month base plus a performance fee on confirmed recovery, the delta between what was submitted and what the carrier ultimately paid, after legitimate adjustments. No performance fee applies where there is no confirmed recovery; the fixed monthly service fee remains payable. Setup runs $5,000–$24,000 depending on location count.
See the six things worth checking before you submit.
One Carrier Decision: what changes across an entire file the moment a carrier reclassifies a loss, and the six things worth checking before you submit.