Upwork or an agency? Pick by project length, not by price
The short answer
Use a marketplace freelancer when the brief fits on one page, you can verify the result yourself, and the work takes under two weeks. Use a company when the code will be maintained after the person who wrote it has gone. The dividing line is continuity, not cost, and it falls at roughly month three.
The comparison everyone makes, and why it misleads
The usual framing is hourly rate. A marketplace developer at $30 an hour against an agency at $110 looks like an easy decision until you notice that the two numbers are not measuring the same thing.
The agency rate includes a second engineer reviewing every change, someone accountable for the architecture rather than the ticket, and cover when one person is unavailable. Whether those are worth the difference depends entirely on how long the work has to last, which is why project length is the better axis.
When a marketplace freelancer is the right answer
We say this on our own site because it is true, and because selling a founder a retainer for a job that needed a fortnight is how a company loses referrals.
- The brief fits on one page and you would recognise a correct result when you saw it.
- The work is bounded: a specific integration, a specific screen, a migration with a defined start and end.
- It takes under two weeks, so continuity never becomes a question.
- Nobody has to extend it afterwards, or if they do, the extension is another bounded piece.
- You already have someone technical who can review what comes back.
Under those conditions a marketplace is faster to start, cheaper, and involves less process than the job deserves in the best possible way.
Where it goes wrong
The failure is rarely bad code. It is that a single person, working alone, with nobody reviewing their decisions and no obligation to anyone who comes after them, produces a system optimised for finishing the ticket.
- No second opinion, so an early architectural decision compounds unchallenged for months.
- Knowledge lives in one head and leaves with it, because documentation is nobody's deliverable.
- Availability is not contractual; a better-paying client can appear at any time.
- Scope disputes have no process, only a rating system both parties are wary of.
- The incentive is to close the contract, not to leave behind something extensible.
The five options, priced honestly
| Model | Typical cost | Time to start | Breaks down when |
|---|---|---|---|
| Marketplace freelancer | $15–80 / hour | Days | The work runs past a couple of months |
| Independent senior contractor | $70–150 / hour | 2–6 weeks | You need architecture supplied rather than executed |
| Low-cost offshore agency | $8,000–25,000 / project | 1–3 weeks | The specification was not finished before it started |
| Dedicated team or partner | $4,500–20,000 / month | 2–4 weeks | The job was actually a two-week brief |
| In-house hire | $90,000–160,000 / year | 2–5 months | You need output before month five |
These are indicative market rates for European and EMEA delivery, not quotes. Our own published starting prices sit on the pricing page.
A middle path most people miss
The choice is not binary. Two arrangements get you marketplace economics with company-grade continuity, and both are underused.
The first is to keep your freelancer and add oversight. A fractional CTO reviews what they ship, sets written standards, and joins planning calls. Your costs stay close to freelance rates and somebody senior is finally reading the code.
The second is to commission an independent code audit at the end of each phase. A few thousand pounds at the milestone is dramatically cheaper than discovering at month nine that the last six months produced something nobody can extend.
The question that actually decides it
Not what does this cost. Ask: in eighteen months, when the person who wrote this is gone, who changes it safely?
If the honest answer is that nobody needs to, because the work is bounded and finished, hire the freelancer and enjoy the saving. If the honest answer is that someone will have to, then you are buying maintainability, and maintainability is produced by review, documentation and continuity rather than by talent.