Freelancer vs agency vs in-house developer: which is right for your project?

The three options at a glance

When a freelancer is the right call

• The project is clearly defined: a landing page, a theme customisation, a specific integration.
• One skill covers it, such as WordPress development or design.
• You (or someone on your team) can write a brief, review the work and make decisions quickly.
• You've seen their previous work, live, and spoken to a past client.

The main risk is continuity. If the freelancer gets busy, ill or moves on, work stops, and knowledge of how your site was built leaves with them. Protect yourself with documentation, code in your own repository, and accounts in your company's name.

When an agency makes more sense

• The project needs design, development, content and testing together.
• You want one party responsible for the whole result.
• You need ongoing maintenance and someone to call when something breaks.
• You don't have time to manage individual people.

Agencies cost more per hour because you're paying for a team, project management and cover. The risks are being passed to junior staff without knowing, and paying for process you don't need on small jobs. Ask who will actually work on your project.

When to build an in-house team

• Software is your product, or so central to operations that it changes weekly.
• There's enough work to keep developers busy all year.
• You can hire, manage and keep technical people, or you have a technical leader who can.

In-house gives you the deepest knowledge of the business and the fastest response. It's also the most expensive and slowest to set up, and one developer alone is a single point of failure, just like a freelancer.

Five questions that usually decide it

1. Is the work a project or permanent? Projects suit freelancers and agencies; permanent work leans in-house.
2. How many skills does it need? One suits a freelancer; several suit an agency or a team.
3. Who will manage it? If nobody on your side has time, choose the option that manages itself.
4. What happens if the person leaves? Plan for that from day one.
5. What can you afford every month, not just once?

Mixed models that work well

• Agency builds, freelancer maintains: fine if the agency hands over documentation and access.
• In-house product owner, external team builds: someone inside the business makes decisions; an agency or offshore team does the work.
• Offshore agency as an extension of your team: common for businesses in the US, UK, Europe and the Gulf working with teams in India. We wrote about doing this well in hiring a web development team in India from the USA.

Whoever you choose, protect yourself

The same safeguards apply to all three: a written scope, milestone payments, code and accounts in your company's name, documentation, and regular visible progress. Our guide on how to hire a web developer without getting burned lists the questions to ask before you sign.

Other things people ask

Are agencies always more expensive? Per hour, usually. Per project, not always: a team that has built similar things before can finish faster, and a single freelancer learning on your project may take longer.

Can I start with a freelancer and move to an agency later? Yes, as long as the code is in your repository, the accounts are yours, and there's enough documentation for someone else to pick it up.

Should my first technical hire be a developer? If you'll build a team, a senior person who can make technical decisions and manage outside help is often more valuable than a junior developer.