Building a website got easy. Finishing one didn't.

You can describe the website you want to an AI tool and get a working version back in an afternoon. Design, front page, contact form, the lot. It looks finished.

So what are you actually paying for, if you hire someone to build?

The uncomfortable first answer is: often nothing. Most businesses don't need a custom website. A template in Squarespace, Wix or WordPress covers it — a clean front page, a bit about what you do, a form people can send in. An advisor who's honest says so out loud. Building something bespoke for a job a template already solves is charging for work that isn't needed.

But there's a point where the maths flips.

It's when the website stops being a brochure and starts being a system. Customers log in and see their own numbers. A clinic takes bookings and appointments. Data has to flow between the website and the accounting system. At that moment it's no longer about how it looks. It's about what happens under the surface.

And this is where it gets interesting: the demo is the easy part.

What you see — the design, the pages, the polished front page — is maybe 20 percent of the job. The 80 percent you don't see is what decides whether the thing holds when someone actually uses it. That customer A can't see customer B's numbers. That a backup exists, and that someone has actually tried restoring it. That you're told when something breaks, instead of hearing it from an angry customer. That personal data is handled the way the law requires.

None of that shows up in a demo. A demo shows that it looks good on the screen of the person who made it. It says nothing about what happens the day a thousand people use it at once, or the day someone comes at it on purpose.

That's exactly where the new AI tools fool people.

They generate something that looks finished but isn't. It has already happened in practice: apps built this way have been shipped with the database left wide open — anyone could pull out every customer's details. It looked finished. It worked in the demo. Only the foundation was missing.

I build these things myself, and what takes time is never the front page. It's everything else: setting up access control that actually keeps customers apart, testing that the backup can be restored, making sure a failure stops safely instead of leaking something it shouldn't. Boring work. It's also the only thing separating a real solution from a nice-looking demo.

"It looks finished" is not the same as "it's finished." The difference is invisible right up until it isn't — and by then it's usually expensive.

So what are you actually paying for?

Not the building. That's got cheap. You're paying for the judgment: knowing which of the two situations you're in, and — if you genuinely need something custom — getting the invisible layers in place before you let customers in.

It depends on what your website is meant to do. If it just needs to tell people who you are, buy a template and spend the money somewhere better. If it's going to handle your customers' data, the question isn't whether it looks finished.

The question is whether it is.