Low risk
It just does it.
Reading. Orders, top items, time patterns, reviews, customers, category splits. Nothing it reads can change anything, so nothing asks.
query_orders · query_top_items · query_reviews · query_customers
The brain
It read yesterday before you woke up.
Here is what it said.
A consultant reads your books once and leaves a deck. This reads the same database that just billed a table, every morning, and ranks what it finds by the rupees at stake — with the button that acts on it already attached.
Aaj kya karna hai
Urgent₹400 at stake
Paneer khatam — reorder karo, warna 6 dishes ruk jayengi.
Add 2 kg Paneeradvisor + add_ingredient_stock
Illustrative advice, in the register the brain writes in. Sample day · Sip & Kush.
A day with it
You don’t check on it. It checks in with you.
Every POS has a reports tab. You open it on the first of the month, if you remember. This turns up in the order the day happens.
A Tuesday.
The part nobody else will show you
What it is allowed to do without asking.
Every action it can take carries a risk level, and the level decides whether it acts, waits fifteen seconds, or waits for you. This is not a setting buried in an admin screen — it is how the thing is built.
Medium risk
Fifteen seconds to stop it.
Turning a dish on or off. It tells you what it is about to do and starts a countdown. Say nothing and it happens; press stop and it does not.
Turning off Paneer Tikka — stock is zero.
Auto-approving…
update_item_availability
High risk
It waits for you.
Changing a price. Announcing something to your customers. No countdown, no default, no quiet yes — it sits there until you press the button yourself.
update_item_price · create_announcement
- Anything applied in bulk is High, whatever it would have been on its own. The same change to one dish waits fifteen seconds; to your whole menu, it waits for you.
- An announcement aimed at everyone is High by definition.
Risk can only ever be escalated by these rules, never reduced.
What it is looking at
Your restaurant. Nobody else’s.
Your own numbers
Orders, bills, menu, recipes, stock, reviews, complaints, shifts — the same database that just billed your last table.
Not a benchmark
It is scoped to your restaurant. There is no pooled average across our customers being quietly computed from your sales.
Every action logged
What it did, what it read to decide, and whether you approved it — written down and readable after the fact.
It says when it does not know
Where the data is too thin to be sure, it says so and marks its confidence rather than producing a confident number.
The twelve
Each of these has a screen of its own.
The day above is what they add up to. This is the list, with what each one reads and what it hands you.
| Skill | What it reads | What it hands you |
|---|---|---|
| Pulse | Today against yesterday and last week | The day in a sentence, and the one thing to do about it |
| Ask | Whatever your question needs | An answer in your own words, off your own numbers |
| Menu Doctor | Sales and margin per dish | Which dishes earn, and which just take up space |
| Prep Predictor | Four weeks of the same weekday, hour by hour | How much to prep today |
| Inventory Alerts | Stock against recipes and today’s pace | What runs out before service does |
| Expected Stock | Opening stock, consumption, the hourly pattern | What should be in the fridge right now |
| Bottlenecks | Ticket timings by station | Where the kitchen loses its minutes |
| Pricing | Ingredient cost against menu price | What a dish should cost, given what it costs you |
| Offer Engine | Dead hours and who has gone quiet | The offer worth running, and who to send it to |
| Churn | Visit gaps per customer | The regulars who quietly stopped coming |
| Staff Insights | Orders and covers per person per shift | Who is carrying the shift, and who is not |
| Complaint Patterns | Complaints, grouped | The same complaint, for the third time this week |
Revenue Forecast and Review Responder ship alongside these — fourteen panels in all. Twelve is the number worth remembering.
Ask it anything
In your words. Including Hinglish.
There is no query language and no report builder. It reads the question, works out which of its own tools to run, runs them, and answers.
- What did Tuesday evening make?
- Which dish lost me money last month?
- Kal kitna paneer lagega?
- Who was my best waiter this week?
- Sabse zyada complaint kis cheez ki aayi?
- Show me the dead hours this month
Watch it read your restaurant.
Fifteen minutes. We point it at a day of your real numbers and you see what it says.