Guide · Hiring a developer
Freelance developer or agency: how to decide.
A freelance developer usually works directly on your project; an agency can assign a team with several specialisms. The right choice depends on scope, availability and how much work must happen at once. This guide explains what to ask both, including the limits of working with one person.
What a freelance developer gives you, and the limits
With a freelancer you normally talk to the person who writes the code. In my projects, you discuss questions and changes directly with me, and we agree the scope in writing. You have one point of contact who is also responsible for the implementation.
One person has limited capacity. Development usually proceeds in sequence, and holidays or illness need a plan. If several specialists must work at the same time, check whether the freelancer has suitable collaborators or whether an agency would fit better.
The other thing you often 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 often 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.
Team coordination and project management contribute to the cost. Ask who will write the code, how you will communicate with them and how changes are approved. These arrangements vary between agencies, so confirm them in the proposal.
An agency may suit a project that needs design, development and testing in parallel. Compare the assigned team and delivery plan with the work required, rather than assuming either type of supplier is always better.
| Freelance | Agency | |
|---|---|---|
| Who you talk to | Usually the person who builds it | Often an account manager and a team |
| Scope changes | Direct; I confirm changes in writing | Often through a project manager |
| Capacity | One person, agreed capacity | A larger team, parallel work |
| Cost structure | Written quote per project, no fixed packages | Includes team coordination and project management |
| Best for | Small and medium projects, first versions, integrations | Large teams working in parallel |
Before choosing who builds it, decide whether to buy or build the software.
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.
To compare proposals with the same scope, first understand what determines the cost of an app.
Which one fits your project?
Consider both the size of the project and its schedule. A first version that one experienced person can build in sequence may suit a freelancer. If design, backend, mobile development and testing must happen together, look for a team with that capacity. I discuss those requirements before accepting a project.
These examples can help you compare the options:
- First version, internal tool
- A freelancer may suit a defined first version with direct communication.
- Ten people needed at once
- Agency. Parallel teams need management, and one person cannot provide that.
- Fixing an existing system
- A freelancer with relevant experience may be suitable; check the scope and availability.
- 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.
If the first release is still unclear, consider whether your idea needs a demo, a prototype or an MVP.
How I work as a freelance developer
I have been freelance since 2016, working remotely from Barcelona for companies in Spain and abroad.
First we discuss what you need, by message or in a free consultation. If a basic demo would help, we agree what it will cover; that demo is free. Before the full build, you receive a written scope, estimated timeframe and price. During development, you test working versions and discuss questions directly with me. We can work remotely in English, Spanish, Catalan or German, or meet in the Barcelona area when needed. I deploy, document and explain the result so another developer can take over if necessary.
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.