Fair rotas for late-night client calls in India teams serving US and UK
TL;DR Rotawise reads team calendars and shares out the late-evening calls that come with serving clients in New York or London, so the same three people stop taking every 9 p.m. stand-up. Managers set a cap per person and the tool proposes rotations and better slots. IT services firms and capability centres pay per seat.
Burnout in Indian tech teams often has a boring, visible cause - the evening call. One big office-suite vendor's telemetry shows meetings starting after 8 p.m. rose 16% in a year, mostly from global teams, and 29% of active workers are back in their inbox by 10 p.m.[1] In an India team serving a US client that load rarely spreads evenly. It lands on the leads and on the people who never say no.
Long hours carry real risk. WHO and ILO linked 745,000 deaths in 2016 to long working hours, with South-East Asia among the worst-hit regions[2]. One large consultancy put the cost of poor employee mental health to Indian employers at about ₹1.1 lakh Cr a year[3].
The seed pitched wearable biofeedback to spot burnout, and I reframed it. Heart-rate data from staff is sensitive, consent given to an employer is hard to call free under the DPDP Act[4], and a stress reading tells a manager nothing about what to change. Late-call load is measurable from calendar metadata alone and you can fix it this week.
Rotawise connects to the major work calendars with each employee's opt-in. It reads only meeting times, attendees and time zones, never content. For each team it shows who carried how many calls after 8 p.m. India time over the past month. The manager sets the rules - no one above two late calls a week, a 12-hour gap before the next morning meeting, protected evenings for people on medical or parental grounds. Rotawise then proposes a rotation for recurring client calls and suggests overlap slots the client side can live with. A model learns which calls actually need which people and flags meetings where half the attendees never speak.
Individuals see their own numbers. HR sees only team totals.
A delivery head or HR business partner buys it, at an IT services firm, a global capability centre or a product company with a US sales team. The engineers and leads on the calls use it. I found no published Indian price for a tool like this. A per-seat fee of ₹150–300 a month is my assumption to test, set below what firms pay for collaboration suites.
India's four labour codes took effect on 21 November 2025[5], and the OSH Code fixes the working day at eight hours[6], which turns evening load into a compliance question and not only a culture one. A global polling firm's 2026 report found South Asia's manager engagement fell 8 points in 2025, the steepest drop of any region[7]. Managers who are burnt out themselves won't fix rotas by hand.
There's no public figure for scheduling tools aimed at time-zone load. On the adjacent side, one market-research firm sizes India's corporate wellness market at US$664.5M for 2025 (about ₹6,400 Cr)[8], and a second estimate differs about fourfold, so treat both as context. The real signal to find is the number of India-based staff in client-facing global teams.
The biggest office suite's built-in analytics give managers team-level views of after-hours work and meeting overload, with private personal insights[9]. They only work inside that suite though, and they don't allocate the late-call burden or enforce caps. Calendar assistants abroad protect one person's focus time, not a team rota. In my limited check I found no Indian product built around rotating time-zone calls. The gap is fairness across a team, made visible and enforceable.
| Difficulty | Moderate (36/100) |
| Starting capital | ₹60–110 L |
| Time to launch | 5–8 months |
The software is ordinary calendar integration. The hard part is behaviour, because clients set meeting times and managers have to be willing to tell a client the 9 p.m. call now rotates. Passing security reviews at large IT firms, which treat calendars as sensitive, also takes months.
No sector licence is needed for calendar scheduling software. Labour and data rules shape what you can promise.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't treat AI output as a health or burnout signal. It counts calls from metadata and says nothing about how a person is doing.
Want to work out the AI layer for Rotawise? Talk to Yash →
I'd say it's worth trying for a founder who has run offshore delivery and knows how client calls get scheduled. It suits a lean SaaS team, and if you're hoping to sell a wellness app then look elsewhere. Prove first that one delivery unit cut its heaviest person's late calls by a third in eight weeks without a client complaint.
Plan for roughly ₹60–110 L, most of it on calendar integrations, a lean product team and long security reviews at large IT firms.
No sector licence. You need DPDP compliance for calendar data and GST registration, and you should know the labour codes on working hours.
Yes, any team serving clients across a big time gap has the same evening load. Check local employee privacy and working-time rules first.
The free Rotawise validation kit has the line-by-line capital breakdown, the effort scoring, the labour-code and data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for delivery heads and engineers, and 5 assumptions to test. Download the kit →
Thinking about building Rotawise or something close to it? The make-or-break work is getting a delivery head to change a client's meeting pattern and then showing the change held, and that's a conversation I enjoy. 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.