Bootstrapping a premium cloud kitchen brand around an 'overloaded' USP, designing everything from name and packaging to menu engineering and digital platform strategy, while running it alongside a full-time job for ten months end to end.
Cloud kitchen biryani is one of the most saturated categories on Indian food delivery platforms. On Swiggy and Zomato, dozens of biryani brands compete for the same searches in any given delivery zone. Most of them compete on price or coupons, which is a race to the bottom that small operators rarely win, and that the platforms themselves benefit from much more than the operators do.
Ghafoor's needed a positioning that justified a premium price point and that was visible from the small thumbnail tile customers actually see in the app. This is the part most cloud kitchen brand work gets wrong. The brand has to communicate its value from a 200-pixel thumbnail, before the customer ever sees the menu, ever sees the packaging, or ever tastes the food. Most brand work in this category was happening at scales the customer never encountered: beautiful packaging that only registered after the order arrived, polished menus that only mattered after the customer had clicked the tile.
The 'overloaded' positioning was a category-truthful answer to that question. More meat, richer flavours, and visibly premium portion sizes that the thumbnail could communicate directly. The question that remained, and the one this project had to answer, was whether the brand design could carry that positioning credibly across every customer touchpoint, from the platform thumbnail through to the moment the customer opened the takeaway box and saw what was inside.
This was also my first proper experience as a founder rather than as a designer-for-someone-else. I was running it alongside my full-time job at CarTrade, which produced unique constraints on how much design polish I could afford and which decisions had to be 'good enough to ship' versus 'right at any cost'.
Research happened in three parallel tracks because all three had to be answered for the brand to actually work commercially.
Category positioning analysis mapped existing biryani brands on Swiggy and Zomato by price point, positioning vocabulary, and visual treatment. The map revealed a clear gap in the premium-but-not-pretentious segment. Most premium brands in the category had drifted toward import-of-Western-minimalism aesthetics that did not resonate with the actual customer base, while the value brands fought on price. The 'overloaded' positioning was opening a third path: premium through visible substance rather than through visual restraint.
Customer behaviour research involved ordering from competitors, talking to friends who ordered biryani regularly, and watching how people actually shopped on the platforms. The pattern that mattered was that most ordering decisions happen in under 30 seconds on the platform, with the customer scanning thumbnails and prices, opening one or two for closer inspection, and ordering. The brand had to win or lose in that 30-second window, which had specific implications for thumbnail design, menu name choices, and the visible-on-tile pricing strategy.
Unit economics modelling ran in parallel with the brand work, because no amount of brand polish would save a business with broken unit economics. Menu engineering, ingredient costing, packaging costs, platform commission structures, and rider fee absorption all had to add up before any brand investment was justified. Some early brand concepts that looked good on Figma had to be retired because the packaging cost they implied was not viable at the price point the positioning supported.
Cloud kitchen brand design has a non-obvious constraint: most touchpoints are not on the customer's screen at the moment of decision. The Swiggy tile, the menu thumbnail, the order packaging when it arrives, and the physical food itself all matter equally, and they all have to carry the same brand consistently.
I designed the brand system to carry consistently across all of these. The logo, typography, and colour system had to read on a 200-pixel thumbnail and on a takeaway box. Many brand systems work beautifully at one scale and fall apart at another. I tested every brand element at the thumbnail scale before approving it for any other use, because the thumbnail was where the brand had to win.
Packaging had to reinforce the 'overloaded' promise visually the moment the customer opened it. This is a critical brand moment that most cloud kitchen brands underinvest in. The customer who has placed an order is already past the acquisition moment, but the unboxing experience determines whether they reorder. We designed the packaging to surface the substance of the food itself rather than to wrap it elegantly. The food was the brand promise, and the packaging needed to amplify it rather than compete with it.
The menu had to make ordering feel like building a meal rather than selecting a SKU. Menu item naming, description copy, and category structure all reinforced the overloaded positioning through language. We deliberately resisted the trend toward minimalist menu language and leaned into descriptive abundance, on the principle that the customer choosing 'overloaded' wanted the menu to feel overloaded too.
The digital platform strategy treated Swiggy and Zomato as different products with different optimisation requirements. Each platform has different thumbnail crops, different menu rendering rules, different ranking algorithms. We designed for the constraints of each rather than treating them as interchangeable distribution channels.
Premium without pretension. The trap with 'premium' positioning in Indian food D2C is descending into pretension that the food and customer base do not actually want. The visual language had to be confident and crafted without losing the warmth that food brands need. I leaned into bold typography, generous illustration of the food itself, and warm colours over the cool minimalism that imported aesthetics tend to default to. The brand reads as confident and indulgent rather than restrained, which matched the positioning and the customer.
Substance-first packaging. Packaging that hides the food and presents the brand is a category default. We inverted this: the packaging surfaces the food and presents the brand secondarily. The customer opening the box should see the substance first, with the brand mark reinforcing what they are seeing rather than competing with it. This was a counterintuitive decision that the packaging vendor pushed back on, because it required printing techniques that were more expensive at low volumes than the standard treatment.
Menu language that matches the positioning. Menu item names and descriptions used direct, abundant language that reinforced the overloaded promise rather than understated it. This was a deliberate choice against the trend toward minimalist food brand language, on the basis that minimalist language does not match the experience of eating an overloaded biryani. The menu has to set the right expectation, and the right expectation in this category is generous substance, not restrained sophistication.
Platform-specific optimisation. Treating Swiggy and Zomato as different products with different optimisation needs produced better results on both than treating them as interchangeable channels. Thumbnail crops, menu rendering, item ordering, and pricing presentation all received platform-specific treatment.
Founder constraints as design constraints. Running this alongside a full-time job meant every design decision had to be shippable on limited time. I could not afford to over-design any single element, and the brand system had to be operable by a small ops team without designer involvement on every decision. This produced a more disciplined brand system than I would have built with unlimited time, because the constraint forced clarity about what actually mattered.
From thumbnail to takeaway
Ghafoor's launched on Swiggy and Zomato with the brand system intact across all customer touchpoints. Beyond the operational milestones of platform launch and order fulfillment, the most useful outcome for me as a designer was the experience of owning every decision end to end.
There was no design review committee to defer to, no engineering team to translate decisions for, and no product manager to scope-cut against. Every design call had to also be a business call. A typography decision had to clear an ROI threshold. A packaging decision had to clear a unit-cost threshold. A brand investment had to be measurable in terms of either acquisition cost or repeat rate.
That experience has informed how I work with founders in my main role at CarTrade and how I think about design's seat at the business table. I am much more direct with internal stakeholders about the commercial implications of design decisions now, because I have lived inside those implications myself. The empathy goes in both directions: I understand why founders push back on design investments, and I can advocate more credibly for the investments that genuinely produce commercial returns.
Running an actual business alongside a full-time job is brutal and clarifying in equal measure. Decisions you can avoid as an employed designer become unavoidable as a founder. Pricing, vendor management, unit economics, and operational tradeoffs all force a kind of clarity that pure product design rarely demands.
I would recommend the experience to any senior designer who has the appetite for it, because it changes how you think about design's place in a business in ways that no amount of reading or talking can. The shift is not just professional but personal: you stop being a designer who works for a business and start being a businessperson who happens to design. The first framing is service-oriented; the second is ownership-oriented. The shift is one-way once it happens.