Store rosters drawn from hourly footfall and bills, not a fixed weekly chart
TL;DR Rosterpeak helps retail chains put staff on the floor when shoppers are actually there. It reads hourly bills and footfall counts per store, forecasts the coming week and drafts a roster that respects shift and weekly-off rules. Chains pay per store for fewer idle hours and fewer lost sales at the evening rush.
Indian retail was worth about US$1,094 billion in 2025, and organised chains keep adding stores[1]. In most of them a store manager still writes the roster on a fixed pattern, with the same headcount at 11 a.m. on a Tuesday as at 7 p.m. on a Saturday.
So staff stand around in the morning and queues pile up at billing in the evening, which is exactly when the sales happen.
Rules make it harder. Each state's Shops and Establishments Act sets daily hours, weekly offs and overtime, and the details change from state to state. Managers juggle all of that on paper or in spreadsheets.
Rosterpeak takes two inputs per store - bills by hour from the POS and footfall from a door counter where there is one. It forecasts each hour of the coming week, with festivals and pay-day weekends built in, and turns that into a target headcount. Then it drafts a roster that fits staff availability and the state's hour limits, which the manager edits and publishes to staff phones.
The seed wanted AI that rates each employee's performance, and we changed that. Scoring individuals by camera or tracking eats away at trust on the floor, and the DPDP Act still asks for notice, purpose limits and safeguards on employee data even where employment is a permitted use[2].
Rosterpeak measures the store and the hour, not the person. The one number it reports is conversion by hour against staff on duty, so the owner can see what an extra person at 7 p.m. is worth.
The buyer is the operations head of a chain with 20–300 stores. Global rostering tools charge per user, and one lists US$5–9 per user a month (about ₹480–870)[3], which is steep for Indian store staff on modest pay. My working assumption is a per-store price of ₹1,500–4,000 a month, tested in pilots.
The DPDP Act of 2023 nudges employers away from ad hoc tracking and towards documented, limited uses of staff data[2]. Demand-based scheduling has gone mainstream abroad, and one global vendor puts demand forecasting and auto-scheduling in its mid-tier plan[3]. Cheap door counters and cloud POS exports mean the hourly data now exists in most organised stores.
There is no public figure for what Indian retailers spend on workforce management. Vendor claims abroad give a sense of the prize - one vendor cites an analyst-firm study reporting 20% less over- and under-scheduling and 50% less overtime[4]. Treat that as a vendor claim.
Adjacent - Indian retail at US$1,093.89 billion in 2025[1].
Global rostering vendors sell demand-based scheduling, priced and built mostly for Western labour markets[3][4]. Indian HR suites handle attendance and payroll but rarely forecast hourly demand. One Indian planning vendor serves Indian fashion and footwear brands with stock planning, not people planning[5].
The gap is a tool priced per store that knows Indian festival calendars and state shop rules.
| Difficulty | Moderate (36/100) |
| Starting capital | ₹50–90 L |
| Time to launch | 6–9 months |
Forecasting hourly bills is routine stuff. Getting many states' hour and weekly-off rules right is fiddly, and a labour lawyer has to check it. Adoption is the hardest part though, because store managers like owning their rosters and don't trust a system that might cut their team.
No sector licence applies. The hard rules here are labour rules, which your rosters must respect.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't use AI to score or rank individual staff. It erodes trust on the floor and adds data duties, so keep it at the level of the store and the hour.
Want to work out the AI layer for Rosterpeak? Talk to Yash →
Here's what can go south -
I think it's a fair bet for a founder with retail operations experience and patience for messy store data. If you're hoping to sell monitoring dashboards then it is not for you. Prove first that drafted rosters lift evening conversion by 5% or more in ten stores without adding total hours.
Plan for roughly ₹50–90 L, mostly on engineers, POS connectors and sales to chains. A pilot with ten stores of one chain keeps the first spend focused.
No sector licence. Your rosters must follow each state's Shops and Establishments Act, and staff data falls under the DPDP Act.
Yes, retail chains everywhere schedule shifts. Local labour law on hours and breaks will shape your rules engine, so check it before you sell.
The free Rosterpeak validation kit has the line-by-line capital breakdown, the effort scoring, the labour-law and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for operations heads and store managers, and 5 assumptions to test. Download the kit →
Thinking about building Rosterpeak or something close to it? The make-or-break work is winning over store managers who see a roster tool as a threat, and that's exactly the kind of thing I help founders with. If you need a hand, you know where to find me. Talk to Yash →
For illustration only. Names are fictional and ideas hypothetical; sourced facts are real but may be out of date. Nothing here is legal, financial or professional advice, and Yash Khatri is not personally liable for any use of it. Read the full disclaimer.