Insurance and financial services firms have been slower than most professional categories to move business software to the cloud. The reasons are not mysterious: layered retention rules, the NAIC Data Security Model Law now in 24 states, updated GLBA Safeguards requirements, and a stack of carrier appointment clauses. What is changing is the cost and fragility of running aging on-premises servers for software that assumes always-on connectivity. The math is shifting.

The retention patchwork is worse than it looks

Insurance record retention is not one rule. A property and casualty agency writing in twelve states might face state producer rules of three to seven years, separate insurance department audit rules, extended life and annuity requirements, surplus lines variations, federal AML documentation under FinCEN, and carrier appointment floors of seven to ten years.

The practical effect: an agency cannot delete a file because one clock has run out. The longest applicable retention period governs. Storage architecture has to support immutable retention with per-record metadata, not bulk lifecycle rules that assume uniform handling.

For vendors, this means the data model has to surface which retention regime applies to each record. A flat archive table will create real problems during a state market conduct exam.

Audit logging: the standard has moved

Five years ago, audit logging in agency software typically meant a record of which user edited a customer record. The 2026 expectation, driven by the NAIC Model Law and updated Safeguards requirements, is broader.

Examiners and carrier audit teams routinely request login and MFA events, file access by user and device, document export and print activity, before-and-after values on policy edits, permission changes, and integration calls to carrier APIs tied to specific customer records.

Retrofitting this onto on-premises deployments, where each agency runs its own server with its own logging configuration, is difficult. Centralized hosted logging, written to immutable storage, turns a state department audit request from a multi-day fire drill into a query.

Regional offices and distributed producers

Independent agencies are rarely single-location operations. A regional brokerage might have a main office of fifteen to forty staff, several satellite branches, a growing population of remote producers, and field underwriters at client sites. The old model, where the agency system ran on a server in the main office and branch users connected by VPN, is increasingly fragile.

Published-application delivery, where the Windows-based agency software runs on centralized servers and reaches any endpoint, addresses this directly. Every user gets identical performance and identical security controls. Endpoint compromise does not become data exfiltration, because the data never leaves the hosted environment.

Cloud-hosted vs on-premises agency software

Frequently asked questions

The customers asking insurance and financial services vendors for hosting today are not patient. Partnering with infrastructure already engineered for Windows-based business software is usually the faster route to a credible offering.

Construction software adoption finally crossed a line in 2025. More than 60% of contractors now use a dedicated project management platform, and estimating software adoption keeps climbing. The holdouts are shrinking. What is not shrinking is the gap between where the software lives and where the work actually happens.

The jobsite-to-office gap

The defining problem of construction technology is geographic. The estimate lives on an estimator’s desktop. Job cost data lives on the bookkeeper’s machine. The superintendent is in a truck forty minutes away with a phone full of photos. Every conversation that should take ninety seconds turns into a voicemail, an email attachment, and manual re-entry at 7 p.m.

Cloud hosting removes the round trip. The application runs on a hosted Windows session reachable from any device with a browser. Estimators, project managers, bookkeepers, and supers all work against the same live data, not synchronized copies of it.

A photo taken in the field uploads into the same database the office is working against. A change order signed on a tablet hits the job cost ledger before the homeowner finishes walking back inside. The sync layer is not an integration. It is the application running in one place that everyone connects to.

Multi-project visibility and crew mobility

A contractor with twelve active jobs has a portfolio problem, not a software problem. They need to know which jobs are bleeding margin, which subs are behind, and which projects are sitting on unsigned change orders. That requires every project’s data in one queryable place at once.

On-prem deployments handle this badly. The data is technically centralized in the office, but accessing it means being in the office or fighting a VPN that was never built for real work. A hosted model treats every active project as a live dataset the owner, office manager, and field leads can pull up from anywhere.

Crews are the most mobile workforce in any industry that touches a computer. Hosted Windows sessions delivered through a browser run identically on a personal iPad, a company laptop, or a field tablet. Cell signal at a jobsite is often worse than the office assumes, and a hosted session over thin protocols handles that better than a syncing app because only screen and input are on the wire.

Why vendors are feeling the pressure

Construction software vendors are hearing the same thing on every sales call: customers want a hosted tier. A contractor evaluating two products will pick the one that does not require maintaining a Windows server in a closet. Firms under a hundred employees rarely have full-time IT and want one bill, one vendor, one phone number.

Disaster recovery is no longer optional either. Insurers and bonding companies ask pointed questions about data continuity. Acquirers value recurring hosted revenue at a higher multiple than perpetual licenses. The math has shifted.

The friction has always been the build. Standing up Azure tenancy, configuring session brokering, hardening the environment, handling per-customer isolation, and staffing 24/7 ops is a separate company from the one writing construction software. That is the gap we exist to close. Vendors keep shipping the application they already build. The hosting layer sits underneath it.

Cloud-hosted vs on-prem construction software

Frequently asked questions

If your customers have been asking for hosting and you have been quietly hoping the question goes away, it is worth a conversation.

A small CPA firm with 600 to 1,200 individual returns runs a workload almost no other industry produces. From mid-January through April 15, concurrent users triple, document volume spikes, and engagement files balloon. Then on April 16, the curve collapses. The closet server sized for that ridge sits idle for eight months and now counts as a compliance liability with a fan.

The shape of tax season demand

Most capacity planning assumes a daily peak and a weekly trough. Accounting firms add a third dimension: the annual peak. Graph concurrent sessions across the year and you get a flat plain with a sharp ridge in Q1.

Concurrency, not throughput, is the constraint. A preparer reviewing a return holds an interactive session for 20 to 90 minutes, pinning RAM and a CPU thread. Doubling client volume in March doubles concurrent sessions. Storage I/O is bursty too, with dozens of small reads and writes per minute per user as preparers jump between working trial balances, depreciation schedules, and linked workpapers.

On-prem sizing for that curve means buying hardware that is 60 to 70 percent idle for eight months. Hosted environments let firms rent the ridge and release it in May.

Multi-client isolation and compliance

Accounting workloads carry a structural risk that most line-of-business software does not: one client’s data corruption can poison shared resources. A malformed file can crash a preparer’s session. When that session runs on a shared host with twelve other preparers, the blast radius is twelve people.

A properly designed hosted environment isolates at two layers. Each preparer’s session runs in its own user context, profile, and process tree, so a crash in one does not propagate. Client engagement files live on per-client storage paths with explicit ACLs tied to preparer identity, and every access is logged centrally.

That access model is what the 2025 IRS Security Summit guidance and the FTC Safeguards Rule expect a firm to be able to prove. The 2024 AICPA PCPS survey ranked technology and cybersecurity ahead of staffing for small firms for a reason. The evidence trail is easier to produce when the platform supplies it by default.

What clients and vendors now expect

Client expectations shifted permanently. A 2025 Accounting Today survey of small business clients found 71 percent expect a secure portal for document exchange, and 54 percent expect to see return status without emailing the firm. Email-as-portal is no longer competitive, and a client uploading a 1099 at 11pm on a Sunday in February is the median case, not the exception.

For software vendors, the accounting, tax, and document stack is increasingly evaluated as one unit. Firms ask how a tax product integrates with secure file exchange, e-signature, and engagement letters. Hosted delivery answers the uptime question by inheriting the underlying cloud SLA, and shared storage plus shared identity make integration a matter of file paths rather than fragile export-import scripts.

Hosted versus closet server

Frequently asked questions

The firms that came through the last three tax seasons intact stopped treating infrastructure as a partner-track distraction. If you build accounting, tax, or workflow software, the question is whether your customers get a hosted option from you or from a competitor who shipped one first.

Intro

Manufacturing software has been the slowest enterprise category to leave local servers. Accounting moved years ago. CRM moved earlier. ERP, the system that tracks work orders, routings, BOMs, and WIP dollars, stayed on a tower next to the controller’s desk. That gap is now closing fast, and the reason shops give is rarely cost. It is uptime, multi-site visibility, and the fact that the IT generalist who used to babysit the ERP server retired and was not replaced.

The three-shift problem

A single-shift shop has natural quiet hours. The server reboots at 2 a.m., backups finish overnight, patches land on Sunday. None of that is true at a two-shift or three-shift operation, or at job shops flexing weekend overtime.

Patch Tuesday turns into a planning meeting. Backups bleed into production windows. A failed RAID controller at 3 a.m. on a Saturday stops being an IT problem and becomes a problem for the foreman who cannot clock jobs.

Cloud hosting changes the math because the underlying compute is no longer the customer’s problem. Host-level patching is transparent, storage is redundant by default, and the application itself can be updated by rolling session hosts in waves. Users either notice nothing or reconnect in a few seconds.

Shop floor, back office, and multiple sites

Most ERP installs are not one application. They are a constellation: core ERP, shop floor data collection, scanners, CAD or CAM links, a quality module, sometimes an MES tier. The pieces talk through direct database access, file shares, and middleware someone configured in 2014 and is afraid to touch.

That stack works on a single VLAN. It falls apart across a remote office or a second site. Hosting the ERP and its adjacent services in the same cloud tenancy fixes the topology without rewriting anything. Latency between components stays sub-millisecond. Users connect to published applications from anywhere and the integrations keep working.

Geography is the most common reason an SMB manufacturer outgrows on-prem ERP. A second location, an acquisition, or a finishing operation across town turns “where does the database live” into a daily problem. With hosted delivery there is one database, one source of truth, and an identical experience at every site. No VPN to tune, no replication to break, no shadow inventory.

Why vendors face pressure to offer hosting

A few things have shifted between 2023 and 2026. Cyber insurance carriers ask pointed questions about where ERP runs and how recovery works, and a single backup tape often fails underwriting. Customer IT staff have shrunk. The lone generalist at a 120-person shop is not managing SQL Server, Windows Server, Active Directory, and an ERP application competently.

Customer expectations have also been reset by every other piece of business software they touch. If CRM and accounting are hosted and ERP is not, ERP looks like the laggard. The vendors winning renewals are the ones who can say yes to a hosted option, even when hosting is not their core competency. That is where a partner model becomes practical: the vendor keeps building manufacturing software, and a hosting partner takes on the tenancy, patching, backups, and day-to-day operational work.

Cloud-hosted vs on-prem ERP for manufacturers

Frequently asked questions

If you build ERP for manufacturers and your customers are asking about hosting, a partner-delivered hosted tier is usually a short conversation worth having before the next renewal cycle.

Professional services firms kept practice management on a back-office server long after other verticals moved on. The reasons were sound: trust accounting carries personal liability, audit trails need to survive bar scrutiny a decade later, and privilege gets messy once a third party touches storage. By 2025, the ABA’s Legal Technology Survey showed 60% of firms running cloud-based practice management, up from 38% in 2019. Aging servers, ransomware events at peer firms, and attorneys working from everywhere finally moved the needle.

Trust accounting and what bar associations actually require

State bar opinions issued between 2020 and 2025 generally permit cloud-hosted trust accounting, provided the firm exercises reasonable care in vendor selection. In practice that means immutable audit logs capturing who viewed or modified ledger data, documented data residency, testable restores of specific transactions, and clear answers about who holds encryption keys.

Hosted deployments of established Windows-based practice management handle most of this natively, because the software was built around these requirements long before cloud was a question. SaaS rewrites sometimes lose that depth and have to rebuild compliance from scratch. That gap is the single most common reason firms switch and then switch back.

Document control and state-by-state compliance

Document management here is not about storage. It is about ethical walls at the document level, instant revocation when a partner leaves, audit logs that show every file a contract attorney touched, and restricted access groups that survive personnel changes. Hosted environments often enforce these requirements more consistently than on-premises deployments, because access control is centralized and no local file server is caching credentials.

National firms face a second layer: compliance varies by jurisdiction, and the system has to enforce the strictest applicable rule per matter. Mature hosted software handles this through configuration, not code forks. One deployment serves firms across all 50 states.

Distributed work and the hosted advantage

Thomson Reuters’ 2025 State of the Legal Market found 78% of attorneys at firms over 50 lawyers regularly work from multiple locations. On-premises deployments handle this poorly. VPNs add latency and break with updates. Self-hosted RDS works but needs IT staff smaller firms do not have.

Hosted practice management running on cloud infrastructure gives attorneys the full Windows application from any device, with identical behavior in the office, at a deposition, or in a hotel. Provisioning a contract attorney takes minutes. Revoking access is instant. Audit logs capture exactly what was touched during the engagement.

Client portals follow the same pattern. Bolting a portal onto an on-prem system requires internet exposure the practice management server should not have. In a hosted environment the portal lives inside the same security perimeter, which is why most vendors now ship portals as part of their hosted tier.

Frequently asked questions

The firms most loyal to depth and compliance are not lost to cloud as a category. They are lost to vendors who never offered cloud as an option for the software those firms already trusted.

Field service has quietly changed. The dispatch board left the whiteboard, the work order left the clipboard, and customers who used to call now text. Mid-market shops driving most of the growth are asking their software vendor one question on repeat: when are you going to host this for us? This post is for the vendors deciding whether to build, partner, or wait.

The dispatcher-to-truck gap

Every field service business runs on the gap between the office and the truck. A dispatcher sees an emergency call, a tech twenty minutes away just wrapped up, and there is a ninety-second window to reroute before the customer phones a competitor. The software in that window has one job: move information without friction.

On-prem software handles this through VPN tunnels, polling intervals, or a remote session into the office server. Each one works until it does not. The VPN drops on a cellular handoff. The polling interval is two minutes and the tech misses the reroute. The remote session times out while the tech is under a sink.

Hosted field service management changes this because the application no longer sits behind the office internet connection. The dispatcher and the tech both connect to the same hosted environment from wherever they are, and the link quality depends on the public internet, not on the office router someone unplugged on Tuesday. This is one of the cleanest selling points a hosted tier offers, because it maps directly to revenue the customer can measure.

The accidental IT person

Walk into any ten to fifty person field service business and ask who handles the software. The answer is almost never an IT person. It is the office manager, the controller, the owner’s spouse, or the senior dispatcher who happens to be good with computers.

This is the person who notices when backups stop running, reboots the server when the database locks, and calls the vendor at 6:50 AM when nothing is loading. For them, cloud hosting is not a technical preference. It is a quality of life change. They stop being responsible for uptime, patching, and the box in the closet.

Vendors should understand this clearly. The buyer signing the check is often this same person, or their boss watching them struggle. A hosted tier closes deals for reasons that have nothing to do with features. Sometimes the office manager just gets to stop being an accidental sysadmin.

Why on-prem vendors keep losing mid-market deals

The pattern in 2026 repeats across every field service vertical. A vendor with a mature on-prem product, ten or fifteen years of feature depth, loses a mid-market deal to a SaaS-native competitor with two-thirds the functionality. The stated reason is always the same: they offered cloud.

What is actually happening is that the buyer translated “cloud” as “this will not be my problem.” The SaaS-native vendor showed up with a one-page deployment story. The on-prem vendor showed up with a server spec sheet and a list of customer responsibilities. The buyer is purchasing an operational model, not a feature set.

For multi-location operators the gap is sharper still. Private equity rollups with three to forty branches cannot run forty servers, and per-branch databases mean per-branch reporting headaches. A hosted single-tenant model with branch as a dimension collapses all of that. Offering hosting closes the deal without a product rewrite. It is a packaging change, not a re-platforming.

Cloud-hosted vs on-prem field service software

Frequently asked questions

On-prem is not going away in 2026, but the middle of the market now expects a hosted option to be available when they ask. Vendors weighing what a hosted tier looks like for their product can book a fifteen-minute consult with CloudTopSaaS to map out the path.