The short answer is no. That answer is worthless on its own, and every page giving it knows why: it only holds if you first say what AI did take, and almost nobody wants to say it.
So here it is. If your offer, written out honestly, is "I will make you a tidy website from your description," that offer has been eaten. Not weakened. Eaten. A coding agent produces a competent, responsive, decent-looking page from a clear description in minutes, and the client can watch it happen. No paragraph about human creativity changes that, and the pages that answer this question with a flat no and stop there are being polite with you rather than useful.
What was not taken: deciding what the site is even for and whose problem it solves. Looking at five outputs and knowing which one is right and why. Sitting with a client who cannot yet say what they want. And the plain fact that when the site breaks on a Friday evening, someone calls a person, not a model.
The job moved. It moved from making the thing to specifying it and judging it. You are the creative director now, and your prompt is the brief. That is excellent news if you can write one, and a genuine problem if the brief was always the part you skipped.
What AI actually replaced
An inventory, without the softening. These are things people were paid for in 2023 and are largely not paid for now:
- Fitting a template to a client's content and making it look intentional.
- "Make it like this competitor's site, but ours."
- The first draft of the copy. Not the good copy. The draft that used to take an afternoon.
- Basic responsive layout, including the breakpoints, the stacking order, and the mobile menu. Real skill, thoroughly automated.
- Choosing a serviceable grid, type scale, and palette when nobody has strong feelings about any of them.
- The third round of "move it up a bit."
That list is not marginal. For a lot of freelance web design it was most of the invoice. Pretending it survived is how you end up quoting for work the client already knows they can get for nothing.
One boundary, because the two questions get mixed constantly: this is about web design, not web development. Whether AI replaces the person building an application with a database and accounts behind it is a different argument with different evidence. Here we are talking about the commercial site, the landing page, the one-page brochure for a business that already knows what it sells.
Which tool produces that page, whether a builder, an agent, or the thing you have used for six years, is a genuinely separate decision, and it is not the one that decides what you are worth.
What it did not touch
The surviving work is not a list of virtues. Creativity, empathy and strategic thinking are not units of work and nobody invoices for them. These are units of work.
Deciding what the page is for
Every site starts with a decision that has nothing to do with layout: whose problem does this solve, and what single thing should a visitor do. That decision is most of what UX actually is, long before anyone draws a wireframe. A model does not make it. It either receives it from you or substitutes the average of everything it has read, which is exactly why so many generated pages feel like a competent answer to a question nobody asked.
Knowing which of five outputs is right
Generating five variations is now free. Choosing correctly is not, and the two skills were never the same one. Anyone can ask for options. Far fewer people can look at them and say which serves the visitor, and defend it to a client who prefers the other one.
The conversation with a client who does not know what they want
Half of any brief is extracted, not submitted. It comes from asking a builder why his enquiries dry up in January, or noticing that a physiotherapist's real competition is not the clinic down the road but people deciding to wait and see. That happens in a conversation. It is not in the intake form, and it is not in the prompt.
Everything after "it looks done"
The page existing is not the project finishing. It needs an address, a domain the client owns, a way to be changed in March, and someone accountable for all three. This is where most of the remaining hours live, and it is the stage the speed conversation skips entirely. The arithmetic of what the 10× actually does to a project is its own piece.
Your prompt is the brief
The difference between a prompt and a brief is not length. It is composition. A brief says who the reader is, what one action matters, what is actually being sold, what must not appear, in what tone, what counts as done, and what is out of scope. The average prompt contains none of those, which is why the average generated site looks like the average generated site. Smaller decisions inherit the same problem: ask for "a good title" and you get one of four different things that go by that name.
If you want that composition as something you can paste rather than compose from scratch, the six website prompts are the same idea in copyable form, and the last two of them end at a live address.
Here is what one looks like written out in full, for a solo physiotherapist's single page. Not a template to fill in, but the actual text:
Reader. Someone in town with back or knee pain who has already decided to see someone. On a phone, usually in the evening, usually mildly anxious.
One action. Book a first appointment: tap the phone number, or open the booking calendar. Nothing else on the page competes with this.
What we are selling. An appointment this week, with evening slots. Not twenty years of experience. Everyone claims that and nobody is choosing on it.
Above the fold. What she treats, which town, the price of a first session, the booking action. In that order.
Must not appear. Stock photography of smiling strangers. A mission statement. A slider. The word "holistic."
Tone. Plain and calm, no exclamation marks. She is a clinician, not a brand.
Constraints. One page. No enquiry form, because booking goes to her existing calendar link. Her existing green, which she likes and is not changing.
Done means. A stranger on a phone can tell within five seconds whether she treats their problem, and can book without scrolling twice.
Out of scope. Blog. Testimonials, until there are three real ones.
Now compare that with "build a modern website for a physiotherapist," which is what most people actually type. Same model, same afternoon. Everything that distinguishes the two results was decided before either of them ran, and none of it was decided by artificial intelligence.
Notice too how much of that brief is unguessable: the green, the evening slots, the banned word, the reason testimonials are excluded. None of it is inferable from the industry, and no amount of user research done by a model would have produced it. It came out of a conversation with a person. That is the part of the work nobody has automated, and it is now the part that determines the output.
Taste is the deliverable now
Taste sounds like an aesthetic quality. In this job it is operational: it is being able to say what is wrong in words the agent can act on.
"I don't like it" is not a brief. "The headline promises efficiency and the page sells reassurance, so the visitor is being sold two different things" is a brief, and it produces a fix on the next pass. The skill is diagnostic before it is aesthetic. See the problem, name the cause, phrase the correction. That is what an art director has always done. It just used to be applied to a junior designer's work instead of a model's.
If the diagnosis is merely “make it cleaner,” use the five testable clean-design rules to name the hierarchy, spacing, type, color, or action conflict before asking for a change.
This is also the whole defence against generic output. AI tools do not produce slop on their own; they produce the average of what they were asked for. We read thirteen rival blogs to find where the line falls, and it fell exactly there: published without a standard, not made with AI. A page looks templated when nobody upstream was willing to reject the first thing that appeared. Every workflow that works with these tools has the same shape. It goes specify, generate, reject, re-specify, and the two steps that decide the result are the ones a person does. Rejection is the job now, and it is uncomfortable precisely because the first thing that appears is usually fine.
Nobody pays a model when the site goes down
Here is the argument the other answers to this question leave out entirely, and it is the sturdiest one, because it is not about skill at all. Every article promising that human designers are safe argues it from talent. The more durable reason is structural.
A client is not buying a layout. They are buying somebody who is answerable for a live site. Whose domain is it. Where does it live. Who rolls back the change that broke the pricing section. Who replies when a phone number is wrong and the client is annoyed. Those questions have to resolve to a person, and no amount of capability on the generation side changes who that person is.
That is also why the work does not end at a good-looking page. A published artifact in a chat is a link on somebody else's domain, not something a client owns. A domain has to actually be pointed at the site, which is a half-hour of work and a wait nobody controls. And a year later, someone has to be able to change one line without republishing everything.
Handling that competently is not a lesser version of design work. For most clients, it is the part they will actually remember.
What the numbers say, and what they do not
You will be shown percentages. It is worth knowing where they come from before you take comfort or fright from them. We did that exercise once for the most-quoted vibe coding statistic, and it is worth doing here too.
One of the pages ranking for this exact question opens with a key takeaways box listing, among other things, that eighty percent of repetitive design work is automatable, attributed to McKinsey, and that forty-five percent of designers expect demand for basic work to fall by 2030, attributed to a Creative Bloq survey. Another page ranking alongside it states that ninety-three percent of designers use AI tools daily, and that consumers will pay sixty percent more for human-intentional design. None of those arrive with a study title, a sample size, or a date. They arrive as a number and a brand name, which is enough to be repeated and not enough to be checked.
We are not going to add to the pile. The US Bureau of Labor Statistics does publish an employment projection for web developers and digital designers, and it is the one genuinely authoritative figure in this conversation. We could not open its page to quote the number exactly, and we are not going to reproduce it from memory or from somebody else's blockquote, so it is not in this article. If you want it, take it from the Occupational Outlook Handbook directly.
An occupational projection counts employed job titles over a decade, using data gathered before the current shift. It does not measure what a solo freelancer can charge for a five-section brochure site this quarter. Even a perfectly sourced figure would be answering a different question than the one you are actually asking.
The honest position is that nobody has a reliable measurement of this yet, and the pages implying otherwise are decorating an argument they had already decided. What you can observe without a statistic: what clients now expect to pay for a simple page, and how quickly they stop asking who made it. If the pay question is yours to answer this quarter, the ranges freelancers actually report, and the margin math behind them, are a better starting point than any percentage above.
What this changes about how you work
Four things follow, and none of them is "learn prompting."
Write the brief before the first prompt. Keep a template with the fields above and fill it in every time, even for a small job. It is now the highest leverage document in the project, and it doubles as the thing you show a client when they ask what they are paying for.
Sell specification and judgement, not production hours. The hours you can defend are the ones spent deciding and rejecting. Production is no longer where your value sits, and quoting as though it were invites exactly the comparison you do not want. What that means for an actual rate card deserves its own article, and this is not it.
Own the last mile. Publishing, the domain, the ability to make a change later. That is what turns a folder of files into a delivered project, and it is the part clients keep paying attention to. Handing over a zip file is how you become invisible.
Be able to explain the difference. When a client says "can't AI just do this," the answer is not defensive. It is: yes, and here is the brief that made this version better than the one you would have got. Show them the brief. It is more convincing than any argument about creativity.
Where Birta fits
Birta is only involved in the last item on that list, so it is worth being exact.
A connected agent publishes the finished site straight to a live HTTPS address, and publishes again after each round of changes, without a repository or a build pipeline in between. Edits go file by file through the same connection, so changing one line does not mean republishing the site. Images and fonts travel with it; video and PDFs still need a public address elsewhere. Each publish is kept as a version and the last ten stay available to roll back to. You can point a client's own domain at it with HTTPS, and each project has its own analytics. The connection itself is MCP, explained without the infrastructure vocabulary, and it is authorized in the browser once rather than per project.
What it does not do is the rest of the job. It will not write the brief, sit through the approval round, or decide which of the five versions is right. That is still the work, and it is still yours.
Own the last mile of the work you directed
Publish the finished site from the same conversation you briefed, update it a file at a time, roll back a bad change, and point the client's domain at it.