Skip to content
DIP Dev — Logo
EN
Deutsch English
Call
Menu

Agency or freelancer: who fits your project?#

Portrait of Dmytro Prylutskyi
Dmytro Prylutskyi

27 October 2026 · updated: 27 October 2026

The question is usually asked morally — "agencies expensive, freelancers cheap". That is the wrong axis. The right question is: **what kind of project is it?** That decides which organisational form fits — and the answer often differs from what the budget prejudice suggests.

When an agency is the right choice#

  • Many stakeholders, many opinions: a relaunch with marketing, sales, legal and management at the table needs project management. Someone has to condense the diversity of opinions into decisions — that is a role of its own.
  • Design as the core requirement: when the appearance is the project, you need designer and developer. An agency has both under one roof.
  • Ongoing operation with an SLA: when someone has to answer at 3 a.m. because the shop is down, you need an on-call contract — structurally, agencies can deliver that better than one person.

When a single person is enough — and faster#

  • One process, one system: the classic in the Mittelstand: orders, appointments, billing or shift schedules live in Excel today. There are clearly defined users, a clear flow and a clear purpose. For that you don't need an organisation — you need someone who builds it.
  • Speed over coordination: in a sprint with one person, the person building decides. No internal handover, no ticket where a question waits. That is why a four-week sprint with one person takes four weeks — and often ten at an agency.
  • Knowledge in one piece: when you talk to the developer writing the code, the lossy relay chain from sales to project manager to team lead to developer disappears. Every stage in that chain is a source of "we understood that differently".

How to tell them apart before you sign#

Regardless of the organisational form — these questions sort serious offers from polished ones:

  1. What happens when it doesn't fit? If the answer is "we'll see", you pay the risk later. An honest answer names a stopping point with defined costs.
  2. Who writes the code? Ask for the person. If they are not shown to you, you are buying an organisation, not a developer.
  3. Where is the scope? "We'll discuss it in the kickoff" is not an answer. A scope that doesn't exist before the signature exists afterwards as material for arguments.
  4. What is yours at the end? Source code, documentation, credentials. If that isn't automatic, ask what it costs to get it.

Where I stand myself#

I am the second case: one person, fixed scope, fixed price, four weeks. My references (AstraCaB, BZBGear) are exactly such projects. For relaunches with ten stakeholders I am the wrong choice — and I say so in the intro call.

Soft CTA: if you are unsure which format your project needs after reading this: free 20-minute intro call — the assessment costs you a coffee break, even if the answer is "agency".