I founded Scoopful and I'm building HUNGRYBLR — and what follows is the actual record. Launches and crashes. Profit and fraud. What I got right, what cost me ₹6 lakh to learn, and the systems built from each lesson.
I didn't start Scoopful from a spreadsheet or a gap analysis. I started it because I had spent a year on the floor of IKEA India — selling, solving, serving — and something unexpected happened: customers began asking for me by name. Not the store. Me specifically.
That kind of recognition doesn't happen by accident. It happens when you genuinely care about the person in front of you. I had a real hunger for the FMCG and F&B space, strong commercial instincts that IKEA had sharpened, and the specific restlessness of someone who knows they're capable of building something of their own.
In late 2023, I co-founded Scoops N Swirls Ice Cream LLP — the entity behind Scoopful. I chose LLP deliberately: lower compliance than a Pvt Ltd, limited liability, and flexibility to bring partners in later. Then came sixteen months of building before selling a single scoop.
"I wanted to create a brand people remember — not just another frozen dessert seller."The founding thesis · November 2023
Once orders started coming in, the personal touch didn't stop at the product. Every single order — more than 4,000 of them — came with a handwritten thank-you note. I wrote every one myself, and no two were the same.
None of that preparation made the reality after launch any softer. The challenges that actually showed up were never the ones I'd planned for — they came from directions I hadn't even mapped. I learned almost everything through the mistakes, not despite them. Three years in, handling one challenge after another has simply become a habit — which, as far as I can tell, is what entrepreneurship actually is. It's also where the thrill comes from. The stakes are just a lot higher now.
One has three years of real numbers, real losses, and real systems behind it. The other is being built right now, the same way — by going in deliberately, learning the hard parts early, and documenting what works.
The launch exceeded every projection we had. In the first week of operation, Scoopful generated over ₹5 lakh in revenue. We sold out completely — fulfilment was under pressure from day three. We hadn't anticipated demand at this level.
That week validated everything: the premium packaging worked, the product quality was there, and the storytelling landed. We didn't launch cheap. We launched right.
Brand storytelling is a commercial asset. Customers don't just buy ice cream — they buy a craving, an emotion, an experience. Build the story before the product, and the product sells itself. Positioning at launch is permanent — you almost never recover from a cheap first impression.
In the second month of operations, my manufacturer substituted ingredients without authorisation. The products coming out were not the products I had designed or contracted. By the time I identified the problem and intervened, the financial damage was done. I lost over ₹6 lakh.
Simultaneously, a cold storage facility used by the business failed due to poor maintenance. Tens of thousands of cups were damaged in a single incident. Two major setbacks within weeks of launch.
Most founders talk about resilience like it's automatic. It wasn't for me. I felt genuinely terrible — at one point I was close to giving up entirely. But I got back up, and rebuilt with a fundamentally different approach to every external relationship that followed.
The model had always been straightforward in theory: we supply the raw materials and the recipe, the manufacturer follows our SOPs, and we get the finished product back. After the fraud, that arrangement got a lot stricter — mandatory presence during production, audit rights, and explicit penalty clauses — and we changed manufacturers entirely rather than just tightening terms with the same one. The ₹6 lakh loss was expensive. The education it bought was worth considerably more.
Every subsequent manufacturing agreement had penalty clauses, production supervision requirements, and quality checkpoints. Cold storage now had redundancy protocols. The core realisation: trust is not a control mechanism — systems are. You build the safeguards before the problem, or you fund the lesson after.
The original model had a product selling at ₹149 with a COGS of ₹45. The margin wasn't the core problem — the price was creating a barrier to impulse and repeat purchase in a category where those are everything.
I made the decision to reverse-engineer the cost structure from the bottom up. Over three months, I renegotiated ingredient sourcing, revisited the manufacturing process, optimised packaging specs, and rebuilt the COGS model entirely. COGS came down from ₹45 to ₹18. That freed us to reprice to ₹89 without destroying margin — and it significantly improved volume, trial, and repeat orders.
This was not a simple procurement exercise. It required challenging every assumption in the cost model, building new leverage with suppliers, testing quality boundaries, and making the call on where to hold quality and where to optimise. The margin didn't just happen — it was engineered.
Reverse COGS modelling: start with your target selling price, work backwards to your target margin, then engineer the cost structure to hit that number. Most founders build a product and price it. The correct approach is to price it first, then engineer the cost structure to fit.
Ambition is a strength until it becomes a liability. On launch day, Scoopful went live across 8 locations simultaneously. The thinking: maximum reach, maximum visibility from day one. The reality: operational resources, quality control, and management attention spread across too many points before the core unit was stable.
The Zomato and Swiggy expansion followed a similar pattern. I was spending approximately ₹1 lakh per month on platform promotions to build momentum. The brand visibility was real — but the commission structures, discount pressure, and CAC dynamics created a situation where volume was growing while contribution margins were being eroded simultaneously.
The honest lesson: aggregator dependency is a trap you can't see clearly until you're inside it. The platforms give you reach and take your margin. Expanding there aggressively before your own channels are profitable is a compounding mistake — more volume just means more value leaving through the commission gap.
Expand only after the unit is profitable, not before. One stable, profitable location with a proven operating model is worth more than eight locations with operational chaos. Fix the unit economics first — then replicate them. Scaling broken economics just gets you to broke faster.
Every major setback produced a system. By the time Scoopful had been operating for a year, the operational documentation was more detailed than most companies three times its size. This is not compliance by instinct — it is a learned response to real operational failures.
The franchise framework alone included brand guidelines, royalty structures, marketing contribution terms, operational requirements, performance metrics, audit rights, termination clauses, and penalty structures. The manufacturing agreements had specific ingredient substitution prohibitions and mandatory production supervision requirements. The storage partner model had temperature compliance protocols and inventory leakage controls built in from day one.
I build systems the way I do because I have personally absorbed what happens when they don't exist. Each document in the Scoopful operating framework has a specific failure behind it that made it necessary. That is not a weakness — that is the most reliable way to build something that doesn't break in the same place twice.
Most operational problems are documentation problems in disguise. If an SOP doesn't exist, the problem will happen. If a penalty clause isn't in the agreement, the behaviour won't change. Build the system before you need it — or pay for the education after.
Scoopful is currently at an inflection point. After three years of building, losing, rebuilding, and iterating, I'm executing a café partnership model — a structured revenue-share arrangement with full cash flow modelling and proposal decks already in motion — as a template I plan to replicate with more café and retail partners, alongside a 10-year FMCG expansion blueprint that includes a new sub-brand and a gifting collection.
I say this openly because I believe transparency about where a business actually stands is more valuable than a polished story. What Scoopful gave me is not a tidy success narrative — it's something more valuable. It gave me three years of managing every single function of a real business under real constraints, making real decisions with real money at stake.
Most operations professionals have theoretical frameworks. I have scar tissue. I know what a manufacturer fraud recovery looks like. I know what a cold storage crisis feels like at 2 AM. I know how to rebuild a COGS structure under pressure. I know what happens when you expand too fast and how to correct it. That specific kind of knowledge cannot be taught in a course or learned from a case study.
"The brand has demonstrated enough resilience and market validation to prove it is more than just an ice cream shop. The next phase is turning that foundation into something that can grow without requiring me to personally drive every decision."
ScoopfulCares isn't a CSR slide added for optics — it runs through the same network I've volunteered with for eight years: Robin Hood Army. Free scoops go out through RHA's existing distribution to underprivileged communities, which means the initiative had real infrastructure behind it from day one instead of being built from scratch.
It isn't a one-off either. We've run it across multiple events — tied to occasions like Children's Day and Scoopful's own one-year anniversary — treating giving back as a recurring part of how the brand operates, not a single feel-good post.
HUNGRYBLR began as a marketing agency for food and beverage brands — a service business, billing for deliverables. It worked, but it wasn't the thing worth building. A marketing agency scales by adding clients. A community scales by adding value to the people already in it.
So I rebuilt the model: a tiered, membership-based founder community connecting F&B, beverage, and FMCG operators across Bengaluru — built around offline events, peer access, and real industry relationships instead of one-off service work. The strategy document and a rebuilt website are already done; the membership tiers and event calendar are what's being built right now.
I'm applying the same operating instinct here that Scoopful forced on me: don't wait for the crisis to write the system. The membership tiers, the event structure, the partner criteria — built deliberately, before scale, not after.
Most founders hire first and systematise later. The business then runs on individuals rather than processes — and when the individual leaves, the process leaves with them. The SOP should exist before the role does. Every Scoopful failure that cost serious money happened in an area without a documented process.
Launching across 8 locations on day one felt like ambition. It was actually a distribution of operational problems at scale. One profitable, stable unit is the only foundation worth replicating. Volume without unit economics is acceleration toward a harder problem.
Vendor fraud, ingredient substitution, cold storage failure — none of these happened because I trusted the wrong people. They happened because the agreements didn't have the right clauses. Audit rights are better than trust. Penalty clauses are better still.
An agency grows by billing more clients for more hours. A community grows by making the people already inside it more valuable to each other. HUNGRYBLR's entire redesign rests on that distinction.
At ABC Technology, I was tasked with building institutional partnerships from scratch. My first move was the most direct one available: I went back to Bangalore Institute of Technology — my own college — and leveraged the alumni network I was already part of.
I didn't pitch a product. I pitched a problem they already had — their students needed structured pathways to first employment. I onboarded 4 hiring companies directly by converting alumni connections into formal hiring partnerships. The first 80+ students placed came from that single institutional relationship.
The 500+ total placements required building everything from scratch: employer onboarding frameworks, student cohort preparation, multi-city logistics coordination, and outcome tracking tools — none of which existed when I joined.
I've also watched a business run without a real backup plan or emergency runway — and seen exactly what that costs the people depending on it, not just the person running it. Cash-flow fragility doesn't stay contained to a balance sheet; it cascades into delayed paychecks and people forced to make decisions about their own careers with no real notice. That's a lesson I apply directly to my own ventures: a reserve fund isn't optional overhead — it's what determines whether a rough quarter is survivable or fatal, for the business and for everyone whose paycheck depends on it.
The other lesson was about consistency. I've seen what happens when direction changes every few weeks without a stable plan behind it — priorities reset before anything finishes, and the people executing on the ground absorb all of that uncertainty. It doesn't just slow a business down. It derails the people who trusted that direction enough to build their own plans around it. That's part of why Scoopful and HUNGRYBLR both run on documented SOPs before they run on instinct.
Contrast that with IKEA, where I spent a year on the floor (Jun 2022 – Nov 2023) before any of this. IKEA hires for values before it hires for a CV — candidates are assessed on whether their principles fit before their experience does. Founder Ingvar Kamprad's Testament of a Furniture Dealer is still treated as a living document decades later, and "togetherness" and "give and take responsibility" aren't posters on a wall — they show up in how decisions actually get made on the floor. A company built on values that are genuinely lived day to day doesn't need constant pivots to survive. The consistency is the strategy.
For eight years, I've volunteered with Robin Hood Army — a zero-overhead, zero-bureaucracy movement that redistributes surplus food to people who need it. Scoopful's free-scoop drives run through this same network, and the wheelchair donation initiative in Vijayawada was organised through RHA as well, not as a separate effort.
Three years of running Scoopful and building HUNGRYBLR means most of what I know came from fixing something that broke, not from a textbook. If you're earlier in that same process, happy to compare notes.
Building the systems that should exist before a crisis forces them into existence — production SOPs, vendor agreements with real teeth, and quality checkpoints that actually get followed.
Sourcing, manufacturing coordination, cold-chain logistics, and the audit and penalty clauses that make a vendor relationship survivable when something goes wrong.
Positioning, pricing architecture, reverse-COGS modelling, and the unglamorous unit-economics work that decides whether a launch is real or just a good week.
What HUNGRYBLR taught me about the difference between a service business and a membership model — and how to design tiers people actually want to renew.
Brand partnerships · HUNGRYBLR membership · vendor & channel tie-ups · business development · advisory and collaboration — based in Bengaluru, open to conversations anywhere.