Blog

Restoration contractors are paying for Encircle. And PSA. And DASH. And a CRM. And a project management tool. And a call tracking service. And a reputation management platform. And an estimating integration. By the time you add it all up, a mid-size restoration company might be running eight separate software subscriptions, each with its own login, its own invoice, its own support line, and its own way of storing data that doesn’t talk to anything else.

I’ve been watching this stack accumulate for years. And I’ve been thinking about a question I haven’t seen anyone ask out loud:

Who owns the data when the job is done?

What Software Companies Are Actually Selling

Encircle is a genuinely good product. So is PSA. So is DASH. I’m not writing this to trash them. They solved real problems — structured photo documentation that insurance carriers accept, drying logs that meet IICRC standards, scope writing that integrates with Xactimate. These things are hard to build from scratch and they matter in a claims-dependent business.

But here’s what all of them are also selling, whether they say it or not: a structured way to store your business’s data. Customer records. Job histories. Equipment logs. Photo sets. Communication trails. Every one of those platforms is capturing the operational intelligence of your company and holding it in their database, in their format, accessible through their interface.

The subscription isn’t just for the software. It’s for continued access to your own data.

That arrangement made sense when there was no alternative. You needed the structure, and the only way to get the structure was to accept the terms. The software vendor provided the architecture. You provided the data. The architecture stayed with them.

That’s the deal. It’s been the deal for twenty years. And it’s changing.

What’s Actually Different Now

The thing that changed isn’t AI, exactly. It’s the integration layer.

For most of the software era, building custom business tools required engineering teams, expensive infrastructure, and months of development time. That’s why SaaS won — you couldn’t build it yourself, so you rented it from someone who could. The subscription model was the price of access to capability that was otherwise out of reach.

What’s different now: a single developer — or an operator who knows how to use modern AI tools — can assemble custom business infrastructure in days that would have taken a team months in 2019. A Google Cloud VM costs $60/month. A CRM custom-built on WordPress with webhooks firing into CTM, Slack, and a Firestore job log costs fractions of what PSA charges. An AI intake agent that handles emergency calls, qualifies the job, creates the customer record, and pings the on-call crew — built on Twilio and Claude on Vertex AI — costs less per month than most restoration companies spend on coffee.

The capability gap that justified the subscription is closing. Not for every business — not yet — but for businesses that have someone close enough to understand what they need and how to build it. And critically: when you build it, you own it. The data lives on infrastructure you control. It doesn’t leave when you cancel a subscription because there’s no subscription to cancel.

What Encircle Still Does That Matters

I said I wasn’t writing this to trash these companies and I meant it. So let me be specific about what they do that’s genuinely hard to replicate.

The compliance layer. Insurance carriers have specific documentation requirements. IICRC has drying log standards. Xactimate has a particular way of handling scope line items. Encircle has spent years building integrations with those systems, getting their formats accepted by carriers, making their documentation hold up in adjuster reviews and litigation. That institutional trust is not a feature you can code in a weekend. It’s accumulated credibility that took years to build and is worth real money to contractors whose revenue depends on claims getting approved.

The field mobile experience. Technicians in the field need something fast, offline-capable, and purpose-built for how they actually work — photos, moisture readings, equipment logs, job updates — all from a phone in a flooded basement. Generic platforms aren’t optimized for that workflow. Encircle is.

So no — the Company OS doesn’t make Encircle irrelevant for everything. What it makes irrelevant is the parts of Encircle — and PSA, and DASH, and the CRM, and the project management tool — that are really just coordination and data structure. The scheduling, the customer records, the communication trails, the job status tracking, the lead attribution, the revenue reporting. All of that can live in a system you own, wired together through APIs, with your data staying on your infrastructure.

You keep Encircle for what Encircle is uniquely good at. You stop paying for the eight other subscriptions that are just doing coordination work you could own.

The Model That Makes This Work

The reason most restoration contractors won’t build this themselves isn’t that they can’t afford it. It’s that they don’t have the time or expertise to architect it — and even if they did, they’d have to manage it forever. That’s not a restoration contractor’s job. Their job is running jobs.

The Company OS model I’ve been developing solves this by flipping the arrangement entirely. Instead of the contractor buying software subscriptions and managing a fragmented stack, I build and host the entire infrastructure — VM, CRM, call tracking, AI intake, content engine, ad management — and take a percentage of revenue I can prove I drove through the system. The contractor pays nothing upfront and nothing ongoing for the infrastructure. They pay on verified results.

The difference from the SaaS model: the data architecture belongs to the system I built, which is operated in the contractor’s interest and accessible to them. The attribution data, the customer history, the job records, the communication logs — all of it lives in a structure we both can see, verified by Call Track Metrics, not locked behind a vendor’s dashboard.

That’s not a software product. That’s an infrastructure partnership. And it produces a fundamentally different answer to the question of who owns the data when the job is done.

The Question Worth Sitting With

I want to be careful here about the scope of what I’m claiming. The vertical software companies — Encircle, Xactimate, PSA — aren’t going away. The contractors who need carrier-compliant documentation and field mobile tools will keep paying for them. The compliance layer is real and the field experience is real and those are genuinely hard problems.

What I think is ending — or at least what I think deserves to end — is the part of the software subscription economy built on the coordination tax. The $200/month CRM that stores your customer records in someone else’s database. The project management tool that knows your job pipeline better than you do. The reporting dashboard that shows you your own business through someone else’s lens. That category of software exists because the integration layer didn’t. Now it does.

So here’s the question I’d ask any restoration contractor right now: for every subscription you’re paying, do you own the data when you stop paying? Do you know exactly where your customer records live, who controls the schema, what happens if the vendor raises prices or shuts down?

Most contractors have never asked this because they’ve never had to. The subscription was the only option.

---

It isn’t anymore.

The question isn’t whether your software does the job. The question is who owns the data when the job is done.