Articles
A freelancer or an agency: the question behind the price
Skill is not the difference. Continuity is — what happens in the week your one contact is unavailable, and how to ask both candidates about it.
- buying
- hiring
- consulting
The difference between hiring a freelancer and hiring an agency is not skill; both camps contain careful work and both contain disasters. The difference is what happens in the week your contact is ill, on holiday, or has taken a better-paid job elsewhere. One arrangement keeps what you know in a single head; the other spreads it across people you have never met, and charges for the spreading. Which one you need follows from how long your business can run with nobody answering.
What are you actually buying?
Capacity, a second opinion, and someone to reach on a Tuesday. Only the first is usually discussed.
Capacity is calendar. One person has five days a week, minus the week they are moving house. A firm can put a second body on the work when yours is unavailable, and that is the real content of the word team: not more skill per hour, but the ability to keep going while a specific human is not there.
A second opinion is a review step — someone reads the schema before it is built, or asks why the invoice total is computed twice. On a single-person project that step is usually you, and you do not know what to look for.
Someone to call is the most expensive piece to get wrong. Every project produces a morning when something is broken and a customer is waiting, and who answers that morning is settled long before the invoice.
Which projects suit one person?
One workflow, one clear owner, and a horizon measured in weeks. When those hold, a single freelancer is not a compromise: there is no relay between whoever decides and whoever builds.
One workflow means the model fits in one head: how an order is taken, how stock is reserved, how a delivery note becomes an invoice. A person holding all of it answers a question in the corridor; three people holding thirds spend ten minutes of every call rebuilding the picture.
One clear owner means decisions do not queue. If two managers can each change the priority of the work, the project stalls whether there is one contractor or nine.
A long horizon is the exception, and it is where this stops working: six weeks of work can be handed over in an afternoon, nine months of accumulated decisions cannot. Note what is absent: budget. A small project with three integrations still fits one person badly.
Which projects do not?
Several integrations, and anything people depend on every morning.
Each integration is a second system with its own failures, its own credentials and someone on the other side who does not answer email. Two integrations are a task; five are a map of other people's release schedules, and that map takes a person who can spend a day on the phone. It also takes a second reader: a fault between two systems is found by comparing two logs, and one person under deadline compares the one they trust.
A system staff use daily is an availability commitment, not a skill requirement. If the workshop cannot open because the job-card screen is down, "he is away until Monday" is not an answer your business can give. That need not be a firm; it means a named second person and a written escalation, whoever provides it.
The same holds where nobody has written the requirement down: two people arguing about the process get further than one person guessing politely.
What is the continuity question, and how do you ask it?
Ask what happens in the second week of an absence, and get the answer in writing before anything is signed.
Each question has an answer that sounds fine and is not. Who is the second person, by name, and have they read this project? Where does the code live — whose account, whose ability to lock you out? Who can rotate the credentials without you? What documentation exists today, not what will be produced at the end? What does a handover include?
An agency that cannot name a second person is a freelancer with an office and a logo. A freelancer who says "there is nobody else, and here is what that means for you" is telling the truth, which is worth more than a team slide. That answer is acceptable when the work is short and you can wait a fortnight; it is not acceptable in the middle of a system your staff open every morning.
Which shape fits which work?
| The work | Freelancer | Agency |
|---|---|---|
| One workflow, one owner, a few weeks | Fits: no relay, no overhead | Works, with a bench you may never call |
| Three or more integrations | Risky: no second reader | Fits, if two names are on it |
| A system staff open every morning | Only with a named backup | Fits, if the rota is real |
| A process nobody has written down | One person, slowly | Two people, arguing it out |
How do you make the decision?
- Write down how many working days you can absorb an unanswered question before money stops moving.
- Name the internal owner, and the decisions only that person can take.
- Count the external systems the work must talk to, and the people on the other side of each.
- Ask every candidate the same continuity question in writing, and compare answers rather than pitches.
- Ask for the second name, and put it in the contract with what that person is expected to do.
- Agree what the end looks like: a repository you control, credentials in your name, a document a stranger can follow.
- Re-run the check the first month one person is the only one who knows how something works.
Where this goes wrong
- The individual who is secretly a team. Subcontractors you never meet, no name on the contract, a delivery date that depends on strangers.
- The firm that is secretly an individual. One person, a logo and three slide templates: the team appears in the pitch, not in the commit history.
- Documentation as a closing ceremony. Promised for the end, delivered as a folder of screenshots, worth only what exists on the day you need it.
- No internal owner. Every decision routes to the vendor because nobody inside may approve anything, so a two-week absence becomes a two-month stop.
What this does not cover
It does not compare quality, and it says nothing about rates — a figure here would be wrong in another city next quarter. Nor does it cover how to check references or run a tender. And if a regulator, an auditor or a bank needs a party that can sign, insure and be held to a warranty, whether an individual can stand in that place is a legal and tax question for a lawyer, not for this page.
We build as a small team with a named second person on every project, and we write that name down before the first invoice.
Services in this article
Articles
Related articles.
What to write down before you commission software
One page of rules — three workflows, their exceptions and the owner of each record — prices better than any list of screens. How to write it.
- requirements
- consulting
- planning
Who owns the code you paid for
Copyright, repository, hosting, domain, database and API keys are six separate assets. What to ask for in writing so you can leave one day.
- ownership
- contracts
- custom-software
What a software demo should show you, and what it is hiding
A demo proves the software can work. What it hides is your case, your volume and your worst day — and the five questions that break the rehearsed path.
- buying
- demos
- consulting
Start a project
Have something to build?
One short brief is enough. You get a written scope and a fixed quote before anything starts.
