Hire a freelancer for a well-defined task you can describe and check yourself; hire an agency for a fixed project with a deadline that needs several skills at once (design, front end, back end, QA); choose a monthly development retainer when your product needs steady, ongoing work from people who already know the code. Most problems with outsourcing come from using one model for a job that fits another.

What you are actually buying

• Freelancer: one person's time, usually billed by the hour or day, sometimes per deliverable. Independent work is common in the profession: 13.9% of respondents to the 2025 Stack Overflow Developer Survey describe themselves as independent contractors, freelancers or self-employed.
• Agency: a company that delivers a project with a team it assembles and manages. You buy an outcome and pay for coordination as well as code.
• Development retainer: a fixed monthly fee for an agreed amount of capacity and responsibility (for example, a set number of hours, code reviews, deployments, hosting care) from the same developer or small team, month after month. You buy continuity.

How the three models compare

Cost structure

Freelancers bill for time, so you pay only for what you use; in German-speaking Europe the average rate for software and web development was €91 an hour in 2026. Agencies add project management and margin, and usually quote per project. A retainer is a flat monthly amount: predictable for budgeting, but you pay for the capacity even in a quiet month. For full numbers, see what it costs to hire a software developer.

Continuity and knowledge

A freelancer may move to another client when your project pauses, and the knowledge leaves with them. Agencies rotate staff between projects, so the person who built your feature may not be the one who fixes it. A retainer is designed for continuity: the same people keep context from month to month, which is what makes small, frequent releases possible (see weekly releases with a remote developer).

Breadth of skills

One freelancer brings one skill set. An agency can staff designers, several developers and testers in parallel. A retainer with a single developer sits in between: one accountable person, with the option of bringing in specialists for specific pieces.

Management load on you

With a freelancer, you are the project manager: you write the tasks, review the work and decide priorities. An agency takes most of that on, which is valuable if nobody on your side can do it, and costly if you could. A retainer works best when you set priorities and the developer owns the technical decisions and delivery.

Speed to start

Freelancers can often start within days. Agencies need a proposal, estimate and contract. Retainers usually start with a short onboarding period; a practical two-week plan is in onboarding a remote developer.

The risks of each model

Freelancer

• Single point of failure. Illness, holidays or a better-paid contract stop your project. Keep the code in your own repository and insist on written handover notes.
• Misclassification. If you treat a full-time freelancer like an employee, tax authorities may too. In the US, the IRS looks at behavioral control, financial control and the type of relationship. In the UK, medium and large clients have been responsible for deciding employment status under the off-payroll (IR35) rules since April 2021. In France, a client who directs the freelancer like an employee risks requalification into an employment contract, with back pay, contribution adjustments and possible penalties for concealed work.

Agency

• Change requests. A quoted project is priced on a fixed scope; every change becomes a negotiation. See fixed price vs time and materials vs retainer.
• Staffing you did not choose. Ask who will write the code, not just who runs the sales call.
• Handover. When the project ends, the team moves on. Make sure you receive the repository, documentation and deployment access, and that the contract transfers the rights to the code (see code ownership and IP when outsourcing).

Retainer

• Unused capacity. If you do not have a backlog, you pay for idle time. Keep a prioritised list of work ready.
• Vague scope. "Development as needed" invites disagreement. Write down what is included (hours, response times, reviews, hosting, support) and what is not.
• Dependency. The same continuity that helps can make you dependent. The safeguards are the same as with a freelancer: your repository, your hosting accounts, documentation and a notice period.

Which one fits your situation

1. A defined, short task (fix a payment bug, build one integration, migrate a WordPress theme): a freelancer, paid per task or for a capped number of hours.
2. A defined project with a hard deadline and several disciplines (a marketing site with a design system, a first version of an app for a launch date): an agency, if you can write the scope clearly.
3. A live product that needs regular releases, fixes and small features every month: a retainer.
4. An MVP whose scope will change as you learn: usually a retainer or time-based freelance work, because fixed-price quotes punish change. Start by scoping the MVP.
5. A team with in-house engineers that needs extra hands: a freelancer or retainer who works inside your process.

How to judge any of them after three months

Whatever the model, measure delivery, not hours. DORA, a long-running research programme on software delivery, defines five delivery metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate. You do not need a dashboard. Ask simple questions every month: how often did working changes reach production, how long did a typical change take from request to release, and how many releases needed an urgent fix?

Also check that you can answer yes to these: the code is in a repository your company owns, you can deploy without the provider, and there is enough documentation for someone else to take over.

Frequently asked questions

Is a freelancer cheaper than an agency?

Usually per hour, because an agency adds project management and margin. But if you have to manage the freelancer yourself, count your own time too. For a multi-skill project with a fixed deadline, an agency can be cheaper overall.

What is a development retainer?

A monthly agreement where you pay a fixed fee for a defined amount of development capacity and responsibilities from the same developer or team. It suits products that need ongoing releases, maintenance and small features rather than a one-off build.

Can a long-term freelancer be treated as an employee?

Yes, if the relationship looks like employment. US, UK and French authorities all look at control, integration into your organisation and economic dependence. Keep the freelancer independent in how they work, and get local advice for long engagements.

Should a startup outsource development?

Outsourcing makes sense when you need to ship before you can justify a full-time hire, or need skills you lack. Keep ownership of the code, the hosting accounts and the product decisions in-house whichever model you choose.

Sources

1. 2025 Developer Survey – Work, Stack Overflow, 2025-07
2. Freelancer-Einkommen: Projektumsatz sinkt um 17 % (Freelancer-Kompass 2026), freelancermap, 2026-04
3. Independent contractor (self-employed) or employee?, Internal Revenue Service (IRS), 2026-05
4. Understanding off-payroll working (IR35), HM Revenue & Customs, GOV.UK, 2026-02
5. Indépendance juridique : risque de requalification du contrat de mission en contrat de travail, Bpifrance Création, 2026-06
6. DORA's software delivery performance metrics, DORA, 2026-01

When you hire a remote developer, the hardest part isn’t the code. It’s knowing what is happening between two calls. A fixed weekly rhythm answers that question before you have to ask it.

Monday: agree the week’s goals

The week starts with a short call. You and your developer agree what should be live by Friday: a feature, a set of bug fixes, or a step towards a larger release. Anything too big for one week is split into pieces that each work on their own.

Midweek: a preview link

Halfway through the week you get a link to try what’s in progress. You click through it like a user would, and you say what feels wrong while it is still cheap to change.

Friday: release, with notes in plain language

On Friday the work goes live, with release notes written for you rather than for developers: what changed, what to check, and what’s next.

Your code stays yours

The code lives in your repository from day one. You can see every change, and nothing depends on access you don’t control.

What you need on your side

• One person who can decide what matters this week.
• Access to your repository and hosting (or a fresh one, set up together).
• About 30 minutes on Monday and a few minutes to try the preview.

When it isn’t the right fit

A weekly rhythm suits ongoing product work. It is the wrong tool if you need a one-off fix, if there’s no clear product goal yet, or if you need a full-time team on site.

The same rhythm on our own products

ShipFastDev uses the same rhythm on its own products. In week 39 of 2026, live ships and satellites joined aircraft on SkyEye’s 3D globe; in week 40, its assistant JARVIS learned to present the news on the globe. The shipping log on the home page lists those releases.