Choose your stack (the one I use and why)

After building 13 real products in a little over a year — as a surgeon, not a software engineer — this is the stack I settled on. I'm not giving it to you as 'the only good one,' because it isn't. I'm giving it to you because it's fast, powerful, and lets me build ALONE products that compete with those made by full teams. And above all, I'm sharing the reasoning behind each piece, because that reasoning is what you'll be able to apply even if a new tool comes out tomorrow.

Think of this stack as a team you hired, where each member is a world-class specialist who comes pre-trained. You're the director. Let's meet the team.

Next.js — frontend and backend in one

Next.js is a React framework that combines the frontend and backend in a single project. They used to be two separate worlds you had to carefully glue together; with Next.js, you write the user-facing interface AND the server logic without jumping between projects. It's fast, modern, and — key point — AI knows it inside out, so it writes Next.js code with virtually no errors. It's the foundation everything else stands on.

Firebase — backend, data, and auth, ready to go

Firebase is from Google and gives me, without setting up a single server, the three pieces every product needs: database (Firestore), user login (Auth), and file storage (Storage). It's like having the kitchen, pantry, and waitstaff already hired and running. It starts for free, and as your product grows, it scales on its own so you only pay for what you use. For a solo builder, this is pure speed: you skip weeks of plumbing.

Vertex AI — the intelligence

Vertex AI is gateway access to Google's AI models (Gemini for text, Imagen for images, Veo for video). It's what lets me embed REAL AI into my products: generating summaries, creating images, analyzing text. It's the 'brain' that allows my apps to do things that seemed like science fiction five years ago. If your product has an AI feature, this is where it lives.

Stripe — collecting payments

Stripe handles payments and subscriptions. It's the piece that turns a project into a BUSINESS: it processes cards, manages monthly plans, and handles money security (which you never want to touch manually). We'll cover it in depth later, but it's part of the stack from day one because charging money is part of building something real.

Worked example: Momentum, piece by piece

To keep this from being abstract, let's map the stack onto a concrete product: Momentum, a personal journal where you write about your day and an AI gives you an insight back (the exact project you'll build in this course). Here's what each piece does:

• Next.js → the screen where you write your entry and the landing page that explains the product. Everything you see and touch.
• Firebase Auth → your account: you sign up, log in, and the app knows those entries belong to YOU.
• Firestore (Firebase) → saves each of your journal entries, tied to your user account, forever.
• Vertex AI → takes your daily entry and returns a summary or advice. The magic of the product.
• Stripe → when you want the Pro plan (more history, more AI), this handles charging the subscription.
• Vercel → makes Momentum live on the internet under your domain, accessible to anyone.

An entire product, complete with users, data, AI, and payments, built by a single person — because each piece of the stack solved the hard part, and you just connected them and provided direction. That is exactly what you are going to do.

Why I DON'T switch stacks every week

A builder who masters one stack is ten times more productive than one who jumps from tool to tool. When you know your stack inside out, you stop fighting the tool and focus on the product. New things come out all the time, and I look at them with curiosity — but I only swap out a piece when something TRULY limits me, not because of hype. Consistency in your stack is a quiet, massive advantage.

Key takeaways

• My stack: Next.js (front+back) + Firebase (data, auth, storage) + Vertex AI (intelligence) + Stripe (payments) + Vercel (hosting).
• Each piece is a specialist handling the heavy lifting for you; you connect them and direct.
• With this stack, a single person can build full-fledged products with users, AI, and payments — like Momentum.
• Don't just copy the stack: adopt the criteria → maximum out-of-the-box utility + strong AI knowledge + painless scaling.
• Avoid stack paralysis and don't switch due to trends. Master one; consistency makes you 10x more productive.

The best stack isn't the newest or the most talked-about. It's the one you master enough to forget about it and focus entirely on your product.