Case study
Hindkesari — 30 days of forecasts, automatic
A non-veg restaurant on FC Road, Pune. Connected directly to Petpooja. Orders sync nightly. Forkcast already maps the next 30 days, factoring in fasting days, festivals, weather, and the salary cycle.
What Forkcast spotted
The 30-day window
Apr 23 to May 22, 2026. Generated from Hindkesari's live Petpooja feed, no spreadsheets.
| What Forkcast spotted | Detail | Action it suggests |
|---|---|---|
| 1 festival day | Buddha Purnima (Fri, May 1) | Cut non-veg prep ~20%, push veg specials |
| 19 fasting days | Ekadashi, Amavasya, weekly observances | Shift portions toward paneer and veg combos |
| 14 quiet days | Below-baseline projection | Lean kitchen, lunch flash offers on Zomato |
| Pre-salary lean window | Last week of the month | Promote ₹199 mini-thali and lunch deals |
| Heat-wave days | Multiple days > 38°C | Stock lassi and buttermilk, push delivery |
Generated from Hindkesari's 30-day forward forecast (Apr 23 to May 22, 2026). Onboarding outlet #2 and #3 next.
The setup
What it took to onboard
Onboarding took 12 minutes. The owner pasted his Petpooja API credentials in Settings, mapped his top 18 dishes to recipe ingredients (auto-suggest got 14 of them right), and set monthly fixed costs (rent, four salary lines, utilities, EMI). The first nightly sync pulled 90 days of orders. Day-2 dashboard already showed a 14-day forward forecast.
He doesn't do anything daily. The brief lands at 7pm. He acts on 1-2 items and goes back to running the kitchen.