Search for stocks /

NewJaisa Technologies Limited H1 FY26 Concall Decoded: – Lost Amazon, lost sleep, but claims 75% revenue déjà vu


1. Opening Hook

Amazon ghosted NewJaisa faster than a bad Tinder date, and FY26 promptly turned into a survival reality show. One fine February, revenues fell off a cliff, management panicked responsibly, and 40% of the workforce got an early career break. Since then, the company has been busy reinventing itself—own website, B2B deals, retail stores, and a lot of optimism.

The CEO insists this is not a downfall arc but an origin story. From ₹6 crore monthly run-rate to ₹1.8 crore, and now crawling back with “confidence,” NewJaisa believes it’s building a brand instead of hiding under Amazon’s umbrella. Losses are explained, inventory is defended, and patience is requested—politely but firmly.

Read on, because the inventory drama, analyst grilling, and management optimism only get juicier from here.


2. At a Glance

  • Revenue down ~30% YoY – Amazon left, revenue followed, management stayed.
  • 75% revenue recovery claimed – Calculated creatively from rock bottom, not peak.
  • EBITDA negative – ESOPs, write-offs, and reality teamed up.
  • Employee cost down ~70% – HR did the most efficient cost-cutting exercise.
  • Inventory at ~₹36 Cr – Large, mysterious, and emotionally sensitive topic.
  • Marketing spend up – Because brand-building fixes everything, eventually.

3. Management’s Key Commentary

“Amazon stopping refurbished sales was a Black Swan event for us.”
(Translation: One platform controlled our destiny 😏)

“We’ve recovered almost 75% of lost revenue in H1.”
(From the lowest base possible, but still, recovery sounds nice)

“We reduced workforce by over 40% to control costs.”
(Efficiency achieved via mass layoff emoji 😬)

“We received R2 certification, only five companies in India have it.”
(Please value us like global recyclers now)

“We are okay being in red this year while rebuilding.”
(Losses are temporary,

Join 10,000+ investors who read this every week.
Become a member
error: Content is protected !!