INSIGHT · DEFENCE · CAPITAL

iDEX is on its 13th edition. The graduates who actually got contracts. The ones who didn’t.

INSIGHT N° 50 · 29 May 2026 · BY SATISH SWAMINATHAN

Eight years after launch, India’s flagship defence innovation programme has run over 13 editions of its Defence India Startup Challenge, opened more than 540 problem statements, and signed roughly 430 contracts. The headline numbers are impressive. The conversion rates underneath them are more interesting — and more useful to anyone underwriting a defence-tech bet.

India’s Innovations for Defence Excellence programme — iDEX — launched in April 2018, at a moment when the Indian defence procurement system was the subject of more frustration than capital. The premise was deliberate and contrarian: that a small fraction of India’s defence requirements could be unbundled from incumbent vendors and routed to startups, MSMEs, and individual innovators, with grants up to ₹1.5 crore (and later ₹10 crore under iDEX Prime) attached.

Eight years later, the headline numbers are real. As of early 2026, iDEX has:

— Run 13 editions of the Defence India Startup Challenge (DISC), with the 13th opened with 28 problem statements on cyber security.

— Opened 549 problem statements across surveillance, autonomous systems, sensors, navigation, communications, materials, propulsion, and adjacent domains.

— Signed approximately 430 contracts with startups and MSMEs.

— Secured Ministry of Defence clearance for procurement of 43 items, with cleared orders worth more than ₹2,400 crore from iDEX winners.

— Expanded into adjacent programmes — ADITI (deep-tech focus, up to ₹25 crore per startup), iDEX Prime (larger grants), SPRINT (Navy-specific), and the ASPIRE programme for dual-use technologies.

For a startup ecosystem that operates on the assumption that government procurement is a closed circle around the public-sector defence undertakings, the iDEX numbers are a structural breakthrough. The Indian Army alone now has 74 active iDEX projects across DISC, ADITI, and Open Challenge tracks; the Navy and Air Force run comparable portfolios.

The conversion gap nobody is talking about.

But the headline numbers conceal the more useful data, which is in the conversion ratios.

Problem statements to contracts. 549 problem statements have produced 430 contracts. That conversion ratio — 430 contracts from 549 problem statements, or about 78% — looks strong on paper. But the more important ratio comes one step down the funnel: of those 430 contracts, the Ministry of Defence has cleared only 43 items for actual procurement — a 10% conversion rate from signed contract to government purchase order. The funnel is steeper than the headline numbers suggest.

Contracts to procurement. This is the more important conversion. 430 contracts have produced 43 items cleared for procurement — a 10% conversion from contract to actual Ministry of Defence order. The remaining 90% includes projects still in development, projects that completed but were not procured, projects that were technically successful but operationally rejected, and projects that stalled at the integration stage.

For investors backing defence-tech startups on the strength of an iDEX win, the 10% number is the one that matters. The grant is real and useful. The contract is meaningful. But the bridge from contract to actual defence procurement — with sustained order pipelines, integration into Service planning, and a path to scale — is what determines whether the startup survives as a defence supplier or graduates into the much harder commercial market.

What the 10% have in common.

We’ve tracked the cohort of iDEX winners that successfully crossed the conversion gap into Ministry of Defence procurement. The publicly known examples — Sagar Defence (robotics, iDEX winner at Dubai Airshow 2025), Skylark Labs (AI-based Foreign Object Detection for the Indian Navy under DISC 7), and QuNu Labs (Quantum Key Distribution, signed as the Indian Army’s eighth iDEX procurement contract) — illustrate the pattern.

First, they solved a problem the Service was actively planning to procure, not a problem that sounded important. The iDEX problem statements span a wide aperture, but only a subset map onto procurement programmes already in the Service’s capability plan for the next five years. The startups that won contracts on those subset problems converted to procurement; the startups that won contracts on tangential problems generally did not.

Second, they built integration into the bid, not after it. Defence systems do not enter service as standalone products. They enter service as integrated subsystems within larger platforms — a sensor that has to talk to the platform’s mission computer, a comms module that has to clear EMI/EMC standards, a software component that has to work with legacy infrastructure. The startups that crossed the conversion gap built integration considerations into the prototype phase. The ones that didn’t finish with a working product that the Service couldn’t deploy.

Third, they had a co-development partner relationship with a DPSU or a large private prime. iDEX allows large industries to participate as a development partner alongside a startup, and this provision — underused in the early years of the programme — turned out to be one of the single highest-leverage paths from prototype to procurement. The DPSU or prime brings the production scale and the integration credibility; the startup brings the technology. The startups that built these partnerships early converted at materially higher rates than the ones that tried to scale alone.

Fourth, they treated the initial order as a reference, not a destination. Many iDEX winners secured initial orders in the ₹50 lakh to ₹2 crore range. The startups that converted these initial wins into multi-year procurement pipelines treated the first order as evidence to use in larger Service tenders. The ones that treated the first order as the goal generally did not appear in subsequent tenders.

What the 90% have in common.

The pattern in the cohort that didn’t convert is, in its own way, equally consistent.

They were heavily concentrated in the first three editions of DISC (2018-2020), when problem statements were broader and the path from challenge to procurement was less well-defined. They had founder teams from outside the defence ecosystem with strong technical credentials but limited insight into how Service capability planning actually works. They completed prototypes that worked in laboratory settings but failed integration testing. And they ran out of runway before procurement orders arrived, because the time gap between prototype completion and procurement contract has been longer than most startup capital structures can absorb.

That last point is the structural one that the iDEX programme itself has been trying to address. The ADITI scheme, launched with a ₹750 crore budget for the period 2023-24 to 2025-26, was designed in part to provide the bridge funding that allows startups to survive the gap between prototype and procurement. ADITI 2.0, launched in October 2024 with 19 new challenges in critical technology areas, extended the same logic. Whether the bridge is long enough remains an open question.

What this means for defence-tech investors.

Three implications for anyone holding or considering a position in Indian defence tech.

One — the iDEX label is necessary but not sufficient. An iDEX win does not predict procurement. The diligence question that matters is not “did they win an iDEX challenge” but “which challenge, in which edition, mapped to which Service procurement plan, and how far along the integration journey are they?” The answers separate the 10% from the 90%.

Two — the partnership question is binary. A defence-tech startup with no DPSU or prime co-development relationship 18 months into its iDEX engagement is structurally unlikely to convert to procurement. The conversation about partnership has to be active and named, not aspirational.

Three — the runway question is the hardest one. The funding gap between prototype completion and meaningful procurement order can run 18-30 months. Defence-tech companies need capital structures that can absorb that gap, and those structures look more like patient industrial capital than venture-style growth capital. The funds that are positioned correctly on this dimension are not necessarily the venture funds that look obvious on a first scan.

The bottom line.

iDEX has done exactly what it was designed to do: open the Indian defence ecosystem to a wider pool of innovators, and produce a pipeline of startups that the Services are willing to engage. The programme is a structural success.

But the underlying conversion data tells investors what the headline numbers don’t. Roughly one in ten iDEX contracts has converted to a Ministry of Defence procurement order so far. The startups in that ten percent have specific characteristics that the other ninety percent do not. The investors who can tell the difference are looking at a defensible advantage in a market that is finally moving real capital.

EDITOR’S NOTE: All iDEX figures are sourced from public MoD and iDEX-DIO records: 549 problem statements, 430 contracts, 43 items cleared for procurement, ₹2,400 Cr in cleared orders (Defence Standard, April 2026; growthgurukul.in, May 2026). Named graduates — Sagar Defence, Skylark Labs, QuNu Labs — are documented in public MoD and iDEX.gov.in bulletins. The 10% conversion rate (43 of 430) is computed from public figures.

— PR —