What vibe coding is and whether you can make things people pay for with it

What vibe coding is and whether you can make things people pay for with it

You assembled a site in an evening with no line of code — and confusion follows: does this count, do people pay for it, and what exactly can I do. The confusion is justified. Below is what this actually is, where the limits of applicability are and what of it people buy.

You assembled a site in an evening with no line of code — and confusion follows: does this count, do people pay for it, and what exactly can I do. The confusion is justified. Below is what this actually is, where the limits of applicability are and what of it people buy.

The site assembled 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. With no line of code written by hand.

The reaction usually comes in two parts. First delight. Then confusion: does this even count? Do people pay for this? And what exactly can I do?

The confusion is justified. A great deal inside genuinely is unclear: how it is built, what will happen under load, what to do if it breaks. Selling something you do not understand is frightening — and rightly so.

Let us go through it properly: what this is, where the limits of applicability are and what of it people buy.

What this actually is

Vibe coding is assembling working things by describing the task instead of writing code.

You state what is needed and the tool assembles it. You then look at the result, say what is wrong, and it corrects.

The key thing to understand at once: this is not "programming has become unnecessary". It is a shift of the work: instead of syntax you deal with setting the task, checking, and decisions about how things are built.

Hence the sentence that explains everything: a vibe coder who does not understand the architecture is a client who does not read the quote. He receives a result and cannot judge what he has received.

Three levels of reading the quote

Worth laying out, because each level is worth separate money.

The first: what was assembled for you. How many blocks, how the forms are built, where the data lands, what will happen 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 is being charged to you. Domain, hosting, service subscriptions. The client will ask "and what do I pay for after that?" — and with no answer the deal sags.

The third: how much to charge yourself. Count not your hours but his task. A surgeon also operates for half an hour.

What genuinely gets built

Confidently: landing pages and multi-page sites, simple internal tools — calculators, forms, trackers, prototypes for showing an idea, small applications for yourself and your team, pages for a specific launch.

With caveats: anything working with payments, personal data or a large number of users. It can be built, but here somebody who understands what to check is needed.

Not built: high-load products, complex integrations with other people's systems, anything where the cost of a failure is high.

And the most common trap. A working prototype and a product that can go into service are different things. Between them lie testing, security, behaviour on errors, and the fact that somebody has to maintain it.

What of vibecoding output people buy

From my scrape — 5 986 jobs over four months across seven categories.

A multi-page site $245–730. A system or a pipeline $490–1 460. For comparison, the median one-off job across the whole scrape is around $60.

One site at the bottom of the range is the equivalent of five to eight clips. It does not take five times as long.

An honest caveat: my parser has no separate "Development" category, so the share of sites is understated by construction, and the ranges for them are a guide from adjacent categories and from practice.

And a separate market observation. In 6 502 posts from eleven channels in the niche over 19 months, the subject of a landing page as a paid service appears twenty times — 0.3% of the feed. And such material performs above average. Everybody teaches assembly and almost nobody shows how it sells.

Who buys and what to approach them with

Three types, and the conversation with each is different.

A small business with no site. Buys so as 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 search for you with this query and find a competitor".

An expert before a launch. Buys a page for a date. The key word is the deadline. The first question worth asking: "by what date do you need it?"

Testing an idea. Buys speed: assemble it in a week and look at the figures before investing further.

And a ready answer to the objection "I could assemble it myself in an evening". Yes, he could. But assembling a page and getting a working tool are different tasks: it needs a structure that leads to an enquiry, texts for the audience, enquiries landing somewhere they will not be lost, and the page not needing somebody else to finish it afterwards. A return question closes the subject itself: "when were you planning to get to it?"

What to deliver to a client along with the work

The difference between "made it" and "delivered it" is four things, and they are what separates a contractor from a jobber.

Credentials. Everything registered to the client rather than to you. A site tied to your email address is a mine that goes off in a year.

A short instruction. How to change the text, how to look at enquiries, where to look if something is not working. Half a page, not documentation.

What he pays for himself thereafter. Domain, hosting, services — with sums and dates. Named in advance it causes no complaints; 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 be interrupted for free and indefinitely.

How to price it

Not as one sum but by composition: structure and texts, assembly, forms and enquiry handling, domain and publication, how many rounds of revisions are included, what the client pays for himself thereafter.

A six-line quote defends itself. People argue with the items rather than the total.

The last point matters especially: somebody who learns about recurring costs after paying feels deceived, even if you hid nothing.

What to learn so as not to be a client with no quote

Three things that turn assembly into a profession.

Understanding the structure at the level of a diagram. Not syntax but what the thing assembled 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 understand what you are delivering.

Being able to test. What happens with an empty form, with invalid data, on a double submission, on a phone. Testing is the main part of the work that every beginner 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 decline a task is worth more than the ability to take it.

And the most practical thing: build your first piece for yourself rather than for a client. On your own project anything can be broken, and it will also be the first item in your showcase.

Where to start

Vibe coding is the largest of the subjects: a full treatment takes dozens of hours and lives in a separate course, VIBE CODING (Creator plan and above), rather than in a short express course.

What is available as a quick entrance:

Site and application interface templates — prompts for animated landing pages and multi-page sites with previews of the result. The showcase and previews are open to everyone; the prompts themselves come with the Plus plan.

Skills for Claude Code — over 10 000. A skill is not a prompt but a chain of agents: the task is divided into parts and each is passed on. The catalogue and descriptions are open to everyone, the files come with Basic, advanced ones with Creator+.

200+ AI assistants across 14 categories, including engineers and analytics — from Basic.

Registration is free. Three days of the Basic plan switch on with one button, no card needed: Basic includes 200+ AI assistants, prompt texts, skill files, five programme courses (including “Sales”) and six Basic mini-courses — among them “Freelancer positioning”, Freelance 2.0, Perplexity and Grok.

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.

The “VIBE CODING” course

The “VIBE CODING” course, Creator plan and above (also Make, N8N, Full). Plus the express course “Claude: from a first prompt to your own library of mega-capabilities” ($9, Creator plan and above): structural prompts as an assignment frame, connecting to external bases and APIs through MCP, creating your own skills.

The logic is the same as throughout the programme: describe the task first, assemble second. A separate chapter of the course covers the method by which that is done.

What can be built with no study at all

Site templates, Plus plan — 343 prompts: 240 whole pages, 80 sections, 23 animated backgrounds. You paste the prompt into Claude Code or Lovable and get a live site. The showcase and previews are open to everyone.

Application interfaces, Plus plan — prompts for dashboards, account areas, mobile screens.

Three income models from the sites section's description: landing pages to order, where your cost falls to one evening while the market price stays the same. MVPs for start-ups — a prototype to show an investor or test demand. A portfolio with no clients — generate a dozen pieces and enter the market with case histories.

Assistants, Basic plan: Software engineer, Programming mentor, Web designer, UX designer.

Where this is taught step by step

In the course “Automator” — the lesson “Working with files. Building sites”: assembly through working with files.

In the VIBE CODING course — the path from an idea to an app step by step: the technical brief, design, interface pre-visualisation, assembling the “skeleton” of a first app, MVP acceptance.

Plus 343 site templates — prompts with previews, each averaging 10 000 characters of a full brief.

And the course “Basic prompting”, the lesson “Cascade prompts” — the principle without which a project falls apart at the third correction: break the task into stages and lead the model along a plan.

“Automator” and the templates — Plus; “Basic prompting” — Basic; VIBE CODING — Creator.

What to take on the platform for this task

What to read next

An application's architecture as a building — so you understand what was assembled for you.

What sells from what you assemble — eight formats with prices.

From prototype to product — what separates deliverable from assembled.

Why a project falls apart at the third correction — how to work without chaos.

Skills for Claude Code — the full guide to skills.

Also on AI SKILLS