AI Made Websites Cheaper to Build. So Why Didn’t Your Quote Go Down?
Here’s a conversation I keep getting some version of. A business owner has used an AI tool to get a site up in an afternoon, or watched a friend do it, and then gets a quote from a real team and goes, “Wait. Isn’t this supposed to be cheap now?”
Fair. I’d ask the same thing. I build with AI every day, so I can’t very well tell you it did nothing.
It did something. It just did less of the thing you were hoping, and more of a different thing. Let’s break down where the hours went.
First, the part that did get cheaper
Kanopi, a WordPress and Drupal agency, put this well in a post called AI changed website rebuilds: here’s what your budget still pays for. They say AI cuts the effort on structured, repetitive work like content migrations, data mapping, documentation, and first drafts of code, by up to 40% in some cases.
Then comes the sentence I wish more people would read twice: that doesn’t make a project 40% cheaper or faster overnight. What it buys is time, “less on busywork, more on the decisions that shape the finished site.”
That matches what I see. The typing got faster. Everything around the typing didn’t.
What a quote is actually made of
When a site gets built properly, the code is a slice of the work. Here’s roughly how it splits, and how much AI changed each piece:
| Part of the project | Did AI shrink it? |
|---|---|
| Discovery: who the site is for, what it needs to do | Barely. Someone still has to ask the questions and listen |
| Content: what to say, what to cut, who approves it | A little for drafts. Not for deciding what’s true about your business |
| Design direction: looking like you, not like everyone else | Faster to explore. Still needs a person steering |
| Build: layouts, templates, first-draft code | Yes, a lot |
| Integrations: forms, CRM, payments, email | Some. Testing them against your actual setup is the slow part |
| QA and accessibility: does it work on a phone, for everyone | Not much. This is where things get caught |
| Launch and what comes after: updates, backups, security, fixes | No. This one never stops |
So the biggest line item that shrank is the one that was never the whole bill.
What “looks done” is hiding
The folks at WebDevStudios just ran a great experiment on this. In a post called Your AI-Built Website Looks Done. Is It?, they had Claude prototype a site in about five prompts and a few hours, and the design was excellent.
Then they showed what was fake underneath. The contact form validated your entry, filtered spam, stamped it “LOGGED,” and sent it nowhere. The cookie banner remembered your choice and blocked nothing. The share image pointed to a file that didn’t exist.
That’s not a dig at the AI. A prototype is supposed to fake the plumbing. The risk is that it fakes it so well that you mistake it for the finished site. Their line is that AI is great at the 20% of a website you can see, and that the 80% you can’t see is what actually keeps it working.
I made a cousin of this point in my post on letting AI build your site. The tool builds what you described. Nobody asks about the lock on the door.
What a quote should itemize now
If you’re comparing proposals in 2026, here’s what I’d want to see written down, in plain English:
- Discovery. Who is this for, what does success look like, and how will anyone measure it?
- Content. Who writes it, who approves it, and what happens to the old pages?
- Integrations. Every form, payment tool, calendar, and CRM connection, with a note on how each gets tested.
- QA and accessibility. What gets checked, on which devices, and by whom.
- Launch. Redirects, analytics, search settings, backups, the boring checklist.
- After launch. Who updates it, who watches it, who answers when it breaks at 9 p.m.
That last one is where a lot of “cheap” quotes quietly go missing. The build price might be low because the care price is a blank. If you want a sense of what that part costs, our pricing page lays out ours, and I wrote about what WordPress maintenance actually costs too. Either way, put a number next to it.
What a suspiciously cheap quote probably skipped
I’m not accusing anybody. Some small builds really are small. But when a quote is a fraction of the others, I’d ask:
- Is there a discovery step, or are we starting with a template?
- Who tests the forms, and how do I find out if one stops working?
- What’s in the price for accessibility, and what isn’t?
- What happens in month three when a plugin update breaks something?
- If I leave, do I get the files, the content, and the logins?
You don’t need to be technical to ask these. If the answers are vague, that’s your answer.
Should your quote have come down at all?
A little, yes, in my view. If a team is doing the same project and the repetitive work takes less time, you should see some of that. It’s fair to ask, “What changed in the estimate now that you’re using AI?” A good team will have a real answer, not a shrug.
What I wouldn’t expect is a quote that drops by half because a model can write a layout. The layout was never the expensive part. Knowing what the site needs to do, and what happens when it doesn’t, was.
Before you ask anyone for a new quote, find out where your current site stands. Our free SEO Snapshot shows how you show up in Google and in AI answers right now, and what I’d fix first. Then you’ll know whether that quote is solving a real problem.
If you want to see how we scope this, here’s why we give away detailed project scopes, and here’s our web design work. So, what’s the line in your last quote that you couldn’t explain? That’s the one to ask about.
