A rough shape so you know what you're walking into. We'll keep moving — there's a lot to ship in one day.
Read all of these. Pick one that solves a real problem you have right now — not the one that sounds the coolest. Tell me your pick before the day so I can pre-stage anything you'll need.
/draft Priya pulls up past client Priya from Supabase and drafts a personalised re-engagement message in TKC's voice. You approve, it sends — or you copy-paste to WhatsApp./draft Priya → bot reads her project history → drafts "Hi Priya, it's been 18 months since we wrapped your Koramangala home..." → ✅ approve.Read all 11. Sit with them for a day. Then reply to me with your pick — and bring any data the build needs (past clients, vendor list, etc).
Three blocks: install software, create accounts, get API keys. Total time if nothing goes sideways: about 60–90 minutes.
If you get stuck on any step, screenshot the error and send it to me. It's normal to get stuck. Don't push through alone.
Whichever laptop you're bringing on the day. Mac and Windows steps are listed where they differ.
node --version — should print v20.x.x or higher.git --version, see a version number like git version 2.43.x.Sign up with the same email everywhere — makes day-of less confusing. Personal email is fine, work email is fine. Be consistent.
An "API key" is a long password your code uses to talk to a service. Treat it like a credit card number — don't share it, don't paste it in WhatsApp groups. Save each one in a fresh note on your laptop labelled clearly.
/newbot. Follow prompts — pick a name (e.g. "Kahba Brand Bot") and a username (must end in bot, e.g. kahba_brand_bot). BotFather replies with a long token like 7234567890:AAH.... Save this in a note labelled "TELEGRAM_BOT_TOKEN". /start to your own bot. (It won't reply yet — that's normal, we haven't built it.)sk-ant-.... Save in a note labelled "ANTHROPIC_API_KEY". You can never see this key again after closing the popup, so save it now.
sk-...) in a note labelled "OPENAI_API_KEY".
Light packing. The build is on Pradeep — you bring the brain.
Mac or Windows, both fine. Make sure it can survive a full day. Bring the charger — outlets are scarce.
You'll be testing your bot from your phone all day. Make sure Telegram is signed in and notifications work.
Past client list (#6), vendor list (#9), recent project facts (#10) — whatever fits your pick. A spreadsheet or doc is perfect.
Pick the build that scratches an actual itch in TKC's day. Motivation matters more than skill at this stage.
The first hour is unglamorous. Things break. We unblock you. Then it gets fun.
Nobody in the room has done this before. The dumb question is the one that saves the next 30 minutes.
All beginner-friendly. None require you to remember syntax — Claude Code writes the code.
Yes. Claude Code writes the code. Your job is to describe what you want clearly and tell Claude when something doesn't work. By 5:30 PM on the day, your bot will reply on Telegram. That's the bar.
Yes. The whole stack runs on Windows the same as Mac. The prep checklist calls out the few places the steps differ. Bring whatever laptop you'd normally use.
You'll spend the first 2 hours setting up while everyone else builds. We'll catch you up — but you'll have less time to actually build. Do the prep. It's 60–90 minutes of your weekend.
Roughly: ~$20 for one month of Claude Pro, ~$5 of Anthropic API credit, ~$2 of OpenAI credit if your build uses voice. Comes to about ~₹2,500 in tools — and you can stop the subscriptions after the workshop if you want. Vercel, Supabase, GitHub, Telegram, LinkedIn are all free for our scale.
It's yours. It lives on Vercel under your account. The code is in your GitHub. You can keep using it forever — the only running cost is the Anthropic API credits, which for a personal bot is a few rupees a day.
Yes. Once the bot is deployed, anyone can find it on Telegram by its username and use it. The TKC team can all share the same bot.
Tell me before the day. If it's the same shape as one of the 11 (Telegram bot + Anthropic + maybe Supabase), we can swap it in. If it's a website or something bigger, we'll honestly assess if it fits in 8 hours.
Screenshot the screen with the error and message Pradeep. Don't push through alone — getting unblocked takes 2 minutes when shared, 2 hours when solo.
Stories from people who've been through a Claude Code build day. Yours could land here too.
So I can pre-stage anything you'll need on the day.
9:30 AM – 5:30 PM. The full hour-by-hour shape of the day.
/start in Telegram. One command works end-to-end. Everything after is making it smarter.Stories help others decide. Yours lands in our inbox first; we publish after a quick review.
This page is for invited participants. Enter the access code shared with you for this workshop.