A research template, not investment advice. Figures are not stated where the public record does not support them.
- Sector
- Managed IT services
- 2022 U.S. NAICS
541512 · Computer Systems Design Services
541513 · Computer Facilities Management Services
541519 · Other Computer Related Services
- 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
Managed IT providers support customer systems through combinations of help desk, infrastructure administration, cloud management and project delivery. Some primarily resell hardware or software; others operate a continuing service desk. The niche spans several classifications, so direct capability evidence matters more than a single industry code.
Revenue can combine periodic managed-service fees, usage-linked charges, vendor resale and implementation projects. Contract labels do not establish gross margin or the labor included. Local customer relationships and technical specialization can sustain separate providers, although multiple brands may belong to one platform and need deduplication.
A technology-enabled-service hypothesis asks whether documented delivery processes support reliable service beyond a few senior engineers. Test it through contracts, tickets and staffing records. It weakens if project work is called recurring, vendor resale obscures service contribution, or a principal controls both customer trust and all privileged technical knowledge.
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.
- A clear division of managed services, projects and pass-through licensing or hardware.
- Support scope, escalation responsibilities and customer expectations documented beyond a marketing promise.
- Delivery capability spread across roles, with vendor relationships and account access transferable under agreed controls.
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.
| Question | Answer type | Options | Why it matters |
|---|---|---|---|
| Which revenue offering is emphasized? | one of | Managed services / Project consulting / Hardware or software resale / Mixed | Prevents a reseller from being screened as a recurring service operation. |
| Which services are performed in-house? | list | Source-supported entries | Distinguishes help desk, infrastructure and cloud operations from partner-delivered capabilities. |
| Are defined support hours or service commitments published? | yes/no | Source-supported entries | Creates a follow-up on coverage cost, exclusions and escalation capacity. |
| Which customer industries are explicitly served? | list | Source-supported entries | Sector concentration can require specialist systems, contracts and operating knowledge. |
| Is security monitoring delivered directly? | yes/no | Source-supported entries | Separates an explicit operating capability from reselling a security product or referral arrangement. |
| Does an excerpt show this stop condition: Product resale or project-only consulting outside the managed-service mandate? | yes/no | Source-supported entries | Triage 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: A shared-services brand already controlled by an excluded platform? | yes/no | Source-supported entries | A 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: A clear division of managed services, projects and pass-through licensing or hardware? | yes/no | Source-supported entries | Treat it as a hypothesis to test against the mandate, not a verified attribute of the company. Unsupported answers stay unanswered. |
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.
| Signal | Where to look | Limits |
|---|---|---|
| Managed service scope | Service pages specifying included administration and support activities. | Service descriptions do not establish signed contract scope or actual account adoption. |
| Vendor relationship claims | Company partner pages and vendor-maintained directory entries. | A badge does not establish current commercial terms, authorization or transferable status. |
| Delivery organization | Professional role histories describing service management and technical leadership. | Profiles are self-reported and do not establish current employment or team capacity. |
| Ownership changes | Dated acquisition and brand announcements. | Match the legal entity and transaction perimeter; retained branding can conceal common ownership. |
| Legal identity and trading names | State entity records matched against the website's legal notices and contact details. | 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. | Vacancies describe hiring intentions. They do not establish filled positions, employee totals or an imminent succession event. |
Ownership and succession signals
- A technical owner who holds primary customer relationships and privileged-system knowledge creates two transition questions. Neither a founder-led website nor missing leadership detail proves a sale preference.
- 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.
- Product resale or project-only consulting outside the managed-service mandate.
- A shared-services brand already controlled by an excluded platform.
- Claims of regulated or specialist capability unsupported by identifiable scope and delivery roles.
Approach with context and approval
- Explain customer and service fit without requesting credentials, architecture diagrams or confidential incident details.
- Avoid suggesting that automation removes service accountability or that customer contracts inevitably transfer.
- 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.
- Reconcile recurring billing to signed scope, ticket effort, vendor costs and customer-level contribution.
- Review retention, concentration, service commitments, subcontracting and change-of-control rights.
- Assess privileged-access controls, incident history, documentation and retention of senior delivery staff.
Research hypotheses to test
Use these theses to frame confirming and disconfirming evidence, then choose a sourcing method suited to the target universe.
Diligence hypothesis
Technology-enabled services
Diligence hypothesis
Recurring maintenance contracts
Diligence hypothesis
Adjacent service cross-sell
Sourcing method
Analyst desk research
Sourcing method
Executive and operating networks
Adjacent playbooks
Technology services
Cybersecurity services
Technology services
Vertical software
Building and facility services
Security and alarm monitoring
Where to check this
Managed service providers describe themselves in near-identical language, so the discriminating facts are the contract model, the customer verticals and the security attestations. CompTIA's research and the NIST small-business cybersecurity resources define the vocabulary providers and customers use; a provider's SOC report, where one exists, is an independent statement about its own controls.
Sources
- CompTIA, CompTIA. IT industry association and certification body, with research on the managed-service provider channel.
- Cybersecurity Framework, National Institute of Standards and Technology. A common vocabulary for security services and the scope against which a provider's claims can be read.
- Small Business Cybersecurity Corner, National Institute of Standards and Technology. NIST guidance written for small organizations, the customer base most managed-IT and security providers serve.
- System and Organization Controls (SOC) suite of services, AICPA & CIMA. Explains SOC reports, the independent attestation that software and service providers show customers about their controls.
- North American Industry Classification System (NAICS), U.S. Census Bureau. The classification every federal dataset keys on, and the first thing a market map has to get right.
- County Business Patterns (CBP), U.S. Census Bureau. Establishment counts, employment and payroll by NAICS code and county. The spine of any honest market map.
Related articles
Article
How to Find the Legal Entity Behind a Brand Name
Article
Form 5500 Headcount Estimates: A Reconciliation Guide
Article
How to Find Out if a Company Is Private Equity Backed
Related reference