Choose a freelancer for small, well-defined tasks; an agency when you genuinely need several specialists working in parallel; and an independent studio when one senior person can own the whole product end to end. Most small and mid-sized software projects fall into that last category and don’t need agency overhead — but the honest answer depends on your project’s size and how much continuity you need. Here’s how the three compare, including where I’m the wrong choice.
How the three options compare
| Freelancer | Agency | Independent studio | |
|---|---|---|---|
| Typical cost | Lowest | Highest | Middle |
| Who does the work | The person you hire | Often juniors behind a senior pitch | The person you hire |
| Communication | Direct | Through an account manager | Direct |
| Capacity | One person, one skill area | A whole team at once | One senior partner, whole stack |
| Runs it after launch | Sometimes | Yes, at a price | Yes, if they run production |
| Continuity risk | Higher | Lower | Medium |
| Best for | Small, defined tasks | Large, multi-specialist products | Focused products, end to end |
These are my own generalisations from years of building and running software — not fixed rules. Any specific freelancer or agency can be better or worse than the pattern.
When a freelancer is the right call
If you have a small, clearly-defined task — a single screen, a bug fix, a one-off script — a freelancer is usually the cheapest and most sensible option. You’re not paying for a team you don’t need. The trade-off is capacity and continuity: one freelancer can only carry so much, often specialises in just one layer (design, or front-end, or back-end), and if they move on, the knowledge can move with them. Reduce that risk by owning the code yourself and picking someone who documents their work.
When an agency is worth the overhead
If your product genuinely needs several specialists working at the same time — say a big launch with a design team, multiple developers and a project manager — an agency gives you that capacity and keeps going if one person leaves. That’s real value. The costs are equally real: overhead you pay for, slower communication routed through account managers, and the common pattern where the senior people who win the work aren’t the ones who do it. An agency is the right choice when the project is too big for one person, not by default.
When an independent studio fits best
An independent studio is one senior partner who designs, builds, ships and runs the whole thing — front-end, back-end, servers and all. For a focused product that one strong person can own end to end, this is usually the fastest and clearest option: no handoffs, no meaning lost between specialists, and the person you talk to is the person building it. The honest limit is bandwidth. When a project truly needs parallel specialists, this isn’t the right fit, and I’ll tell you so.
That’s the model I work in. I built and run Givore end to end — the app, the backend, the servers and the community — across iOS, Android and web. I hand over clean code and accounts, and I run production — the ongoing part that most people forget to budget for — so continuity doesn’t depend on any one person being irreplaceable.
The short version
Match the option to the project, not the hype. Small and defined → freelancer. Large and multi-specialist → agency, overhead included. Focused and ownable by one senior person → an independent studio, which is where most small-business software actually lands — custom software built and kept running by the same team. Still deciding what to build and what it costs? See how to choose who builds your app, what it costs to build one, or, if your problem is manual work rather than a new product, how to automate your business. If you want a straight opinion on which fits your specific case — even if that’s “you need an agency” — tell me about it.