If AI can build a website, why pay a web agency? You're paying for responsibility

How reading tools work

Listen reads the article aloud. Speed read shows phrases in sequence at your chosen pace. Language practice compares available translations. Save keeps a bookmark in this browser; find it in the player’s bookmarks. Play this article as Breakout turns its own words into bricks for you to knock out.

Share this article
If AI can build a website, why pay a web agency? You're paying for responsibility
AI-generated image
Advertisement
Advertisement

Easier with this first: The AI Fixed It Overnight. Why Is the Live Website Still Showing Yesterday?

AI has made building a simple website much faster and cheaper, but what an organization really pays a web agency for is someone who handles updates, security, outages, change requests and handover, and who takes the blame when something breaks.

An organization gets a quote for a thin little info site: several hundred thousand yen up front, plus tens of thousands of yen every month for maintenance.

Look at the pages alone and you think:

"Couldn't AI knock this out in no time?"

Honestly, that gut feeling isn't wrong. Copy, layout, mobile-friendly design and a basic contact form now take far less time to build than they used to.

But say "I could build that myself" out loud in that meeting, and a different future opens up:

"Great, then you do it."

And just like that, a website project turns into a lifetime appointment as the organization's unpaid web person.

1. The short answer: AI made building cheaper, not responsibility

What AI has squeezed hard is mostly the building part.

Drafting copy. Planning the structure. Writing the page code. Polishing the look. Producing a bunch of alternative versions.

That really has gotten faster.

But the money an organization pays an outside agency covers more than building:

  • who sorts out what everyone wants
  • who takes change requests
  • who pushes updates live
  • who looks after the domain and the security certificate
  • who makes backups
  • who handles software updates and security holes
  • who brings the site back when it goes down
  • who answers when someone says "the site looks weird"
  • who keeps things running when the staff member in charge quits
  • whose name is on the line saying "that's on us, we'll fix it"

So they aren't just buying page code.

They're also buying the right to dump the whole headache on some agency they've never met.

2. What AI actually made cheaper

For a small info site, AI is really strong.

These jobs, for example, now take a fraction of the time:

  • a first draft of the site layout
  • headings and descriptions
  • color and spacing options
  • making it work on phones
  • the basic page code
  • routine edits
  • tidying up existing text
  • automating a simple publishing routine

So if all you hear is "a few thin pages for several hundred thousand yen," it's natural to think that's a lot.

The trouble starts when you treat build time and contract value as the same thing.

AI can write the code in 30 minutes, and next month's "Please change our opening hours," "Please update the staff list" and "The site won't load?" still show up.

The code got faster.

The people asking for things did not go away.

3. What a web agency is really selling

If you judge a web agency only by the finished screens, you miss most of the job.

For an organization's site, at least these kinds of work can come up.

Figuring out what everyone wants

Someone has to ask who wants what on the site and untangle requests that contradict each other.

An organization is never one person. "The chair said this," "the office says that," "at the last meeting we agreed the opposite" is completely normal.

Hosting and keeping it online

Someone manages the domain, the security certificate, the server, the publishing settings and getting things back up after a failure.

Updates and upkeep

Someone updates the software and building blocks the site runs on and patches security holes when needed.

The U.S. National Institute of Standards and Technology treats software security as something that runs through a product's whole life, not just the time it's being built.[1]

Its guide to managing updates also describes patching as "preventive maintenance" for technology and a cost of keeping a business running.[2]

When something breaks

"It won't open," "the form isn't arriving," "the layout is broken." Someone has to take those calls, figure out what's wrong and fix it.

Handing it over

When the person in charge changes, the domain owner, admin access, how to update the site and the contract details must not vanish with them.

A website doesn't turn into a stone statue the moment it's finished.

If anything, launch day is when its life as something to maintain begins.

4. What a monthly maintenance fee is worth depends on what's included

"Tens of thousands of yen a month" on its own tells you nothing about whether that's expensive or cheap.

If it really means "we pay the server bill and do nothing unless something happens," it might look overpriced.

But if it includes the following, that's a different story:

  • server and domain management
  • regular backups
  • updates
  • security work
  • checking that the site is up
  • first response when it goes down
  • small text edits
  • answering questions from your staff
  • restoring the site
  • moving everything over when the contract ends

The U.S. cybersecurity agency CISA has also pushed hard on the idea that providers stay responsible for their customers' security even after a product ships.[3]

In other words, the thing to compare isn't just "how much a month."

For that monthly fee, who takes on what, how far, and how fast do they respond?

Without that, you can't really compare prices at all.

5. Your own website? Building it with AI is a great fit

A personal site has a beautifully clean setup:

  • who decides: you
  • who builds it: you
  • who breaks it: you
  • who fixes it: you
  • who loses out: you

It's all you.

Break the design at midnight and you can just say "eh, I'll fix it tomorrow."

You get to decide whether an hour of downtime is fine, how many backups you need, and whether to just ditch that annoying feature.

In that situation, AI's speed turns straight into a win for you.

If you do everything yourself, you also take all the responsibility yourself.

Who decides and who's responsible are the same person.

That's a strong position.

6. The worst setup when you run someone else's organization site

The dangerous version looks like this:

  • who does the work: you
  • who decides: other people
  • who asks for changes: several people
  • who gets blamed in the end: somehow, you
  • pay: sometimes just "goodwill"

This isn't a tech problem.

It's a hellish triangle where all the responsibility gets boiled down onto you.

"It's just changing one word, right?"

"It's just adding one photo, right?"

"With AI that's instant, right?"

Each of those really does take no time on its own.

The real question is who approved that one change, who undoes it if it's wrong, who checks it after it goes live, and whether the next request lands on the same person again.

A 5-minute fix can suddenly turn into a five-year help-desk contract.

7. When AI makes the work easier, the requests can actually pile up

This part is a little ironic.

In the past, a change would stop at "hiring someone costs money, so let's save it up for next time." Once there's someone nearby who uses AI, it turns into:

"You can fix that easily, can't you?"

Time per request goes down.

But the number of requests goes up.

Once building stops being the bottleneck, the next jam is approvals, messages back and forth, priorities, explaining, and who's responsible for what.

Even if AI makes writing code 10 times faster, the committee doesn't make decisions 10 times faster.

The machines move into the future, and the meetings stay exactly where they were.

8. Before deciding whether a quote is too high, ask these questions first

When you look at a quote for a website, "this many pages for this much money" isn't enough.

At minimum, check these separately.

Building the site

  • number of pages
  • how much of the writing they do
  • how polished the design is
  • mobile support
  • contact form
  • tools for updating content yourself
  • member areas or logins
  • moving over existing content
  • accessibility work
  • basic setup for showing up in search

Monthly maintenance

  • are server and domain costs included
  • how often backups are made
  • updates and security fixes
  • monitoring for outages
  • how you contact them when something breaks
  • how many hours or business days they take to respond
  • how many text edits a month are included
  • how much it costs to add photos or pages
  • whether fees for outside services are included

When the contract ends

  • whose name the domain is registered in
  • whether you get all the source files
  • whether admin access can be handed over
  • whether you can move to another company
  • whether the site disappears when you cancel

If after all that there's almost nothing included and the price is still high, it's fair to ask, "What exactly are we paying for?"

On the other hand, if maintenance, outages, updates and handover are all clearly covered, that's a different product from a simple "fee for a few pages."

9. When to build it yourself and when to hire an agency

Building it yourself with AI works well when:

  • there's basically one person making decisions
  • nothing terrible happens if the site goes down
  • it rarely needs updating
  • it handles little or no personal or member data
  • you can back it up and restore it yourself
  • you can cut features if they become a pain
  • you're willing to keep maintaining it yourself in the future

Hiring an agency becomes worth more in the opposite cases:

  • lots of people are involved
  • wrong information on the site would hurt your reputation
  • it needs regular updates
  • someone has to answer questions and requests
  • security work has to keep going
  • the site has to survive staff changes
  • it would be a problem if nobody clearly knows who fixes it when it breaks

So don't decide on technical difficulty alone.

When it breaks, who picks up the phone?

Factor that in when you choose between doing it yourself and hiring someone.

10. In the end, people pay less for code than for a name to call

AI has definitely brought down the cost of making a website.

So if an agency still builds sites the old way and charges the old prices, it's fair to expect those prices to be questioned.

But you can't jump from there to "web agencies are all unnecessary."

Maintenance, updates, recovery, answering questions, security, coordination, handover.

That work is still there even when the page code appears in an instant.

If it's your own site, go ahead and do it all yourself.

You're taking all the responsibility anyway.

But on someone else's organization site, saying "AI could build that in no time" can turn into a free, never-ending maintenance contract.

That's why sometimes quietly paying the agency fee is the sensible move.

You're not buying several hundred thousand yen worth of code.

You're buying a world where, when the late-night "The website won't open" message comes in, someone other than you picks up the phone.

References (3)

  1. NIST, Secure Software Development Framework (SSDF) Version 1.1: https://csrc.nist.gov/pubs/sp/800/218/final
  2. NIST, Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology: https://csrc.nist.gov/pubs/sp/800/40/r4/final
  3. CISA, Under the Digital Radar: Defending Against People’s Republic of China’s Nation-State Cyber Threats to America’s Small Businesses: https://www.cisa.gov/news-events/news/under-digital-radar-defending-against-peoples-republic-chinas-nation-state-cyber-threats-americas

AdBooks on this topic

This article contains affiliate links (ads). About advertising As an Amazon Associate I earn from qualifying purchases.

If this article helped you, you can support the site. Support

Advertisement
Advertisement
Advertisement

One more? Anything fun?

Since you're done reading: a couple of nearby stories and some totally different, fun ones.

  1. NearbyIs 6 million yen a high salary?Why "all my friends earn it" misleads
  2. Is the Dancing Rumpelstiltskin From an Old Movie?The VHS Tape That Never Existed
  3. Totally different, but funSix Wins With Set 9 Aggro NightmareWin by Turn Six, Except Against Pirates
  4. Why are kids so energetic?How "bored, so run" shifts with age
  5. 40 Human Pageviews, 281,000 Bot RequestsA Blog Awaiting Ad Review
  6. Why the Flowers of Evil ending theme "Hana" sounds so unsettling

Read this today

Each one answers a question readers of this article tend to ask next.

Browse all articlesMore on AI

Find other articles

All articles

Mendoi-chan

Who runs this site

Mendoi-chan

She turns friction at work and in everyday life into clear structure and practical next steps.