---
title: What's the difference between freelancer, agency, and retainer?
url: https://varstatt.com/jurij/p/whats-the-difference-between-freelancer-agency-and-retainer
author: Jurij Tokarski
date: 2026-03-06
description: Three service models with different incentive structures. The key insight: productize the workflow, not the service.
section: Blog (https://varstatt.com/jurij/archive)
tags: principles-faq (https://varstatt.com/jurij/c/principles-faq)
---

Three models, three different incentive structures.

**Fixed-price freelancing** has a perverse irony. Bad projects have unclear scope and clients who don't pay. Good projects require so much upfront scoping — calls, scope documents, negotiation — that the overhead kills profitability. Better projects mean more overhead, which means less profit.

**Agencies** typically have one developer doing the work, but the client pays for a team of five: project manager, account manager, QA, and overhead. Client pays triple for the same output.

**Retainer** productizes the relationship — the workflow, process, and cadence — not the service itself. Client pays weekly, developer delivers weekly, both stay invested. No awkward renegotiation when a good project wants to continue.

The key insight: you can't productize the service (every project is different), but you can productize the relationship.

[Hours Are Wrong](/principles/philosophy/hours-wrong) explains why measuring presence instead of outcomes creates broken incentives. [Weekly Accountability](/principles/partnership/weekly-accountability) creates feedback loops with teeth — delivered value means you continue, dropped the ball means you stop. [Exit Freedom](/principles/partnership/exit-freedom) makes cancellation easy so the relationship continues because the work earns it.

Sizing the three options against your actual scope is what [Build Cost](/discovery/build-cost) does — same comparison the post above runs, against your specific feature list.

Choose a model that aligns incentives. Retainer works when you need continuous development and want predictable costs without scope creep arguments.