Day 02
Customer home
Search professionals, see ratings, book a slot.
From "what's a terminal?"
You'll ship a real app. In 10 days.
You've never written a line of code. By the end of day ten you'll have a working booking platform, on the web and on your phone, that you built yourself.
How it works
You describe it. Claude builds it. You decide what happens next.
That loop is the whole job, and ten days is enough time to get good at running it.
Say what you want, in plain English
No syntax to learn. "Customers should be able to pick a time slot and pay." That's a valid instruction.
Claude writes the code
Files appear and the app updates while you watch. Every day has the exact prompts to type, ready to copy.
You check it and say what to change
You test it, you find what's broken, and you decide what comes next. Claude won't do this bit for you.
The idea
You are not learning to code.You are learning to direct.
Most courses hand you syntax and hope a product appears at the end. This one is the other way round. You decide what gets built and why. Claude writes the code. You read what came back, test it, and say what to change.
What a machine is now good at
- Syntax and boilerplate
- Wiring services together
- Remembering the exact command
What still takes a person
- Judgement about what to build
- Sequencing the work
- Knowing when something is wrong
Those three are what these ten days train you in.
The project
One real product, start to finish
A services booking platform. Customers find professionals, book a slot, and pay. Professionals manage their availability and their bookings. You build all of it.
Day 04
Provider dashboard
Manage availability, confirm bookings, track earnings.
Day 04
Booking flow
Pick a date, choose a slot, pay, get confirmed.
Day 07
Mobile app
The same backend, running natively on your phone.
The tools you'll be using
These are industry standard. All free to start, and all worth having on your CV.
- Next.jsThe website
- SupabaseDatabase and login
- ExpoThe mobile app
- RazorpayPayments
- VercelPutting it live
- GitHubSaving your work
The plan
The 10 days
Two hours a session. Every day ends with something that works, so you're never more than one session away from seeing progress.
Setup
Before we startAccounts and tools ready before the first session.
Terminal, Git, deploy
Live linkYour first project, live on the internet by the end of the day.
Design and fake data
ClickableEvery screen built and clickable, before any database exists.
Database and login
Real accountsReal people can sign up and log in.
Booking engine
It booksAvailability, slot locking, and both dashboards working end to end.
Build lab
Your ideaCatch up, then plan an app of your own with the instructor in the room.
Money and messages
It takes moneyPayments flow through. Confirmation emails go out.
Mobile app
On your phoneThe same product, running on your own phone.
Polish and debugging
UnstuckLoading, empty and error states. Reading errors without fear.
Build lab
Pre-flightEverything checked against the pre-launch list.
Ship it
ShippedLive links, and the first screen of your own idea.
The material
What's written down so far
This cohort hasn't run yet, so there are no student numbers to show you. Here's what exists today instead, all of it countable.
10Days
Two hours each, live
60Written pages
A companion to every session
35Session pages
Four for each day of the course
5Agents
Installed and yours to keep
What you get
No testimonials yet. This cohort is new.
So instead of quotes from people you can't check, here's exactly what's in the box. All of it exists right now.
Every prompt, word for word
The exact text to type, ready to copy and paste.
A "when it breaks" page every day
The five most likely failures for that day, each with the exact fix.
Five agents
Product brief, screen builder, database, fix-it, and ship. Installed and yours to keep.
A written companion to every session
Miss a day and read it instead. Nothing lives only in the live call.
Lifetime access
Including updates as the tools change.
A repeatable checklist
The process for starting your next project after this one ends.
Before you build
Four Claude Projects for working out what to build
Building is the fast part now. Working out what deserves to be built is the slow part, so you get a Claude Project set up for each step of it, in the order you need them.
Ideation
Turn a vague hunch into one specific idea, by being asked the questions you would not have thought to ask yourself.
Market research
Find who already does this, what they charge, and where the gap is, before you commit ten days to it.
Validation
Pressure test the idea against real people and real objections, so you find the problems now rather than at launch.
User experience
Work out the screens, the flow and what happens when things go wrong, before a line of code exists.
These sit alongside the five agents you install during the course, and they stay yours afterwards for the next idea.
Who it is for
Built for people who were told they'd missed the boat
Who it is for
Designers
You know Figma and you know user flows. Ship the real thing without a handoff.
Career switchers
Marketing, sales, ops, finance. You solve problems daily. Build the tools you wish existed.
Founders and PMs
Stop waiting for a technical co-founder. Build the first version yourself.
Students and freshers
Finish with something live you can show people.
Who it is not for
- Developers already shipping production code. This will move too slowly for you.
- Anyone looking for a no-effort shortcut. You still show up and do the work.
- People who want to memorise syntax. You'll be learning product thinking here.
After Day 10
You leave with the thing, not a certificate
A live URL anyone can open. An app file you can put on your phone. A GitHub repository with your name on every commit.
And the part that outlasts the course: a written process for starting the next one on your own.
- A working web app, deployed and public
- A mobile app running on a real phone
- The five agents, installed and yours
- A repeatable checklist for your next idea
What it costs
One fee, ten seats
One price, paid once. Everybody in the room gets the same thing, and there's no premium version holding anything back.
₹10,000
One payment, for the whole course
- All ten live days, two hours each
- A room capped at 10 people
- All 60 written pages, yours for life
- The five agents, installed and yours to keep
- Four Claude Projects for ideation, research, validation and UX
- Every prompt, word for word
- Updates as the tools change
Paid in full
One payment. Instalments aren't offered.
Non-refundable
The seats are capped, so a booked seat is one nobody else can take. Ask us anything you're unsure about before you pay.
What else you'll spend
GitHub, Supabase, Vercel, Expo and Razorpay in test mode all have free tiers, and the course is built to stay inside them. The one paid tool is a Claude subscription, which you take out on day 1.
Questions
The things people ask before signing up
None. The course assumes you've never written a line. Day 1 covers what a terminal is, how to run a command, and what Git does, all explained in plain English.
You describe what you want in plain English. Claude writes the code. You review it, test it, and tell it what to fix. You're the architect and Claude is the builder. The course teaches you to be a good architect.
GitHub, Supabase, Vercel, Expo and Razorpay in test mode all have free tiers, and the course is built to stay inside them. The one paid tool is a Claude subscription, which you take out on day 1.
A maximum of 10. The sessions are practical and you're meant to be building during them, which doesn't work in a room of a hundred people. It also means seats run out.
Everything is written down: every prompt, every step, every fix. Catch up before the next session. Lifetime access means there's no rush.
Yes. Every command and every fix is checked on Windows as well as Mac.
You keep access to everything, including the agents and the new project checklist. Day 10 itself is about starting your own idea.
The fee isn't refundable. These are live, practical sessions with only 10 seats, so a seat you book is a seat nobody else can take. Please be sure before you pay, and ask us anything you're unsure about first.
No. The fee is ₹10,000, paid once.
Next step
Join the next cohort
Two fields to start. Leave your details and we'll write back with the dates and the fee.
- You get the dates and the fee first
- No payment now, and no card details
- A reply from a person within two working days
- Any laptop works, Mac or Windows
Your details go to the course organiser and nobody else. We won't add you to a newsletter or sell them on, and you can ask us to delete them whenever you like.
Required fields0 of 2