Hire a freelance developer when one person can build what you need: a business website, a first version of a product, or fixing an app that's stuck. Hire an agency when brand, design, and development all have to happen at once. In my experience, agencies often quote about twice what a freelancer does for the same website.
Most people ask this after getting one of each: a long agency proposal with a discovery phase and a team page, and a shorter quote from a freelancer. They look like different products, so they're hard to compare. The honest way to choose is to look at the job, not the proposal. I'm a freelancer, and I'll say where an agency is the better buy. Below: prices side by side, what each one actually gives you, what one developer can build alone, four real projects, and how to check either before you sign.
Freelance developer or agency: the short answer
Hire a freelance developer when
One person can build it
- One person can build it: a website, a first version, a takeover
- You want to talk to the person who writes the code
- Designs are ready, or the design is simple
- Budget matters, and you'd rather pay for code than meetings
Hire an agency when
The work needs a team at once
- Brand, design, and development all start from zero
- Several big pieces have to be built at the same time
- You need someone on call around the clock by contract
- Nobody on your side has time to make decisions weekly
The cut
Notice what's not on either list: the size of your company. Large companies hire freelancers for well-defined jobs all the time, and small ones sometimes need an agency because they're starting a brand from nothing. If you're weighing a salary instead of either, see full-time developer or freelancer.
Freelance developer vs agency cost
The first three freelancer prices are mine. The hourly row is the typical range for senior US freelancers. The agency column is what I see in the quotes clients show me: agency prices vary more, but the gap is consistent.
| Project | Freelancer | Agency |
|---|---|---|
| Business website | $8,000–22,000 | Often about twice |
| First version people pay for | $30,000–70,000 | Often about twice |
| Review of an existing app | $900–1,500, fixed | Often about twice |
| Hourly rate, senior level | Senior US freelancers: about $100–150 | Often about twice |
The extra money isn't a markup for nothing. It pays for a project manager, a designer, testers, account managers, an office, and sales. If your project needs those people, that's good value. If it needs one developer, you're paying for people who won't touch your project much. The line-by-line prices are in what a custom website costs and what a web product costs. For the freelance range on your own website, answer a few questions in my website cost calculator.
What an agency gives you, and what it doesn't
What an agency gives you
Several people working at once. A designer can create a brand while developers build and a copywriter writes the pages. A project manager keeps it on schedule, so you spend less of your own time running it. If someone leaves, someone else steps in. For big projects with many moving parts, that structure is worth paying for.
What it often doesn't
Direct contact with the person writing your code. Your questions go through an account manager, and the senior people who pitched the project are often not the ones who build it. Changes can wait for the next weekly meeting. And the team that built it may be busy on another client when you need a fix in month four.
What a freelancer gives you
The person who quotes is the person who builds. You message them, they answer, and small decisions take minutes rather than a meeting. You pay for development, not overhead. The trade-off is capacity: one person does one thing at a time, and can't do the brand, the copy, and the code in the same week.
What one freelance developer can build
People often underestimate how much one experienced full-stack developer can own. "Full-stack" means both the parts you see (the pages and screens) and the parts you don't (the server, database, and hosting). On a typical project, one person can handle:
- Turning designs into a working site or app
- The backend: logins, payments, emails, admin panels
- The database and how data is kept safe
- Hosting, domains, and a launch without downtime
- Technical SEO: page speed, titles, structured data
- Fixes and small changes after launch
What one developer usually shouldn't take on: creating a brand identity from nothing, writing dozens of pages of marketing copy, 24/7 on-call support, or several large products at the same time. If your project needs those, hire for them separately, or hire an agency. A good freelancer will tell you which parts they'd hand to someone else, like a copywriter or a brand designer, and can often recommend people they've worked with before.
Four real projects and who should build them
Two of these started with designs from someone else. Two started with an agency that didn't finish.
Designs ready: one developer builds it
A technology consulting firm had its designs in Figma already. I built the frontend, about 10 pages, for $23,000, and load time dropped from about 3 seconds to about 450ms. An aviation company was similar: 120+ pages from Figma, $16,000, and load time down from about 8 seconds to 676ms. Neither needed an agency. The design was done, so the rest was a build.
An agency left it half-built: one developer finishes it
A social challenge app and a local news app both came to me after an agency left them half-built. I finished the first in 8 weeks for $16,000; it now has 10,000 users. The second, an iOS and Android app with a backend and editor admin, took 12 weeks and $25,000, and has 50K downloads. More on that kind of work in what a takeover costs.
When I'd tell you to hire an agency
A new company that needs a name, a brand, a marketing site, and a product all in the same quarter. That's four jobs at once, and one person doing them in a row would take too long.
Using a freelancer and an agency together
You don't have to pick only one. Some of the best-run projects split the work by skill: a design studio creates the brand and designs, then a freelance developer builds from them. The two Figma-based projects above worked this way. It gets you agency-level design without paying agency rates for development.
The split works when each side owns a clear piece. Design is finished and approved before the build starts, one person on your side makes decisions, and the developer can ask the designer questions directly. It goes badly when both sides change the same thing, or when design is still being invented while the site is being built. Then every design change means rework, and each side blames the other for the delay. Decide the order up front: design first, then build. Whether you need a designer at all is covered in designer or developer first. And ask the designer to hand over the files in a tool the developer can read directly, like Figma, so nothing gets lost between the two.
How to check a freelancer or an agency
The questions are the same for both. The answers are what differ. Ask these before you sign anything:
- Who exactly will write the code?Get names. With agencies, ask whether it's the senior team you met or someone else, and whether any work is subcontracted.
- Whose accounts will it live in? Code, hosting, and domain should be in your name from day one.
- Can I see live work and talk to a past client? Live sites, not screenshots. A short call with a past client tells you more than a portfolio.
- What happens after launch? Who fixes bugs, how fast, and what it costs per month.
- How do we communicate? Directly with the developer, or through a manager? How often?
Watch how they answer as much as what they say. Vague answers about who does the work, or reluctance to put accounts in your name, are reasons to walk away, whichever kind of hire it is. The full list, with good and bad answers, is in what to ask before hiring a developer.
A brief to send a freelancer and an agency
Send the same short brief to everyone you're considering. It makes quotes comparable, and how each one responds tells you a lot. A good reply asks questions about it. A reply that sends a price without any questions hasn't really read it. It fits on one page:
If the answers show one clear build with designs ready or simple, a freelancer will likely save you half the cost. If they show brand, design, and product all starting from zero, get agency quotes. If it's somewhere in between, a small studio, or a design studio plus a freelance developer, is often the best fit. Either way, send me the brief, and I'll tell you which it is.
