Never built software before? Start here.

You can do this. Here's exactly how it works.

This page is for you if the idea of owning a software platform excites you — and the idea of building one scares you. Ten minutes from now you'll know what you need, what the tools actually do, and what your first day looks like. No jargon until the very end, and even then we'll translate it.

01 · What you need

What you need before you begin.

Less than you think. There's nothing to buy beyond the Build Pack, and every account you'll create has a free tier that's plenty to start.

A computer

Mac or Windows, nothing fancy. If it runs a web browser, it can build a platform.

Three free accounts — connected in minutes

GitHub stores your code. Vercel publishes your platform. Neon holds your data. All free to start. You connect them with one click each inside the portal — no setup guides, no terminal commands, no 20-minute account configuration.

About 5 minutes to live

Connect GitHub, Vercel, and Neon — one click each. Name your platform. Press Deploy. Your live URL, your code repo, and your database are ready before you've finished your coffee. Then Claude Code takes it from there.

You will also use the terminal — the plain window where you type commands instead of clicking. It looks intimidating and isn't: every command you'll ever need is written out for you, ready to copy and paste. Nobody expects you to memorize anything.

That's genuinely the complete list. No dev experience. No technical background. No secret prerequisite hiding at the bottom. People who've run businesses, managed clients, sold services — people exactly like you — have built working platforms from this starting point.

02 · The tool

What Claude Code is, in one paragraph.

Claude Code is an AI developer that lives in your terminal. You type what you want in plain English; it writes the code, creates the files, sets up the database, and tells you what it did. Think of it as a developer who can read a 200-page blueprint and build everything in it, step by step, asking you to review before moving on. The Build Pack is that blueprint. Claude Code reads it and builds your platform — pausing after each stage so you stay in control.

Want the longer version — what it costs, what a session looks like on screen? Read “What is Claude Code?” →

03 · First session

Your first build session, step by step.

  1. Step 01

    You connect and deploy

    Inside the portal: connect GitHub, Vercel, and Neon — one click each. Name your platform. Press Deploy. Your live site is up in minutes. No ZIP file. No folder to unzip. No files to move around.

  2. Step 02

    You open the repo in Claude Code

    Your private GitHub repo was created automatically. Clone it, open it in Claude Code. One command to install Claude Code if you haven't already — our walkthrough covers it.

  3. Step 03

    You give it one instruction

    Something like: “Read the project brief and build this platform stage by stage. Pause after each stage so I can review.” That's genuinely the whole prompt.

  4. Step 04

    It builds. You watch and approve.

    The agent works through the build plan — login system first, then the database, then the screens. After each stage it stops and tells you what it did. You say “continue” when you're happy.

  5. This is the moment most people describe as the turning point.

    Not when it's done. When it's working for the first time — login screen, database, real pages — and you realize you didn't write a line of it. That's when “I wonder if I could do this” becomes “I'm doing this.”

  6. Step 05

    You see your platform running

    By the end of the first session there's a working platform on your own computer, at an address only you can see. That moment — seeing it real — is when most people stop being scared of this.

What the first 24 hours look like

Your platform is live the moment you press Deploy — that happens in the first five minutes. Claude Code then builds on top of the running platform, stage by stage. Most owners complete the full build in one to three sessions. From first click to fully built: one to three days. See the full day-by-day →

04 · The journey

What comes after your first build.

01

You'll understand the stack.

Not because you studied it — because you watched it get built in front of you, stage by stage, and now you've seen what a production Next.js platform actually looks like from the inside.

02

Your second build is faster.

The first one is orientation. The second one is execution. Most people cut their build time in half on the second platform — same process, less hesitation.

03

You'll see the opportunities differently.

Once you know you can build a B2B platform in a day, every industry problem you've ever noticed looks different. You stop wondering “who should build that?” and start thinking “I could build that.”

Your first platform will surprise you.

Not because it's easy — because it's real. Real login screen, real database, real pages you decided on. The distance between “I have an idea” and “I own a working platform” used to be a dev team and six months. Now it's a folder, a free afternoon, and the willingness to follow a checklist.

You're more ready than you think.

Connect GitHub, Vercel & Neon → Name it → Deploy. Done.