Build log/Working with us

Agency, freelancers or an in-house team: choosing who builds your product

Agencies give you a complete team quickly, freelancers give flexibility with less overhead, and an in-house team gives long-term control. Many products use more than one over their life.

The short answer

  • An agency or studio supplies a complete team, including design, development, testing and project management, under one contract, which is usually the quickest way to start but costs more per day than individual freelancers.
  • Freelancers usually cost less per day and are flexible, but you take on the coordination yourself, and continuity depends on particular people staying available.
  • An in-house team is the slowest and most expensive option to set up and builds knowledge the company keeps; a common path is to start with an agency and move work in-house as the product proves itself.

The three ways to get a software product built are an agency or studio, freelancers, or your own in-house team, and each trades cost, speed, risk and control differently. An agency provides a ready-made team under one contract. Freelancers are individual contractors you coordinate yourself. An in-house team is employed by you. The right choice depends mostly on how central the software is to your business and how long it will need active development.

The three options compared

Agency or studioFreelancersIn-house team
Cost structureDay or project rate covering the team, management and overheadsDay or hourly rate per personSalaries plus employment costs, paid whether or not there is work
Speed to startQuick, because the team already existsQuick for one person, slower to assemble severalSlow, because hiring takes time
Range of skillsDesign, web, mobile, testing and operations in one placeWhatever you hireWhatever you hire and can keep busy
Management loadLow, the agency coordinatesHigh, you coordinateHigh, you manage and develop people
ContinuityDepends on the agency and on handoverDepends on individualsStrong, while people stay
Ownership of codeMust be assigned to you in the contractMust be assigned to you in the contractYours, for work done in the course of employment

Cost structure

Comparing day rates alone is misleading. An agency’s rate covers project management, design, testing, holidays, equipment and the cost of finding and training people. A freelancer’s rate covers their own time, and the coordination falls to you. An employee’s salary is only part of what they cost. The full cost of an in-house developer includes the items below.

  • Salary.
  • Employer’s National Insurance contributions.
  • Workplace pension contributions under auto-enrolment.
  • Recruitment fees, or the time spent hiring.
  • Equipment, software licences and training.
  • Management time, and the cost of the team during quieter periods.

In-house becomes cheaper per day of work when there is a steady, long-term stream of development. For a burst of work followed by quieter maintenance, an agency or freelancers usually cost less overall.

Speed and risk

An agency can usually start within weeks, because the team exists. Hiring an experienced developer can take months once you count advertising, interviews, notice periods and getting up to speed. A single freelancer can start quickly, while assembling and coordinating several takes time and skill.

The risks differ too. With an agency, you depend on one supplier, so the contract, the repository and the handover terms matter. With freelancers, the main risk is key-person dependency, where one person holds knowledge nobody else has. With an in-house team, the risks are a poor hire and gaps in skills, because a small team rarely covers design, backend, mobile, testing and operations equally well.

Continuity, knowledge and ownership

Keeping the knowledge

Whoever builds the product, the knowledge needs to outlive them. Insist on the code being in a repository your company owns from day one (you get the repository), with documentation, automated tests and a deployment process someone else can run. These make it possible to change supplier, bring work in-house or rescue a project that has stalled (taking over a stalled project).

Ask any supplier how they would hand the product over if you parted ways, and what you would have on the last day. A good answer is specific. It covers the repository, hosting accounts, credentials, documentation and a few days of overlap with whoever comes next.

Who owns the code

Under the Copyright, Designs and Patents Act 1988, work an employee creates in the course of their employment belongs to the employer, unless agreed otherwise. Work by a freelancer or an agency belongs to its author unless it is assigned, and an assignment of copyright has to be in writing and signed by the person assigning it. So contracts with agencies and freelancers need a clear assignment of intellectual property to you. Who owns the code in the UK covers the detail, The contract wording matters, so ask a solicitor to check it.

Freelancers and IR35

If a freelancer works through their own limited company, the off-payroll working rules, often called IR35, may apply. Where the client is a medium or large business, the client must decide whether the freelancer would be an employee for tax purposes if engaged directly, and give them a status determination statement. Small businesses don’t have that duty, and the freelancer’s company decides instead. Public sector clients always make the decision themselves. HMRC publishes guidance and its Check Employment Status for Tax tool, and an accountant can advise on your case.

A hybrid path

Many products use more than one option over their life. A path we’d often suggest runs in five stages.

  1. Start with an agency or studio for discovery and the first release, so you get a full team without hiring.
  2. Hire a technical lead once the product has paying customers or a clear future, to own technical decisions and review the agency’s work.
  3. Share the work. The in-house lead and the agency work in the same repository, and the agency hands over areas as the internal team grows.
  4. Move the core in-house. Your own team runs the product day to day.
  5. Use specialists for peaks, such as an agency for a mobile app or an AI feature, or a freelancer for a short, well-defined piece of work.

The handover in the third and fourth stages goes best when everyone expects it from the start. Tell the agency at the outset that you plan to build an in-house team, so the code, documentation and ways of working are set up for it.

How to decide

Answer these questions honestly before you choose.

  • Is the software the core of your business, or a tool that supports it?
  • Will it need active development for years, or a build followed by maintenance?
  • Do you have someone who can manage developers and judge their work?
  • How soon do you need something live?
  • Would losing one person stop the project?

If the software is your product and you can wait for hiring, plan to build an in-house team, with outside help to get started. If it supports your business, an agency or studio on a retainer is usually simpler. If you already have a strong technical lead, freelancers can fill specific gaps well.

Weighing up who should build your product? See how we work with businesses on building and running their software.

Questions people ask

Is an agency more expensive than hiring developers?

Per day, an agency usually costs more than an employee’s salary, because its rate covers management, testing, design and overheads. Over a whole project the answer depends on how long you need the work. Employees cost money every month whether or not there is work, while an agency can be scaled down when the build is done.

Who owns the code a freelancer writes?

Under UK copyright law, a freelancer owns the copyright in the code they write unless a written, signed agreement assigns it to you. Make sure the contract includes an assignment of intellectual property, and that the code sits in a repository your company controls.

Can an agency hand a product over to an in-house team?

Yes, if the handover is planned. It goes best when the code has been in your repository from the start, the documentation and deployment process are up to date, and your new developers work alongside the agency for a period before taking over.

Do I need a technical co-founder or CTO before hiring an agency?

It isn’t required. You do need someone on your side who can make product decisions quickly and check that the work is going well. Some founders use an independent technical adviser for a few days a month to review code, estimates and plans, then hire a permanent technical lead as the product grows.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.