Handover packs built during an engineer's notice period, from tickets and code
TL;DR Batonly turns an engineer's notice period into a proper handover. It reads the person's tickets, commits and project chat, drafts what the successor needs to know and books short recorded walkthroughs to fill the gaps. IT services firms and GCCs pay per departure, because lost context slows down every replacement.
People leave Indian tech teams all the time. A rating agency's sample of the five largest IT services firms saw annual attrition peak near 23% in 2022–23 and settle around 13% from late 2023, against about 18% before the pandemic[1]. One large IT services firm reported 14.5% for July–September 2024[2]. Global capability centres, which now employ over 1.9 million people[3], face the same churn.
Every exit walks out with knowledge nobody wrote down - why a workaround exists, which client contact actually decides, which test is flaky. Notice periods are often long, and yet the time goes on one hurried knowledge-transfer call and a thin wiki page. I found no Indian study that measures the cost of a poor handover, so this is a gap you'll have to put a number on in pilots.
When HR marks a resignation, Batonly opens a handover file for that person. It reads the systems the company connects, like issue trackers, code repositories, wikis and chat, and drafts a pack. That covers open work and where it stands, the systems the person touched most, recurring decisions they made, people they dealt with and questions nobody else seems able to answer. Then it schedules three or four 20-minute recorded sessions where the leaver answers those questions, and attaches the transcripts.
The successor gets one page to start from and can search the rest. Managers see a simple status for every exit - pack drafted, gaps closed, successor signed off.
Batonly is not a general wiki or enterprise search tool. It works on one moment, the weeks before someone walks out, when the knowledge is still recoverable and the person still has time.
Leavers, successors and project managers use it. The buyer is a delivery head, GCC site leader or HR business partner who gets measured on ramp-up time and client continuity. Price per departure, say ₹3,000–8,000 per handover (my assumption, with no public benchmark found), so the cost tracks the pain and the buyer pays only when someone actually leaves.
Language models can now summarise tickets and code history cheaply, which makes a drafted pack practical where a blank template never got filled. Attrition has settled at a steady 12–13%, which the agency expects to hold[1], so exits are a predictable flow you can budget for and not a crisis.
There's no public figure for handover tools. Here's a rough bottom-up view - 1.9 million GCC staff[3] at about 13% attrition would mean roughly 2.5 lakh exits a year, before you count IT services firms. That's my arithmetic though, and GCC attrition may not match the big IT firms' rate.
Enterprise AI search tools index a company's data[4], which helps find documents but doesn't interview the leaver. Employee-listening bots track sentiment through the lifecycle and predict turnover[5], but stop short of capturing work knowledge. Wiki tools depend on people writing pages, and we all know how that goes. The gap is a tool that owns the exit moment.
| Difficulty | Moderate (40/100) |
| Starting capital | ₹60 L–1.2 Cr |
| Time to launch | 6–9 months |
The hard parts are access and trust. Clients often own the repositories and tickets, so each account needs approval before Batonly can read them. Leavers have very little reason to help, so the process has to be quick and count toward their exit clearance.
No sector licence is needed. The approvals that matter come from the employer and its clients.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't trust AI drafts as the final record. A model can misread why a workaround exists, so the leaver and successor confirm the pack.
Want to work out the AI layer for Batonly? Talk to Yash →
I like how focused this is, and it suits a founder who has managed delivery teams through heavy churn and has patience for enterprise security reviews. If you want self-serve SaaS growth then look elsewhere. Prove first that successors reach their first solo task faster with a pack than without, on at least ten exits.
Plan for roughly ₹60 L–1.2 Cr, most of it on engineering, integrations with issue trackers and code repositories, and security reviews.
No sector licence. You need DPDP compliance, written client approval before reading their systems and GST registration like any SaaS seller.
Yes, attrition and lost context exist in every tech hub. Check local employee privacy law and works-council rules before you pilot.
The free Batonly validation kit has the line-by-line capital breakdown, the effort scoring, the data-protection checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for managers and buyers, and 5 assumptions to test. Download the kit →
Thinking about building Batonly or something close to it? The make-or-break work is getting clients to approve read access to their systems, and that's a conversation I'm happy to help you plan. 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.