Skip to content

From "what's a terminal?"

You will ship a real app. In 10 days.

You have never written a line of code. By the end of the tenth day you will have a working booking platform, on the web and on your phone, that you built yourself.

A student holding a laptop and a phone, both running the booking app they built, surrounded by floating app screens
A student gesturing at a row of screens that grow from a rough wireframe on the left into a finished app on the right

How it works

You describe it. Claude builds it. You decide what happens next.

That loop is the whole job. The course teaches you to run it well, which is a different skill from memorising syntax.

  1. Say what you want, in plain English

    No syntax, no jargon. "Customers should be able to pick a time slot and pay." That is a valid instruction.

  2. Claude writes the code

    Files appear, the app updates, and you watch it happen. Every day has the exact prompts to type, ready to copy.

  3. You check it and say what to change

    This is the part that takes a person: testing it, spotting what is wrong, and knowing what to build next.

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. That is a real job, and it is the one worth learning now.

The project

One real product, not a set of exercises

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 02

Customer home

Search professionals, see ratings, book a slot.

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 will actually use

Industry standard, all of them free to start, and all of them worth having on a 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 are never more than one session away from seeing progress.

  1. Setup

    Before we start

    Accounts and tools ready before the first session.

  2. Terminal, Git, deploy

    Live link

    Your first project, live on the internet by the end of the day.

  3. Design and fake data

    Clickable

    Every screen built and clickable, before any database exists.

  4. Database and login

    Real accounts

    Real people can sign up and log in.

  5. Booking engine

    It books

    Availability, slot locking, and both dashboards working end to end.

  6. Build lab

    Your idea

    Catch up, then plan an app of your own with the instructor in the room.

  7. Money and messages

    It takes money

    Payments flow through. Confirmation emails go out.

  8. Mobile app

    On your phone

    The same product, running on your actual phone.

  9. Polish and debugging

    Unstuck

    Loading, empty and error states. Reading errors without fear.

  10. Build lab

    Pre-flight

    Everything checked against the pre-launch list.

  11. Ship it

    Shipped

    Live links, and the first screen of your own idea.

The material

What is actually written down

This cohort has not run yet, so there are no student numbers to show you. Here is 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 cannot verify, here is exactly what is in the box. All of it exists right now.

Every prompt, word for word

Not a summary of what to ask. The exact text to type, ready to copy.

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. Deciding what deserves to be built is the part that still takes a person, so you get a Claude Project set up for each step of it, in the order you need them.

  1. Ideation

    Turn a vague hunch into one specific idea, by being asked the questions you would not have thought to ask yourself.

  2. Market research

    Find who already does this, what they charge, and where the gap actually is, before you commit ten days to it.

  3. Validation

    Pressure test the idea against real people and real objections, so you find the problems now rather than at launch.

  4. 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 had missed the boat

Three students working on laptops around floating interface panels, one raising a hand to ask a question

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 a live thing you can show, not a certificate.

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. This teaches product thinking instead.

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
A student standing on ascending steps built from app screens, holding up a phone running their finished app

What it costs

One fee, ten days, ten seats

No tiers, no upsell, and nothing held back for a premium version. Everybody in the room gets the same thing.

₹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
Join the next cohort

Paid in full

One payment. Instalments are not offered.

Non-refundable

The seats are capped, so a booked seat is one nobody else can take. Ask us anything you are unsure about before you pay.

What else you will 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 have never written a line. Day 1 covers what a terminal is, how to run a command, and what Git does, all with analogies rather than jargon.

Next step

Join the next cohort

Two fields to start. Leave your details and you will hear from us with the dates, the fee, and how to confirm a seat.

  • 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. No newsletter, no resale, and you can ask us to delete them at any time.

Required fields0 of 2