Guide · Hiring a developer
Freelance developer or agency:how to decide.
A freelance developer is one person who designs, builds and answers for the work; an agency is a team that sells capacity and coordination. Which one fits depends on the size of the project and how much parallel work it needs, not on which sounds cheaper. Here is an honest look at both, including my own limits.
What a freelance developer gives you, and the limits
With a freelancer you talk to the person who writes the code. Questions are answered by someone who knows the answer, decisions do not pass through three people, and the scope is agreed in writing between you and the one who will deliver it. One person is accountable for the result, which is simpler than a team where responsibility is shared.
The limits are just as real. One person has one person’s capacity: work happens in sequence, not in parallel, and holidays or illness pause the project unless that is planned for. A freelancer cannot put five people on a deadline, and an experienced one will say so rather than promise it.
The other thing you get is continuity: the person who designed the data model is the person who fixes it a year later, without a hand-off. That is a strength as long as the source code, the deployment and the documentation are in your hands from the start, so the knowledge does not live in one head only.
What an agency gives you, and what it costs
An agency can run several workstreams at once: design, backend, mobile and testing in parallel, with a project manager keeping them aligned. It has more disciplines in-house, can absorb a person leaving and can scale a team up for a launch. For a large product with a fixed date, that matters.
The costs come with the structure. Overhead is built into every hour, hand-offs between account manager, project manager and developers lose detail, and the senior person you met in the sales meeting is not always the one writing your code. Scope changes take longer to agree because more people are involved.
None of this makes an agency the worse choice. It makes it the right choice for a different kind of project: many features built at once, a fixed launch date, several disciplines needed at the same time. The mistake is paying for that structure when the project does not need it, or expecting one person to provide it.
| Freelance | Agency | |
|---|---|---|
| Who you talk to | The person who builds it | An account manager and a team |
| Scope changes | Direct, in writing | Through a project manager |
| Capacity | One person, agreed capacity | A larger team, parallel work |
| Cost structure | Written quote per project, no fixed packages | Usually higher overhead |
| Best for | Small and medium projects, first versions, integrations | Large teams working in parallel |
Questions to ask a freelancer or an agency
The same questions work for both, and the answers tell you more than the price:
- Who exactly will write the code, and will I speak to that person?
- What is included in the scope, in writing, and what is not?
- How will I see progress: working versions, or reports?
- What happens if the scope changes, and how is that priced?
- Who owns the source code, the accounts and the deployment at the end?
- What documentation is handed over, so someone else could continue?
A vague answer to any of these is a warning, whoever gives it.
Which one fits your project?
Size is the first filter. If the first version can be described on one page and built by one experienced person in sequence, a freelancer keeps it cheaper and clearer. If it needs design, backend, two mobile platforms and testing at the same time, with a date that cannot move, you need parallel hands and someone managing them. Most projects that reach me are the first kind and a few are the second; to those I say no.
Honest rules of thumb, from someone who is one of the two options:
- First version, internal tool
- Freelance. Direct contact, less coordination and a scope that fits in one head.
- Ten people needed at once
- Agency. Parallel teams need management, and one person cannot provide that.
- Fixing an existing system
- Freelance. It rewards one experienced person who reads the code and asks you directly.
- Small start, may grow
- Either. Start with a freelancer, keep code and documentation, add a team when needed.
If your case is not here, describe it and I will tell you which fits, even if it is not me.
How I work as a freelance developer
I have been freelance since 2016, working remotely from Barcelona for companies in Spain and abroad.
The process is the same for every project. A free 30-minute consultation to understand the idea. For suitable projects, a free basic demo with an agreed scope. Then a written scope with features, an estimated timeframe and price, and visible progress: working versions you test yourself, with questions answered by the person writing the code. Everything happens remotely, in English, Spanish, Catalan or German; if necessary, we can meet in person in the Barcelona area. At the end I deploy, document and explain the result, so a team can continue without me.
Questions before we start
Is a freelancer riskier?
The risk is different, not necessarily higher. With one person you depend on their availability, so agree capacity and a plan for absences; with an agency you depend on their staffing and hand-offs. In both cases, a written scope, source code you own and visible progress are what actually reduce the risk.
Can a freelancer hand over to a team later?
Yes. I hand over the source code, the deployment, the accounts and documentation written so another developer can continue. Handover is part of the build, not an extra.
Can I start with a freelancer and grow?
Yes, and it is often the sensible order: a first version built by one person, tested with real users, then a team added when the product needs parallel work. Keep the code and documentation in your hands from the start and that path stays open.
What if I need design, copy and marketing too?
I do design and code, and I write the copy for the pages I build. For a large marketing programme with campaigns, content and advertising, an agency or specialists are the better fit, and I will say so.