# Technical analysis: assess performance and readiness

> Assess product performance and readiness with evidence. Learn what a demonstration establishes and what a deployment claim still needs.

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

In this Academy, technical analysis means evaluating a project's technology, product and deployment evidence. It does not mean trading-chart analysis or price-pattern prediction.

## Start here

[How to distinguish a demo from a deployable product](/academy/technical-analysis/demo-vs-deployable-product/)

The guide covers system boundaries, test conditions, repeatability, integration and support assumptions. It explains why a readiness label needs its framework and evidence, and why security or AI-risk claims require their own examination.

## What you will practice

Narrow an overbroad claim to what a demonstration actually shows. Identify a missing denominator or omitted run. Separate a component's performance from the integrated product. Record an open question without inventing a defect or a passing result.

## Choose your perspective

**For experts:** preserve configuration, environment and limitations in the written assessment rather than relying on an unexplained maturity label.

**For readers:** ask whether the evidence concerns the task and setting that matter to your research question.

## Continue the learning path

Use the [robotics guide](/academy/sector-analysis/robotics-company-due-diligence/) for an application-specific example. Move to [traction evidence](/academy/commercial-analysis/startup-traction-evidence/) to examine customer adoption separately. Read [expert disagreement](/academy/critical-reading/interpreting-expert-disagreement/) when authors use different assumptions or scopes.

[Browse public project profiles](/)