Questions People Actually Ask

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. People 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.

Alumni join from 8 countries. 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. The basics are a pre-read before weekend 1 (tokens, context windows, what a call costs), so no live session is spent on them. Weekend 1 starts at agents, then MCP, evals, and RAG and fine-tuning. By weekend 5 you're running your own job on Claude Code.

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. 18-24 people 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 people 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. What you built is yours to keep: the product, its repository and data, and the Claude Code setup you run your job on. So is the community - the Academy, offline build days, and the WhatsApp group that never closes. A cohort for eight weekends, a tribe for life.

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.

No. ₹12,000 takes your seat and the rest follows as you go. There is no contract, and if you are between jobs, tell me and we will go slower.

Any time until the very end, just message me. Say "Hey, this isn't working for me. Can I get a refund?" I'll ask for your payment details and send back whatever you have paid within 48 hours. No interrogation. No trying to convince you to stay. Clean and simple.

Yes. If the timing was wrong or you weren't ready, you can join later. The only reason you wouldn't be welcome back is if you were disrespectful to the community.

Because free doesn't filter, and it wouldn't last. I've seen free communities fall apart because people don't show up. When you make this commitment, you show up. You do the work. And the fee is what keeps this sustainable. That's what makes it good for everyone.

No. Tools and credits are included. The one optional extra is a month of Claude Max, priced separately so you can skip it if you already have one. You will not get three weeks in and discover you need to expense a subscription to keep going.

No. Same cohort, same sessions, same support, and the same attention from me. You're all equals here.

"I understand budget is tight. Could we explore the L&D budget or professional development fund? Also, the investment is quite modest compared to typical training programs - one fee for eight weekends of hands-on learning, with a dedicated Claude Max subscription and every other tool included. I'm also happy to contribute part of it personally if that helps."

"I've tried that actually - there's tons of content but it's scattered, outdated, and mostly theory. This program is designed for people who build products, with live sessions, real projects, and direct access to a mentor. More importantly, I'll have actual deployed projects to show at the end - not just knowledge, but proof I can build."

"I hear you on timing. The program is designed for working professionals - only 5-6 hours per week, with live sessions in evenings. The next cohort starts in November, which actually works well with [current project] wrapping up. If now isn't ideal, could we plan for the following cohort?"

"Great question. First, I can start prototyping AI features myself before involving engineering - saving their bandwidth. Second, I'll be able to evaluate AI vendors and tools from a technical perspective. Third, I can run internal workshops to share what I learn with the team. The skills compound across the whole team."

"I've gone through some of our internal resources - they're helpful for understanding company-specific tools but focus more on using AI, not building with it. This program teaches hands-on development - actually coding and deploying AI applications. It's complementary to what we have, and fills a gap that internal training doesn't cover."

"Of course! Would it help if I set up a quick 15-min call with the program founder? He's happy to answer questions directly. Also, I can connect you with someone from [Company Name] who went through the program. Let me know what would be most useful."

Anyone in a Curious PM cohort, past or present. Sign in with the email you joined with and pull a chair.

No. The coffee and the snacks are on us. Bring the thing you're stuck on.

Whenever a table goes up, usually on a weekend, for about two hours. A different café each time, and the city changes too.

Pick a table and write a line on what you're building. The host answers asks in the order they come in. Once your chair is confirmed, you get the café.

Ask anyway. You join the queue, and if a chair opens up, it's yours and we'll email you.