I Get Asked This a Lot Right Now
Usually it's a client, sometimes it's a friend who runs a small business, and lately it's shown up in my own head at 11pm more than once: is AI going to make what we do irrelevant? I'm not going to pretend that's a silly question. It isn't. AI can spin up a decent-looking landing page in about the time it takes me to finish a cup of coffee. It can write website copy that's genuinely fine. It can do a basic SEO pass that used to take a junior marketer a full afternoon. If your mental model of "web design" is "someone builds pages and writes words for them," then yeah, a big chunk of that job is already being eaten, and it's going to keep going.
But that's not actually the question that matters for a business that depends on its website, and I want to walk through why.
Building a Site and Running a Site Are Two Different Jobs
Here's the distinction I keep coming back to. Building a website — the design, the layout, the copy, the initial SEO setup — is a project with a beginning and an end. It's task-based work, and task-based work is exactly what AI tools are good at and getting better at every single month. I don't think that's controversial, and I don't think it's worth arguing with.
Running a website is a different job entirely. It's not a project, it's an ongoing responsibility. Someone has to decide whether this WordPress core update is safe to apply to your specific site with your specific plugins, or whether it needs to sit in staging first. Someone has to notice when a plugin update quietly breaks your checkout page at 6am on a Saturday. Someone has to be the person you call when the site goes down during your busiest week of the year, and someone has to already know your setup well enough to fix it fast instead of starting from zero. That's not a task. That's a standing responsibility, held by an accountable party, for as long as the site is live.
AI Doesn't Take Responsibility. It Can't.
This is the part I think gets missed in a lot of the "AI is coming for your job" conversation. AI can generate an answer. It can even generate a very good answer. What it can't do is be the party that's on the hook when the answer turns out to be wrong. If an AI-suggested plugin update breaks your site, there's no AI to call, no AI you can hold to a service agreement, no AI that shows up accountable in front of your board or your compliance officer. A person has to own that outcome. That's true today and I don't see a version of the next few years where it stops being true, regardless of how good the models get.
That's actually the whole idea behind WebOps as a discipline, and it's worth being direct about it since it's the term I use for what we do: it's not web design, and it's not really "maintenance" in the small sense people usually mean. It's the same relationship DevOps has to software development — development builds it, DevOps is the discipline of keeping it running, safely, in production, with someone accountable for every change. WebOps is that same discipline applied to WordPress. Nobody's worried DevOps is getting automated out of existence just because AI writes code faster now. Same logic applies here.
Where I Think This Actually Bites
I want to be honest instead of just reassuring, because I think the "AI can't replace human judgment" line gets said too easily and too often without anyone specifying where the line actually falls. Here's my honest read: the freelancer or small agency whose whole offer is "I'll build you a site" or "I'll write your blog posts" is in real trouble, and I don't think that's an exaggeration. That's task-based labor, it's commoditizing fast, and a business owner with a decent AI tool can increasingly do a passable version of it themselves for a fraction of the cost.
What doesn't commoditize as fast is anyone whose value is being accountable for an outcome, not just producing a task. A financial advisor's compliance obligations don't disappear because AI can generate a form. A law firm's malpractice exposure doesn't shrink because AI can write a landing page. If your website supports a business where being wrong actually costs something — a missed filing deadline, an exposed client record, a checkout that silently breaks during your highest-revenue week — then the question was never really "who can write the copy fastest." It was always "who's accountable when this goes wrong," and that question doesn't have an AI-shaped answer.
Where We Actually Use AI Ourselves
I'll say this plainly since I'd rather be straight about it than pretend we're some kind of AI holdout: we use AI tools where they genuinely help us move faster on the task-level work — drafting, research, first passes at content. What we don't do, and won't do, is let an AI push an unsupervised change to a client's live production site. Every change still goes through staging, gets tested, and has a person's name attached to the decision to deploy it. That's not us being behind the curve. That's the actual product we're selling — the accountable layer sitting on top of the tools, not instead of them.
So, Will AI Replace Web Design?
Some of it, yes — probably faster than most people in the industry are comfortable admitting out loud. But "web design" was never the whole job for a business whose site actually matters to its revenue or its compliance obligations. The part that was always worth paying for — someone accountable, watching, testing, and answering for what happens to your production environment — isn't a task an AI can pick up, because it was never a task in the first place. It's a relationship. That's the part of this business I think gets more valuable from here, not less.
