Which technology service lines are a significant part of the Applicant's revenue (consulting, MSP/MSSP, development, BPO, QA/testing, IT staffing/project management, telecom/ISP, e-recycling/data destruction, etc.)?
Each service line on this list carries its own claim pattern, and carriers maintain appetite line by line.
What the carrier is actually asking
The carrier is asking which technology service lines make up a significant part of revenue: consulting, managed services, development, business process outsourcing, testing, staffing, telecommunications, electronics recycling and data destruction, and others.
Why it is underwritten
Managed services carry correlated exposure across clients. Development carries defect liability. Staffing carries vicarious liability for placed personnel. Data destruction carries a direct exposure if data is not actually destroyed. Underwriters treat these as distinct risks rather than as one technology category.
Where the answer lives in Microsoft 365, Entra ID, and Azure
This is a description of your services supported by revenue attribution.
| Platform | Where the setting lives | What has to be true |
|---|---|---|
| Finance | Revenue by service line | A split identifying every line above a materiality threshold. Attested |
| Managed services | Client count and the access held in client environments | The aggregation exposure, which underwriters focus on most |
| Development | What is built and for whom | Whether software is delivered into safety-critical or high-consequence use |
| Staffing | Personnel placed into client environments | Whether placed staff act under your direction or the client, which determines liability |
| Data destruction | Chain of custody and certificates of destruction | A verifiable process, since undestroyed data is a direct and provable exposure |
Once a meaningful share of revenue comes from managing client environments, the underwriting shifts to aggregation. Expect questions about client count, privileged access, and remote management tooling, and expect a narrower market. Disclosing it early is far better than having it emerge later.
What a defensible yes requires
- Every material service line is disclosed with its revenue share.
- Managed service client counts and access models are described.
- Development output and its use context are described.
- Staffing arrangements clarify direction and control.
- Data destruction processes produce verifiable evidence.
How this answer goes wrong
Managed services are omitted because they are a small revenue line, while the access held in client environments is extensive. Exposure follows the access rather than the revenue, and this is the disclosure carriers most dislike discovering after a loss.
Frequently asked
Do we have to list small lines?
List anything material and anything that carries access to third-party systems, regardless of size. Access is the exposure, not revenue.
Why is data destruction on the list?
Because failing to destroy data creates a direct breach exposure with a clear paper trail, and claims in that area are unusually well evidenced.
What about staffing?
Placed personnel can create liability for acts in a client environment. Whether they work under your direction or the client is the question that matters.
How does this affect appetite?
Some markets decline managed service providers or apply substantially different terms. Accurate disclosure gets you to the right market first time.
Related questions
Stop answering this from memory
Connect Microsoft 365, Entra ID, and Azure read-only. Insurance Posture reads the live configuration behind each application answer and shows you which ones you can prove before you sign.
Assess your posture