DIY is fine, until the website has a job

We tell people to use Squarespace all the time. Grab a template, spin up a builder, get the thing live. We mean it.

The tools are genuinely good now. They are cheaper, they are faster, and for a lot of businesses at a lot of stages they are the correct call. A new venture testing an idea does not need a studio. A side project does not need a design system. A café that mostly wants an address, a menu and a phone number is not being underserved by a template. It is being served exactly right.

So this is not the usual agency speech about how you should never touch a builder. You should. Often. We would rather you spent the money when it starts to matter than burned it before it does.

The question is never whether you can build it yourself. It is whether you will want to live with the result.

Here is the turn. The tools did not get worse. Your situation got more demanding. The site that was perfectly fine at launch did not degrade on its own, you simply started asking more of it, and it was never built to carry the load.

The trouble almost never shows up on day one. It shows up months later, when the website quietly stops being a brochure and becomes part of how the business actually runs. That is the moment the seams start to show.

A CMS update breaks the layout, and nobody is sure why.
There was never a content strategy, just pages that accumulated.
SEO gets harder because the structure fights you instead of helping.
Growth gets messy, because there is nowhere clean to put the new thing.
Accessibility and governance stop being optional and start being risk.
The brand drifts a little with every rushed edit.

None of that is a template failing at what it was for. It is a template being asked to do a job it was never optimised for.

A template is optimised for the first day. A business needs the next five years. Those are not the same brief, and the gap between them is where most of the pain lives. The first day is a beauty contest. The next five years are a maintenance question.

That maintenance question is really a content-management question. When a care organisation has services, teams, referrals and regions that all change on their own schedule, the site has to be something a non-technical person can update on a Tuesday without breaking the layout or the brand. That is why we tend to build on a real CMS, and why we like the content system underneath more than we like a clever template. It is less impressive in a screenshot and far kinder in year three.

So what are you actually buying, when you decide the DIY version has run out of road? Not a nicer template. Not a prettier hero. Something quieter than that.

You are not buying a website. You are buying the decisions it makes easier.

Better decisions later, made faster, because the structure already accounts for them.
Less friction every time you want to change something.
A CMS people are actually happy to open.
A brand that scales without a rebuild.
Content that stays organised instead of accumulating.
A site that gets easier to run over time, not harder.

That is the difference nobody puts on the sales page, because it does not photograph well. A considered site is one that keeps making the next decision cheap, long after launch day is a memory.

From the shelf

Design is not just what it looks like and feels like. Design is how it works.

The honest difference is not features. Both a builder and a studio can put a nice-looking page on the internet. The difference is judgement: knowing which structure will still make sense when the business is twice the size, which shortcut becomes a trap, which page you should not build at all.

AI turned making a website into something close to trivial, which is exactly why a considered one now stands out. When anyone can generate a passable site in an afternoon, the value moves to the part the machine cannot fake: the judgement about what should exist, how it should be structured, and what it is quietly asking your team to maintain forever.

We are not here to talk anyone out of a builder. If you want a plainer version of this argument, it is over there. Some things should not be DIY, and some things absolutely should. The whole skill is knowing which is which.

If you are clearly at the template end, use the template and spend the saving somewhere it earns more. If your site has quietly picked up a job, and you can feel it straining against the thing you built it on, that is worth a proper look.

And if you are somewhere in the middle, unsure which one you are, that is a good place to start a conversation.