Agency, freelancer, or in-house — who should actually build your website?

This decision gets treated like a budget question when it's really an operating question: who is going to own this thing, for how long, and what do you need from them when something breaks at 9pm on a Friday? Price matters, but it's the least useful lens to decide with. Here's what actually distinguishes the three options.

The freelancer

One person, usually wearing every hat — design, build, sometimes copywriting. That's the appeal: direct communication, no account manager relaying messages, and typically the lowest cost for a straightforward brief. The risk is concentration. If they get sick, get busy with another client, or move on entirely, your project (or your site's future maintenance) stalls with them. Vet a freelancer on their actual portfolio and their availability for ongoing support, not just their day rate.

The agency

A team with separate design, development and project management functions, which means redundancy — if one person is out, the project doesn't stop — and typically a broader skill set on tap (SEO, copywriting, ongoing support) without you having to coordinate multiple freelancers yourself. The trade-off is cost and, at bigger agencies, distance: more people between you and the person actually writing the code. A good small studio gives you agency-level redundancy without the layers.

In-house

Hiring a developer or small team as employees makes sense once your website is core, ongoing infrastructure rather than a project with an end date — think a product with a constant release cadence, or a business where the site itself is the revenue engine. It's the most expensive option per hour by a wide margin once you count salary, leave, equipment and management overhead, and it only pays off when there's enough continuous work to keep that person genuinely busy. Most small-to-mid businesses don't clear that bar, and end up with an expensive hire doing occasional tweaks.

Questions that actually settle it

Skip the vibes and work through these:

• Is this a one-off build, or does the site need constant, ongoing development? One-off leans freelancer or agency; constant leans in-house or a strong agency retainer.
• What happens if your main point of contact is unreachable for two weeks? If that's a real problem for your business, you need redundancy — an agency, not a sole freelancer.
• Do you need more than website code — brand strategy, copywriting, SEO, ongoing content? A team covers that under one roof; a freelancer usually doesn't.
• What's your actual budget ceiling, including the years after launch — not just the initial build? In-house salary costs don't stop when the project ends; freelance and agency costs mostly do.
• How much oversight do you want to provide? Freelancers often need more direction on process and project management; a good agency runs that for you.

The mistake worth avoiding

Don't choose based on who's cheapest for the initial build and ignore what happens in year two. A freelancer who vanishes leaves you with a site nobody can safely touch. An agency you never hear from after invoicing isn't actually giving you the redundancy you paid for. Whichever route you pick, ask upfront what ongoing support looks like, who owns the code and hosting access, and what it costs to make a change six months from now — that answer tells you more about the real deal than the quote for the build itself.