Vibe coding: build your first web app with AI
Short answer Vibe coding is building software by describing it in plain words to an AI tool that writes the code. It suits small tools like a quote calculator or job tracker. Plan it on one page, build one feature at a time, lock down keys and data, cap AI spending, and get a security review before storing sensitive data.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callVibe coding: what it is and what it's good for
Vibe coding means you describe an app in everyday language and an AI tool writes, runs and often hosts the code. AI researcher Andrej Karpathy named it in a post on X:
"There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists." (Andrej Karpathy on X, February 2, 2025)
Collins Dictionary made it its Word of the Year for 2025 (Collins Language Blog, November 2025).
For a business owner, "forget that the code even exists" is the risky part. You don't need to read the code. You still decide what gets built, test it, and answer for what it does with customer data.
| Good first projects | Bring in a developer first |
|---|---|
| A quote or price calculator on your site | Taking card payments in your own code |
| A request form that emails you and saves the lead | Health, financial or government ID data |
| An internal job checklist or crew schedule | Customer accounts holding private records |
| A one-off tool: event sign-up, referral tracker | An app the business can't run without |
Lovable, an AI app builder, says so in its own security docs:
"For apps handling sensitive data or critical functionality, consider an additional professional security review." (Lovable Docs: Security overview)
How to plan a vibe coding project before the first prompt
Write a one-page brief. Developers call it a product requirements document (PRD); yours can be six lines in a notes app. The AI builds from it, and you test against it.
| Line | Example: roof quote calculator |
|---|---|
| Who uses it | Homeowners on your website, mostly on phones |
| The one job | Show a price range and send you the lead |
| Screens | Roof size and type, price range, contact form, thank-you |
| Data it keeps | Name, phone, email, address, roof answers. Nothing else |
| Not in version 1 | Online payment, customer logins, photo uploads |
| Done when | A test quote reaches your inbox within a minute, sent from a phone |
The "data it keeps" line matters most. The FTC's data security guide for business says:
"SCALE DOWN. Keep only what you need for your business." (FTC: Protecting Personal Information, A Guide for Business)
Then paste the brief into the tool and ask for a plan, not code. Lovable and Replit both offer a Plan mode that lays out the approach and waits for your approval before any files change (Lovable Docs: Plan mode; Replit Docs: Build with Agent). Strike anything you didn't ask for, and shrink the plan to the smallest version you can test today.
Which vibe coding tool should you use?
For a first app, a browser app builder: it handles hosting, a database and logins in one place. Listed prices in US dollars, November 2026:
| Tool | Paid plans start at | Free use |
|---|---|---|
| Lovable | $25 a month, 100 credits | Free plan: 5 build credits a day, up to 30 a month |
| Bolt | $25 a month | Free plan: 1 million tokens a month, 300,000 a day |
| Replit | $20 a month, or $18 billed yearly (Core) | Starter plan: daily Agent credits; 1 published app, taken down after 30 days |
Sources: Lovable Docs (Subscription plans; Credits and usage), Bolt and Replit pricing pages, Replit Docs (Starter plan).
Two costs the table hides. A custom domain needs a paid plan on Lovable and Bolt. And if the app itself uses AI, such as a chatbot or a summary, that usage draws on monthly grants and then credits (Lovable Docs: Credits and usage).
If a developer may take over later, pick a tool that syncs the code to GitHub, a service that stores code and its history. Lovable includes Git sync on every plan, free included; downloading the code needs a paid plan (Lovable Docs: Subscription plans).
How to prompt an AI app builder: one feature at a time
Replit's own guide boils it down to five habits: "be specific, plan the work, add context, review and test, and use checkpoints" (Replit Docs: Build with Agent). In practice:
- Build the smallest version first. The calculator alone, then the form, then the email.
- Say what must not change. "Add a roof-pitch question. Keep the other fields and colors as they are."
- Test like a customer after every change. On your phone, with fake data, start to finish.
- Report bugs as facts. What you did, what you saw, what you expected. Paste error messages word for word.
- Roll back when it gets worse. Builders save each version so you can return to it: Lovable calls this version history, Replit calls them checkpoints. After two failed fixes, go back and ask a different way.
| Vague prompt | Specific prompt |
|---|---|
| "Make the form better" | "On the quote form, make phone required and email optional. Show errors under each field. Don't change the layout." |
| "Fix the bug" | "When I submit the form on my phone, the thank-you page shows but no email arrives. Find the cause before changing anything." |
How to secure an AI-built app
Assume the first version has holes. In Veracode's October 2026 test of 18 AI models in four programming languages, 38% of coding tasks produced code with a security flaw when the request gave no security guidance, down from 44% in July (Veracode, 2026). Builders' scanners help, but Lovable warns they "cannot guarantee complete security" (Lovable Docs: Security overview).
Five checks before anyone else uses the app:
| Risk | What to check | What the platform says |
|---|---|---|
| Stolen API key: the password your app uses to call a paid service, like an AI model | The key sits in the tool's secrets settings and is used only on the server, never in page code | Google: "Keys compiled in client-side code can be extracted by users." |
| Open database | Row-level security (rules on which records each user can see) is on for every table. Log in as one test user and try to open another's records | Supabase: "A table in an exposed schema without RLS is readable and writable by any role with a grant on it." |
| Bots and spam | A bot check on forms, and rate limiting: a cap on requests per visitor | Cloudflare calls Turnstile its "smart CAPTCHA alternative", free for up to 20 widgets; its free plan has 1 rate limiting rule |
| Runaway AI bill | A hard spending limit, not only an alert | OpenAI: "To enforce a monthly cap, set a hard spend limit." |
| Holes added by later changes | Read the builder's security scan before each publish and fix what it flags | Lovable's quick scan runs on every publish and checks database rules and known flaws in the add-on code your app uses |
On bills, an alert and a cap are different things. Google Cloud says "Setting an alerts-only budget doesn't automatically cap Google Cloud or Google Maps Platform usage or spending", and offers spend cap budgets only for some services (Google Cloud Docs). Anthropic lets you set a monthly spend limit below your account's cap (Claude Docs: Rate limits).
Does privacy law apply to an app you vibe coded?
Yes. Privacy rules attach to the personal information you collect, however the app was built.
In Canada, PIPEDA, the federal private-sector privacy law, says:
"Personal information shall be protected by security safeguards appropriate to the sensitivity of the information." (PIPEDA, Schedule 1, Principle 4.7)
Clause 4.7.2 adds that more sensitive information calls for a higher level of protection. Alberta, British Columbia and Quebec have their own private-sector privacy laws, which generally apply instead of PIPEDA inside those provinces (Office of the Privacy Commissioner of Canada).
In the US, start with the FTC's advice above: collect less. Every state also has a breach notification law, so if the app leaks personal information you may have to tell the people affected (FTC: Data Breach Response, A Guide for Business). For health data, see is ChatGPT HIPAA compliant?.
Before you launch a vibe-coded app
| Check | Why |
|---|---|
| Connect your own domain | Your ads, Business Profile and printed materials point there, not to the builder's address |
| Have someone else use it on a phone | You know how it's meant to work; they don't |
| Make sure keyboard and screen reader users can finish the main task | See ADA website compliance |
| If it should appear on Google, check that Google can read the pages | See AI website builders |
| Count what it produces | Track form sends and bookings as GA4 key events |
| Name who maintains it | Someone reruns the scan and fixes what breaks, every month |
Example
Illustrative cases with invented round numbers.
A roofer's quote calculator (US dollars)
He writes the six-line brief, builds on a free plan over a weekend, then moves to a $25-a-month plan to put it on his own domain. Before launch he adds a bot check to the form and confirms the email service key sits in the tool's secrets. In the first month, 30 homeowners get a price range and 12 leave their number.
A cleaning company's crew app
Each of 8 cleaners logs in to see the day's jobs and client notes. In testing, one test cleaner can open all 200 clients' notes. The owner asks the builder to fix the row-level rules, logs in again as each test user, and reruns the scan before anyone gets a login.
A physiotherapy clinic's patient intake
The owner wants new patients to enter their health history online. That is sensitive health data, so she uses her practice software's intake form instead, and vibe codes only a booking request page with no health questions.
FAQ
Do I need to know how to code to vibe code?
Not for a first version. You do need a clear brief, a test after every change, and the judgment to stop when the app touches sensitive data.
Can I take my app's code with me?
It depends on the tool and plan, so check before you build. Lovable syncs code to GitHub on every plan, but downloading it needs a paid plan.
Is a vibe-coded app safe?
Only as safe as your checks: secret keys, database rules, a bot check, a spending cap, and a scan before each publish.
How much does vibe coding cost?
Free plans are for trying. Paid plans start at $20 to $25 a month on Replit, Lovable and Bolt, plus your domain and any AI use inside the app.
Different for you?
- You need a website, not an app: AI website builders.
- Comparing building it yourself with hiring: small business website cost.
- The app will collect patient information: is ChatGPT HIPAA compliant?.
- Customers with disabilities must be able to use it: ADA website compliance.
- You'd rather have the site built, written and kept up for you: Website Agent.