News
The Next Wave: Why it rained at your favourite cloud kitchen
The Unseen Costs of Cloud Kitchens It was a typical Tuesday evening when I first heard about FoodCourt's abrupt shutdown.

It was a typical Tuesday evening when I first heard about FoodCourt's abrupt shutdown. I had been following the story on TechCabal, where it was reported that the cloud kitchen had paused operations entirely. As I delved deeper, I couldn't help but think about my own experience with FoodCourt. I had been a loyal customer, ordering their Korean chicken burger every week. The food was always good, and the convenience of having it delivered to my doorstep was unbeatable. But what really caught my attention was the story behind FoodCourt's demise. On the surface, it seemed like a classic tale of a startup that had failed to secure funding. However, as I dug deeper, I realized that there was more to it than meets the eye.
FoodCourt's story is, at its core, a kitchen story. And a kitchen, in many ways, is a factory. Factories succeed or fail on two things: what they pay for their inputs, and how many outputs they can produce from those inputs. This is exactly what happened with FoodCourt. The company operated several virtual restaurant brands and ran its own logistics, marketing, and customer support. But what about the costs? Osarumen Osamuyi, a researcher who has conducted over 200 interviews with riders, restaurant owners, and platform operators, broke down the economics on TechCabal's Headlines podcast. For every ₦100 ($0.073) a customer spends, roughly ₦30 ($0.022) goes to ingredients, ₦5 ($0.0036) to packaging, and ₦25 to ₦30 ($0.018$0.022) to customer acquisition or aggregator fees. The remaining ₦40 ($0.029) or so must cover staff salaries, energy, rent, delivery, marketing, and a profit.
It's clear that FoodCourt's costs were higher than they anticipated. The company had been relying on a $1.7 million funding round to sustain its operations, but it seems that the money was not enough to cover its expenses. The strike by kitchen staff over months of unpaid salaries was the final blow. As TechCabal reported, the company's delivery times had already been a point of contention among customers. It's clear that FoodCourt's business model was unsustainable, and the company's demise was a warning sign for the cloud kitchen industry as a whole.
FoodCourt's story is a cautionary tale for cloud kitchens and startups alike. It's a reminder that the costs of running a business can be higher than anticipated, and that a successful business model must take into account the prices of inputs and the number of outputs that can be produced. As I reflect on my own experience with FoodCourt, I realize that I was blinded by the convenience of having my favorite food delivered to my doorstep. I didn't stop to think about the costs behind the scenes. But now, I see that FoodCourt's story is not just about a failed startup, but about the unseen costs of cloud kitchens and the importance of sustainable business models.
As a writer, I often find myself drawn to stories that highlight the human side of business. FoodCourt's story is a perfect example of this. It's a reminder that businesses are not just about profits and losses, but about people and their stories. The kitchen staff who went on strike, the customers who were left without their favorite food, and the investors who lost their money - all of these people were affected by FoodCourt's demise. And as I reflect on their stories, I realize that FoodCourt's shutdown was not just a business failure, but a human one as well.
The cloud kitchen industry is still in its early stages, and FoodCourt's story is a warning sign for the future. As more and more startups enter the market, it's essential that they take into account the costs of running a business and the importance of sustainable business models. Only then can we expect to see a new wave of successful cloud kitchens that prioritize both profits and people.


