Ask the controller for a list of every technology system the company pays for. Then ask operations for a list of every system people log into.
If the two lists don't match, read the differences line by line. That's where the useful questions are.
Plenty of restoration platforms earn their keep. Before buying the next one, it helps to know what you already own, what each system is for and how they connect.
Where technology touches a restoration job
Follow one water loss from the first call to the final payment and count the systems.
The call comes in through the phone system, maybe an answering service, maybe a text line. Intake lands in a CRM or the job management platform. A tech documents the loss in a field app with photos and moisture readings. An estimator writes the scope in Xactimate. The job runs through DASH, PSA or another management platform. Billing and collections happen in QuickBooks or another accounting system, with email, file storage, reporting tools, security software and a few carrier and TPA portals around all of it.
Depending on how the company is set up, one job can touch most of those systems. None of that is a problem by itself. It becomes one when nobody can say who owns each system and how information moves between them.
Who keeps the technology inventory?
NIST's Cybersecurity Framework 2.0 treats inventories as a basic outcome. ID.AM-02 covers inventories of software, services and systems, and ID.AM-04 covers inventories of services provided by suppliers.
In a restoration company the inventory can easily end up as nobody's job. IT tracks devices. Accounting sees the invoices but not who uses what. A useful inventory lists every system with its business owner, the vendor contact, seats assigned, monthly cost and which department or card pays for it.
Overlap, unused seats and former employees
Overlap tends to come from growth. A branch adopts its own documentation app, or an acquisition arrives with its own job management platform, and both keep running.
Seats are easier to measure. In Microsoft 365, the Active Users report shows which licenses are assigned and which products each person actually uses. Restoration platforms keep a user list in their admin settings. Compare both against your current employee list. A license assigned to someone who left in March is still billing.
Where data gets entered twice
Duplicate entry shows up at the handoffs. The customer's name and address get typed at intake and again in accounting. Photos get downloaded from one system and uploaded to another. Moisture readings get re-keyed into a report.
Integrations help when they're set up and maintained. Encircle and Verisk, for example, announced an integration that imports Encircle floor plans into Xactimate to generate a sketch, and it requires both an Encircle subscription and an Xactimate license. Encircle also lists integrations with job management platforms including PSA. Many integrations work this way: both sides have to be licensed and configured, and somebody has to notice when one stops working.
What happens between estimate and collections
The chain that matters most for cash runs from field documentation to estimating to job management to accounting to collections.
When those systems share information cleanly, an approved scope change flows into the job file and onto the invoice. When they don't, the invoice goes out at the old number, or accounting and the estimate disagree and collections waits while someone reconciles them by hand. The controller usually sees this first, as invoices that need explaining.
Which integrations are critical, and what happens when one changes
Some connections matter more than others. If the link between job management and accounting fails, invoices stop. If the web form stops feeding the CRM, leads sit unseen. NIST's framework also calls for prioritizing assets by criticality (ID.AM-05), and ownership should know which links the business can't run a week without.
Vendors update products and retire features. Someone has to notice the change and test the connections that depend on it. If that's nobody's job, the first alert is often a frustrated employee.
What complexity costs beyond the subscription
The subscription is the cost everyone sees. Complexity adds costs that never appear on a vendor invoice: duplicate entry, extra training for every new hire, reports that don't reconcile across systems, manual handoffs and more vendor relationships to manage.
I won't put a dollar figure on those. They depend on your volume and your setup. They're real, and they tend to land on the controller and the office staff first.
Spending that's hard to see
Technology spending can be spread across department budgets, branch credit cards and the owner's own card. No single report shows the total unless someone builds it.
It's also worth asking whether recent purchases solved a process problem or covered one up. If estimates are late because nobody owns the handoff from the field, a new estimating add-on leaves the handoff exactly where it was.
A one-page technology inventory
Start with these columns and one row per system. Blank cells are the first findings.
| System | What it's for | Business owner | Seats | Monthly cost | Connected to | Critical? |
|---|---|---|---|---|---|---|
Before you sign the next software contract
- Pull 12 months of card and accounts payable statements and list every technology charge.
- Ask each department and branch what they actually log into.
- Compare assigned seats against the current employee list.
- Mark which systems the company can't operate for a week without.
Questions about restoration software stacks
Should a restoration company run everything on one platform?
Not necessarily. One platform can reduce handoffs, and specialized tools can do individual jobs better. The decision should come from your workflow and from who will own each system.
How often should we review our software?
Before major renewals, acquisitions and new locations, and at least once a year alongside the budget.
Who should own the technology inventory?
One named person, usually in operations or finance, with input from IT and every branch.
Sources (accessed October 5, 2026)
- NIST: The NIST Cybersecurity Framework (CSF) 2.0 (CSWP 29, February 2024)
- Microsoft Learn: Microsoft 365 Active Users report
- Restoration & Remediation: Encircle and Verisk announce integration to automate sketch generation in Xactimate
- Restoration & Remediation: Encircle announces wide array of new integration options
