Embedded delivery coaches for new GCCs, paid against measured team results
TL;DR Cadencewright places experienced delivery coaches inside newly opened global capability centres in India for their first one to two years. Each coach works with three or four teams, and part of the fee depends on measured delivery speed and stability. The GCC head pays, out of a budget that's already set aside for ramp-up.
India had about 1,700 global capability centres employing 1.9 million people in 2025, and the count may reach 2,200 by 2030[1]. A new centre typically hires hundreds of engineers in its first year, then has to deliver to a parent company that already runs agile at scale.
Many stumble. The 17th State of Agile report found that medium and large companies are less satisfied with agile than small ones, and report real barriers to adopting it across the organisation[2].
In a new GCC the usual pattern is a two-day certification course, a few scrum ceremonies and then teams that hold standups every morning without shipping any faster, and the parent sees missed sprints and starts to doubt the centre.
Why I reframed the seed. The seed called this a platform. It's really a service, because coaching works through people in the room and not through software. I kept the goal and made the commercial model sharper.
Cadencewright embeds one coach per three or four teams for 6 to 12 months. In the first month the coach baselines each team on a few delivery measures made popular by the DORA research programme, such as how often code ships and how often a release fails, plus sprint predictability.
Then the coach works on the specific blockers - unclear ownership between the centre and headquarters, handoffs across time zones, and backlogs written by people 8,000 kilometres away.
A share of the fee, say 20%, is paid only if agreed measures improve by a set amount. That makes Cadencewright easy to buy and hard to copy for trainers who sell by the head.
The GCC site leader or head of engineering pays, usually from a transition or ramp-up budget, and the teams are the users. Today the alternative is certification training, where a popular scrum-master certification course costs US$250–2,495 (about ₹24,000–2.4 L) per person[3], or a large consultancy's transformation team at a much higher price. My estimate for coaching is ₹2–4 L per coach-month.
GCCs are moving from back-office work to owning products, and the higher US fees on H-1B visas in 2025 pushed more work to India[1]. The 2024 DORA report also found that unstable priorities hurt productivity and raise burnout[4], which is exactly what a new centre faces. Coaches who can show measured change have a clearer pitch than ever.
There's no public figure for spending on agile coaching in India. The narrowest signal is the count of new centres, around 1,700 today and up to 2,200 by 2030, so roughly 100 new centres a year (my estimate from that projection)[1].
If one in ten bought a 12-month engagement of three coaches at ₹2–4 L per coach-month then that's about ₹70 L–1.4 Cr a year (my estimate). Small, but enough for a focused firm, and bigger once established centres are included.
The large consultancies run agile transformations for parent companies, often at global rates. Independent trainers in Bengaluru, Pune and Hyderabad sell certification courses accredited by agile certification bodies[3]. GCC setup firms help with real estate and hiring.
Few tie their fees to delivery measures, and almost none specialise in the first two years of a new centre.
| Difficulty | Easy (25/100) |
| Starting capital | ₹30–60 L |
| Time to launch | 3–6 months |
Building this is easy. The hard parts are hiring coaches who have actually shipped software (not just taught scrum) and agreeing on measures with clients before the first invoice. Keep revenue per coach high enough to retain good people, because your clients will try to hire them.
No licence needed. Consulting and coaching have no sector permit, so the baseline applies.
Building this outside India? The categories above usually have a local equivalent, so check with your own regulator.
Don't use AI metrics to rate individual engineers. The measures are for teams, and using them on people would sour the engagement.
Want to work out the AI layer for Cadencewright? Talk to Yash →
Here's what can go south -
I'd back this for a founder who has led delivery inside a GCC or a product company and knows a bunch of site leaders. If your experience is only training then it is a poor fit. Before scaling, prove that two paying teams improved their release frequency within six months and that their site leader will say so on record.
Plan for roughly ₹30–60 L, most of it for coach salaries and hiring before the first engagements start to pay.
It can be if revenue per coach stays high. No public spending figure exists, so prove it with two paying teams first.
Yes, new engineering centres open in many countries. Check local contract and tax rules for outcome-based fees.
The free Cadencewright validation kit has the line-by-line capital breakdown, the effort scoring, the contract and tax checklist, a 14-day validation sprint with pass/fail targets, a 90-day launch plan, 10 interview questions for GCC leaders, and 5 assumptions to test. Download the kit →
Thinking about building Cadencewright or something close to it? The make-or-break work is agreeing outcome measures that both you and the GCC head trust, and I've helped founders think through exactly that kind of deal. 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.