From a website to a productplanned
Now other people's data is your problem.
This is the rung where it stops being your website and starts being their account. Logins, data that belongs to one person and nobody else, money that arrives every month whether you did anything or not, and all the failure modes that come with it. It's the biggest jump on the ladder. Very little of it is difficult and almost all of it has to be right.
You'll need a paid Claude plan, which is $20 a month, and a machine you can install things on. Everything here builds on a working site that already talks to outside services.
What It Covers
The jump from a site to a product.
Where the mistakes stop being embarrassing and start being other people's problem.
Auth, and why it comes first
Signing up, signing in, forgetting a password, and proving you're who you say on the next request. Everything else in this course sits on top of this, which is why it goes first. Bolting it on afterwards is how people end up with a login they don't understand.
Data that belongs to somebody
The moment a row has an owner, every single query needs to know who is asking. This is where the missing check quietly shows one customer another customer's information, and it's the most common serious bug in software built this way.
Keeping customers apart
Tenants, and what it means for two companies to use the same software without ever seeing each other. Where the boundary lives, how it gets enforced, and how to test that it holds.
Subscriptions
Recurring money is a different animal from a one-off payment. Plans, upgrades, downgrades, proration, and the fact that you now have a customer who expects the thing to keep working.
When the card fails
Cards expire, banks decline, and people forget. What happens to their account, how many times you ask, and how to handle it without losing the customer or giving software away for free.
Roles and permissions
Not everyone inside a customer's account should be able to do everything. Owners, members, who can invite, who can see the billing, and how to write this once so it holds everywhere.
Changing the database under a live product
Migrations when there are real people using the thing. How to add a column without downtime, how to roll one back, and why the change that worked locally is the one that bites you.
Finding out before your customer does
Error tracking and the two or three alerts worth being woken up for. The gap between something breaking and somebody emailing you about it is where most of the damage happens.
Backups, and restoring one
Somebody will delete the thing they needed. A backup you have never restored is a rumour, so this covers taking them, testing them, and what you can actually promise a customer about getting their data back.
Support, refunds and the human parts
Somebody will be charged twice. Somebody will delete something they needed. The tooling and habits that let you fix it in five minutes, and the decisions about refunds that are better made before it happens than during.
Know when it opens.
Leave your email and we'll tell you when the first lessons are up. You'll hear from us once, at the point where there's actually something to watch.
Everyone on the list pays the founding price of $149 a course. It opens at $199. Nothing to pay now, and no date attached to any of it.
Would rather we just built it for you? See what that costs.