Target a specific site and project trigger, then qualify the current controls, decision team, response requirements, serviceability, and budget path.
In brief
The best physical-security prospects have a site-level project, such as a new facility, system replacement, contract review, or repeated access problem. Target one project type in a serviceable area, then confirm the current controls, decision team, response process, and assessment path.
Guarding, patrol, alarms, monitoring, video, access control, locksmithing, consulting, and systems integration are different businesses. Define what the company is licensed and equipped to sell, install, monitor, maintain, and support in each territory before building a list.
Start with how the site operates: its purpose, hours, public access, critical activity, assets, current controls, known concerns, and response partners. Use incidents only when the customer can lawfully share them. Never manufacture urgency from neighborhood or demographic data.
A camera, guard, alarm, credential, gate, policy, or training course is only one control. Map what happens after an event: who verifies it, communicates, dispatches help, escalates, preserves evidence, restores operations, and reviews the outcome. Technology without an owned response path creates false confidence.
Inventory the sites, protected areas, users, devices, wiring, networks, power, panels, software, monitoring, contracts, permits, and integrations. Mark what can be reused, what needs testing or consent, and what remains unknown.
Price the assessment, design, permits, equipment, installation, testing, training, monitoring or guard labor, maintenance, software, connectivity, reporting, and contract exit. Compare the complete operating obligation, not a low hardware price or hourly rate.
A new location, expansion, lease, renovation, changed hours, new restricted area, system end-of-life, provider review, contract renewal, or approved risk project creates a concrete discovery reason.
These accounts can benefit from consistent credentials, monitoring, devices, reporting, maintenance, and procurement, but local systems, landlords, permits, responders, and site practices still require discovery.
A qualified takeover requires ownership, codes, contracts, devices, wiring, networks, software, records, compatibility, tests, defects, permits, warranties, data, and transition responsibilities.
A provider can support selected controls when leadership has defined people, operations, risks, responsibilities, policies, training, response, recovery, review, and budget instead of outsourcing the entire problem to equipment.
Owns physical conditions, access, utilities, contractors, maintenance, landlord coordination, installation windows, permits, acceptance, and ongoing service.
Defines scenarios, people, critical operations, existing controls, response, escalation, evidence, reporting, training, service levels, and outcome.
Review network and identity security, remote access, employee and visitor implications, recording, retention, biometrics, investigations, workplace policy, and legal authority.
Validate licensing, insurance, references, background and training standards, subcontractors, equipment ownership, pricing, labor, recurring charges, terms, renewal, termination, and financial approval.
Doors, users, hours, visitors, contractors, parking, yards, restricted areas, networks, response, and emergency plans may change. Discover the operating design before recommending controls.
Renewal, unsupported equipment, recurring failures, ownership disputes, rising cost, consolidation, or integration needs can justify review. Confirm contract and technical facts before claiming replacement savings.
Respond without blame or fear. Preserve appropriate evidence, respect investigations and affected people, identify immediate safety ownership, and avoid promising that one product will prevent recurrence.
Ask for the exact requirement, authority, date, scope, evidence, and acceptance route. Do not invent compliance obligations or imply an insurer, regulator, or customer endorses the provider.
We cover [market] and help [verified facility type] operators replace, expand, or take over access, intrusion, and video systems. Who owns physical-security systems at [company]? I can send the assessment checklist we use before recommending a site visit.
Share territory, services, supported systems, site prerequisites, information needed, stakeholders, assessment terms, response models, implementation range, and clear exclusions.
A system renewal, new site, access expansion, vendor review, or monitoring change is a respectful opening. Never claim to have found a blind spot, incident, unsafe employee, or vulnerable population from public data.
Explain detection, verification, notification, dispatch, escalation, customer action, emergency-service limits, evidence, restoration, reporting, testing, maintenance, and exception handling.
The physical-security example uses US warehouses and logistics operators to define the market. Each account still needs a suitable site, real project trigger, known current controls, responsible contact, and location inside the provider's service area.
| Category | Businesses | Unique emails / business coverage | Unique phones / business coverage |
|---|---|---|---|
| Warehouse | 48,000 | 24,500 (24.1%) | 38,500 (51.1%) |
| Logistics Service | 18,000 | 9,900 (37.3%) | 19,000 (90%) |
Research and data review by
Raphael CanyasseSphereScout founder; review covers source use, list-building, and data methodology
Updated August 10, 2026
Cybersecurity and Infrastructure Security Agency - Accessed August 10, 2026
Occupational Safety and Health Administration - Accessed August 10, 2026
Occupational Safety and Health Administration - Accessed August 10, 2026
Federal Trade Commission - Accessed August 10, 2026
Federal Trade Commission - Accessed August 10, 2026
Federal Trade Commission - Accessed August 10, 2026
Define one service, site type, territory, project range, response model, and exclusion set. Combine local search and referrals for active demand with narrow account outreach tied to verified changes such as a new site, system replacement, contract review, access expansion, or stated assessment need. Qualify operational fit before proposing equipment or guards.
Facilities, security, risk, loss prevention, operations, property, or an owner may own the requirement. IT, cybersecurity, privacy, legal, HR, safety, procurement, finance, insurers, landlords, and emergency partners may influence design and approval depending on the system and site.
The buyer should own a real site requirement and be authorized to discuss it. The requested service must fit the provider's territory and licenses, and both sides need a workable assessment, response, data, implementation, budget, and decision path.
Only with scope, authorization, confidentiality, access, safety, information handling, deliverables, assumptions, exclusions, ownership, and next steps defined. A remote review cannot establish hidden conditions, and an assessment should not imply certification, guaranteed prevention, or a requirement to buy.
Only make objective claims supported under the stated conditions. Crime, loss, alarm, response, and safety outcomes depend on customer operations and third parties as well as the service. Define how a time or result is measured, exclusions, dependencies, and remedy instead of implying guaranteed prevention.
Compare adjacent industries that use some of the same business categories but require different qualification rules.
Find businesses with a real connectivity project, then qualify the locations, applications, timing, and buying team before proposing a service.
Define the client problem your firm can solve, choose channels that transfer expertise and trust, and qualify whether a conversation can become a viable engagement.
Build a commercial-insurance pipeline around businesses your licensed team and carrier relationships can serve, then qualify exposures, renewal timing, quote readiness, and account economics.
Compare client-acquisition channels, choose a service niche, and build a qualified list for accounting outreach.
Choose an acquisition mix, define the environments your MSP can support, and build qualified account lists around one managed-service offer.
Choose a US market, then verify the site, project, decision owner, current controls, service footprint, response, privacy, integration, licensing, implementation, and lifecycle economics.