Private equity · Fire protection platforms
Multi-branch operators and acquisition platforms run inspections, service, and compliance on Inspect Point, with 1,000+ technicians in the largest single deployments. Every company you own inspects to the same code-aligned question sets on one data model, so a deficiency count or a proposal acceptance rate means the same thing in the company you bought last quarter as in the one you started with. The ERP stays, every screen filters by branch, the next add-on onboards to that standard, and at exit the data leaves as a full export.
Inspect Point at scale
Inspect PointTroy, NY
60%
Margin strong operators earn on inspection and service work at scale
Test and inspection work carries the strongest margins in fire protection, and it recurs on the code’s calendar rather than the sales team’s. Across the customer base, field inspections run 67% faster, proposal acceptance has doubled, and service revenue runs up to $4 for every $1 inspected. Nearly half of Inspect Point customers have expanded past their first purchase.
OutcomesInspect Point customer base
| Proposal acceptance | 2× |
|---|---|
| Field inspections, faster by | 67% |
| Service revenue per $1 inspected | Up to $4 |
| Expanded past first purchase | 49% |
“With Inspect Point, we’re able to quote the deficiency, create the work order, and dispatch the work order to the technicians directly from the report.”
Hampshire Fire ProtectionNew Hampshire180 people, ten acquisitions
2×
“We have doubled our production since having it.” Glen Wells, Hampshire Fire. Ten acquired companies on one system, and reports read the same across the sprinkler, extinguisher, and alarm divisions.
“We do everything in fire protection. With 180 employees, we needed to change and get something as dedicated to fire protection as we were.”Jimmy Snowden · Hampshire Fire Protection
One Inspect Point instance is segmented into territories by branch, region, department, or customer group; buildings, technicians, and back-office users are assigned to one, and every backend screen filters by it: dashboard, buildings, inspections, schedule, proposals, deficiencies, reports, time entries. Branch staff see their own book. Leadership flips the filter and reads the whole portfolio from the records the field wrote.
Branch roll-upMonth to date
| Branch | Inspections | Open deficiencies | Proposals out | Invoices paid |
|---|---|---|---|---|
| Northeast | 312 | 41 | $86K | $210K |
| Southeast | 268 | 67 | $112K | $174K |
| Midwest | 195 | 28 | $54K | $141K |
| Acquired · week 3 | 44 | 19 | $12K | $9K |
Rolled up from the records the field wrote
Territory access sets what a user can see; the territory filter sets what they are viewing. Apply it once and a regional manager compares branches on the screens the branches work in, without a report someone built for the meeting.
Filters on · dashboard · buildings · inspections · schedule · proposals · deficiencies · reports · time entriesInvoice Insights (total invoiced, total due, outstanding customers, a monthly issue history) and Proposal Insights (approval rate, average approval time, proposals and dollars by status) filter by territory and report on the proposals and invoices that run in Inspect Point. Inspection Assistant Insights tracks issues caught, resolved, and escaped over time, with a technician-level view.
Territory filter · Invoice Insights · Proposal InsightsDBA headers, the cover letter, report settings, tag colors, and labor rates are set per territory. The add-on runs on the platform’s standard while its customers and AHJs keep seeing the name they know, so standardizing the inspection layer does not mean rebranding the book you just bought.
Per territory · DBA · cover letter · report settings · ratesThe Inspect Point Assistant answers from the same live data: overdue inspections, open deficiencies, revenue. Nothing gets exported first and nobody waits on a report.
Inspect Point Assistant · live data · 30-minute undo on bulk actionsEach acquisition arrives with its own records and its own back office. Buildings, contacts, systems, and assets move with the company. Scheduling, dispatch, customer records, invoicing, and billing can stay in the ERP the company runs today, with Inspect Point as the inspection layer syncing to QuickBooks Online and Desktop, Sage, BuildOps, Simpro, and ComputerEase out of the box, and paid custom builds for Dynamics 365, Odoo, Q360, NetSuite, and others. Where proposals and invoices run in Inspect Point, its insight dashboards report on them; where they stay in the ERP, that reporting scope is part of the integration plan. Technicians on Android hardware move to iPads. The rollout runs crawl, walk, run.
Rollout3 phases
Buildings, contacts, systems, and assets come in the same door for every acquisition, including the one that closed last quarter. An Android shop budgets iPads here.
Technicians are inspecting in the platform early in implementation, so the acquired inspection book starts landing in the roll-up before the project is over.
The tenth company runs the same way as the first, one at a time or all at once.
Start with one company or one division, prove the model, then onboard the rest. Enterprise plans start at 15 technicians; below that, plans start at three technicians, or one or two technicians running 400 or more inspections a year.
Buildings, contacts, systems, and assets come in at onboarding. If a company is sold on its own or moves off the platform, it leaves with a full export.
NFPA, ULC, AES, Joint Commission, DNV, and regional forms by jurisdiction share one library, and every company inspects from it.
Every territory runs the same workflows. An add-on with a healthcare book or a Canadian one inherits the forms at onboarding.
Buildings, systems, assets, and deficiencies are structured records down to the component, identical across every brand you own.
The chain runs inspection to deficiency to proposal to work order to invoice, and nothing is re-entered downstream: the deficiency that becomes a proposal, a work order, and an invoice is the record the technician wrote. Proposals are included from Gold and service work orders from Platinum; see plans.
Alarm, sprinkler, extinguisher, suppression, backflow, doors and dampers, and special hazards run on the same library of trade-specific question sets, independent of manufacturer or panel ecosystem. Whatever the add-on installs, its inspections run on the portfolio’s standard.
Our code experts maintain the question sets as editions and jurisdictional requirements change. The cost of keeping forms current sits with us.
An accepted proposal is where a found deficiency turns into the service work that carries the margin. Across the customer base, proposal acceptance doubled on Inspect Point. Getz Fire Equipment went from one in five to more than seven in ten.
Getz Fire Equipment · 20% → 70%+ acceptedEvery inspected system with an unserviced deficiency is service revenue left on the table. Up to $4 in service revenue for every $1 of inspections is the ratio to manage toward, and on one data model it is measured the same way in every company you own.
Deficiency → proposal → work order → invoiceThe edition a jurisdiction enforces sets what the form has to ask. On Inspect Point, NFPA 25 follows the code year you pick, with a per-building override, and code experts maintain the question sets as editions change.
Question sets · NFPA · ULC · AES · Joint Commission · DNVThe ERP can stay; the inspection software is what changes. Buildings, contacts, systems, and assets move, and crawl, walk, run puts the technicians on the platform trade by trade and office by office.
Crawl · walk · runEmail and portal uploads are labor and lag. Inspect Point submits from the report to The Compliance Engine, IROL, and LivSafe, the three major AHJ compliance portals.
TCE · IROL · LivSafeInspect Point holds a SOC 2 Type II attestation and runs GDPR-aligned practices, with data encrypted in transit and at rest. The report is available under NDA through the account team; details on the security page.
Buildings, contacts, systems, assets, and inspection history come in at onboarding and leave with the company as a full export, on request. The same export applies if one portfolio company is sold on its own.
Company content is not used to train public models. Bulk actions preview first and can be undone for 30 minutes.
ControlsSecurity review
| Attestation | SOC 2 Type II |
|---|---|
| Practices | GDPR-aligned |
| Encryption | In transit · at rest |
| Access | Set per user, by territory |
| Export | Full, on request |
| Public-model training | Your content excluded |
| Undo window | 30 minutes |
The platform running three brands on three systems with no roll-up view, the add-on still on paper, or the company in diligence: any of them walks through live in the platform, company by company.
The walkthrough produces the rollout order, which of each company’s systems stay and sync, and where the integration seams fall. The enterprise team has run multi-branch rollouts before, with a support team behind it that knows fire protection.
Bring the operating partner or the platform CEO into the same session.