Training
Certification Leadership Frameworks Agentic for Business
Community Keynotes Retreat Blog Book A Consultation
Protocol 02 of 18 · Track, Mindset · How we think

The stack, Claude plus GitHub plus Vercel plus Supabase

Four tools, one operating model. Claude is the AI partner, GitHub is version control, Vercel is deployment, Supabase is the database. Master these four and you can build almost anything.

Protocol 01 CMS is dead, AI is the CMS All 18 Protocol 03 Agents, the folder is the agent
Why this matters

The pain it
solves

Protocol 01 named what is gone, the CMS. This protocol names what replaces it. Four tools, one operating model. If you can describe a thing, this stack can build, ship, and host it.

This is the stack we use ourselves for every project. It is not the only stack. It is the one we have proven, can support, and can teach in 48 hours in the room.

The teaching

What this
actually is

The four tools, one sentence each

Every Infinite Leverage project rides on the same four-tool spine. Each one has a single, clear job. If you can keep these four jobs straight in your head, you can debug any problem to the right tool in under a minute.

  • Claude, the AI
    The model that does the thinking. Claude Code runs in your terminal and edits files; Claude Desktop runs in a window and plans with you. Same Claude, two surfaces. You talk to it in plain English; it writes code, drafts copy, reasons over your data.
  • GitHub, the code
    A time machine for your files. Every change is a commit, every commit is a snapshot you can roll back to. The shared workspace where humans and agents make changes without overwriting each other.
  • Vercel, the live site
    Takes the code in GitHub and serves it on a URL the world can hit. Push to GitHub, Vercel builds and deploys in under a minute. Custom domains, preview URLs per branch, free SSL.
  • Supabase, the data
    When your product needs to remember something (a lead, an order, a user setting), it remembers it here. Postgres in a friendly skin. You only need it the moment something has to outlive a page refresh.

How a single change moves through the stack

The whole point of this stack is that one sentence in Claude can land on your live URL in under two minutes. Here is the path it takes.

You type a prompt in Claude Code, in the project folder. Claude edits the right file. You glance at the diff, accept it. Claude commits to GitHub. GitHub fires a webhook to Vercel. Vercel builds and deploys to your domain. If the change reads or writes data, Supabase is the layer that holds it across requests. End to end, under two minutes for a small change.

Anything that takes longer is a tooling problem, not how websites work. Memorise that sentence. It is the rule that stops you from accepting friction as normal.

Which tool to blame when something breaks

The single biggest skill upgrade in this protocol is knowing which tab to open when something goes wrong. Each tool has its own failure shape.

  • Code looks wrong, button is in the wrong place, copy says something stupid
    Claude. Open Claude Code, describe what you want, accept the diff.
  • Wait, what changed yesterday? Who edited this?
    GitHub. Open the repo, look at the commit history, read the diff.
  • It works on my laptop but breaks in production
    Vercel. 80% of the time it is a missing environment variable. Open the project settings, compare with your local .env.local.
  • The form submitted but the lead is missing
    Supabase. Open the table editor, check if the row landed. Then check the API logs.

Why this stack, not another one

Plenty of stacks could do this. We chose these four because all four are American, audited (SOC 2 Type II across the stack), and run for the biggest companies in the world. When you build on this stack, you are on the same rails Microsoft, Adobe, OpenAI, and Nike use.

You can run a real business on free or near-free tiers. Vercel hosts your site for free. Supabase gives you a real Postgres database for free up to 500MB. GitHub is free for public repos and cheap for private. Claude is the only one with meaningful cost, and that is the one that does the most work.

Try it yourself 30 minutes

Ship Hello World end-to-end in 30 minutes

Open four browser tabs. You are going to create accounts for all four tools, connect them, and watch a single git push deploy your name to a public URL. No prior coding required.

  1. Step 01
    Create your Claude account and install Claude Code

    Sign up at claude.ai. Then follow the Claude Code install guide. On a Mac, it is one terminal command. You should end with `claude --version` printing a number.

    Claude Code install
  2. Step 02
    Create your GitHub account and make a new repo

    Sign up at github.com. Click the green New button. Name it il-hello-world. Public is fine. Add a README so the repo is not empty. Clone it to your machine.

    GitHub Hello World
  3. Step 03
    Create your Vercel account, import the repo

    Sign up at vercel.com with your GitHub. Click Add New, then Project, then pick your il-hello-world repo. Vercel will offer to deploy. Click Deploy. It will fail because the repo is empty. That is fine, the connection is made.

    Vercel quickstart
  4. Step 04
    Ask Claude Code to build a Next.js Hello World

    In your terminal, cd into the il-hello-world folder and run `claude`. Tell it: "Set this up as a Next.js project with a Hello World homepage that says Hello, my name is [your name]." Accept the changes it proposes. It will run npm install and create the files.

  5. Step 05
    Git push and watch it deploy

    Tell Claude: "Commit everything and push to main." Claude will run the git commands. Switch to your Vercel tab and watch the build go green. Click the URL it gives you. Your name is now on the public internet.

  6. Step 06
    Make a change by prompt

    In Claude Code: "Add a subtitle under my name that says Day 1 of Infinite Leverage. Commit and push." Watch Vercel rebuild in under a minute. Refresh your live URL. The subtitle is there.

Outcome

Four accounts created and connected. A live URL with your name on it. A working instinct for which tool did what. You did not type a single line of code yourself, you described what you wanted and the stack did the rest.

Official resources

Straight from
the source

What you walk out with

By the end of this
protocol

At the retreat

You learn it by
doing it

You open all four tabs at once and watch a one-sentence prompt move through Claude, GitHub, Vercel, and Supabase end-to-end on your own Hello World site.

Connects to

Other protocols this
compounds with

← Previous, Protocol 01 Next, Protocol 03 →