Building and facility services

Fire and life safety origination playbook

Separate suppression, alarm monitoring, inspection and installation so a compliance thesis rests on the correct service scope.

Last reviewed · report an error

A research template, not investment advice. Figures are not stated where the public record does not support them.

Sector
Fire and life safety
2022 U.S. NAICS

238220 · Plumbing, Heating, and Air-Conditioning Contractors

561621 · Security Systems Services (except Locksmiths)

Classification limits
Starting points for discovery, not a complete niche definition. Classify the actual activity and verify scope against the U.S. Census NAICS reference.

Understand the operating model

Fire and life safety spans several businesses: suppression installation and service, alarm systems, extinguisher work and inspection. A single category label conceals different technical authorizations and customer obligations. The listed codes are starting points for suppression contracting and alarm services, not a complete classification of every inspection activity.

Revenue can combine installation projects, scheduled inspection visits, deficiency repairs and monitoring arrangements. Inspection frequency and required scope depend on the system, jurisdiction and applicable requirements. Do not translate a general compliance obligation into a guaranteed contract for a particular provider or a guaranteed customer renewal.

Local authorizations, installed-system knowledge and building relationships can support distinct operators. The origination hypothesis is that retained inspection relationships and competent service delivery matter. Test it against actual contracts, technician scope and deficiency conversion; it weakens where the business mainly wins one-off installation tenders.

What makes a target worth investigating?

These are fit hypotheses to test against your mandate. They are not verified attributes of any company or a prediction of acquisition performance.

  • System categories, technician qualifications and operating jurisdictions documented separately.
  • An inspection and service workflow with traceable reports and clear responsibility for outstanding deficiencies.
  • Customer and system records that can be transferred subject to contracts, privacy and authorization requirements.

Screening questions for Scout

Tailor these questions before collection. Each accepted answer needs a supporting verbatim excerpt from a retained page. Options describe permitted answers, not default assumptions. When no source supports an answer, leave it unanswered; absence from a website is not a “no.” See screening criteria for defining gates and weights.

QuestionAnswer typeOptionsWhy it matters
Which systems are explicitly supported?one ofSuppression / Alarm / Extinguishers / Multiple systemsDifferent systems require different capabilities; do not infer one from another.
Which activity is emphasized?one ofInspection and testing / Service and repair / Installation / Monitoring / MixedDistinguishes recurring obligations from project work without guessing revenue shares.
Is monitoring delivered directly rather than only referred?yes/noSource-supported entriesFlags third-party station dependence and the identity of the contracting provider.
Which jurisdictions and authorizations are disclosed?listSource-supported entriesThe relevant requirements must be checked locally; a national service claim does not prove authorization.
Are inspection records or customer reporting services described?yes/noSource-supported entriesIdentifies a process capability while leaving record completeness for diligence.
Does an excerpt show this stop condition: A compliance-service label unsupported by identifiable systems, scope or operating entity?yes/noSource-supported entriesTriage applies this gate before research is paid for. It needs a quoted excerpt and the written mandate; silence leaves the question open and never answers yes or no.
Does an excerpt show this stop condition: Installation-only work outside an inspection-led mandate?yes/noSource-supported entriesA second gate checked before detailed collection. An unresolved fact stays open for review; it does not become a negative finding.
Does the record support this fit hypothesis: System categories, technician qualifications and operating jurisdictions documented separately?yes/noSource-supported entriesTreat it as a hypothesis to test against the mandate, not a verified attribute of the company. Unsupported answers stay unanswered.
Suggested question schema. Financial mix, retention and operating performance usually require direct records at a later stage.

Four questions apply to every playbook (ownership category, locations, sale process, exclusions) and are listed once on the playbooks overview.

What public evidence can establish

Match every source to the correct entity, location and collection date. Use the data-source directory to choose discovery paths, and evidence standards to decide what an excerpt actually supports.

SignalWhere to lookLimits
Licensed installation scope
Relevant state contractor records for suppression or alarm work.

Source guide →

Not every service falls under the same licence; check each activity rather than the brand.
Inspection offering
Service pages identifying systems and testing activities.

Source guide →

An offering does not establish contractual cadence, current customers or completed compliance.
Technical specialization
Trade association directories with named service categories.

Source guide →

Directory membership does not establish accreditation or current authorization.
Monitoring relationship
Published monitoring terms and descriptions of delivery partners.

Source guide →

Marketing may obscure subcontracting; confirm the contracting and servicing entities directly.
Legal identity and trading names
State entity records matched against the website's legal notices and contact details.

Source guide →

Registration establishes an entity, not its ultimate beneficial ownership, operating scale or willingness to transact.
Current operating roles
Dated vacancies describing supervisors, delivery staff and administrative responsibilities.

Source guide →

Vacancies describe hiring intentions. They do not establish filled positions, employee totals or an imminent succession event.

Ownership and succession signals

  • A technical principal who also signs reports may be a delivery dependency. Establish who can assume those responsibilities without presuming that the principal wants to leave.
  • Compare dated leadership pages with entity records and transaction announcements. A missing management biography is an evidence gap, not proof that the owner lacks a successor.
  • These are research signals, not proof of intent to sell. Confirm control, decision rights and succession preferences directly through an approved conversation before treating them as transaction facts.

Read succession and ownership before turning a continuity question into an ownership claim.

Reasons to stop or separate the record

Apply a disqualifier only when supported by evidence and your written mandate. Unresolved facts stay open for review; they do not become negative findings.

  • A compliance-service label unsupported by identifiable systems, scope or operating entity.
  • Installation-only work outside an inspection-led mandate.
  • Unresolved authorization gaps for the territories or systems the mandate requires.

Approach with context and approval

  • Use precise system terminology and ask about business continuity without suggesting deficiencies at the target's customers.
  • Avoid claiming a universal inspection schedule or guaranteed regulation-driven growth.
  • The client approves each target and the messaging before contact. Check suppression records and applicable channel requirements; coordinate email, LinkedIn and phone so the business receives one coherent approach.

Use the outreach compliance guide to define channel requirements and suppression handling before optional outreach begins.

Questions for later diligence

These require direct records, management access and appropriate specialist review. Public screening identifies the questions; it cannot settle them.

  • Sample inspection reports, deficiency follow-up, technician authorization and quality controls by system type.
  • Review contract renewals, customer assignment rights, monitoring counterparties and record migration requirements.
  • Investigate liability history, missed inspections and the resources needed to maintain promised coverage.

Use these theses to frame confirming and disconfirming evidence, then choose a sourcing method suited to the target universe.

Adjacent playbooks

Where to check this

Recurring inspection is the economic core of this niche, and it is set by codes: NFPA 25 for water-based systems and NFPA 72 for fire alarm and signaling, adopted and enforced locally. Ask what share of a company's work is code-driven inspection against one-off installation, and whether monitoring is performed in-house or contracted to a central station listed with The Monitoring Association.

Sources

Related articles

Send us ten targets. We research them for free.

A target list and your acquisition criteria are enough. You get back company records with scores, the evidence behind every field, and the questions the public record could not answer.