# Sector analysis: ask questions that fit the project

> Learn how sector context changes the evidence a project assessment needs. Start with an application-focused robotics due diligence guide.

Canonical HTML: [https://orbitrum.io/academy/sector-analysis/](https://orbitrum.io/academy/sector-analysis/)

Sector context gives a research question its practical boundaries. This track shows how to adapt an assessment to what a project actually builds and the setting in which it is expected to work.

## Start here

[How to evaluate a robotics company](/academy/sector-analysis/robotics-company-due-diligence/)

The guide begins with the robot's task and environment. It then examines measurement conditions, human intervention, deployment evidence and the commercial arrangement. Its fictional calculation exercise shows why a headline completion rate can hide an important distinction.

## What you will practice

Describe the use case precisely. Read performance results with their test conditions. Keep technical maturity separate from commercial adoption. Identify which questions need specialist safety or operational assessment rather than treating this guide as a certification checklist.

## Choose your perspective

**For experts:** explain why the evidence you selected is relevant to this particular application.

**For readers:** compare projects on a stated task or problem, not only on a broad sector label or an impressive demonstration.

## Connect learning and discovery

[Orbitrum Sectors](/sectors/) organizes the actual public catalog. Academy provides learning material; it does not create a second classification of companies. A lesson about robotics does not mean that every industrial project in the catalog is a robotics company.

Continue with [technical analysis](/academy/technical-analysis/) for the demonstration-to-deployment gap and [commercial analysis](/academy/commercial-analysis/) for customer evidence.