What You Will Actually Ship

# What You Will Actually Ship Let me tell you what "shipped" means in this course, because most Claude Code tutorials lie about it. They show you a demo that runs locally. They walk you through generating some components. They say "and now you know how to use Claude Code!" and end there. You close the tab, open your terminal, stare at a blank directory, and wonder what you actually learned. This course ends differently. By the end, you will have a deployed, multi-tenant web app with: - Real auth (not a hardcoded bypass) - A payments flow (Stripe, test mode, real webhook handling) - Error monitoring (Sentry, so crashes go somewhere besides into the void) - A live URL you can send to a real user - Multi-tenancy — the structural decision that most solo builders skip and spend months paying for later That's the bar. Not localhost. Not "it mostly works on my machine." Deployed. ## The thing you're going to build Through this course, you'll build a **workspace-scoped link shortener with analytics**. That description probably sounds underwhelming, so let me tell you why it's the right choice. It's small enough to finish in 8 hours. It's not trivial — it has auth, a data model, a real API, and a frontend. It demonstrates multi-tenancy clearly (each workspace has its own links). It has payments you can actually reason about (one plan, $9/month, unlocks more links). And it's useful enough that you might actually keep running it. Here's what it does: - You sign up, create a workspace - You create short links (`yourapp.com/go/abc123`) - Each link tracks clicks over time (basic analytics: click count, last clicked) - You invite teammates to your workspace - The free plan gives you 10 links; paid gives you unlimited You'll build this with Claude Code doing most of the scaffolding — but you'll direct it. You're the architect. Claude Code is the contractor. By the time you deploy, you'll have built it correctly: every table in your database scoped by workspace, Row Level Security policies so users can't access each other's data, a checkout flow that actually works, and Sentry watching for crashes in production. ## Why "ship" means deployed with payments and monitoring A lot of people draw the finish line at "it works in my browser." That's fine for learning. It's not fine for building something real. Here's what you learn by taking it all the way to production: **Auth in production is different from auth in development.** OAuth flows behave differently with real redirect URLs. Session handling has edge cases you don't see locally. The errors you get in production are real errors. **Payments teach you about business logic.** When does a user get access? What happens when a charge fails? When they cancel? When they refund? Wiring this correctly forces you to think about your app as a product, not a demo. **Monitoring changes how you work.** Once you have Sentry set up, you stop guessing what's broken and start getting told. That feedback loop is one of the biggest productivity differences between junior and senior engineers. **Multi-tenancy is not a feature, it's an architecture decision.** Add it on day one or spend a month retrofitting it later. This course adds it on day one. ## What Claude Code actually does for you here Claude Code is a coding assistant that runs in your terminal. It reads your files, writes code, runs commands, and reasons about your project. It's not a code snippet generator — it's a collaborator that can hold the full context of what you're building. In this course, you'll use Claude Code to: - Scaffold the project structure - Write database migrations - Generate API routes and React components - Debug errors in real time - Wire together integrations (Stripe, Sentry) from documentation What you'll do is direct it. Write the briefs. Review the output. Catch mistakes. Make architectural decisions. Claude Code is fast at generating working code — but it generates the code you describe, so the quality of your direction determines the quality of the output. This is the skill this course teaches: not how to type less, but how to think clearly enough about what you're building that Claude Code can build it accurately. ## How this course is structured Twelve lessons. Roughly 40 minutes each. The first four lessons cover setup: Claude Code, your CLAUDE.md file, skills, and MCP servers. These aren't busywork — they're the foundation that determines how well Claude Code performs for the rest of the course. Lessons 5 through 11 are the build. You'll scaffold the project, wire in multi-tenancy, add payments, add monitoring, and ship. Lesson 12 is what comes after: the daily loop that keeps a product moving after launch. Watchtower — Braintied's session observer — runs in the background during setup lessons and automatically credits you when it detects you've completed the step. No manual signal required for most lessons. It watches your git commits, MCP setup, and deployments. ## One thing before we start If you've been building side projects that never make it past localhost, this course is for you. The gap between "it works locally" and "it's deployed and real people can use it" is mostly psychological — it feels like there's a mountain of complexity between here and there. There isn't. It's maybe five hours of focused work, if you know what to do. After this course, you'll know what to do. Let's build something.