As the Presenting Partner of FFCC India 2026, Sapaad continues to play a key role in shaping conversations around technology, operations, and the future of the F&B industry.
We sat down with Vishnu Vardhan Madabhushi, Founder and CEO of Sapaad, to talk about the evolving restaurant landscape, the growing role of AI and automation, and what operators need to pay attention to as the industry moves into its next phase of growth.
Sapaad, one of the leading cloud-based POS and restaurant management platforms powering restaurants across global markets. With a strong focus on technology-led growth for the F&B industry, he has been at the forefront of helping operators streamline operations, improve customer experiences, and make smarter business decisions through data and AI-driven insights. As a recognised voice in restaurant technology, Vishnu continues to shape conversations around the future of hospitality and digital transformation in the industry.
Everyone talks about simplifying operations, yet most restaurants still feel buried in complexity. What are operators still getting fundamentally wrong?
In conversations with operators across 40+ countries, including India, a clear pattern emerges: most mistake digitisation for simplification. Instead of reducing complexity, they layer multiple tools: POS, delivery aggregators, inventory systems, CRM, and loyalty platforms. The result is often 6–8 disconnected systems that don’t communicate effectively.
In India specifically, where 30–35% of orders in urban markets now come via aggregators, this fragmentation creates major reconciliation gaps. Orders don’t sync with inventory in real time, leading to stock mismatches, wastage, and revenue leakage.
Each tool works well in isolation, but collectively, they create what can best be described as a “translation problem.” Operators are not running on real-time data; they are often making decisions based on partial visibility.
True simplification is not about fewer features; it’s about fewer systems doing more, with a single source of truth that reflects what’s happening across channels in real time.
You've worked with thousands of restaurants globally. What's the one behaviour you consistently see in brands that scale well versus those that plateau early?
The difference comes down to decision-making cadence.
Brands that scale know their numbers by Tuesday morning, not at month-end. They track:
- Outlet-level profitability
- Channel-wise contribution, and
- Margins and cost ratios
In contrast, brands that plateau rely heavily on monthly P&L statements, which are inherently retrospective.
In India’s highly competitive F&B market, where EBITDA margins often range between 8–15%, even a 2–3% delay in identifying leakages can significantly impact profitability.
Scaling brands operate on signals (real-time or near real-time insights), allowing them to act quickly, whether it’s correcting pricing, fixing inventory issues, or adjusting promotions. Others operate on summaries, where by the time issues are identified, the financial impact has already occurred.
This is also reflected in our customer behaviour, with an average lifetime of 7.5 years and an NPS of 88%. The operators who grow tend to stay, because they get answers faster than their competition.
Software today doesn't just track data, it interprets it. At what point does it stop being a tool and start becoming a decision-making partner?
The shift happens when software moves from answering “what happened?” to “what should I do next?”
In a typical setup, a dashboard might tell you the next day that ticket size dropped by 8% at a particular outlet. But a decision-making system flags this during service hours, identifying the cause, say, top-selling combos being unavailable, and suggesting alternatives to push.
This is especially relevant in India, where high peak-hour dependency (weekends, evenings) means that missed opportunities during service windows directly translate to lost revenue.
When a system can:
- Detect a change in performance
- Diagnose the reason behind it, and
- Recommend immediate corrective action
then it stops being a reporting tool and becomes an active operational layer embedded in daily decision-making.
There's a lot of noise around AI in F&B right now. From where you sit, what's genuinely useful and what's just buzzwords?
The biggest misconception is that AI automatically delivers value. In reality, AI is only as reliable as the data it is built on.
In India, many operators still rely on fragmented or exported datasets (like CSV files), which often exclude critical elements such as refunds, voids, or discounting patterns. This leads to misleading outputs, for example, incorrectly identifying “best-sellers.”
Genuinely useful AI in F&B today focuses on three areas:
- Demand forecasting, which can reduce food waste by up to 10–15%
- Anomaly detection, such as unusual billing patterns or recipe deviations, and
- Margin optimisation, especially in identifying hidden costs like commission overcharges
If AI cannot be directly linked to cost savings or revenue improvement, it remains a buzzword rather than a business tool.
For operators expanding across locations or formats, where do things usually begin to break behind the scenes and how can tech prevent that?
Operational breakdown in multi-outlet businesses is rarely sudden; it’s gradual and cumulative.
In India, common issues include:
- Recipe inconsistencies across outlets
- Price variations due to manual overrides
- Commission discrepancies across aggregator platforms, and
- Lack of real-time outlet-level profitability visibility
Individually, these may seem minor, but across 10–20 outlets, can lead to significant margin erosion.
Technology’s role is shifting from analysis to real-time intervention. The right systems:
- Standardise operations at the source
- Continuously monitor deviations
- Flag issues as they occur, and
- Increasingly suggest corrective actions
This transforms technology into an early warning system, rather than a reporting tool.
Being bootstrapped in a space full of heavily funded competitors isn't easy. How has that shaped the way you've built the product?
Bootstrapping enforces discipline and clarity. It prioritises utility over visibility.
In a market like India, where operators are highly value-conscious, products succeed only if they deliver tangible, day-to-day impact. If a tool isn’t useful, customers stop paying; it’s that simple.
This approach shifts focus towards:
- Long-term customer retention (average lifetimes of 7+ years)
- High satisfaction metrics (NPS ~88), and
- Product development driven by operator needs rather than market hype
It also influences technology decisions. A cloud-native architecture, for instance, allows continuous updates without downtime, which is critical in a country with rapidly scaling multi-outlet brands.
Every feature is built with a clear question in mind: Does this solve a real operational problem?
If you had to call it bluntly, what's one hard truth about running a restaurant today that most operators still don't want to hear?
Most restaurants don’t have a demand problem; they have a control problem.
India’s food delivery boom and rising dining-out culture mean demand is relatively strong, especially in urban centres. However, high volumes often mask underlying inefficiencies such as:
- Food cost leakages
- Billing inconsistencies, and
- Commission overcharges
Revenue is visible in real time. Margin loss isn’t.
By the time these issues reflect in bank balances or financial statements, the damage has already compounded. In an industry where margins are already tight, unnoticed leakages can quietly erode profitability.
You operate in 40+ countries with very different tax regimes. How do you engineer compliance in without slowing the product down?
The key is to treat compliance as a design principle, not an add-on.
While tax regimes vary globally, the fundamentals remain consistent:
- Transactions should be immutable.
- Invoices should not be editable.
- And, all changes should be traceable through audit logs.
In India, with increasing regulatory scrutiny and digitisation (for example, GST frameworks), this becomes even more critical.
There is also growing awareness around global standards like SOC 2 compliance, especially among enterprise operators and investors.
When compliance is embedded into the system architecture, it eliminates the need for manual enforcement; good behaviour becomes the default outcome of good design.
India has dozens of low-cost POS players. What's your pitch to a restaurateur who's just looking at the monthly bill?
India is an extremely price-sensitive market, and low-cost POS systems (often priced around ₹999/month) are attractive at first glance.
However, the real cost lies beyond the subscription fee.
Most low-cost systems lack:
- Detailed cost tracking
- Commission reconciliation, and
- Real-time profitability insights
As a result, operators may save a few thousand rupees on software but lose significantly more through inefficiencies.
In fact, many operators report savings of ₹50,000 to ₹1 lakh per outlet per month simply by identifying and fixing operational leakages through more integrated systems.
The real question is not “What am I paying for software?” but “What is my current system costing me in lost margins?”
There's a wave of AI tools where a restaurant uploads a CSV and gets an instant "audit." What makes Sapaad's approach different?
The limitation of most “instant audit” tools is that they rely on exported, static data, which is often incomplete or inconsistent.
In India especially, where operational data can be fragmented across multiple systems, this leads to insights that may look polished but lack accuracy.
A more reliable approach is to operate at the data source level, where:
- Transactions
- Inventory movements, and
- Customer interactions
are all captured in real time within a unified system.
This ensures that insights are:
- Based on complete data
- Contextual and timely, and
- Immediately actionable
The difference is fundamental: Static insights explain the past. Live insights help you act in the present.