From Zero to 20+ Production Apps in 12 Months

The Premise

You don't need to learn to code first and build later. You build from Day 1 and learn by doing. AI coding tools (Claude Code) are the unlock — they let you build real things immediately while absorbing technical concepts through repetition, not study.

What you need to start:

• A computer (Mac or PC)
• A real problem you want to solve (not a tutorial project)
• Willingness to be confused and keep going

The full list of accounts to create and software to install is in the Beginner's Setup Guide, in two paths: laptop only (start here) and with a VPS (once you want agents running 24/7).

What you don't need:

• Programming experience
• A CS degree
• Money for a dev team

Mindset

You're not “learning to code.” You're building something real with an AI partner. The AI writes most of the code. Your job is to know what you want, describe it clearly, and learn to recognize when things are working.

Tools to Set Up

Setup Steps

1. 1Install Ghostty(ghostty.org) — this is your workspace. A fast, GPU-accelerated terminal that makes everything feel smooth and professional. Open it and leave it open. This is where you'll live.
2. 2Install Node.js from nodejs.org
3. 3Sign up for Claude Pro ($20/mo at claude.ai) — this powers the AI that writes your code.
4. 4Install Claude Code in Ghostty: npm install -g @anthropic-ai/claude-code
5. 5Type claudein Ghostty. That's it. You now have an AI coding partner. Tell it what you want to build in plain English and watch it work.
6. 6Create a GitHub account (github.com) — where your code lives
7. 7Create a Vercel account (vercel.com, connect to GitHub) — deploys your site to the internet

Week 1: Your First Website

What you'll build: A simple website for something real — your business, a landing page, a personal site.

Tools introduced:

• Terminal basics (cd, ls, running commands)
• npx create-next-app (scaffolds a project)
• Claude Code (describe what you want, it builds it)
• Git basics (save your work: git add, git commit, git push)

Daily progression:

What you'll learn without trying:

• How a project is structured (folders, files)
• What JSX looks like (HTML-like code in JavaScript)
• How deployment works (push code → site updates)
• The feedback loop: describe → build → see → iterate

Week 2: Make It Interactive

What you'll add: A working contact form, dynamic content, basic styling.

Tools introduced:

• Tailwind CSS (styling with utility classes)
• React components (reusable pieces of UI)
• Environment variables (storing secrets safely)
• Vercel environment settings

Key exercises:

• Add a contact form that actually sends emails (use Resend or SendGrid)
• Add a page with dynamic content (a list of services, portfolio items, etc.)
• Make it responsive (looks good on mobile)
• Deploy every change — get comfortable with the push → deploy cycle

Week 3: Add a Database

What you'll build: Turn your site into an app that stores and retrieves data.

Tools introduced:

What to do:

1. 1Create a Supabase project (supabase.com)
2. 2Tell Claude: “Add a Supabase database to store [contacts/products/entries/whatever your app needs]”
3. 3Build a page that displays data from the database
4. 4Build a form that saves data to the database
5. 5Deploy. You now have a real app.

Concepts you'll absorb:

• Tables, rows, columns (database basics)
• API calls (your app talking to your database)
• CRUD operations (Create, Read, Update, Delete)
• Environment variables for database credentials

Week 4: Add User Accounts

Tools introduced:

• Supabase Auth (login/signup)
• Protected routes (pages only logged-in users can see)
• Row Level Security (users can only see their own data)

What to do:

1. 1Tell Claude: “Add authentication with Supabase Auth. Users should be able to sign up, log in, and only see their own data.”
2. 2Add a login page, signup page, and a dashboard
3. 3Protect your main pages behind auth
4. 4Deploy. You now have a multi-user app.

Week 5: Polish and Ship

What to focus on:

• Error handling (what happens when things go wrong)
• Loading states (spinners, skeletons)
• Mobile responsiveness
• A real favicon and metadata (not the default Next.js icon)

Tools introduced:

• PostHog (analytics — see who's using your app) — Free tier
• Basic SEO (page titles, descriptions, Open Graph images)

Week 6: Get Feedback, Iterate

• Share your app with 3-5 real people
• Watch them use it (or review PostHog recordings)
• Fix what's broken, add what's missing
• Practice the cycle: feedback → Claude Code → deploy → repeat

Weeks 7-8: React Native with Expo

Tools introduced:

What to do:

1. 1npx create-expo-app my-app
2. 2Tell Claude: “Build a mobile version of [your web app] using Expo and React Native. Connect it to the same Supabase database.”
3. 3Run it on your phone with Expo Go
4. 4Iterate on the mobile UX (navigation, gestures, platform conventions)

Key concepts:

• React Native components (View, Text, ScrollView, TouchableOpacity)
• Navigation (tabs, stacks)
• Shared backend — your mobile app and web app use the same database

Week 9: TestFlight (iOS)

Tools introduced:

• Apple Developer Account ($99/year)
• Fastlane (automates iOS builds)
• TestFlight (Apple's beta testing platform)

What to do:

1. 1Set up an Apple Developer account
2. 2Tell Claude: “Set up Fastlane for iOS builds with automatic TestFlight upload”
3. 3Run your first build. Send the TestFlight link to testers.

Week 10: Ship to App Store

• Screenshots, app description, privacy policy
• Submit for review
• You now have an app in the App Store.

By now you have a pattern: describe → build → deploy. Start applying it to every problem you see.

Weeks 11-12: Second and Third Apps

Build 2-3 more apps using the same stack. Each one gets faster because:

• You know the tools
• You can copy patterns from your first app
• Claude Code has context on how you like things built

Speed benchmarks (what's realistic):

Weeks 13-14: Shared Services

When you have 3+ apps, you'll notice duplication. Time to centralize.

Tools introduced:

What to build:

• A shared API that handles forms, email, newsletters for all your sites
• Reusable React components (form renderer, newsletter signup)
• API key authentication so each site is isolated

Weeks 15-16: Custom Domains and Professional Infrastructure

Tools introduced:

• GoDaddy/Cloudflare DNS management
• Custom domains on Vercel
• SendGrid for transactional email
• Proper secret management (1Password CLI)

Weeks 17-18: VPS and Background Jobs

Tools introduced:

What to build:

• Set up a VPS with your development tools
• Write scripts that run on a schedule (data sync, content updates, health checks)
• Move background processing off Vercel and onto your server

Weeks 19-20: AI Agents

What you'll build: Autonomous agents that do work without you.

Examples from the real journey:

• Content writer agent (generates SEO blog posts on schedule)
• Data enrichment agent (scrapes and updates business listings)
• Email task agent (receives emails, spawns Claude Code workers to execute tasks)
• Sync agents (keep Google Contacts, analytics, etc. in sync)

Pattern:

1. 1Write a script that does one thing well
2. 2Wrap it in a cron job
3. 3Add error handling and logging
4. 4Let it run

Weeks 21-22: Monitoring and Self-Healing

Tools introduced:

• Agent monitoring dashboard (track all your automated jobs)
• Health checks (detect when agents fail or go stale)
• Self-healing agents (automatically restart or fix failed jobs)
• Exception-based management (dashboard shows problems, not status reports)

What you'll build:

• A dashboard that shows the health of all your agents
• Alerts when something breaks (email/SMS)
• Agents that monitor other agents

What Mastery Looks Like

At this point, you're not “using AI to code.” You're running a software operation:

• 10+ production apps serving real users
• 30+ cron jobs running autonomously
• Shared infrastructure (API platform, component library, monitoring)
• Mobile apps in the App Store
• Custom email systems (inbound and outbound)
• OAuth integrations with Google, Apple, Spotify, etc.
• Analytics tracking user behavior across all products
• Self-healing systems that fix themselves

The Full Tech Stack You'll Know

Claude Code stays the main driver. But every major lab now ships a coding agent that runs in the terminal, and they're good at different things. Install all of them on the VPS and use them side by side.

What changes:

• One model writes the code, a different model reviews it. They catch different bugs.
• API keys for Anthropic, OpenAI, and Google so your own apps and agents can call models directly
• Upgrade from Claude Pro to Claude Max once you run Claude Code all day. The $20 plan runs out.

MCP Connectors

MCP (Model Context Protocol) is how Claude plugs into other services. Connect one once and Claude can read and act on it in plain English: “What's on my calendar Thursday?”, “Draft a reply to that email”, “Why did the last Vercel deploy fail?”

APIs for Everything Else

• GoDaddy API: Claude creates DNS records whenever a new site goes live
• Google Workspace Admin API: create email groups and users from the terminal
• Instagram (Meta) API: agents publish posts
• Google Analytics + Search Console + Ahrefs: agents read traffic and SEO data
• Every key goes into 1Password first. Nothing is hardcoded.

Give Your AI a Memory

• CLAUDE.md files: the rules of the house. Deploy steps, safety rules, where credentials live. Claude reads them at the start of every session.
• Persistent memory: decisions, preferences, and lessons learned carry over between sessions. You stop repeating yourself.
• Plugins and skills: packaged workflows (deploy, review, DNS, spawn a worker) that Claude runs the same way every time.

Agents running today:

• Inbox drafter: reads incoming email and drafts replies for review. It never sends on its own.
• Social agent: writes, renders, and publishes Instagram posts for three brands after a human approves them
• Content engine: SEO articles, with Google Analytics and Search Console reporting
• Tour manager: syncs show dates to the website, manages proposals and contacts
• Newsletter: an in-house send system on SendGrid instead of a paid platform
• Finance: drafts bookkeeping entries that a human posts
• Ops: health checks, a self-healer, a crontab auditor, a daily report email

Working in parallel:

• Spawn several Claude Code workers in tmux, each on its own task, and check back later
• Subagents: one session fans a big job out to several agents and merges the results
• Work from anywhere: SSH from an iPhone over Tailscale, or email the VPS a task

My Actual Stack (What I Use Every Day)

These are the specific tools and services I use. Not theoretical recommendations — this is what's running right now across 20+ live apps and sites and 70 agents. Updated September 2026.

AI & Development

Infrastructure & Hosting

Frameworks & Languages

DevOps & Automation

Services & APIs

Monitoring & Ops

Key Principles

The Numbers (Real Results)