Freelance developer vs. agency: which should you hire?

I'm a one-person studio, so read this knowing which side I'm on. The honest answer is that each model is right for different situations — here's how to tell which one you're in.

What you're actually buying

• From a freelancer or solo studio: the time and judgment of one experienced person. You talk directly to the person doing the work, decisions are fast, and there's no markup on anyone else's hours. The whole thing depends on that one person being good — and available.
• From an agency: a team and a process. Strategists, designers, developers, QA, and a project manager coordinating them. You get breadth and capacity, and you pay for the coordination as well as the craft.

When an agency is the right call

• You need many disciplines at once. A rebrand, a content strategy, paid media, and a new site launching together is a team sport.
• The timeline requires parallel work. If the only way to hit the date is several people building simultaneously, one person can't get there no matter how good they are.
• Your organization needs it. Procurement requirements, vendor insurance minimums, and formal SLAs are easier to satisfy with a company than an individual.

When a freelancer or small studio is the right call

• The project is a website or a focused app. Most small-business sites, dashboards, portals, and first-version products are well within one experienced developer's range — and get built faster without handoffs.
• You want the senior person doing the work. At an agency, the person who pitched you is rarely the person building your product. With a freelancer, they're the same person.
• Budget matters. You're paying for engineering, not account management. The same money goes further.
• You'll want changes after launch. A direct relationship with the person who knows your codebase makes small ongoing changes quick and cheap.

The real risks — on both sides

The honest risk with a freelancer is dependence on one person: if they get busy, disappear, or move on, you need to be able to carry on without them. The mitigations are simple and you should insist on them — you own the code and every account from day one, the code is written in mainstream, well-documented technology another developer can pick up, and there's documentation of how things work. I build every project this way for exactly that reason.

The honest risk with an agency is dilution: the senior people sell the project and junior people build it, communication runs through a project manager, and the process that keeps a large team coordinated adds cost and slows small decisions. Good agencies manage this well. Ask who specifically will be doing your work.

Questions to ask whoever you hire

• Who exactly will design and build this? Get names. Then look at what those people have shipped.
• Do I own the code, the domain, and the hosting? The only acceptable answer is yes, from day one.
• Is the price fixed, and what happens when scope changes? A clear scope and a clear change process protect you both.
• What technology, and why? You're looking for mainstream, maintainable choices — and an explanation you can follow.
• What does support look like after launch? Everyone is attentive before the invoice is paid. Ask what the relationship is afterward.

Talk it through

If you're not sure which you need, tell me about the project. Discovery is free, and if it's a job for a bigger team, I'll say so and point you in the right direction.