You did the work. The file gets a Submit, Hold, or Fix recommendation 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 Submit, Hold, or Fix recommendation before you send it. Your team makes the corrections, submits the claim, and manages the carrier relationship.
Every file lands on one of three outcomes.
Not a vague "looks good." A specific recommendation before the file goes out. You make the call.
Scope, evidence, and pricing all support the work performed. The file is ready.
Critical information is missing. The file should wait until your team has 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 on every enrolled file.
This is the real sequence a file runs through. Not a simplified version of it.
Findings report, before submission
NanoForce reviews the file against your carriers' documented reduction and denial patterns and returns a findings report: every documentation gap, its severity, the dollar amount at risk, and the correction language. It covers the estimate header, equipment monitoring notation, psychrometric completeness, category and class, scope-to-estimate alignment, and cause-of-loss narrative.
Confirmation, after your corrections
Your team makes the corrections. NanoForce re-checks the corrected file, confirms each flag is resolved, and issues a one-page confirmation. Then you decide: Submit, Hold, or Fix.
You submit. NanoForce keeps tracking.
Your team submits under your own name, decides when, and handles carrier communication, negotiation and collection. NanoForce never contacts the carrier, adjuster or TPA. After submission, NanoForce tracks reductions from the records you share, sends event-driven alerts and a weekly open-file report, and prepares up to two documentation-based rebuttal packages per active file, each responding to one substantive carrier response. Your team sends them.
Estimating defaults can contradict the field record. Someone has to check.
In Xactimate, equipment lines can carry default settings, such as a “No Monitoring” selection, unless the estimator changes them. Estimating software doesn't check its own defaults against the field record, and Encircle doesn't check itself against the estimate. In many companies, no one's job is to confirm that the field documentation, the psychrometric log, and the estimate line items tell the same story. When they don't, the mismatch can surface at carrier review instead of before submission.
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 recommendation on every file
You know where a file stands and what closes the gap before you decide to send it, not a vague "documentation could be stronger."
Included with every file.
Prevention before submission is the job. The same file stays covered after it goes out.
- Two pre-submission review passes.
- Written findings and correction guidance informed by carrier-specific patterns.
- A Submit, Hold, or Fix documentation-readiness finding. It is not a carrier decision or a coverage determination.
- Weekly open-file reporting.
- Up to two documentation-based rebuttal packages per active file, each responding to one substantive carrier response. NanoForce prepares them. You send them. This is not carrier representation.
- Event-driven alerts and reduction and outcome tracking, based on records you share.
A file counts once, when NanoForce accepts it for review. Its correction review, rebuttal packages and tracking do not count as additional new files. Pricing is two numbers: a one-time setup fee by location count and a monthly subscription by new files accepted. See the pricing page.
Your 12-month baseline comes first.
We start with your last 12 months of available claim-file records. Up to 100 historical files are collected, indexed and analyzed, and up to 20 representative files get a detailed review. You receive a Historical Baseline Report at the end of onboarding. There is no minimum file count.
Onboarding does not reopen old claims, prepare rebuttals for previously submitted historical files, reconstruct missing historical documentation, or perform collection or negotiation. That is separate from support on your active enrolled files.
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 recommendation on every file. You make the call |
| Correction language | Written under deadline pressure | In the Pass 1 findings report, confirmed in Pass 2 |
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 | Yes. Your team submits and manages the carrier | 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 composite, not a client result. This is what a Submit recommendation looks like once Pass 1 and Pass 2 are done.
This file had two of the most common gaps NanoForce finds: dehumidifier equipment class billed without a room-volume calculation on file, and antimicrobial charges billed with no cross-reference to the documented affected zone.
Both were flagged in Pass 1, corrected by the contractor's team, and confirmed in Pass 2 before submission. The equipment-class math and the affected-zone match were both on file before submission.
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?
It is designed not to add a separate step. Pass 1 runs on the file your team already builds, and most corrections happen in the same workflow. Corrections your team still has to make, or evidence that is still missing, can add time before a file is ready. Delivery times are not published on this site, and your team decides when to submit.
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 recommendation actually mean?
Every enrolled file gets one of three recommendations before it's sent. Submit means no material gaps were found: scope, evidence, and pricing support the work performed. Hold means critical information is missing, and the file should wait until your team has it. Fix means specific corrections are needed first. NanoForce recommends. Your team decides and submits.
How is this priced?
Claims-to-Cash has two pricing parts. A one-time setup fee is based on location count: $5,000 for 1 to 4 locations, $10,000 for 5 to 8, $14,000 for 9 to 12, $19,000 for 13 to 16, and $24,000 for 17 to 20. A monthly subscription is based on new files accepted for review each month across your enrolled locations: Essential, up to 10 files, $2,000. Growth, up to 25 files, $3,500. Professional, up to 50 files, $5,500. Regional, up to 100 files, $9,000. There is no percentage-of-recovery fee. Location count sets setup. File volume sets the subscription. No discounts. See the pricing page.
How are files counted, and what does each file include?
A file counts once, when NanoForce accepts it for review. Its correction review, rebuttal packages and tracking do not count as additional new files. Each file includes two pre-submission review passes, written findings and correction guidance informed by carrier-specific patterns, a Submit, Hold, or Fix documentation-readiness finding, weekly open-file reporting, up to two documentation-based rebuttal packages, and event-driven alerts with reduction and outcome tracking based on the records you share.
What happens after a carrier responds?
Prevention comes first, but support continues on active files. You share the carrier response. NanoForce tracks the reduction and, when a response needs an answer, prepares a documentation-based rebuttal package that responds to that one substantive carrier response. Each active file includes up to two packages. You send them. NanoForce does not contact carriers, adjusters or TPAs, does not negotiate or collect, does not represent insureds, and is not a public adjuster.
What does onboarding include?
Onboarding starts with your last 12 months of available claim-file records. NanoForce collects, indexes and analyzes up to 100 historical files, selects up to 20 representative files for detailed review, and delivers a Historical Baseline Report at the end of onboarding. There is no minimum historical file count. Onboarding does not reopen old claims, prepare rebuttals for previously submitted historical files, reconstruct missing historical documentation, or perform collection or negotiation. Rebuttal packages apply to active enrolled files.
Related reading: Documenting O&P when a carrier cites a three-trade minimum · The pre-submission audit restoration owners are missing
Wondering what this costs, or whether Claims-to-Cash fits your setup? See the pricing page and the Fit & Limits page.
Five AI prompts for better restoration job notes.
Five prompts for drafting fact-based job notes, plus a worksheet to check that the notes, photos, logs, and estimate tell one consistent story. Your team still reviews the whole file.
Sending this opens the download page. Your email address goes to our form provider (Netlify). See the Privacy Policy.