What actually sells from vibe coding: eight formats
Vibe coding is a method rather than a service. A service is a specific result for a specific type of client. Below are eight formats people genuinely buy, with who the client is, what it costs and where the catch is in each.
Vibe coding is a method rather than a service. A service is a specific result for a specific type of client. Below are eight formats people genuinely buy, with who the client is, what it costs and where the catch is in each.
I can assemble things and do not know what to offer
Somebody has mastered assembly. It works: pages, forms, small applications.
And then a dead end. What exactly to sell? "I make websites" — everybody says that. "I build applications" sounds too large, and the client will ask about something you cannot handle.
The problem is that vibe coding is a method rather than a service. A service is a specific result for a specific type of client.
Below are eight formats people genuinely buy. For each: who the client is, what is delivered, the order of prices and where the catch is.
The prices come from my scrape of 5 986 jobs over four months. A caveat: an explicit budget appears in 17% of listings, and there is no separate "Development" category in the parser, so the web ranges are a guide from adjacent categories and from practice.
1. A landing page for a launch
Who buys: an expert with a date fixed. A course, a webinar, an intake for a programme.
What is delivered: a single page that collects enquiries, with the data going somewhere they will not be lost.
The order of prices: the upper part of the range for a single page, because the deadline is hard.
The key word in the conversation is the deadline. The first question to the client: "by what date do you need it?" It immediately separates you from those who start by discussing design.
The catch: the launch shifts and you have held a week for it. Fix the date and the conditions for postponement in the quote.
2. A site for a business with no site
Who buys: a car repair shop, a dental practice, a children's centre, a coffee shop, a local retailer. There is no site at all, or something from a decade ago is still up.
What is delivered: a multi-page site with prices, services and a way to get in touch.
The order of prices: $245–730.
How to approach it: not with an offer of a website but with an observation. "People search for you with this query and find a competitor." Specific and verifiable.
The catch: a client like that often does not understand why he needs a site and will ask "and what will I be paying for after that". Name the recurring costs before payment rather than after.
3. Testing an idea
Who buys: somebody testing an idea who wants figures before building a product.
What is delivered: a page with a form and a clear way of receiving the data, assembled quickly.
The order of prices: $490–1 460 — more is paid here, because a decision about an order of magnitude more money is at stake.
The key word is speed. "I will assemble it in a week, you look at the figures and decide whether to build further."
The catch: the client may get carried away and start adding features. Hold the frame: this is a test rather than a product.
4. An internal tool
Who buys: a small company where something is calculated by hand in spreadsheets.
What is delivered: a calculator to their formulas, a record form, a simple tracker.
Why this is a good format: there are many such tasks, they are not commissioned from a developer — too expensive and too slow — and so they get done by hand for years.
The catch: the formulas and rules have to be extracted from people. That is an interview, and it takes longer than the assembly.
5. A specialist's personal site
Who buys: an expert, a coach, a doctor, a lawyer, a designer. Somebody who needs a page rather than an account.
What is delivered: a portfolio site: who, for whom, what they can do, examples, a way to get in touch.
Why the format is underrated: the entry threshold is low and demand is steady — specialists appear constantly.
The catch: the most frequent case of endless haggling. Work to a fixed structure rather than "make it look nice somehow".
6. A shop window or catalogue
Who buys: somebody with goods and no shop. Or with one that is inconvenient.
What is delivered: product pages, search, a way to place an order.
An important catch: as soon as payment handling appears, that is no longer your zone if you have no such experience. Say so honestly: I assemble the shop window, a specialist does the payments.
7. A prototype for showing
Who buys: somebody who has to show an idea to an investor, a partner or management.
What is delivered: a clickable mock-up that looks and behaves like a product.
Why this is good value: no data, no payment, no error handling needed. It is the least work with high value — because a decision gets made on the strength of that showing.
The catch: record in writing without fail that this is a prototype. Otherwise in a month the client will ask you to "just launch it" — and that is a different project.
8. Rebuilding something that exists
Who buys: somebody who has a site that does not work.
What is delivered: an analysis of where visitors are lost, and the rebuild.
Why this is the best way in to a client: you arrive not with an offer but with a ready observation about his own site. Three precise remarks work better than any commercial proposal.
The catch: somebody else's project can turn out harder than building from scratch. Look at it before naming a price.
How to choose one format out of eight
You do not have to offer all eight. The one-tool rule applies here too.
Take the one whose type of client you understand from the inside. Worked in catering — go to coffee shops. Know how a private practice runs — go to specialists.
Understanding the domain matters more than assembly skill: it determines whether you land on a real pain or offer a handsome page.
And assemble from a description rather than from requests. A project with no document falls apart at the third correction, and there will always be corrections.
What is delivered alongside the work
Four things separating a contractor from a jobber. They also justify the price.
Credentials registered to the client rather than to you.
A short instruction: how to change the text, where to look at enquiries, what to do on a failure.
What he pays for himself thereafter — domain, hosting, services, with sums. Named in advance it causes no complaints; discovered later it always does.
The terms of support: whether it is in the price, what a change costs.
What the platform offers for vibecoding
Site templates — 343 prompts, sorted by exactly these formats: hero sections 80, landing pages 61, SaaS 33, agencies 10, portfolios 8, shop windows 8. Plus 80 individual sections — pricing, testimonials, footer, login form — and 23 animated backgrounds.
Each prompt is a full brief averaging 10 000 characters, the most detailed up to 75 000. The preview is visible before launch. The prompts are not tied to a service and paste into any environment that writes code.
Plus plan.
Skills for Claude Code — over 10 000. The catalogue is open to everyone, the files come with Basic.
Assistants — "Engineers" for the assembly, "Marketing" for analysing somebody's site before approaching them, "Legal" for the contract (for example, the Paralegal). From Basic.
Registration is free and opens three days of full Basic access.
Where to start today
One action. Choose one of the eight formats — the one whose clients you understand best.
Then write out five specific companies or people of that type whose problem is visible from outside: no site, an outdated one, no page for a launch.
Five minutes of work and you have five addresses where you are not competing with twenty applications on a marketplace.
One more model not on the list
The eight formats above are selling a result. There is a ninth option, and it is about something else.
Selling access instead of work. You wrap a working process in a simple interface and sell access to small business owners who need the result and have no time to work it out.
How that differs from the eight formats. There you do the work for money. Here you assemble a tool once and sell a subscription to it.
What you need to be able to do. Exactly what is described in the article: assemble an interface, connect payment, sort out access. All of that is the four layers from the article on prototypes and products.
And an honest assessment. It is the slowest of the nine models to first money and the most interesting in its ceiling. It is not worth starting with, but worth keeping in mind.
Plus the lesson “Working with files. Building websites”
A separate lesson in the “Automator” course on assembling sites through working with files — the practical part for the first formats in the list.
The “Automator” course — Plus plan.
What people buy — by platform section
The income model phrasings are taken from the sections' own descriptions:
Site templates, Plus plan — 343 prompts. Three models: landing pages to order, where your cost falls to one evening while the market price stays the same. MVPs for start-ups — a fast prototype to show an investor or test demand. A portfolio with no clients — generate a dozen pieces and enter the market with case histories.
Application interfaces, Plus plan — prompts for dashboards and account areas.
The “Automator” course, Plus plan — eleven lessons on solving business tasks with neural networks on files: analysing contracts, reports, marketplace product cards, translating texts, building sites. That is the answer to this article's question: what sells is not "a website" but a business task solved.
The automation templates section — the most stable model in its description: you implement it, then support and refine it monthly. Recurring income instead of a one-off deal.
What is needed before selling. The lesson “How to create your own premium product” in the “Sales” course, Basic plan — about a high-ticket product. What you assemble sells when it is described as a result for the client rather than as "I made an application".
Skills that take what you assembled to something sellable
The difference between "works for me" and "can be given to a client" is a set of checks. Here they are (all three are advanced: Creator and up, or $9, or 1000 XP).
- A single configuration for several environments — protective rules against dangerous commands, unnecessary refactoring and contracts drifting apart between parts of the system. What vibe coding most often falls apart on
- Strengthening a prompt into a working instruction — it turns a raw request into a structured assignment with rules for tool use
- Documents for registering software rights — it scans the project, identifies the stack and assembles a technical description with the sources. The jurisdiction is specific, but the technique itself — documenting development as an object of rights — works anywhere a client asks "and whose is this"
What most often prevents what you assembled from selling. Not the quality of the code but the absence of an answer to the question about rights. A client paying for a system wants to understand what he is buying and what he can do with it.
What to pick up on the platform for this task
- Landing page architect — analysing references and building high-conversion landing pages; from the Basic plan
- Landing page from a brand interview — a Claude Code skill; advanced (Creator+ / $9 / 1000 XP)
- Audit and optimisation of online-shop landing pages — for the "shop window" format; advanced (Creator+ / $9 / 1000 XP)
- AI chatbot for a website with online booking — an n8n template: an add-on to a business site; standard template, Creator plan and up
- The “Automator” course — the “Building sites” lesson and file analyses for a client; Plus plan
- The VIBE CODING course — from the idea and brief to a first app; Creator plan
What to read next
A specialist's portfolio site — the lowest entry threshold of the eight.
From prototype to product — what separates deliverable from assembled.
A 30 000 character prompt — how not to get a mediocre result.
The AI freelancer price list — what to check your figures against.
Skills for Claude Code — the full guide to skills.