Why Licious had to lay off after all
February 16, 2024
10 min
186
Full
186 of 773
Episode 186 · February 16, 2024
Why Licious had to lay off after all
0:00 / 10:55
Excerpt playback isn’t available for this episode — use the full-episode link.
Search the Record
Moment search isn’t open for this episode yet
When it opens, you’ll be able to type any phrase and jump straight to the second it was said.
Bengaluru Traffic Police Episodes Around February 16, 2024
Episode 186 of 773 — walk the feed in the order it was published.
How Shark Tank India has spawned an ecosystem of risky investments
Why Licious had to lay off after all
Summary
<p>While most startups were facing a reckoning earlier last year with mass layoffs, Licious, the meat delivery platform, was sitting proud, unaffected. Both the founders, Hanjura and Gupta, were giving interviews talking about how their company had made no job cuts and how they did not want that kind of bad karma. It became the anomaly in a market that was seeing a bloodbath that going on all around.</p><p><br /></p><p>But to be honest, the strategy of not laying off, didnt really help Licious. In fact, it saw some of its top talent at leadership positions leave the company.</p><p>And now, as it turns out, it may not be all good karma for Licious founders after all. The company has laid off 80 of its employees as a part of what its calling an operational reset. </p><p>What’s going on? </p><p><br />Tune in.</p><p><a href="https://the-ken.com/the-nutgraf/why-india-wont-see-a-100-billion-internet-company-anytime-soon/"><em>Recommended read: California users</em></a></p><p><em>Daybreak is produced from the newsroom of </em><a href="https://the-ken.com/"><em>The Ken</em></a><em>, India’s first subscriber-only business news platform. </em><a href="https://the-ken.com/"><em>Subscribe</em></a><em> for more exclusive, deeply-reported, and analytical business stories</em></p>
Topics
Episode details and artwork are published by the show’s own feed. Sentinel plays short cited excerpts and links every episode back to its publisher.