We tried to hire people who knew these tools. In all of Kanpur, we found nobody. So we built the room where they get made.
We tried to hire people who knew these tools. In all of Kanpur, we found nobody.
So we built the room where they get made. Twenty-eight days. Three guided projects, then your own idea, shipped.
The gap
What is taught here and what is hired for have come apart.
of engineering graduates are without a job or internship offer.
Source: Unstop Talent Report 2025, via Business Standard, 21 March 2025
BE/BTech employability, down from 71.5% the previous year.
of Indian employees already work with generative AI tools.
Market context, not a prediction of any student's outcome.
Those four facts describe one problem.
What you work with
Four tools, used properly, for twenty-eight days.
Claude Code · AI agents · AI video generation · AI Web/App development
Claude Code
Building real software by directing an AI coding agent, not by typing every line. For example: adding a working payment page to a site that already exists, or turning a bug report into a tested fix.
AI agents
Systems that carry out multi-step work on their own. For example: an agent that reads incoming enquiries, answers the ordinary ones and passes the rest to a person.
AI video generation
Producing video with generative tools, start to finish. For example: a thirty-second advertisement for a shop, or a voiced walkthrough of the project you built.
AI Web/App development
Putting these together into something that actually ships. For example: a booking site for a clinic in the city, or a phone app with a real sign-in and a database behind it.
The shape of it
The twenty-eight days
Fourteen days we decide. Fourteen days you decide.
First, learn in the classroom in Kanpur with three guided builds. Then choose your own idea and finish it remotely, with our support.
Days 1 to 3
Tool fluency
You learn the tools by using them, and something of yours is live on the internet in the first three days.
3 days · Classroom
Days 4 to 12
Three projects
Three complete builds, three days each. A working application. An agent that does the work on its own. A media piece about what you made. Every day ends with you explaining what you built and why.
9 days · Classroom
Days 13 to 14
Hardening
You make it solid, then sit a mock interview about your own work. Real questions, real feedback.
2 days · Classroom
Days 15 to 28
Your own idea
You decide what to build. We help you scope it so it can actually be finished, then stay with you for fourteen days until it ships. The project does not get abandoned at day fourteen.
14 days · Remote
See the full 28-day plan
Everyone builds the same three guided projects. Each is a full cycle: build, break, fix, ship and explain. In the final fourteen days, the idea is yours.
Days 1 to 3
Tool fluency
Learn by using the tools. By day 3 you have a live link you can share with your family.
- Day 1
- Set up and build
Understand how the tools work, give your first real instruction, and get a small build running locally.
- Day 2
- Iterate and debug
Ask for changes, read what comes back and fix what breaks. Make at least ten iterations on a useful page or script.
- Day 3
- Put it on the internet
Learn about domains and deployment, then ship a live URL that belongs to you.
Days 4 to 6
Project 1: a working product
Build a real web application with a purpose, data going in and out, and a user who is not you.
- Day 4
- Scope the product
Decide what it does and what it does not do, then build the skeleton.
- Day 5
- Make it work end to end
Connect the data, find the first real bug and work through a debugging session.
- Day 6
- Ship and explain
Deploy the application and explain what you built, why you built it that way and how it works.
Days 7 to 9
Project 2: an agent that does the work
Automate a real repeated task. Learn where the system can act on its own and where it needs a person.
- Day 7
- Map the task
Pick a boring, useful task and write down what a human does, step by step.
- Day 8
- Build and watch it fail
Build the agent, observe its failures and understand why they happen.
- Day 9
- Add guardrails and ship
Run it on real input, add boundaries for unsafe or uncertain actions, then ship and explain it.
Days 10 to 12
Project 3: media about your work
Use video, design, brand and copy to help someone else understand and take your work seriously.
- Day 10
- Generate, edit and judge
Work with image, video and voice. Learn to spot what the tools get wrong and correct it.
- Day 11
- Give your product a face
Apply the design and media work to the application you built in Project 1.
- Day 12
- Assemble and explain
Make a short media piece about your work and explain the choices behind it.
Days 13 to 14
Make it solid. Defend your decisions.
Two days to improve the work you already have. The mock interview is about your own project.
- Day 13
- Break it on purpose
Handle errors, write the README and clean the repository. Make the project survive a stranger opening it.
- Day 14
- Sit the mock interview
Explain your approach, what broke, how you found it, what the AI wrote and what you decided. Get specific feedback.
Days 15 to 28
Your own idea, finished by you
Fourteen days of remote work with a written scope, two scheduled live check-ins and asynchronous help between them.
- Days 15 to 16
- Choose and scope
Propose your idea. We help cut it to something finishable in twelve days, then lock the scope in writing.
- Days 17 to 21
- Build, week one
Make daily progress remotely. At the live check-in on day 21, review what works, what is stuck and what needs to be cut.
- Days 22 to 26
- Build, week two
Finish the agreed scope, with support as you work through the final problems.
- Days 27 to 28
- Ship and document
Publish the project, organise the repository and explain the finished work at the live check-in on day 28.
What a classroom day looks like
- First hour
- Understand the work
What you are building today, why it matters and what usually goes wrong.
- Middle
- Build with a mentor nearby
The mentor moves between students. You spend the session trying things and typing, not watching a screen.
- Last 30 minutes
- Explain it back
Each student explains what they built and why. The others ask one question each. Every classroom day ends with a student talking.
What you leave with
Eight things you own
Press and hold. Nothing here arrives without the work.
01
A live web application
Your first guided project: a working product with real data and a user beyond yourself.
02
A working agent
Your second guided project: an automation for a repeated task, tested on real input with guardrails.
03
A media piece
Your third guided project: image, video or voice work that presents what you built.
04
Your own project
Chosen, scoped and finished by you during the final fourteen days, with our support.
05
Public URLs and clean repos
Each project has a public link and an organised repository, with a README that helps someone else open it.
06
A mock interview
Questions about your own work, with specific written feedback.
07
The explain-back habit
Practice saying what you built, why you chose that approach, and what you changed when it broke.
08
An honest certificate
It says what you actually did. Nothing inflated.
Work you can show. Decisions you can explain. That is the point.
Three students. The whole team.
Batch 1 is three people. Not because it is exclusive, but because a project you actually ship needs attention a hall of forty cannot get.
Three students, with the whole team on them. Daily mentor attention in the classroom, then two live check-ins and asynchronous help while you build your own idea remotely.
What it costs
The number is on the page.
Total, including GST.
Books your seat₹5,900
Balance, before the batch starts₹29,500
Registration feeNone
Material chargesNone
Contact us for pricing usually means the price depends on who is asking. Ours does not.
Questions people actually ask
The ones that decide it.
Do you guarantee a job?
No. Nobody honestly can. What we commit to is the work: three guided projects, a project you choose yourself, public links and repositories, and a mock interview on your own work with real feedback. Those are yours to show and explain.
Are there students who finished already?
Not yet. Batch 1 has not started. We would rather tell you that plainly than write testimonials nobody earned.
Do I need to already know how to code?
You need to be comfortable with a computer and willing to work. These tools changed what knowing how to code means. Tell us where you are starting when you apply and we will be straight with you about fit.
How is this different from a full-stack course?
You complete three guided builds — a web application, an agent and a media piece — then choose and finish your own project. Each build goes through scoping, debugging, shipping and explaining your decisions. The work, and your understanding of it, are what you leave with.
Is it online or offline?
Days 1 to 14 are in the classroom in Kanpur. Days 15 to 28 are remote, working on your own idea with a written scope, live check-ins on days 21 and 28, and asynchronous help in between.
Do I choose all three guided projects?
The first fourteen days are guided: everyone builds the same three projects, so you can focus on learning the tools and finishing the work. On days 15 and 16 you choose your own idea and agree its scope with us, then build and ship it by day 28.
What happens after the classroom phase?
You work remotely on your own project for fourteen days. We agree in writing what done means, review progress in a live check-in on day 21, and meet again on day 28 for the final explain-back. Asynchronous help continues between those check-ins.
Is the certificate worth anything?
On its own, no certificate is. Ours says exactly what you did. Your shipped projects, their repositories and your ability to explain the decisions are the parts that carry weight.
Can my parents talk to someone before I decide?
Yes, and we would prefer it. There is a page written for them, and the institute is a real place in Kanpur you can visit before any money changes hands.
Apply
Tell us where you are starting from.
Four questions. It takes a minute, and a real person reads every one.