Course A · Module A4 Build · Lesson 11 of 17
You don't write code. You describe what you want, look at what you get, and steer. That loop — done well — builds real software.
The automations you've built so far connect existing apps. This module is different: you're going to build something that didn't exist — a small custom tool for your specific business. You don't need to write a line of code. Your single win: by the end of this lesson you'll understand the loop that makes that possible, and you'll know the one principle that separates apps people actually use from apps that just sit there looking like a chatbot.
Vibe coding is not a single prompt. It's a tight, repeating loop:
Each loop takes two to five minutes. A working first version usually takes five to eight loops. Depth and polish come later — in Course B. This course's goal is a working tool you can hand to someone.
The single biggest lever on output quality is not your word choice or your tone — it's clarity about what the app does. Before you type anything into the builder, answer these three questions on paper:
You can refine the design through iteration. But if the AI doesn't know the one job, no amount of iteration converges on the right thing. Write the brief first.
Imagine hiring a new assistant and handing them a blank notebook with a pen. "Just, you know — help." Helpful? Not really. Now imagine handing them a form: "When a tenant misses rent, fill in this notice and put it in the out-tray." That they can do immediately.
Your users are the same. A blank text box that says "Ask me anything" is an assistant with a blank notebook. Nobody knows what to type, and nobody gets a result.
The principle: design for results, not conversations. Every screen should have a button that does the thing.
Two tools cover almost everything at this level: Lovable and Bolt. Both let you describe an app and get a working version in your browser within a minute. Both are free to start.
Set realistic expectations. The first build is a quick win — a working prototype in an afternoon. It will look decent, handle the main case, and be something you can show people. What it won't be: production-grade, fully tested, or ready for thousands of users. That depth is what Course B is for. Right now, the goal is a working tool, not a finished product.
Answer before opening — recalling it is what makes it stick.
Describe → Generate → Look → Iterate. The key is that it's a loop — you don't describe once and wait. You look at what you got, decide the next specific change, and go around again.
Write a clear brief first. "HR stuff" is not a one-job brief. Narrow it: who uses it, what one task does it perform, what goes in, what comes out. Until that's clear, no tool can build the right thing.
Users want results, not a text box. A blank chat box puts the burden on the user to know what to ask and how to ask it. A button that does one specific thing delivers value immediately, with no learning curve.
Read this next (primary source)
Best Vibe Coding Tools in 2026 — Lovable — a practical overview of the leading AI app builders, what each is best at, and how the describe-and-iterate loop works in practice. ~12 min. See RESOURCES.md for more.
New words this lesson — vibe coding, build brief — are defined in the course glossary. Keep it open.