SnapshotJuly 2026a point-in-time write-up, left as written

Decisions Claude can’t un-commit you from

You can vibe-code your way to a working prototype. You cannot vibe-code your way out of a bad infrastructure decision made in week one.

Most of this course is about how to work with Claude. This chapter is about the small set of choices that sit upstream of that work, where Claude will happily help you ship faster than you can untangle the trade-offs. None of these decisions can be reversed by a regeneration from the spec. They need a minute of human thought before you commit.

This is the short list of questions you want answered before you pick.

Platforms: where does this live?

Decide first: web app, native app, chat interface (a Claude Skill or GPT action), or some mix.

Many products end up multi-platform. Starting on one and adding the others later is almost always easier than starting on all three.

Auth: who does it and how much can you own?

If you’ll serve enterprises eventually, pick an auth provider that can do SAML/SSO from day one; retrofitting it later is painful.

Database hosting: the decision you’re stuck with longest

Migration strategies are almost always hand-rolled. Whatever provider you pick, assume you’ll eventually move off it. Keep schemas portable, avoid vendor-proprietary features where you can, and factor migrations out of your app code.

App-layer hosting

Watch for pricing cliffs: many hosts are cheap until a specific usage threshold, then steep. Understand the pricing curve before committing architecture to a host’s primitives.

I/O services: email, SMS, notifications

The trap here is usually late integration: shipping a product, then adding transactional email at the last minute, then discovering your host doesn’t play well with your email provider.

Observability: see what’s happening

Start simple: Sentry + console logs is fine for most apps under 1,000 users. Upgrade when you actually need the extra signal.

User analytics

The trap: events get over-tracked and under-cleaned. Decide on a tracking plan before wiring anything up, or you’ll drown in noise within a month.

Ads and marketing platforms

Each platform (Meta, Google, TikTok, LinkedIn) has distinct APIs, attribution models, and reporting quirks. Picking one to start is fine. Picking three simultaneously without infrastructure to compare them is a trap.

A pragmatic default stack for small teams

For solo / small-team builders without specific requirements:

All of these have generous free tiers, work well together, and can scale you to small-revenue before you need to revisit.