How much to charge for vibe coding work

Every new vibe coder makes the same pricing mistake, usually twice. They finish a job in two days that the client expected to take a month, feel slightly guilty about it, and charge for two days.

The client is delighted. The vibe coder has just taught them that a month of value costs two days. And next time, there’s no room to charge for the job that turns out to be genuinely hard.

Why “hours times rate” breaks with AI

Hourly pricing assumes your hours are what you’re selling. With AI doing the typing, your hours shrink while the value you deliver stays the same, or grows. Price by the hour and every improvement in your tools becomes a pay cut.

What you’re actually selling is:

• The outcome: a working tool that saves time, makes money or solves a problem.
• Your judgement: what to build, what to leave out, where the risks are.
• Speed: the client gets it weeks sooner, which is often worth more than the build itself.
• Reliability: it works, it’s secure, and you’ll be there when it doesn’t.

Three ways to price, and when to use each

Model	How it works	Use it when
Fixed price per milestone	An agreed price for each clearly defined chunk of work	The scope is clear. This is the default for most jobs.
Day rate	A set price per day, invoiced as you go	Ongoing work, or exploring something nobody can scope yet
Value-based	A price tied to what the result is worth to the client	You can see the money it saves or makes, and so can they

Fixed prices are where AI speed works in your favour. If you finish faster than you estimated, that margin is yours. Just make sure the scope is written down, because scope creep is how fixed prices go wrong.

Working out a fixed price

1. Estimate the honest effort, including everything around the building: calls, revisions, testing on phones, writing the handover notes, and fixing the thing the client “just quickly” changed.
2. Add a buffer for the unknown. Fifty per cent is not paranoid for a new client or an unfamiliar kind of build.
3. Check it against the value. If the tool saves the client ten hours a week, a price that pays for itself in a couple of months is an easy yes.
4. Split it into milestones, each one something the client can see and approve.

Handling “but didn’t the AI do it?”

You will hear this. A calm answer:

“The AI writes code very quickly. My job is to know what to build, to make sure it works and is secure, and to get it done in days instead of months. You’re paying for that, and for having someone to call when you need changes.”

Then point at your portfolio. The best defence against “anyone could do this” is a page of things you’ve done that clearly not everyone could.

Don’t forget the money after launch

The build is often the smaller part of what a client relationship is worth. Offer:

• A care plan: a monthly fee for hosting, updates, small fixes and being on call.
• A change rate: a clear price for small changes, so clients don’t feel nervous asking.
• Version two: once the first version is in use, the client will have ideas. Be the person they bring them to.

The platform fee is part of your price

If you find work through a marketplace, the platform takes a cut for finding the client, holding the payment and sorting out disputes. Build it into your quote rather than resenting it later. Escrow is worth something too: when the client’s payment is held before you start, you never do a job for money that isn’t there.

Signs you’re charging too little

• Every client says yes immediately.
• You’re busy all the time and still not earning what you’d like.
• You dread scope changes because there’s no margin to absorb them.
• You’re competing on price with people whose work you think is worse.

If two or more of those are true, raise your prices for the next client. Not the current one, the next one. You’ll be surprised how few people blink.