You did the work. The file
may not pay for it.
NanoForce reviews your claim file before it reaches the carrier: missing scope, proof gaps, and estimate-to-invoice mismatch, caught while the evidence is still easy to prove. Built for restoration and reconstruction contractors with 1–20 locations and $1M+ in annual revenue, every file gets a Submit, Hold, or Fix decision, not a vague second opinion.
What a corrected file looks like before it ever reaches the carrier.
Same job. Same estimate. Three documentation gaps found and closed before submission, not disputed after the fact.
Illustrative file structure, drawn from the pattern NanoForce finds across enrolled claims. See the full file-by-file walkthrough on the Proof page →
The work may be complete. The file may still be underpaid.
A finished estimate doesn't mean a claim file is ready. If the scope, photos, job notes, and invoice don't support the work your team performed, the missing dollars become a carrier cut, a delayed payment, or a write-off nobody catches in time.
Work was required in the field but never made it into the estimate or the carrier submission.
The work got done, but photos, notes, and logs don't clearly show why it was necessary.
The invoice exceeds approved scope, and nobody owns the gap between what was done and what was approved.
Depreciation, change conditions, and approved balances stay open because nobody is tracking them to close-out.
The cheapest time to protect margin is before the file leaves your company.
Once a claim is submitted, the carrier's estimate becomes the anchor. Once a condition is covered up or the job is complete, your team has to reconstruct evidence. Once an invoice ages, a correctable gap can turn into a write-off before anyone catches it.
Two systems. One team running both.
Each one stands on its own. Together, they're how a multi-location restoration owner keeps control without adding headcount.
Claims-to-Cash
Each enrolled file reviewed against the specific way your carriers reduce and deny. Identified gaps can be addressed before submission.
Reconciliation
Invoices, vendors, subcontractors, and job costs checked against the books daily. Not discovered at month-end.
Every file gets a Submit, Hold, or Fix decision before it reaches the carrier.
NanoForce checks the relationship between the field work, the scope, the evidence, the estimate, and the invoice before the claim goes out. The goal is simple: don't submit a file until it can support the work your team expects to be paid for.
The file is ready. Scope, evidence, and pricing all support the work performed.
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.
From field work to a file that pays.
The same five-step check, on every enrolled file.
File enters the check
The estimate, carrier scope, photos, job notes, and invoice are gathered into one file.
NanoForce compares the job to the file
We identify missing scope, proof gaps, estimate-to-invoice mismatch, and known carrier-cut patterns.
Your team gets a Submit, Hold, or Fix result
A prioritized action list, before the file goes to the carrier.
The team submits a carrier-ready file
Missing support gets resolved while the work and the people who did it are still reachable.
Open dollars stay visible
Supplements, depreciation, and approved balances stay on the list until they're resolved, not forgotten.
QuickBooks is syncing. Xactimate is connected. The gap is still there.
Integration moves data from one system to another. It doesn't check whether the numbers agree, whether the file is complete, or whether the invoice actually matches the job. That job belongs to a person, and once you're past a handful of locations, no single person has time to do it on every file, every invoice, every claim, every week.
So the software keeps reporting that everything is running. And the reduction line on your P&L keeps showing up anyway. NanoForce is the person that job belongs to. We just happen to run it with software instead of a headcount line.
If any of this sounds familiar, margin is already leaking.
- A PM finds concealed damage, but it never reaches the estimate.
- Work starts or finishes before anyone checks that the file supports it.
- Photos exist, but they're not tied to the line item or condition they're supposed to prove.
- The final invoice exceeds approved scope, and the gap has no owner.
- Supplements get built after the crew has left, when conditions can't be documented clearly anymore.
- Depreciation, change conditions, and carrier cuts aren't tracked to close-out.
- Your team says "we did the work," but can't quickly prove it from the file.
This isn't only a documentation problem. It's a revenue-control gap.
How engagement actually works.
No pilot theater. No twelve-month contract you can't get out of.
Margin Leakage Consult · 30 minutes, owner and controller
We look at your footprint and your current systems and estimate where leakage is most likely. You leave with a specific number to check, not a pitch deck.
Scoped build against what you already run
Xactimate, Encircle, QuickBooks, your PM software. We build against it. Nothing gets replaced that doesn't need to be.
NanoForce runs it, not you
We operate the system day to day. You see results and exceptions that need a decision. Not a dashboard you have to remember to check.
Priced on what it recovers or protects
A fixed monthly base plus a share of confirmed recovery, per system. If nothing is found, there's no performance fee to pay.
What each part of the price actually funds.
Three components, three different jobs.
Why done-for-you beats another login.
The difference isn't the software. It's who's responsible for checking it.
| What determines the outcome | Software you manage | NanoForce, done-for-you |
|---|---|---|
| Who checks the file before it's submitted | Whoever has time that day | NanoForce, every file |
| Who catches a duplicate or misapplied invoice | Usually no one, until month-end | NanoForce, the day it happens |
| What you have to log in and check | A dashboard, regularly | Nothing. You get the exception list |
| What happens when a gap is found | A ticket, eventually | Corrected before it costs you |
Questions owners actually ask.
What does NanoForce actually do?
NanoForce runs two done-for-you systems for restoration and reconstruction contractors: claims file auditing before carrier submission, and daily invoice and job-cost reconciliation. We build each system against your existing software and run it day to day. You receive a prioritized exception list and visibility into verified opportunities, not another dashboard.
Who is NanoForce built for?
Restoration and reconstruction contractors, water, fire, smoke, mold, roofing, and asbestos, with 1 to 20 locations and $1M or more in annual revenue, operating anywhere in the continental United States. Below that scale, the leakage NanoForce catches usually isn't large enough yet to justify the engagement.
Does NanoForce replace our existing software?
No. NanoForce builds against what you already run: Xactimate, Encircle, QuickBooks, your PM software. Nothing gets replaced that doesn't need to be.
How is NanoForce priced?
Claims-to-Cash is priced by location count: a flat $2,000/month base, with setup between $5,000 and $24,000 depending on your location tier, plus a performance fee on confirmed recovery. If no recovery is confirmed, no performance fee applies, though the setup and monthly base remain payable. Reconciliation is scoped and quoted individually.
What's the difference between NanoForce and hiring for these roles internally?
Past a handful of locations, no single hire has time to check every file and every invoice, every week. NanoForce runs that check as a system, not a headcount line, and it's the same discipline applied consistently across every location.
What we can actually show you.
Full file walkthroughs, corrected claim examples, and recovery logic live on the Proof page. We'll show you how a file changed, what was missing, what was corrected, and where the recovered dollars came from. Before we ask you to believe any big number claims.
- File-by-file walkthroughs: the exact gap, the exact correction, before and after.
- Real Submit, Hold, and Fix decisions, and exactly what changed each file's outcome.
- Reconciliation exceptions caught before they show up on the P&L.
Built by Mark Kurywczak, who watched this leakage pattern repeat for years.
Mark has spent more than 35 years building and fixing operational systems across IT, construction, and restoration. Including as Director of Internet Technologies at Flashpoint before founding NanoForce. He's been down in the weeds with water mitigation, emergency response, and job documentation, watching margin disappear between what the crew did, what the estimate says, and what the carrier pays. NanoForce is the contractor-side system he built to close that gap.
Read more about NanoForceSee 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.
Not sure NanoForce fits your company? See who this is built for, and who it isn't, or go straight to Founding Six pricing.