All articles
DevelopmentNovember 12, 202611 min read

Freelancer, studio or in-house team: how to choose who builds your product

An honest comparison of freelancers, studios and in-house teams: what each is good at, where each lets you down, and how to check a contractor before you sign.

The choice comes down to three things: how large and how well defined the task is, how long the product will keep being developed, and how much management you are prepared to do yourself. A freelancer suits a small, precisely defined task. A studio suits a product that has to be designed, built and launched as a whole within a limited time. An in-house team suits a product that is your business and will be developed for years. The details follow, including the cases where a small studio like ours is the wrong choice.

What are the strengths and risks of hiring a freelancer?

Strengths:

  • minimal overhead: you pay for one person's work;
  • direct contact with the person doing that work;
  • flexibility on timing and format;
  • a good way to bring in narrow expertise for a specific task.

Risks:

  • one person means one skill set. Design, front end, back end, infrastructure and testing are rarely equally strong in a single specialist;
  • there is no backup: illness or another project stops your work;
  • management, quality control and acceptance fall to you;
  • knowledge of the project lives in one head.

A freelancer works well when the task is described, the result is easy to verify, and someone on your side can judge the code.

What are the strengths and risks of working with a studio?

Strengths:

  • a full set of roles: product design, interface design, development, testing, launch;
  • an established process, with estimates, iterations and regular demos;
  • a company, not an individual, is contractually responsible for the result;
  • work does not stop when one person is unavailable;
  • experience of similar problems from other projects.

Risks:

  • an hour of work usually costs more than a solo contractor's, because you also pay for management and for the range of roles;
  • you are not the only client, and the studio's attention is shared between projects;
  • in larger agencies one person sells and another builds, so find out who will actually do the work;
  • knowledge of your industry has to be handed over;
  • if the code and documentation are not transferred to you, you become dependent on the contractor.

A studio fits an MVP, a product launched from scratch, and internal systems such as a CRM, automation or customer portals in companies without a development department of their own.

What are the strengths and risks of an in-house team?

Strengths:

  • complete focus on one product;
  • domain knowledge accumulates and stays in the company;
  • a fast response to change;
  • you control priorities entirely.

Risks:

  • hiring takes time and is itself a skill: someone has to be able to assess engineers;
  • the costs are fixed and do not depend on workload;
  • you need a technical lead to hire and run the team;
  • one or two employees do not cover every role;
  • people leave, and part of the knowledge leaves with them.

An in-house team is justified when the product is the core of the business, is developed continuously, and there is funding for it over a clear horizon.

Which option fits which stage and type of project?

  • Testing an idea, building an MVP. A studio, or a strong freelancer with technical oversight. Hiring a team before demand is confirmed locks in costs too early. How to narrow the first version is covered in how to build an MVP.
  • A small, clear task such as a landing page, a script, a single integration or a fix. A freelancer.
  • An internal business system. A studio; later support comes from the same studio or from one in-house developer.
  • A product that has found demand and is growing. The core team in-house; a studio or freelancers for peak load and separate modules.

Mixed arrangements are common: a studio builds the first version and then hands it over to an in-house team.

When is a small studio the wrong choice?

The honest answer: in several cases.

  • You need many people at once and the deadline is hard. A large volume of parallel work is a job for a large contractor or your own team.
  • There are formal requirements. Industry certifications, tender procedures, round-the-clock support with guaranteed response times: a small studio, as a rule, does not offer these.
  • The product is your core business and the funding is there for years. Build your own team; a studio can help you start but will not replace it.
  • The task takes a couple of days. A freelancer will do it faster and cheaper, without a process such a task does not need.
  • You need deep, narrow specialisation the studio has no track record in, for example embedded systems or game development.

We would rather say this in the first conversation than after the contract is signed.

Fixed price or time and materials: which is better?

Fixed price. Scope, cost and deadline are agreed before work starts. You know the budget, and the risk of underestimating sits with the contractor. It only works when the scope can be described; every change goes through approval, and the price includes a margin for uncertainty.

Time and materials. You pay for the time actually spent. It is flexible and suits work where requirements are bound to change: exploratory tasks, product development after launch. The budget risk is yours, so it requires transparency: time reports, regular demos, the right to stop.

In practice the two are often combined: a fixed price for a well-described first version, then time and materials or a monthly arrangement for further development. For a large or vague project, a separate discovery stage comes first; after it, a fixed price becomes possible.

For projects with a clear outcome we fix scope, cost and timeline before development begins. More on that in how we estimate a project.

How do you check a contractor before signing?

  • Live products you can open. Not screenshots and not a slide deck, but links. Click through them yourself, on a phone as well. Ours are in the case studies.
  • A conversation with the person who writes the code. If the contractor will not introduce you to them, you do not know who is building your project.
  • How the estimate is put together. Ask for a breakdown by module, and notice which questions you were asked before a figure was named.
  • Who owns the code and the accounts. The repository, hosting, domain and third-party services should be registered to you or transferred to you; rights to the code are set out in the contract.
  • What happens after launch. A warranty period for fixing bugs, support terms, documentation, and whether another developer could pick the project up.
  • A small first stage. Starting with a limited paid stage is the most reliable way to learn how a contractor really works.

What are the red flags?

  • A price far below the others with no cut in scope. Either the task was not understood, or the difference will return as extra charges or as quality. Ask what is not included.
  • No questions about your business. You cannot estimate what you do not understand.
  • No written scope. Each side remembers a verbal agreement in its own way.
  • No access to the repository. You should see the code as the work progresses, not only after the final payment.
  • Any deadline accepted without questions. A promise made before the task has been studied rests on nothing.
  • Full prepayment for the whole project. Payments should be tied to stages and results.
  • Nothing live to show.
  • No clear answer about who exactly will do the work.

What should a good contract and scope document contain?

  • the goal of the project and the core scenarios in plain language;
  • a list of features and screens, and a separate list of what is out of scope;
  • user roles and their permissions;
  • integrations: who provides access, and what happens if an external system limits what is possible;
  • supported platforms, devices and browsers;
  • acceptance criteria: how both sides know a stage is done;
  • stages, dates and payments tied to stages;
  • a change procedure: how a new requirement is estimated and approved;
  • transfer of rights to the code, ownership of accounts, confidentiality;
  • warranty and support terms after launch;
  • what you provide and by when: content, access, feedback.

How do you work with a remote team across time zones?

  • Agree on a shared window. A couple of hours a day when both sides are online is enough for calls and urgent questions.
  • Write things down. Tasks and decisions are recorded in a tracker or a document, not in the memory of whoever was on the call.
  • Regular demos of the working product. On a fixed rhythm, on the same day.
  • One person on your side makes decisions and answers quickly. Slow feedback is a common reason deadlines slip.
  • Shared access to the task tracker, the repository and a staging version where the current state is visible at any moment.
  • A channel for urgent matters. Agree in advance what counts as urgent and how quickly it gets a response.

A time difference can also work in your favour: a question asked in the evening is answered by your morning.

A short decision checklist

  • The task is small and precisely described, and you can check the result yourself: a freelancer.
  • You need a whole product, from idea to launch, and have no technical team: a studio.
  • The product is the core of the business, the funding is long-term, and there is someone to lead engineers: an in-house team.
  • You are not sure the demand exists: do not hire anyone yet, test it with an MVP first.
  • In every case: a written scope, payment by stage, code and accounts in your name, and the contractor's live products, which you have opened yourself.

Where to start

Describe the task in a few paragraphs: who will use the product, what those people need to be able to do in it, what already exists, and what the time constraints are. Send the same description to two or three contractors of different types and compare not only the figures but the questions they ask in return. If you would like our view, tell us about the task: we will say honestly whether a studio is the right fit here and, if it is not, who you should be looking for.

FAQ

Is a freelancer always cheaper than a studio?

Per hour, usually yes. But the total depends on how much management, testing and rework ends up with you, so compare the cost of the whole project, your own time included.

Can I start with a studio and move development in-house later?

Yes, it is a common arrangement. It works if the code, accounts and documentation are in your name from the start and the handover is described in the contract.

Who should own the source code?

The client, and the contract should say so. You need access to the repository during the project, not only at the end.

What is the difference between outsourcing and outstaffing?

In outsourcing the contractor is responsible for the result and organises the work. In outstaffing you add specialists to your own team and manage them yourself.

How many contractors should I compare?

Two or three are enough to see the spread. It matters more to give all of them the same description and compare what exactly each proposal includes.

What if the contractor disappears in the middle of the project?

Payment by stage, plus a repository and accounts in your name, limit the loss to the current stage. With access to the code, another team can continue the project.

Shall we discuss your project?

Tell us about it — we'll come back with an estimate and a proposal.

WhatsAppTelegram