What vibe coding is and whether you can make things people pay for with it
You built a website in an evening with no code — and then bewilderment: does this count, do people pay for it, and what is it exactly that I can do. The bewilderment is justified. Below is what it actually is, where the limits are and what of it gets bought.
You built a website in an evening with no code — and then bewilderment: does this count, do people pay for it, and what is it exactly that I can do. The bewilderment is justified. Below is what it actually is, where the limits are and what of it gets bought.
---
The site came together in an evening — and then it is unclear
Somebody tries assembling something with AI for the first time: described it in words, got a working page. In an evening. Without a single line of code written by hand.
The reaction usually comes in two parts. First delight. Then bewilderment: does this even count? Do people pay for this? And what is it exactly that I can do?
The bewilderment is justified. Plenty inside genuinely is unclear: how it works, what happens under load, what to do if it breaks. Selling something you do not understand is frightening — and rightly frightening.
Let us go through the substance: what this is, where the limits are and what of it gets bought.
What it actually is
Vibe coding is assembling working things by describing the task instead of writing code.
You state what is needed, the tool assembles it. Then you look at the result, say what is wrong, and it corrects.
The key thing to understand immediately: this is not "programming has become unnecessary". It is a shift in the work: instead of syntax you are doing task-setting, checking and decisions about structure.
Hence the phrase that explains everything: a vibe coder who does not understand the architecture is a client who does not read the quote. They receive a result and cannot judge what exactly they received.
Three levels of reading the quote
Worth laying out, because each level is worth separate money.
The first: what got built for you. How many blocks, how the forms work, where the data lands, what happens with three hundred simultaneous visitors. Until that is clear you can neither answer for the result nor explain it to a client.
The second: what you are being charged for. Domain, hosting, subscriptions to services. A client will ask "and what do I pay after that?" — and with no answer the deal stalls.
The third: what to charge yourself. You count not your hours but their task. A surgeon also operates for half an hour.
What genuinely gets built
Confidently: landing pages and multi-page websites, simple internal tools — calculators, forms, trackers, prototypes for showing an idea, small applications for yourself and a team, pages for a particular launch.
With caveats: anything working with payments, personal data or large numbers of users. It can be built, but here you need somebody who understands what to check.
Does not get built: heavy-load products, complex integrations with other people's systems, anything where the cost of a failure is high.
And the most frequent trap. A working prototype and a product you can put into service are different things. Between them lie validation, security, behaviour on errors, and somebody having to maintain it.
What of it gets bought
From my scrape — 848 job listings over 24 days across 13 categories.
A multi-page website — $245–730. A system or pipeline — $490–1 460. For comparison, the median for one-off work across the whole dataset is $30–75.
One website at the lower bound is the equivalent of five to eight clips. It does not take five times as long.
An honest caveat: my scraper has no separate "development" category, so the share of websites is structurally understated, and the ranges for them are a guide from adjacent categories and practice.
And a separate market observation. Across 6 502 posts from eleven channels in the niche over 19 months, landing pages as a paid service appear twenty times — 0.3% of the feed. And such material performs above average. Everybody teaches building; almost nobody shows how it sells.
Who buys and what to approach them with
Three types, and the conversation with each differs.
A small business with no website. Buys to be found. Fears paying and getting a page nobody uses. You approach not with an offer of a website but with an observation: "people are searching for you by this query and finding a competitor".
An expert with a launch. Buys a page for a date. The key word is the deadline. The first question worth asking: "what date do you need it by?"
Testing an idea. Buys speed: build it in a week and look at the figures before investing further.
And a ready answer to "I could build it myself in an evening". Yes, they could. But building a page and getting a working instrument are different tasks: you need a structure that leads to an enquiry, copy for the audience, enquiries landing somewhere they will not get lost, and a page that will not need finishing by somebody else later. The counter-question closes the subject by itself: "when were you planning to get to it?"
What ships with the work
The difference between "made" and "delivered" is four things, and they are exactly what separates a contractor from a pair of hands.
Credentials. Everything registered to the client rather than to you. A website tied to your email address is a mine that goes off in a year.
A short guide. How to change the text, how to see enquiries, where to look if something is not working. Half a page, not documentation.
What they pay for themselves afterwards. Domain, hosting, services — with amounts and dates. Named in advance it causes no complaint; discovered later it always does.
What to do if it breaks. Who to go to, whether support is in the price, what a change costs. The absence of that point means you will get called on for free and indefinitely.
How to build the quote
Not as one sum but as items: structure and copy, the build, forms and enquiry collection, domain and publishing, how many rounds of revisions are included, what the client pays for themselves afterwards.
A quote of six lines defends itself. People argue with the items rather than the total.
The last point matters particularly: somebody who learns about recurring costs after paying feels cheated, even if you hid nothing.
What to learn so you are not a client with no quote
Three things that turn assembling into a profession.
Understanding the structure at diagram level. Not syntax but what the thing built for you consists of: where the data is, where the logic is, where the interface is, what connects to what. That is enough to answer a client's questions and to know what you are delivering.
Being able to check. What happens with an empty form, with wrong data, on a double submission, on a phone. Checking is the main part of the work every newcomer skips, and it is exactly why delivery turns into endless revisions.
Knowing what you do not do. Payments, personal data, load — those need somebody who understands the consequences. The ability to turn a task down is worth more than the ability to take it on.
And the most practical thing: build your first thing for yourself rather than for a client. On your own project you can break anything, and it becomes the first item in your showcase.
Where to start
Vibe coding is the largest of the subjects: a proper treatment takes dozens of hours and is split into modules in the main programme rather than a short course.
What is available as a quick way in:
Website and app interface templates — prompts for animated landing pages and multi-page sites with a preview of the result. The showcase and previews are open to everyone; the prompts themselves come with the Plus plan.
Skills for Claude Code — more than 10 000. A skill is not a prompt but a chain of agents: the task is split into parts and each gets passed on. The catalogue and descriptions are open to everyone, the files come with Basic, advanced ones with Creator+.
140+ AI assistants across 14 categories, engineering and analytics among them — from Basic.
Registration is free and opens three days of full Basic access — plus six foundational express courses and the ten-lesson sales module.
Do one thing today: write out five companies in your area with no website or a hopelessly outdated one. Five minutes of work, and you have five addresses where you are not competing with twenty applications.
---
Where this gets taught step by step
Module 5, lesson 10, "Building websites" — assembly through working with files.
Module 5, lesson 12 — installing a local AI agent: working with repositories, setting programming tasks through an assistant even with no experience, building a Python bot and publishing it to a server.
The phrasing from the lesson: an agent can call any tools, follow links, load the libraries it needs and produce finished projects rather than text.
Plus 343 website templates — prompts with previews, each averaging 10 000 characters of full brief.
And module 3's lesson on cascades — the principle without which a project falls apart at the third revision: break the task into stages and lead the model along a plan.
Module 5 and the templates — Plus; module 3 — Basic.
---
What to read next
[App architecture as a building](/en/blog/app-architecture-as-building) — so you know what got built for you.
[What of this actually sells](/en/blog/what-sells-from-vibecoding) — eight formats with prices.
[From prototype to product](/en/blog/prototype-to-product) — what separates deliverable from built.
[Why a project falls apart at the third revision](/en/blog/spec-coding) — how to work without chaos.
[Skills for Claude Code](/en/blog/claude-code-skills-guide) — the full guide to skills.