Commercial Due Diligence on a Fire-Inspection Software Vendor: What a Buyer Should Believe Before Bidding

1. The recurring base is real and durable. Contract-level records must reconcile ARR to billings and recognized revenue. GRR and NRR must survive consistent cohort definitions, and the loss or repricing of a large contractor platform must not overturn the growth case.
2. Compliance depth changes customer behavior. Customer and industry interviews, product demonstrations, and inspection-record tests must show that Target Co. materially reduces documentation work or errors compared with credible alternatives. A code-driven end market does not, by itself, give any software vendor a moat.
3. Expansion is profitable and repeatable. New-account acquisition, seat and module expansion, and payments must be separated. The buyer needs measured customer acquisition cost (CAC), payment adoption and margins, and evidence that implementation and support costs do not rise faster than account value.

The valuation implication is substantial. Supplied third-party estimates span 2.8–4.9× revenue for core field-service software, approximately 4.0× for a private SaaS M&A median, 4.2× for one vertical-SaaS sample, 5.8× for another vertical-SaaS median, and approximately 7.0× for field services. They cover different populations and are not a single comparable-company set. Applied mechanically to current $38.0 million ARR, 2.8–7.0× produces $106.4–$266.0 million of enterprise value (EV). Those are EV/ARR illustrations, not transaction prices or directly comparable EV/revenue valuations.

Market Attractiveness: Recurring Work, Conditional Software Demand

**NFPA 25** addresses inspection, testing, and maintenance of water-based fire-protection systems. **NFPA 72** addresses fire alarm and signaling systems. These standards support recurring contractor workflows. The legal requirements, applicable editions, system types, frequencies, and enforcement practices depend on jurisdiction and adoption. Extinguisher work belongs in the target customer definition, but its applicable requirements need separate local-code validation; neither linked standard establishes a universal extinguisher-inspection schedule.

The software opportunity follows from the work surrounding an inspection: identifying an asset, scheduling a technician, recording results, documenting deficiencies, delivering a report, quoting remedial work, and preserving a history for the customer. A contractor can face recurring compliance work without purchasing Target Co.’s software. The buyer must establish which steps are genuinely costly in customers’ current processes and who controls the purchasing decision.

A fragmented contractor base and private-equity-backed contractor roll-ups are commercial hypotheses to test, not quantified findings in the supplied sources. Fragmentation could favor small-account acquisition; a roll-up could deploy one product across acquired branches. The reverse is also possible: a consolidator can standardize on a rival system and remove several accounts at once. Interviews should cover independent shops, multi-branch operators, and buyers that have recently integrated acquisitions.

Bottom-up US software opportunity

Assumption: The addressable universe contains 15,000 US fire and life-safety contractor accounts. No verified contractor census accompanies that estimate; overlapping specialties, branches, and legal entities could materially change it. Financial assumption (illustrative): Potential annual spend is $25,000 per account at full adoption. This is above Target Co.’s derived current average of roughly $15,833, so it assumes a richer market-wide spend opportunity rather than merely extending today’s realized average.

At the central full-adoption assumptions, $38.0 million ÷ $375.0 million equals 10.1% implied ARR-to-TAM penetration. The roughly 2,400 customers equal 16.0% of the assumed 15,000-account universe. Those percentages differ because the TAM uses $25,000 per account while Target Co.’s derived ARPA is lower; neither is verified market share. If the entire universe instead spent today’s derived Target Co. ARPA, the calculation would be approximately 15,000 × $15,833 = $237.5 million. The TAM therefore depends at least as much on spend and account definitions as on contractor count. Before a bid, obtain a deduplicated account list and price/seat evidence by contractor size; do not capitalize the $375 million headline as an established market fact.

Competition: Test Depth Against Breadth

The buyer should compare real alternatives through the same inspection-to-repair workflow, not through feature-list counts. ServiceTrade describes its fire-protection software offering; ServiceTitan’s investor-relations site establishes a public trades-software reference point, but a public-company valuation or product breadth would not establish Target Co.’s niche win rate. The other named vendors below are comparison candidates specified for this diligence. Their precise fire-inspection coverage, pricing, and win rates have not been verified by the supplied sources.

The defensible claim is narrower than “specialists always beat generalists.” A niche product can win if it handles assets, inspection evidence, jurisdictional variation, and follow-up work more reliably at an acceptable total cost. A broad platform can win if its accounting, scheduling, and management suite reduces the need for separate systems. Request recent, dated win/loss records and run equivalent demonstrations using actual customer-form samples. Distinguish a missing feature from a feature available through configuration or an integration.

Growth Drivers and Their Durability

Recurring inspection activity is the strongest underlying demand driver, subject to applicable code adoption. It creates repeated workflow volume, not guaranteed software renewals. Its commercial durability should be tested through active assets managed per customer, inspection completion, and whether customers retain records in Target Co. after contracts or personnel change.

New-logo penetration has room but an uncertain ceiling. On the central market assumptions, 2,400 accounts leave 12,600 potential accounts before fit or adoption screens. Many may be too small for $25,000 annual spend, already committed to another system, or counted twice through branches. Segment the prospect universe and compare acquisition costs and realized ARPA for each segment.

Contractor consolidation has two-sided economics. A parent company could expand seats and standardize Target Co. across acquisitions, raising NRR with limited incremental selling. It could instead negotiate lower prices or mandate a competing platform. Track ARR by ultimate parent, not just billing entity, and compare acquired-branch deployments with post-acquisition cancellations.

Service-lifecycle cross-sell is plausible but execution-dependent. Inspection findings can lead to quotes, repair scheduling, invoicing, and asset updates. Additional modules should improve a contractor’s documented workflow, not merely increase product complexity. Measure conversion from recorded deficiency to quote and completed repair, plus module-level gross margin and retention.

Embedded payments can monetize transaction flow, but their durability is unproven. Seven percent of revenue is a revenue mix, not the percentage of customers using payments. Processing yield, eligible invoice volume, payment gross margin, chargebacks, and processor terms determine whether more payment revenue improves value. None is provided. These distinctions matter particularly if payments grow faster than software subscriptions and obscure core ARR growth.

Customer Concentration and Cohort Quality

Financial assumption (illustrative): Top-10 ARR is $38.0 million × 22% = $8.36 million; the largest account contributes $38.0 million × 6% = $2.28 million. One account therefore represents more than two-thirds of the assumed annual gross starting-book erosion of $3.42 million calculated below. That is a scale comparison, not a prediction that it will churn.

The following nonoverlapping distribution adds assumptions for the top 20 and top customer decile. It avoids counting the top 10 twice.

The top-20 and top-decile shares are modeling choices, not findings. A parent-level concentration analysis could be higher if multiple billed accounts belong to one contractor platform. Obtain contract terms, renewal dates, payment histories, and implementation status for the largest accounts; interview a sample without allowing management-selected references alone to determine the answer.

Financial assumption (illustrative): GRR is 91% and NRR is 108%, both measured against the same opening-customer ARR. On a $38.0 million opening book, gross losses and contractions are $38.0 million × 9% = $3.42 million. Gross retained ARR is $34.58 million. Expansion of $38.0 million × (108% − 91%) = $6.46 million brings that opening book to $41.04 million. The 17-percentage-point gap is expansion relative to opening ARR; it is not a customer-adoption rate.

Financial assumption (illustrative): The three vintage allocations and their identical retention rates are teaching examples, not historical cohort observations. Actual vintage performance may differ sharply. Under the base case, reaching $47.12 million next-year ARR requires $47.12 million − $41.04 million = $6.08 million of new-customer ending ARR, assuming the supplied retention rates apply to the entire opening book for that year. At today’s average ARPA, that is roughly 384 average-sized account equivalents ($6.08 million ÷ $15,833), not a forecast of logo additions: new customers may have different prices, start dates, and payment arrangements.

For diligence, calculate GRR and NRR by start vintage, account size, specialty, acquisition channel, and ultimate parent. Keep new-logo ARR out of NRR. Separate logo loss, price reductions, seat reductions, price increases, added seats, and new modules. A 91% GRR does not imply 9% logo churn: downgrades can cause revenue erosion without a customer leaving.

Business Model and Unit Economics

The stated profile supports ARPA arithmetic but not a measured CAC or LTV. Financial assumption (illustrative): $38.0 million ARR across approximately 2,400 accounts gives $15,833 annual ARPA, or approximately $1,319 per month. Financial assumption (illustrative): Applying the stated 78% blended gross margin to ARR as a proxy produces $12,350 annual or $1,029 monthly gross profit per average account. Recognized-revenue margin and ARR do not necessarily have matching product mixes; this is a unit-economics convention to verify.

Financial assumption (illustrative): Suppose gross-profit CAC payback is 16 months. Then implied, rather than measured, CAC is $1,029 × 16 = approximately $16,467 per acquired account. Sales-and-marketing costs, acquired-logo counts, and implementation economics have not been supplied. A real payback calculation needs fully loaded acquisition expense matched to the customers acquired and their realized gross profit.

LTV is even more conditional. Financial assumption (illustrative): For a simple sensitivity only, treat annual logo attrition as 9%, hold per-account revenue and gross margin constant, and exclude expansion, discounting, and costs beyond cost of revenue. These assumptions do not follow from GRR. Simple gross-profit LTV is then $12,350 ÷ 0.09 = approximately $137,222. Dividing by the payback-implied $16,467 CAC gives 8.33× LTV/CAC. A previously posited 4.5× ratio would not reconcile with that same 16-month payback and 9% attrition model; at the same LTV it would imply about $30,494 CAC and 29.6 months’ payback. Neither ratio is an observed Target Co. result. Do not compound 108% NRR indefinitely to manufacture LTV.

Payments need a separate bridge. Financial assumption (illustrative): If annual recognized revenue happens to equal $38.0 million and includes the payment line, then 7% payment revenue is $2.66 million, leaving $35.34 million of nonpayment recognized revenue. This does not establish that payment revenue is ARR, or that nonpayment revenue equals software ARR. Financial assumption (illustrative): At 30% payment gross margin, payment gross profit would be $2.66 million × 30% = $0.798 million. If the total 78% gross margin also applies to that $38.0 million revenue base, total gross profit is $29.64 million and the implied nonpayment gross margin is ($29.64 million − $0.798 million) ÷ $35.34 million = 81.6%. This illustrates why growing a lower-margin payment line could dilute the blended margin. It does not establish payment profitability after fraud, support, or processing arrangements.

Measure payment attach as active payment-using accounts divided by eligible accounts. Measure yield as payment revenue divided by processed volume. Neither denominator is available; 7% revenue mix must never be presented as 7% attach.

Valuation Context: A Spread, Not a Comp Set

The supplied market commentary consists of third-party estimates with different samples and denominator conventions. In particular, Windsor Drake’s private SaaS report describes an approximately 4.0× EV/TTM revenue median, attributed there to SEG, while its Q2 2026 vertical-SaaS report describes approximately 5.8× for vertical SaaS versus 4.1× for horizontal SaaS and approximately 7.0× for field services. Those estimates disagree materially with Eilla’s core field-service-management range of 2.8–4.9×. A Yanne Capital press release distributed via EIN Presswire describes a 4.2× H1 2026 median for its selected vertical-SaaS sample and says sponsors accounted for 63% of deals. These are source-described estimates, not independently validated transaction data for this report.

Financial assumption (illustrative): The EV column substitutes ARR for the revenue denominators described by the sources. Its figures are therefore EV/ARR sensitivities. A comparable EV/revenue analysis requires Target Co.’s trailing recognized revenue, payment accounting and mix, growth period, profitability, transaction perimeter, and debt-free/cash-free terms. The spread is a reason to reconcile those items before bidding, not a reason to select the most favorable multiple. No conclusion about buying or selling a listed security follows from the ServiceTitan reference.

Illustrative One-Year Scenarios

Financial assumption (illustrative): Measure the scenarios one year after the $38.0 million ARR starting point and treat that date as a hypothetical exit. Base growth continues at 24%; upside growth is 40%; downside growth is 4%. Scenario EBITDA margins and EV/ARR multiples below are modeling choices, not expected outcomes. Financial assumption (illustrative): EBITDA dollars use annual recognized revenue equal to ending ARR. Without that additional convention, an EBITDA margin cannot be converted into dollars from ARR alone.

The downside calculation is $39.52 million, not a rounded $39.50 million input. The base 5.0× multiple sits between the source-described 4.2× and 5.8× estimates; the 7.0× upside tests the field-services figure rather than asserting Target Co. merits it. Holding base ARR fixed isolates multiple risk: $47.12 million × 4.0 = $188.48 million EV, versus $47.12 million × 7.0 = $329.84 million EV, a $141.36 million difference without changing operations.

EV is not equity value or an acceptable bid. Equity value equals EV minus net debt, subject to working-capital and other closing adjustments. Financial assumption (illustrative): Only if net debt and all other adjustments were zero would equity value equal the EVs shown. The profile supplies no balance sheet or entry price, so these cases do not establish proceeds or investment returns.

Red Flags and Open Diligence Questions

The following are tests, not assertions that defects exist. Prioritize the first two groups before relying on a valuation multiple.

Revenue quality and financial integrity

1. ARR perimeter: Which contracts and payment fees enter ARR? Reconcile each customer’s contract, billings, recognized revenue, and ARR movement. Red flag: transaction fees classified as committed recurring software.
2. Recognition: Are payment fees reported on an appropriate gross or net basis, and are implementation charges separated? Red flag: denominator inflation in revenue or margin comparisons.
3. Retention definitions: Are GRR and NRR calculated on identical opening populations and dates? Red flag: new-logo bookings or acquired accounts counted as expansion.
4. Margin by product: What are software, implementation, and payment gross margins after support and processing costs? Red flag: blended 78% margin masking weak incremental economics.
5. Acquisition efficiency: What fully loaded spending and new-logo counts produce actual CAC payback? Red flag: attractive payback based on an unallocated or selectively chosen cost base.

Customers and commercial position

1. Ultimate-parent exposure: How many top accounts share a parent, renewal decision-maker, or contractor consolidator? Red flag: concentration above the legal-entity view.
2. Largest-account durability: When does the $2.28 million illustrative largest account renew, and what rights does it have to reprice or terminate? Red flag: near-term platform-wide migration.
3. Cohort dispersion: Which vintage, size, and specialty segments generate the assumed 91% GRR and 108% NRR? Red flag: aggregate growth dependent on a few expansions.
4. Competitive evidence: What do dated win/loss records and customer interviews say about ServiceTrade and other alternatives? Red flag: wins explained only by incumbent relationships or discounting.
5. Market count: Can a deduplicated contractor and branch database support the 15,000-account assumption? Red flag: an addressable universe much smaller than the bid model requires.

Product, operations, and compliance

1. Inspection accuracy: Do field records and generated reports preserve required data across applicable NFPA 25 and NFPA 72 workflows? Red flag: material manual reconstruction outside the system.
2. Code maintenance: Who owns standards updates and jurisdiction-specific configuration? Red flag: untracked, customer-by-customer report changes.
3. Implementation burden: What are median and high-end time-to-live, migration cost, and first-year customer profitability? Red flag: expansion requiring disproportionate services labor.
4. Reliability and portability: Can customers retrieve complete asset and inspection histories after an outage or termination? Red flag: weak recovery, audit trails, or export capability.
5. Integration dependency: Which accounting, scheduling, or processor connections are essential, and who controls them? Red flag: one third party can disrupt a core workflow.
6. Payments adoption: How many eligible accounts actually process payments, at what volume and net yield? Red flag: most payment revenue depends on a handful of accounts.

Contractual, legal, and transaction exposure

1. Documentation liability: What do customer contracts, insurance policies, and incident logs say about erroneous reports or missing records? Red flag: uncapped or uninsured exposure.
2. Consolidation clauses: Do change-of-control, assignment, or volume-pricing provisions alter economics after a contractor or Target Co. acquisition? Red flag: expected roll-up expansion becomes repricing.
3. Privacy and security: Are technician, building, and payment data access and retention controls evidenced by tests and incident history? Red flag: unresolved material findings.
4. Exit comparability: Are trailing recognized revenue, net debt, and deal adjustments available on a consistent basis? Red flag: an EV/ARR illustration presented as a transaction-ready EV/revenue bid.

Buyer View and 100-Day Value-Creation Plan

Recommendation: proceed with conditions. Commission transaction-specific financial and commercial diligence, but make any bid contingent on the three executive-summary truths. If the ARR bridge fails, the largest-parent exposure is materially understated, or compliance testing finds no meaningful customer advantage, re-underwrite the case and price from the verified facts rather than the illustrative base scenario. Do not assume that the upside case will pay for a high entry multiple.

1. Days 1–30: protect and measure the base. Establish a customer-level ARR ledger tied to contracts and the general ledger; separate software, services, and payments. Map ultimate parents and renewal dates, assign accountable owners to the top 10, and review open security or inspection-record incidents. Baseline GRR and NRR by segment before announcing expansion targets.
2. Days 31–60: prove the commercial motion. Interview lost prospects and recently renewed customers; run equivalent product tests against named alternatives. Build segmented acquisition reporting that matches fully loaded CAC to realized account gross profit. For contractor roll-ups, pilot an account plan that measures deployed branches and net pricing, not just contracted seats.
3. Days 61–100: pilot expansion with controls. Test one deficiency-to-quote or related service-lifecycle improvement with a defined customer cohort. Measure usage, gross-margin effect, and implementation hours. Test payments only after establishing eligible accounts, processed volume, contribution margin, and contractual processor risk. Continue, revise, or stop each pilot against its measured economics.

The 100-day objective is a trustworthy operating baseline and evidence for scalable growth, not an assumed jump from 24% to 40% ARR growth. Management should review software-only ARR, segment-level retention, realized CAC payback, payment contribution, and top-parent renewals in one reconciled monthly pack.

Principal Risks

These risks are connected. A smaller usable market can force sales into larger contractor platforms, increasing concentration; consolidation can then accelerate either expansion or churn. Product testing, parent-level retention, and segmented market sizing should therefore be read together rather than as independent workstreams.

Assumptions Register

All entries below are modeling inputs or conventions. Derived results elsewhere in the report follow from these inputs; none is a Target Co. observation.

Sources

• NFPA: NFPA 25, Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems
• NFPA: NFPA 72, National Fire Alarm and Signaling Code
• ServiceTrade: fire-protection and service software
• ServiceTitan: investor relations
• Windsor Drake: Vertical SaaS valuations, Q2 2026
• Windsor Drake: vertical SaaS valuation report
• Yanne Capital via EIN Presswire: vertical SaaS M&A multiple estimate
• Eilla: field-service-management software valuation playbook