A ₹6.5 Cr Profit Is Not Always a ₹6.5 Cr Business

Every earnings season, I watch founders celebrate the topline. Almost nobody interrogates the quality of the profit sitting underneath it. And that is precisely where the most interesting architectural story usually hides.

The Signal

This week, drone major ideaForge reported a net profit of ₹6.5 Cr for Q2 FY27, a sharp turnaround from a ₹19.6 Cr loss in the year-ago quarter. Revenue grew 124% YoY to ₹91.3 Cr. That is a genuinely impressive growth number.

But now read the footnote.

Where the Profit Actually Comes From

Total income was ₹97.6 Cr, including ₹6.3 Cr of other income. Total expenses came in at ₹90.1 Cr. Do the arithmetic and the picture sharpens dramatically: of roughly ₹7.5 Cr in pre-tax profit, ₹6.3 Cr arrived from non-operating sources. The operating contribution was closer to ₹1.2 Cr – an operating margin in the low single digits on ₹91.3 Cr of revenue.

And on the cost side, ₹48.1 Cr went into materials consumed. That is more than half of revenue flowing straight into the bill of materials.

This is the classic signature of Indian deep-tech hardware today: real demand, real growth, and a P&L still anchored to imported components. Flight controllers, batteries, cameras, gimbals, radios. We are assembling excellent products while someone else captures the margin on the parts inside them.

The Sawtooth Problem

There is a second, quieter signal. ideaForge was profitable in FY26, slipped to a ₹2.6 Cr loss in Q1, and is back in profit in Q2. Each quarter swung hard.

Any architect who has built for government and defence procurement will recognise this immediately. Revenue recognition follows delivery milestones, not calendar months. Working capital gets trapped in inventory and receivables. The P&L becomes a sawtooth.

Which raises the real design question: are you building a product company or a project company?

The Moat Is Not the Airframe

Here is where I would push any CTO or founder reading this. The durable asset in dronetech is not the hardware. It is the telemetry.

Every flight hour generates data – terrain models, failure telemetry, mission logs, autonomy edge cases, maintenance predictors. If that data is treated as exhaust, the business stays a BOM business forever. If it is designed as a first-class product from day one – fleet management, predictive maintenance, mission software, analytics-as-a-service – the company migrates from lumpy capex sales to recurring opex revenue.

That is not a marketing pivot. It is an architecture decision made three years earlier: schema design, edge buffering, telemetry sync over intermittent links, and a data layer that survives the drone.

The Northeast Is a Stress Test, Not Just a Market

I have often argued in STPI and state technology forums that the Northeast is the hardest possible proving ground for this sector – and therefore the most valuable one.

Five thousand-plus kilometres of international border. Brahmaputra flood plains that need rapid aerial damage assessment. Hill districts where a blood sample or a vaccine has no road worth the name. If a drone platform can hold telemetry integrity in monsoon humidity across a riverine flood zone, it can handle any market in the world.

But state-by-state, tender-by-tender procurement will keep reinforcing that sawtooth. The region’s opportunity is not in selling one aircraft at a time. It is in a service layer – shared fleet operations, mapping-as-a-service, disaster response contracts – funded programmatically rather than project-wise.

Takeaways

• Read the profit, not the headline. Separate operating profit from other income before you celebrate. It tells you whether the business model is working or the balance sheet is.
• Watch the BOM ratio. If materials exceed 50% of revenue, your strategic work is supply chain and value capture, not sales.
• Design for lumpiness. Elastic capacity, dual-sourced components, and cash-flow modelling tied to delivery milestones – not to topline dreams.
• Make telemetry a product. The airframe depreciates. The data compounds.
• For young founders: a profitable quarter is a data point. A repeatable margin structure is a business.

Closing Thought

Hardware gets you the order. Software, data, and disciplined unit economics get you the decade.

---

About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.