Buyer's guide
Freelance developer vs agency vs in-house
Three ways to get software built, with genuinely different economics. This page lays out what each one actually costs, how fast it moves, where it fails, and how to tell which one your situation calls for — written by someone who loses work when the answer is 'agency'.
- Freelancer
- Fastest start, lowest cost, one point of failure
- Agency
- 2–4× the cost, more capacity, more process
- In-house
- Slowest to start, best long-term ownership
- Rule of thumb
- Freelancer to prove it, team to scale it
What you get
- A cost comparison you can put in front of a co-founder
- The questions that expose a weak quote from any of the three
- A risk checklist for hiring a solo builder safely
- The hand-off conditions that let you switch later without a rewrite
Cost: where the money actually goes
For the same first version, the three routes rarely land within sight of each other. An agency quote includes people who never touch your product — that is not waste, it is the cost of an organisation, but you are paying for it. In-house looks cheapest per month and is the most expensive per shipped feature until the product stabilises.
- Freelancer: one rate, no overhead, price moves only with scope
- Agency: account manager, PM, designer, QA and bench time built into the number
- In-house: recruiting fees, salary, equity, onboarding, and months before line one ships
- Hidden in all three: deployment, support, and whatever the quote quietly excluded
Speed: the first four weeks decide it
A solo builder starts the week you agree. An agency starts after a discovery phase, a statement of work and a slot in the schedule. An in-house hire starts after a hiring process. If your deadline is investor-shaped or seasonal, that difference is the whole decision.
- Freelancer: days to start, no coordination overhead, decisions in one conversation
- Agency: weeks to start, but genuine parallelism once running
- In-house: months to start, then permanent capacity
Risk: be honest about the failure modes
Each option fails differently, and the fix is contractual rather than emotional. A freelancer can vanish; an agency can rotate your senior developer onto a bigger account; an in-house hire can be the wrong hire and take a quarter to unwind. Protect against all three with ownership, milestones and readable code.
- Own the repository, domain, hosting and database accounts from day one
- Pay against visible milestones, never a large sum up front
- Require standard, boring technology a successor can pick up
- Ask who specifically writes the code — and whether that is contractually guaranteed
When I tell people to hire an agency instead
If the work needs three specialists simultaneously, if you are in a regulated sector needing formal audit and liability cover, or if your procurement process cannot contract with an individual, an agency is the right answer and I will say so on the first call. Losing a badly matched project is cheaper for both sides than delivering it.
The pragmatic sequence most founders should follow
Prove the idea with the smallest real version, built fast by one person who is accountable. Get users, revenue or a funding round from it. Then hire in-house around a product that has already survived contact with reality — with a codebase written to be handed over rather than defended.
Who this is (and isn't) for
Good fit
- — You need a first version live in weeks, not after a discovery phase
- — One decision-maker who can answer questions the same day
- — Budget that would buy a fraction of an agency engagement
- — You want the person building it to also be the person you talk to
Not a fit
- — Regulated work needing formal audits and liability insurance
- — Several workstreams that must run in parallel from week one
- — Procurement that can only contract with a registered supplier
- — A product that already has a team and needs headcount, not delivery
Questions I get asked
- Is a freelance developer cheaper than an agency?
- Usually by a wide margin — often half to a third of an agency figure for the same first version. The reason is structural, not heroic: an agency price carries account management, sales, project management and bench time. A solo builder carries none of that, and passes the difference on.
- When is an agency the better choice?
- When the work genuinely needs several specialists at once, when procurement requires a company with insurance and a legal department, or when the project must survive one person being unavailable. Those are real reasons and worth paying for.
- Is hiring in-house better than outsourcing an MVP?
- Not before product-market fit. Hiring costs three to six months of search, then salary and equity, for a product that might change shape twice. Hire in-house once the thing works and needs continuous ownership.
- What is the biggest risk of hiring a freelancer?
- Bus factor and follow-through. Mitigate both the same way: your own repository and accounts from day one, milestone payments tied to visible progress, and code that a competent successor can read. Ask for those in writing before you pay anything.
- How do I compare quotes fairly?
- Normalise them. Ask each party for scope in user stories, who does design, who does QA, what happens after launch, and what an out-of-scope change costs. A cheap quote that excludes deployment and support is not cheap.
Keep reading
Prefer chat? Message on Telegram instead — same inbox, faster.