Products Decoded · seven-day live programme
Seven evenings. One working product, live on the internet, with your name on the address. Or you get your fee back.
Two days on your roadmap and your system design before anyone writes a line. Then Claude Code writes the code while I walk you through what it just wrote. Understanding is the goal. Shipping is the guarantee.
Eight senior operators filled in the form after my two-day masterclass in August. Seven said they left with something running that they would use on Monday. This is the seven-day version, and at the end of this one the thing is live. Their words, unedited →
AI writes code now, and it writes it well. That is not where people get stuck.
People get stuck in the gap between code that runs on a laptop and a link you can send to somebody. That gap is a database that survives a restart, a login that is not hardcoded, a domain, a certificate, environment variables, and something that stops a bot from signing up four hundred times overnight. None of it is glamorous and all of it is the difference between a screen recording and a product.
I have written about this twice, because I keep watching it happen: everyone is vibe coding and nobody is getting paid, and the gap between a proof of concept and production. This programme is the closing of that gap, done with you, in a week.
No. Seven days does not make you a software engineer, and anybody selling you that is lying to you. What seven days does is get one real application out of your head and onto the internet, and teach you enough of how it works that you can change it afterwards.
What you can do by day eight
What you cannot do by day eight
Both columns are the honest answer. If the left one is what you needed, this is built for you. If you want the right one, you want a computer-science degree or three years of practice, and I would rather say so here than take ₹10,000 from you and disappoint you on day seven.
Design first, code second. That order is the whole method.
Day one is spent on your idea, not on slides. What it does, who opens it, what gets cut so that seven days is actually enough. You leave with a written roadmap for your own product that we both agreed on.
Day two you draw the thing: the data model, the screens, where login sits, what talks to what. Most people skip this part and pay for it on day five when nothing fits together.
From day three the code gets written by Claude Code in front of you, and then we read it together. You are not typing semicolons. You are doing the job an engineering manager does: deciding what gets built and checking what came back.
Deploy, domain, HTTPS, rate limits, secrets out of the repository, a backup. The difference between a demo on your laptop and something a stranger can sign up for at midnight.
What day two produces
Four boxes and the arrows between them. Who stores what, who is allowed to read it, and what happens the moment somebody signs up. Get this right on Tuesday and Friday is calm. Skip it and Friday is a rewrite.
What day three looks like
Line by line, in plain English, with the one line that matters pointed at. You do not need to be able to type this. You need to be able to spot when it is missing.
1export async function GET(req) {
2 const session = await getSession(req)
3 if (!session) return unauthorized()
4 const rows = await db.entry.findMany({
5 where: { userId: session.user.id }
6 })
7 return json(rows)
8} Lines 4 to 6 are the whole lesson. Take the where clause out and every user
on your product can read every other user’s rows. That is the single most common hole in
software built quickly, and by day three you can spot it on sight.
You will understand more than you expect. The guarantee does not depend on it. Even if the code has not fully clicked for you by Sunday, you still finish with the product live, because the roadmap, the design and the seven daily tasks are built to carry you there. Then you have the recorded walkthrough for the part that lands later.
Two hours live each evening, then a task. The tasks are not homework around the edges. Stacked, they are the product.
Day 0 · setup clinic, two days before we start
Ninety minutes, screen shared. Claude, terminal, Node, git, editor, hosting account. Then your idea gets approved, reshaped or swapped, in writing, before the clock starts. Nobody begins day one on a broken laptop.
You leave with: a machine that works and a scope in writing.
Day 1
Your one idea turned into one page: the user, the objects, the screens, the rules, and the list of everything we are deliberately not building this week. The cut list matters more than the build list.
Task: your roadmap, written, in your own repository.
Day 2
Tables and the relationships between them. Who is allowed to see which row. What happens on sign-up. Where files live. How the front end talks to the back. You draw yours, I mark it, you fix it.
Task: your system design, reviewed and corrected.
Day 3
Repository, database, sign-up and login, the first screens. Written by Claude Code against your design, then read line by line with me. This is the day you find out that reading code is far easier than writing it.
Task: two accounts exist, each one sees only its own data.
Day 4
The core action, start to finish. The longest working session of the week. Everything else on your roadmap is decoration until this works.
Task: the main action works, recorded.
Day 5
Your supporting feature, usually the AI one, plus the pass that separates a demo from a product: validation, empty states, loading states, error messages, and the phone layout.
Task: five deliberate attempts to break your own product, and what you fixed.
Day 6
Deploy day. Public URL, environment variables, push to deploy. Then the hardening, taught off a real incident: a live product of mine took a slow, distributed bot signup flood across roughly fifty exit nodes, and not one of its defences fired, because every one of them was keyed on speed or on IP address. What it cost me, what actually closed it, and the four controls you add to yours in the session.
Task: your URL is public, rate limited, and a classmate has signed up on it.
Day 7
Every product is demoed live and audited against the ten points below, in front of the group. Anything failing gets fixed in the room. Then what it costs to run, what to build next, and how to talk about this in an interview or a sales call.
You leave with: a live URL, a public repository, a passed audit.
Not a syllabus. The list of sentences you can say out loud afterwards and back up by opening your own product.
Ten checks. Every one of them is something you can test yourself. This is what I audit on day seven, and it is what the guarantee is measured against.
Not promised, and never will be: users, revenue, funding, a job, app-store approval, or something that holds up at ten thousand people at once. The promise is a working, deployed product that passes those ten checks, and a design you can defend in a room.
The guarantee
Do the seven days and end without a live product that passes the ten checks, and you pick one of two things. A full refund of your fee. Or I keep working with you, at no extra cost, until it is live and it passes. Your choice, not mine.
All I ask in return is the part that is in your hands:
To claim, email me within seven days of the last session. There is no form and there is no argument. Refunds go back to the original payment method within five to seven working days. Full terms live on the refund policy.
Your own URL, your own accounts, your own repository. Nothing runs on my infrastructure and nothing gets switched off when the course ends.
Two documents in your own words that explain what you built and why it is shaped that way. These are what you show an interviewer or a client, not the code.
Your own product explained file by file, recorded on day seven, so the understanding does not evaporate the week after.
How to take the next idea from a sentence to a live URL on your own. The seven days are a worked example, not a one-off.
The first twelve products built at the founding price go up here, each one the day it goes live, with the builder’s name on it. Nothing is on this wall yet, because nobody has shipped yet.
Founder, Products Decoded
I am a system designer and a full-stack developer before I am anything else. Eight years as a founder, more than a hundred products built for clients from startups to government departments, and platforms I architected that scaled and shipped to users around the world. The system design I teach on day two is the one I have drawn on a whiteboard for a decade, not something I read about.
Then ten years in product across fintech, insurance and embedded finance, most recently as Senior Principal Product Manager at MoneyLion, where I ran a business unit to $9.6M in annual revenue and shipped embedded insurance inside Microsoft Copilot.
I still build. Jobtune and Astrika are both mine, both live, both taking real payments from real people, and both have taught me things at two in the morning that no course covers. The bot-flood story on day six is one of them. I teach this the way I run my own week.
Founding price
₹10,000
Up to 12 people in a run, and it runs for one. Priced this way for the first twelve people only, because what I want out of them is a wall of live products I can point at. After that it goes up.
Not included: Claude Pro at roughly ₹2,000 to ₹2,400 for the month you need it, and a domain at about ₹1,000 a year if you want your own name on it. Hosting and the database stay on free tiers at this size.
Take your seatEven if it is just you
It still runs
One sign-up means a solo run at the same price, one to one, same seven days and same guarantee. I am not cancelling on somebody who cleared their week because eleven strangers did not turn up.
Bring one person
₹18,000 for two
₹9,000 each instead of ₹10,000, paid once, by whichever of you gets there first. Building next to somebody you know is the single biggest thing that stops people quitting on day four, so I would rather pay for it than advertise for it.
Yes. You will not write code. You decide what gets built, you read what Claude Code produces, and you approve or reject it. In my August masterclass most of the room had never opened a terminal, and seven of the eight who filled in the form left with something running. The people who struggle here are not the non-coders. They are the ones who skip the daily task.
You still finish with your product live. Understanding is the goal of the teaching, and shipping is the guarantee. Those are two different promises on purpose. The roadmap on day one, the design on day two and the daily tasks are built to carry you to a live URL whether or not every file has clicked by Sunday. The recorded walkthrough is there for the part that lands later.
Then it runs for one person, at the same price, one to one. I am not going to cancel on somebody who cleared their week because eleven strangers did not turn up. A solo run gets the same seven days, the same tasks and the same guarantee, and you get every minute of the review time instead of a twelfth of it.
Yes. Two seats cost ₹18,000 instead of ₹20,000, which is ₹9,000 each. Put their email in the form and you pay for both seats in one go, so there is no chasing the other half later. Sort the money out between yourselves however you like. It takes two of the 12 seats.
Whenever suits you. There is no batch calendar and nothing to wait for. Enrol, and I am in touch inside 24 hours to agree your seven days, which for most people starts within a week. It runs for a single person, so your dates are a conversation rather than a queue. If you want to start on a Monday three weeks out because of work, say so and that is what we do.
Then do not pay on this page. I run this on campus for colleges and departments, with one invoice for the group and a rate per head rather than the individual price. Email debashis.deb94@gmail.com or message +91 80939 62212 and I will send the group rate and how the seven days fit around a college timetable.
No. A bootcamp spends three to six months making you employable as a developer, and mostly starts with syntax. This is seven days aimed at one outcome: your product, live. You are learning to specify, design, direct and review software rather than to type it. If what you want is a developer job, do a bootcamp or a degree. If what you want is the thing built, this is faster and about a fiftieth of the price.
One stack for the whole group, a mainstream JavaScript one, chosen because I can debug anybody in the room at nine at night without thinking. You get the exact list in the day-zero setup clinic and we install it together. You are not picking, and that is on purpose: teaching one stack seven times is what makes seven days enough.
No, and nobody honest will promise you that. What it gives you is a live link an interviewer can open, a repository with your name on it, and the ability to explain the data model and the trade-offs behind it. For a recent graduate that is a better twenty minutes of an interview than any certificate. The job is still yours to win.
Yes, as long as the timing works for you. Sessions run in the evening India time, which is late afternoon in Europe and the middle of the night in North America. Every session is recorded, but the review loop works far better if you are live, so think hard before joining from a timezone that puts you at 3am.
Claude Pro, which is roughly ₹2,000 to ₹2,400 a month, and one month covers the course. Hosting and the database sit on free tiers that cost nothing at this size. A domain in your own name is about ₹1,000 a year and is optional.
Almost everyone arrives with one that is. We cut it together on day zero, in writing, down to something that can genuinely be live by day seven. If it cannot be cut that far, I will tell you before you pay rather than after.
Build whatever you like, but not on your employer’s real data. Sample data only. A student project is the wrong place for your company’s records, and your security team would agree.
Two hours in the evening, India time, seven days running. Every session is recorded. Missing the live call is fine. Watch the recording and submit the task before the next session, because the task is what carries the guarantee.
If what you want is a certificate, no. If what you want is a link an interviewer can open on their own phone, plus the ability to explain the data model and the trade-offs behind it, that is exactly what this produces, and it is not what a college project looks like.
It is yours. Your repository, your hosting account, your domain, your database. I have no access to any of it once the week ends unless you ask me to look at something.
Free, and it takes a minute
Most ideas can, once the right two thirds are cut away. Some genuinely cannot, and I would rather tell you that now than take ₹10,000 and disappoint you on day seven.
Send me one line about what you want to build and I will reply on WhatsApp with a straight answer: what it would look like cut down to seven days, what gets left out, and whether it is worth your time. No charge, and no obligation to book anything.
Got it.
I read these myself and reply within a day, usually sooner. If your idea does not fit seven days, I will say so and tell you what would.
There is no batch to wait for. Pay, and I am in touch inside 24 hours to fix your seven days around your week. Two hours each evening, India time. Most people start within a week of paying.
You are in.
Payment received. Your setup-clinic invite and the scope questionnaire are on their way to the email you used. If anything looks wrong, reply to that email and I will fix it.
Paying another way?
Colleges, departments and groups: I run this on campus and take payment offline, one invoice for the group. Same seven days, same guarantee, priced per head. Email debashis.deb94@gmail.com or message +91 80939 62212 and I will send the group rate. If a college is arranging it for you, do not pay here.
Payments are handled by Razorpay. Card, UPI, net banking and wallets. The payment gateway adds its own processing fee on top at the checkout screen, so the final amount depends on how you pay and UPI is usually the cheapest. Founding price, GST as applicable at checkout. Naming somebody buys both seats in one payment, ₹18,000 for the two, and I email them their own joining details. A company invoice is available if your employer is paying. Cancellation windows and the outcome guarantee are both set out in the refund policy.