A freelancer sells you a finished thing. A retainer sells you an ongoing state. The difference shows up in month nine, when the arrangement has quietly become “if they are free” and nobody has been watching the system in between.
I spent years working as a freelancer, so let me be careful about what this is. It is not a piece about freelancers being worse. A great deal of the best work on the internet was built by one person on a contract, and I was that person for a long time.
It is a piece about one specific moment the freelance model has no answer for. It arrives roughly a week after launch, and it decides most of what happens to your system over the next three years.
The moment the relationship quietly changes
The moment is this: the build is finished, the invoice is paid, and the relationship has quietly changed from “someone is working on your system” to “someone will help if you ask and they are free.”
Nothing goes wrong that week. It goes wrong in month four, when you email about something odd and get a reply five days later because they are mid-project for someone else. Then again in month nine, when the reply comes back saying they have moved into something else entirely and can recommend a friend.
By then your system has been running unattended for most of a year. Nothing dramatic has failed. Plenty has drifted.
Freelancer and fractional, side by side
| What you are comparing | Freelancer | Fractional engineer |
|---|---|---|
| What the engagement is | A project with an end | A relationship with a rhythm |
| What happens at handover | The work stops | The work changes shape |
| Availability later | If they are free | Contracted, with a response time |
| Who watches it between requests | Nobody | Monitoring, then the engineer |
| Breadth | Usually one discipline done well | Infrastructure, web, data, automation |
| Cost shape | Lower, per project | Higher, monthly, predictable |
| Documentation | Varies enormously | Part of what you are buying |
| Right when | The job is defined and finishes | The system has to keep working |
The part nobody negotiates
Every freelance contract I have ever seen is precise about delivery and vague about afterwards. That is not sharp practice, it is just what both sides are thinking about while signing. You are buying a thing. They are quoting a thing. Neither of you is imagining month nine.
So the arrangement after launch is almost never written down. It becomes an understanding, and understandings decay at exactly the speed the freelancer’s calendar fills.
The tell is in how the work arrives. Under a project, everything is a quote: you notice something, you describe it, you wait for a number, you approve it, then it gets done. That loop is slow enough that small problems do not make the cut. They just accumulate, unmentioned, because raising them costs more than living with them.
A backup that had never been restored
A site I inherited had been backed up faithfully every night for two years. The plugin was configured correctly, the schedule ran, the dashboard was green, and every one of those backups was written to a directory the web server could serve. Anyone could have downloaded a full copy of the database, which is to say every customer record in it. Nobody had done anything wrong. It is just that taking backups is a task, and thinking about where they land is an ongoing responsibility, and only one of those was in scope.
What actually changes with a retainer
Not the skill. Often not even the person. What changes is the shape of the arrangement.
Small things get fixed. Under a retainer nobody has to decide whether a fifteen minute problem is worth invoicing. It just gets done, which means it gets done at fifteen minutes rather than becoming a two hour problem in a busy week.
Somebody is watching between your requests. This is the real difference. A freelancer responds to what you notice. A retainer includes noticing on your behalf, which matters because the failures that cost the most are the ones that never announce themselves.
Leaving is designed for. Every system I run is documented so that somebody else could take it over, and I would rather you have that and never need it. A handover written at the end, under time pressure, by someone already mentally on their next job, is worth much less than one written continuously.
A freelancer sells you a finished thing. A retainer sells you an ongoing state. The gap between those is where most systems quietly rot.
When a freelancer is genuinely the right hire
Frequently, and I will say so on a call rather than talk you into something larger.
Hire a freelancer when the work is genuinely finite and the result does not need tending. A landing page for one campaign. A specific integration built to a spec. A design job. A piece of work with a clear edge, where “done” is a real state rather than a milestone.
Hire one, too, when budget is the binding constraint and the system is simple enough to survive inattention. A retainer you cannot comfortably afford is worse than a good freelancer you can, and anyone who tells you otherwise is arguing for their own invoice.
And hire a specialist freelancer when you need depth I do not have. I work across four disciplines, which means there is always someone deeper in each one. If the job is one hard problem in one domain, go and get the person who only does that.
Ask who notices if it stops
One question, asked before you sign anything.
“When this is finished, who notices if it stops working?”
If the honest answer is “we would, quickly, and it would not matter much for a few days”, hire the freelancer. Get the thing built, get it documented, and keep your money.
If the honest answer is “nobody, until a customer tells us”, then the build is not the problem you are solving. The problem you are solving starts the day the build ends, and a project cannot solve it because a project is defined by ending.
If you do hire a freelancer, negotiate the boring part while you still have leverage, which is before the final invoice. Ask for the runbook, the credentials in a place you control, and a written answer to what happens if you email in six months. A good freelancer will have no problem with any of it.