A deeptech project doesn’t move in a straight line from idea to sold product: it crosses distinct technical stages, each with its own risks and its own support needs. The technology readiness level — or TRL — gives a common language to place a project on that trajectory. Many researchers and founders in Morocco discover this scale too late, after already requesting funding or support that was miscalibrated for their actual stage.

TRL: a 9-level technology readiness scale

TRL was formalized by NASA before being adopted by research and innovation funding agencies worldwide, including the European Union through Horizon Europe. The principle: nine stages, from a still-theoretical scientific concept to a product sold under real conditions.

TRLWhat is demonstratedConcrete example
1-2Scientific principle formulated, first observationsA research paper identifies a promising mechanism
3-4Proof of concept in the labA prototype works under controlled conditions
5-6Validation in a representative environmentThe prototype is tested under conditions close to the field
7-8Demonstration under real conditions, qualified systemA pilot runs at an industrial or institutional partner
9Operational product, deployed commerciallyThe solution is sold and used routinely by customers

This scale doesn’t judge the scientific quality of the work: a result at TRL 2 can be academically excellent while still being far from a product. It only measures the distance left before a technology works reliably outside the lab.

Why knowing your technology readiness level changes your strategy

Most mistakes made by deeptech founders come from a mismatch between their actual TRL and the type of support they’re seeking. A researcher at TRL 2 preparing a pitch deck for investors wastes time: at that stage, no serious investor will fund a project that doesn’t yet have a proof of concept. Conversely, a team at TRL 7, already running a validated pilot with a partner, would waste time going back through an ideation program designed for TRL 1 projects.

TRL also serves as a common language with outside stakeholders: a selection committee, a university technology-transfer office, or an industrial partner immediately understands what a TRL 4 project implies compared to a TRL 8 one, even without knowing the technical details. This avoids misunderstandings where a founder overstates their maturity out of enthusiasm, or understates it out of excessive caution.

Assessing your own technology readiness level

Self-assessing TRL requires honestly answering a series of questions about what has actually been demonstrated, not what seems likely.

  • Do I have a formulated and documented scientific principle, or just an intuition? (TRL 1-2)
  • Have I made a version of my technology work under controlled conditions, even an imperfect one? (TRL 3-4)
  • Have I tested that version in an environment that resembles real usage conditions, without simplified constraints? (TRL 5-6)
  • Do I have a partner (a hospital, a farm, an industrial site) using or having tested my technology in their own environment? (TRL 7-8)
  • Is this technology sold and used routinely by customers today, without constant technical supervision from my team? (TRL 9)

The level to keep is the last one you can answer yes to without reservation. Many founders overstate their TRL by counting a single successful demonstration as a full validation of that stage.

Caution: TRL is not a merit score, and climbing levels quickly is not always desirable. Advancing a stage without having consolidated the previous one — for example, testing under real conditions a technology that still fails one time in five in the lab — exposes you to a costly, visible failure instead of a contained, cheap one.

What technology readiness level does not measure

TRL is useful but partial. It says nothing about three dimensions that matter just as much for a deeptech project’s success:

  • The market. A technology can reach TRL 9 without any customer being willing to pay the price needed to make it profitable. TRL needs to be complemented with market-need validation, which follows its own logic independent of the technical level.
  • The business model. A technically mature product can still be unsellable if its production or deployment cost exceeds what the market will pay.
  • Team and governance. Moving a technology from the lab to the market requires different skills at each stage — research, then engineering, then sales and industrial — that the founding team doesn’t always have in-house.

A solid project advances on these three fronts alongside TRL, not after it.

Moving your project from one stage to the next

Each stage transition calls for a different type of support, not simply “more funding.”

Between TRL 1 and 4, the challenge is research time and access to a lab or prototyping space: this is the territory of university technology-transfer structures, described in our guide to valuing university research. Between TRL 4 and 6, the challenge becomes validation under representative conditions, which often requires dedicated R&D funding rather than equity investment. Between TRL 6 and 9, the central challenge becomes finding a pilot partner willing to test the technology in their own environment — a process detailed in our article on moving from research to market.

For a broader view of what sets a deeptech startup apart from a classic tech project, including on capital and team, our article deeptech: what it is, and why Morocco needs it completes this framework.

Checklist before seeking funding or support

  • Identify your actual TRL by honestly answering the questions above, without rounding up to optimism.
  • Check that the type of support you’re targeting (a research grant, incubation, an industrial partnership, fundraising) actually matches your stage, not your ambition.
  • Document the evidence that justifies your current TRL (lab report, pilot data, partner feedback): a selection committee will ask for it.
  • Assess market validation and your business model in parallel — they don’t advance automatically with TRL.
  • If you cannot clearly answer “who tested this, and under what conditions,” you are probably at a lower stage than you thought.

Conclusion

Technology readiness level doesn’t replace a market strategy or a business model, but it prevents a frequent and costly mistake: asking for the wrong type of support at the wrong time. A founder who knows precisely where their technology stands — not where they’d like it to be — saves time with every stakeholder, from a university selection committee to an industrial partner.

Next step: place your project on the TRL scale using the checklist above, then explore EIC programs suited to your actual maturity stage.