Lesson 002Field guide · Build With AI
No-Code vs Code with AI
Choose the right building approach for your idea and skills.
You'll learn
- The three ways to build: spreadsheets, no-code builders, and AI-assisted code
- Why most "app ideas" are really a spreadsheet
- What AI-assisted coding changed — and what it honestly didn't
- A decision guide that matches the approach to your idea, skills, and stakes
01Section
Three ways to build the same idea
You scoped an idea down in the last lesson. Now: how do you actually build it? There are three honest options, and they form a ladder — each rung more flexible than the last, and each demanding more from you.
The mistake most beginners make is starting at the top of the ladder. The skill is starting at the bottom and only climbing when the idea genuinely requires it.
Spreadsheets, forms & templates
Tools you already have. Rows, columns, formulas, and a form on top cover more ideas than anything else on this list.
No-code builders
Assemble an app visually from ready-made pieces — forms, buttons, stored records — without writing code.
AI-assisted code
Describe what you want in plain language; an AI assistant writes actual code you run, test, and refine.
The rule of the ladder
The best approach is the lowest rung that does the job. Simpler means finished sooner, broken less, and easier to fix.
Checkpoint
02Section
Most apps are a spreadsheet in a costume
Say the idea out loud: "I want an app where I enter jobs and it tracks which are paid." Now listen to it. Things entered in rows. A column that flags status. Maybe a total at the bottom. That's a spreadsheet — and it's been one all along.
This isn't settling for less. A spreadsheet is a real tool: it stores data, calculates, sorts, filters, and updates instantly. Add a form in front of it and other-you (or a family member, or a teammate) can feed it without ever seeing the grid.
The quote calculator as a spreadsheet
Sam's lawn-care quote "app": one sheet, three input cells (lawn size, extras, travel distance), one formula, one bold cell showing the price. Built in twenty minutes, used every week. No code, nothing to maintain.
Checkpoint
03Section
No-code builders: the middle rung
Plain-language definition
No-code builder — a tool that lets you assemble working software from ready-made pieces — forms, buttons, lists, stored records — by arranging them visually instead of writing code.
They come in a few categories, whatever the brand names happen to be this year: form builders (collect structured input), automation connectors (when X happens, do Y), app assemblers (turn a data table into a phone-friendly app), and website builders. If your idea is made of standard pieces — a form in, records stored, a notification out — a no-code builder can snap it together fast.
The honest trade-offs: most run on subscriptions, you can only build what the platform's pieces allow, and your tool lives on someone else's product — if it changes pricing or shuts down, your tool changes with it.
When it's the right rung
Standard pieces, arranged your way. The moment you're fighting the builder to do something it wasn't designed for, you've found the ceiling — and the next rung.
Checkpoint
04Section
AI-assisted code: what actually changed
Here's what's genuinely new. You can now describe a tool in plain language — "a page where I paste my week's hours and it totals them and formats my Friday message" — and an AI assistant will write working code for it. The wall that used to stand between having an idea and having software — years of learning syntax — has a door in it now.
And here's what didn't change: you still test it, you still iterate when it's not right, and you still own the result. AI writes plausible code quickly; it does not write guaranteed-correct code. It can misunderstand you, miss cases, or produce something that works on the happy path and breaks on a weird input. The rest of this path — briefs, working habits, testing — exists precisely because of that gap.
Key takeaway
AI removed the typing barrier, not the responsibility. Describing, testing, and owning the tool is still your job — and it's a learnable one.
The payoff for climbing to this rung: full custom logic. Your exact rules, your exact format, no platform ceiling, no subscription. For small personal tools, a single page of AI-written code you keep on your own computer is often the most durable option of all.
Checkpoint
05Section
The decision guide
Three questions, asked in order, sort almost every idea onto the right rung:
Could a spreadsheet do it?: Rows, formulas, a form on top. If yes — stop here. Most ideas end at this step, and that's a win, not a compromise.
Is it made of standard pieces?: Form in, records stored, notification out, viewable on a phone. If yes, a no-code builder assembles it fastest.
Does it need custom logic?: Your specific calculation, your exact formatting rules, a transformation nothing off-the-shelf does — that's AI-assisted code territory.
One question overrides the ladder entirely: the stakes. If the tool touches other people's data, money movement, or anything sent automatically on your behalf, the choice of rung matters less than getting experienced eyes on it before you rely on it.
Pause and think: Take the tool idea you scoped in the last lesson. Which of the three questions stops it — and is that a lower rung than you'd assumed?
Checkpoint
Prompt exercise
Run your idea through the ladder
Copy this prompt into ChatGPT, Claude, Gemini, Copilot, or whichever AI tool you have access to — the website doesn't run AI itself. It walks your specific idea through the decision guide and gives you a recommendation with reasoning you can push back on.
I have an idea for a small personal tool and I want to choose the simplest approach that works. Ask me one question at a time to understand: what the tool takes in and gives out, whether the pieces are standard (forms, stored records, notifications) or custom (my own calculations or formatting rules), my comfort level with spreadsheets and technology, and whether the tool would touch other people's data or money. Then recommend one of: a spreadsheet/form setup, a no-code builder (describe the category, not a brand), or AI-assisted code. Explain your reasoning in plain language, tell me what the runner-up approach would be and why you ruled it out, and be honest about the trade-offs of your recommendation.
Reflection: Did the recommendation land on a lower rung than you expected? Most first ideas do — and the ones that genuinely need code are now buildable too.
Quick check
3 quick questions — no pressure
There's no pass or fail here. Answer them all, and we'll show you the answers either way.