Cohort 09 starts November 14, 2026 and registration is open right now. Seats are limited and it closes the moment it's full - register on the site or DM me on WhatsApp if you want to talk it through first.

The audience moved again. PMs joining now already use these tools every day - what they lack is a way of working, not an introduction. Two sessions in one weekend left no room to go and use any of it. One three-hour session a weekend, across eight weekends, gives you six days in between to run it on your own job, and everything that reads better than it teaches moved into the Academy.

About 40% of alumni are outside India - Singapore, US, UK, UAE, Germany, Nigeria, Ghana, Australia. Session timing is set per cohort based on the group, with recordings and 1:1s to cover any timezone gaps.

Good - that's the new bar. Week 2 still covers fundamentals + API building because everyone needs the same vocabulary, but the centre of gravity moved. Most of the program is MCP, agents, evals, ops, RAG and fine-tuning. You'll start shipping by Week 3.

Because I'm coaching, not lecturing. I personally vet every applicant on a 20-30 minute call. I'm fully in for every cohort - past cohorts averaged 5-10 1:1s per participant across the program. 12-18 PMs is the ceiling for me to stay personally involved. More than that and I'd just be a content factory.

You book a slot. We talk. About what's blocking you, what you're building, the dumb question you're embarrassed to ask in the group. Past cohorts averaged 5-10 calls per person over the program weeks. Setup and tool-stack help is covered too. If you're stuck at 11pm, we'll figure it out.

Every session is recorded and shared with the cohort, so you can catch up on your own time. That's also how PMs in other timezones keep pace. But the recording is the backup, not the plan - the live build is where the actual learning happens, and a 1:1 is there if you need to close a gap properly.

No. The product you took over is yours: the repository, the data, and the right to take it to market. So is the community: live sessions whenever something new lands, offline build days across Pune, Bengaluru, Delhi, Chennai and Hyderabad, a job board, and the WhatsApp group that never closes. You join a cohort for eight weekends and a tribe permanently.

Probably not, and I say that from the data. Every cohort asks people to self-rate on the way in, and the low scores are consistently wrong - they come from PMs who have written SQL, shipped with engineering teams, or already prototype with AI tools. People rate their confidence, not their ability. If you have ever been in a technical conversation and followed it, you are not a beginner here.

Yes, and roughly a third of each cohort joins for exactly that. Two goals show up again and again: ship without waiting on a dev team, and hold a technical discussion without a translator. The second one needs the same foundations as the first - you cannot ask an engineer a sharp question about evals or retrieval if you have never built either. You still do the builds. The point of them is the fluency, not the artifact.

No. Recent cohorts have skewed senior - a lot of people between 4 and 18 years in, including staff engineers turned PMs and product leaders. That's deliberate. I'd rather teach the AI layer on top of real domain expertise than run a fresh-grad bootcamp. Nobody here is going to explain what a roadmap is to you.

Tell me. That's what the 1:1s are for, and past cohorts averaged 5-10 of them per person. Recordings cover a missed session; a 1:1 covers a missed concept. The failure mode I actually worry about is people going quiet for three weeks and trying to catch up alone - so I check in, and I'd rather have an awkward conversation in Week 4 than a polite one in Week 8.