Should we use a website builder or hire a studio?

When a builder is the right choice

For a lot of situations, a builder is the sensible answer, and paying for a studio would be paying for capacity you don't need yet. Modern builders are fast to stand up, cheap to run and capable enough that the result doesn't look homemade. If the site is a starting point rather than an engine, that's usually enough.

A builder tends to be the right fit when:

• It's your first site and you just need to be visible.
• It exists for a single moment: an event, a launch or a campaign that ends.
• It's a side project or a small business where the budget is tight.
• You're testing an idea and want to learn before you invest.
• The content is small and stable, and one person can keep it current.
• You don't expect the structure to change much over the next year or two.

None of that is a compromise. Getting something live and learning from it beats waiting for a bigger build you're not ready to brief.

Where builders start to cost you

The strain rarely shows up on day one. It shows up six or twelve months in, when the site has a job to do and the tool starts working against you. The costs hide in time and frustration, so they never show up on an invoice.

• A marketing person can't update the content without nudging the layout out of shape, so edits stall or go through one nervous gatekeeper.
• There's no content strategy underneath, so pages just pile up.
• SEO gets harder, with less control over structure, markup and performance, and templates that weren't built with search in mind.
• Growth turns messy: new sections get bolted on, navigation swells and the original tidy template stops holding.
• Accessibility and governance are hard to guarantee, which matters more as the audience and the legal exposure grow.
• The brand drifts, because the guardrails live only in one person's judgement.

Any one of these is survivable. Several at once is usually the signal that the website has become infrastructure, and it's being run on tools meant for something lighter.

What a studio adds

The honest difference is judgement, and a system that stays easy to run. A good build is a set of decisions made once, carefully, so the hundred smaller decisions afterwards become simple. You're buying the structure as much as the surface.

• A CMS your own team can run day to day, so updates don't depend on us or on one person's nerve.
• A content structure that holds as you add pages, sections and campaigns.
• A brand that scales cleanly across every template.
• Content and SEO that stay organised because the foundations were built for them.

That's the same principle behind our QC Process: the work is finished when it keeps working after we leave the room. Part of that is the tooling itself, which is why we tend to reach for a proper CMS. We've written about why we like Craft CMS for sites that have to earn their keep.

A quick way to tell which side you're on

You don't need a scorecard. A few honest questions usually settle it. If most of your answers point one way, that's your answer, and neither answer is a failure.

• Who needs to update this site, and how often? One person occasionally leans builder; a team regularly leans studio.
• How many people have a say in it? A single owner is simple; several stakeholders need a structure that can hold competing needs.
• Does search matter to the business, or is the site mostly a brochure people are sent to?
• Do you expect it to grow in ways you can't fully picture yet, or is the shape of it settled?
• What does a wrong turn cost you? A small site can be redone; a site the business runs on can't be casually torn up.

There's no shame in choosing a builder, and no glory in over-buying. The mistake is only ever a mismatch: running a serious website on a light tool, or paying studio rates for a page that could have been a template. We've made the fuller version of this argument in Some things shouldn't be DIY, but the short version is simply to match the tool to the job the site has to do.