About
Kitchens that cannot afford drift.
Less guessing. Fewer spreadsheets. Sharper prep. One loop the whole team trusts.
Naming
Annapurna
अन्नपूर्णा — the Sanskrit goddess of food and nourishment. Anna meaning grain, purna meaning full. The deity of the kitchen who makes sure no one in the household goes without.
We chose the name because the goddess of the kitchen is also the goddess of no waste. Abundance and discipline together. That is the operating principle of the product.
Why this product
Most restaurant software treats the kitchen as a cost centre. We don’t.
Kitchens drift quietly. A missed leftover. A forecast nobody approved. A sales upload nobody reconciled. An inventory log out of sync with the menu. None of these break loudly. All of them compound.
One loop closes those gaps. Every day. Built around how a multi-branch restaurant in India actually runs — not what a SaaS template assumes.
The metric we care about: do managers open the platform before service. When they do, prep gets sharper, waste falls, and the kitchen stops guessing.
Operating principles
Four things we will not compromise on.
Restaurant-first. Always.
Every workflow follows how kitchens actually move — closing entries, morning checks, manager approvals, post-service reconciliation. We follow the rhythm. We don’t bolt software onto chaos.
Each branch is its own world.
Begumpet never sees Hi-Tech City. Cream Centre never sees another restaurant. Permissions are how trust scales.
Clever only where it earns its keep.
The assistant answers in plain English. The forecast learns from your history. Nothing is added for show — only where it removes a keystroke.
Calm beats clever.
Good software makes the day quieter, not louder. Fewer pings. Fewer tabs. One loop the team trusts before service.
Founder photo
Founder
Guru Teja
Building AnnapurnaOps from Hyderabad. Most evenings, inside Cream Centre kitchens — watching what closes well, what forecasts get wrong, what signals never leave the line cook’s head.
Background in software. Conviction that the next decade of restaurant operations runs on one calm loop, not five disconnected dashboards.
In pilot with
Cream Centre
Hyderabad · 2 outlets
Currently rolling out across two Cream Centre outlets in Hyderabad. Daily close-outs, prep forecasts, sales reconciliation, and inventory all running on the same daily loop.
2
outlets live
6+
weeks of daily kitchen history
Where we work
Planet Earth
Within walking distance of the kitchens we serve.
We believe Indian multi-branch restaurant operations are best understood from inside an Indian kitchen. The product is shaped by what happens between 10 PM close-out and 9 AM stock check — not by a global SaaS template.
Looking for pilot partners
If you run a multi-branch restaurant in India and want to be the second or third pilot, book a call. Onboarding is hands-on for the first ten teams.
Join the pilot
Be the kitchen we build this around.
The first ten teams get hands-on onboarding and a direct line to the founder.