Sooner or later, a client asks it. Sometimes it’s a joke on a kickoff call, sometimes it’s a line in an email after they’ve seen your quote: “Couldn’t AI just do this?” Or the softer version: “Now that you’re using AI, shouldn’t this be cheaper?”
If you’re a designer or developer, the question lands hard because it’s half right. AI really has made parts of your work faster. A first-pass layout, a component scaffold, a batch of copy options — those take a fraction of the time they used to. What the question gets wrong is what the client was ever paying for.
You don’t need to get defensive, and you don’t need to cut your rate. You need a calm answer, and a way of pricing that makes the question less likely to come up at all.
Clients increasingly expect AI to lower prices, but most of what they pay for — judgment, taste, getting it right first time and someone accountable for the result — didn’t get cheaper. Answer the question directly: agree that drafting is faster, then explain what the fee covers. Price outcomes rather than hours so speed stops being visible as a discount, and offer a smaller scope instead of a lower rate when the budget really is tight.
Why clients are asking now
Clients aren’t being cynical. They’re seeing the same headlines you are, and many of them have tried the tools themselves. They typed a prompt, got a logo or a landing page in thirty seconds, and reasonably wondered what your three weeks were for.
What they usually didn’t do is ship it. The thirty-second logo doesn’t work at favicon size, the generated landing page has no idea what their product actually does, and the code runs until it meets real data. The gap between “something that looks finished” and “something you can put your name to” is exactly where your work lives — but from the outside, that gap is invisible.
So treat the question as a request for information, not an attack on your rate. The client who asks is telling you they don’t yet see what the fee buys. That’s fixable.
What the client is actually paying for
Before you answer anyone, be clear with yourself about what didn’t get cheaper. For most design and development work, it’s this:
- Judgment. Knowing which of the twenty options is right for this brand, this audience, this codebase — and why the other nineteen aren’t.
- Taste and context. A model can produce a thousand plausible layouts. It can’t know that the client’s last rebrand failed because it looked too corporate.
- Getting it right. Generated output is cheap to produce and expensive to check. Reviewing, testing and fixing the subtly wrong parts is where the hours now go — the same point made in invoicing for AI-assisted contract work.
- Accountability. When something breaks the week after launch, the client calls you, not the model. A named person standing behind the work is part of the price.
None of that is new. AI just removed the drafting time that used to hide it.
How to answer the question
Keep it short, honest and unbothered. Something like this works well in an email or on a call:
“Yes — I use AI where it helps, and it does make the first draft faster. What you’re paying for is what comes after that: deciding what’s right for your users, making sure it actually works, and having someone accountable for it once it’s live. That part takes the same care it always did.”
A few things make that answer land:
- Agree with the true part first. Pretending AI hasn’t changed anything costs you credibility. Admitting it has, and moving on, makes you sound like the expert in the room.
- Name the outcome, not the effort. “A checkout flow that converts” beats “forty hours of design”. Clients buy results; hours invite haggling.
- Don’t apologise for the price. Explaining isn’t the same as justifying. Say what the fee covers, then stop talking.
- Offer proof if you have it. A past project where the obvious first idea would have failed is worth more than any argument about AI.
Price so the question doesn’t come up
The deeper fix is structural. If your quote reads as hours × rate, every efficiency gain looks like money you’re keeping from the client. If it reads as a price for a defined result, there’s nothing to discount.
- Quote fixed fees for defined deliverables. “Marketing site, five pages, two revision rounds” has a price. How long it takes you is your business. How to set freelance rates covers working out what that price should be.
- Turn hourly retainers into scoped ones. “20 hours a month” invites the question the moment you get faster; “ongoing design support for these three products” doesn’t. Retainers vs project fees walks through the switch.
- Keep tracking your time anyway. Not to bill it, but to know it. If a fixed-fee project secretly took twice the estimate, that’s the number you need when you price the next one — and it’s your evidence if a client challenges the quote. Using tracked time to defend a quote shows how.
When the budget really is smaller
Sometimes the AI question is really a budget question in disguise. The client has less to spend and hopes technology can close the gap.
Don’t close it with your rate. Close it with scope:
- Cut deliverables, not price. Three page templates instead of eight. One brand direction instead of three. A prototype instead of production code.
- Let them do more themselves. If they want to generate a first draft of the copy or the illustrations with AI, you can review and refine instead of creating from scratch — priced as a review, with clear limits.
- Name the trade-off in writing. “This version doesn’t include responsive testing on older devices” protects you later and makes the full scope look like the better deal.
A smaller project at your normal rate keeps the relationship and your pricing intact. A discount on the full scope teaches the client that your rate was negotiable all along — and makes the next rate increase twice as hard.
When to walk away
Some clients have decided the work is now worth a tenth of what it was, and no explanation will move them. That’s fine. They’re shopping for output, not for you, and there will always be someone willing to sell them generated drafts with no one accountable for the result.
The clients worth keeping are the ones who care whether the work is right. Those clients will ask the AI question too — and then they’ll listen to the answer.
Frequently asked questions
Should I lower my prices because I use AI?
No. Lower prices only make sense if what the client receives is worth less, and for most design and development work it isn’t — the judgment, review and accountability are the same. If AI lets you deliver more in the same time, keep your rate and take on better work, or move to fixed fees so the gain is yours.
Should I tell clients I use AI tools?
Yes, before the project starts. Some clients have policies against AI tools or are bound by their own clients’ contracts, and confidentiality agreements may limit what you can paste into a hosted tool. A sentence in the proposal and the contract settles it, and being upfront makes the pricing conversation easier rather than harder.
What if a client says they can do it themselves with AI?
Let them try, politely. Offer to review what they produce at a set fee, or point to the parts AI handles badly for their project — accessibility, edge cases, brand consistency, maintainable code. Many clients come back once they’ve seen how far a generated draft is from something they can launch.
Is hourly billing still viable for creative work?
It works for open-ended support where the scope genuinely can’t be defined, but it’s increasingly awkward for defined projects, because every efficiency gain shrinks your invoice. For anything with a clear deliverable, a fixed fee or milestone pricing protects your rate and gives the client a number they can approve up front.
Where Billable comes in
Holding your price is easier when your quotes describe outcomes and your numbers back them up. Billable lets you send quotes built around deliverables and turn them into invoices once the client approves, while time tracking quietly records what each project really took — so you know whether a fixed fee paid off before you quote the next one.
It’s free for your first active project, then flat plans with no per-user fees. Quote your next project with confidence.