You’ve heard “just describe what you want” and “anyone can build apps now.” What nobody explains: what happens after you type your first prompt.
Canva made this painfully clear. They gave 5,000 employees a full week to explore AI, and most couldn’t figure out how to start. Five thousand smart people, seven days, and the wall wasn’t effort. It was that every tutorial assumes you already know something they never taught.
Not your fault. Most vibe-coding tutorials expect you to know what a terminal is, why Git exists, and where your files even live.
Good news, none of that is required.
Vibe coding works like this: you describe what you want, the AI writes the code, you test it, and you ask for changes in plain language. That’s the whole loop.
This guide walks you through building a real tool this weekend: an expense tracker that runs in your browser, using only free tiers. It took me about 40 minutes including fixing two errors.
Pick one tool and ignore the rest
The biggest beginner trap isn’t technical skill. It’s spending three days comparing tools instead of building.
My default is Lovable for total beginners, because it runs entirely in the browser and shows you a working page after your very first prompt. No terminal, no Git, no Stack Overflow at 2am.
💡 Tip Replit (free Starter plan) and Bolt.new (300K free tokens daily) are fine too. They just expose more knobs, and knobs are what stalled you last time.
| Tool | Free tier | Paid starts at | Beginner fit |
| Lovable | 5 credits/day (~30/month) | ~$25/month (Pro) | Best first pick |
| Replit | Starter plan: free daily agent credits, 1 live project | $25/month (Core) | Good second step |
| Bolt.new | 300K tokens/day, 1M/month | $25/month (Pro) | Fine, more technical |
âš Warning Free tiers reset daily but are small. One full build usually eats most of Lovable’s daily 5 credits. Do your thinking before you start prompting. Wasted prompts are wasted credits.
Three fears, handled
- “I can’t read code, so I can’t check if it’s right.” You don’t need to read it. You need to test it the way a user would: click everything, type weird input, refresh. Broken things announce themselves.
- “It’ll get expensive.” Every tool above has a genuinely usable free tier. My first four builds cost ₹0.
- “I’ll pick the wrong tool.” You won’t, because any of them builds a tracker. Pick Lovable and start.
Your first build: an expense tracker
Why this project? It has one screen, one form, one list, and one number at the bottom. Small enough to finish, real enough to use on Monday.
- Go to lovable.dev and sign in with Google. Click “New project.”
- Type this prompt: “Build a personal expense tracker web page. Fields: amount, category dropdown (food, travel, bills, other), date, and a note. Show all expenses in a list below the form, newest first, with a running total at the top. Clean, simple design.”
- Wait about 60 seconds. You’ll see a working page. Add two fake expenses. Does the total update? Refresh the page. Do they stay?
- If something’s off, don’t re-describe everything. Say exactly what broke: “The total disappears when I refresh. Fix that.”
- Ask for one improvement: “Add a delete button next to each expense.”
That’s it. You built software.
âš Warning Your work lives on their server under your account. Don’t put real financial data in yet. Test data only until you understand how the tool stores and shares projects.
What breaks first time (all three happened to me)
- Vague prompt, mushy output. If you say “make a nice expense app,” you’ll get something generic. Fix: name fields, behavior, and layout explicitly (like the example prompt above).
- One fix breaks another feature. You ask for dark mode; the delete button stops working. Fix: report it immediately and specifically. These tools handle “the X you just added broke Y” well.
- Lost work. You closed the tab assuming autosave. Fix: open your project list and confirm the build is there before closing anything. Takes five seconds.
Choosing your second build
Don’t copy someone else’s idea. Build the thing you do manually every week.
Tracking reimbursements in a spreadsheet. Copying invoice details into email templates. Checking three sites for price drops. If you do it weekly and it follows the same steps, it’s a build candidate.
For inspiration on what these tools can handle, see our roundup of the best AI coding agents ); every tool listed there works with this exact workflow.
When NOT to vibe code
It will not replace a developer for serious software. It will not securely handle payments or other people’s data. It will not survive heavy traffic.
- No production apps taking real money. Payment handling needs review by someone who understands security.
- No storing user data (even emails) without understanding where it lives and who can see it.
- No business-critical anything. If its breaking ruins your week, it needs a professional.
Great for: personal tools, internal team utilities, prototypes that show an idea before you fund it.
Reality check
Your first version will be raw. It will have a bug you didn’t cause and can’t name yet. The design will look generic.
That’s normal. Every builder’s first version looks like that. Including mine.
But here’s the actual math: my tracker took 40 minutes to build and now saves me roughly 30 minutes a week. Every project after that gets faster, because the loop (describe, test, request changes) is a skill that transfers.
You know your weekly grind better than any tutorial does. Start there.
When you build something, I’d genuinely love to hear about it. Drop it in the comments.
TLDR
- Sign up for Lovable (free tier): no installs, no terminal.
- Paste the expense-tracker prompt from section 3.
- Test like a user: click everything, refresh, type weird input.
- Report breakage specifically: “X broke when I did Y.”
- Second build: automate whatever you do manually every week.
Keep learning
- How to set up Claude Code for SEO ), for when you’re ready for a more technical workflow.
- How to use Claude for SEO tasks ): practical AI-assisted workflows beyond building.
- React vs Vue vs Angular ): what the AI is actually writing underneath, explained simply.
- Benefits of custom software development ), for when your prototype outgrows vibe coding.
