Agency or one developer: what actually changes.

Written by a one-person shop, so read it with that in mind. It still says when to hire the agency, because pretending otherwise would not be useful.

Short version: the price gap between an agency and one developer is mostly structural, not a quality gap. An agency quote carries a project manager, a designer, a developer and often a salesperson; every handoff between them is real cost and real time. Hire the agency when the work genuinely needs parallel people or specialist sign-off. Hire one developer when the scope is clear and the main thing you want is for it to be built.

Where the money actually goes

People assume the difference is quality of code. Usually it is headcount. A site passing through four people needs briefs written, meetings held, work reviewed and messages relayed. None of that is waste from the agency's side — it is how you coordinate four people — but you are paying for the coordination as well as the build.

Remove the coordination and the same scope costs less and ships sooner, because the person writing the code is the person you spoke to. That is the entire trick. There is nothing else clever going on.

What you give up

Being honest about this is more useful than a list of advantages:

·Bench depth. One person is a single point of failure. An agency can put someone else on it; I cannot.
·Parallel work. Two things at once take twice as long, not the same time.
·Specialists. No dedicated brand designer, no copywriter, no compliance reviewer. For some projects that matters a great deal.
·Institutional continuity. An agency outlives any individual in it.

What you get instead

✓You talk to the person writing the code, so nothing is lost being relayed
✓Decisions land in hours, not after the next internal sync
✓Published prices instead of a discovery call before any number exists
✓All the code and every account in your name, so you are never locked in

Which one to pick

Your situation	Better fit	Why
Clear scope, ordinary functionality, want it built	One developer	no coordination overhead to pay for
First working version to test an idea	One developer	speed matters more than process
Internal tool for a small team	One developer	the spec lives in one person's head anyway
Several languages, ERP integration, regulated data	Agency	specialists and sign-off are the actual work
Hard deadline needing parallel workstreams	Agency	one person cannot compress calendar time
Brand identity built from nothing	Agency or a designer	a different discipline from development

Four questions to ask either one

Does writing the copy fall to you or to me? What exactly happens if I want a change after handover — included, quoted, or a monthly fee? Whose name are the domain, hosting and app-store accounts in? And what happens to this project if you disappear?

The third is the one people forget and the one that costs most later. The fourth is the one a solo developer should answer without flinching — see the questions below.

Frequently asked questions

What happens if you are ill, or on holiday, or busy?

This is the real risk and it deserves a straight answer rather than a reassuring one. One person is a single point of failure: an agency has bench depth and I do not. What I do instead is keep the work handover-ready — your code, your repository, your accounts, a short write-up of how it fits together — so another developer can pick it up without archaeology. Ask any solo developer this question, and be wary of one who says it is not a concern.

Can one person handle a big project?

Up to a point, and the point is real. A build needing several languages, ERP integration, regulatory sign-off, or more parallel work than one person can carry is an agency job, and I will tell you that rather than take it and let it drag. Most business websites, stores with ordinary functionality and internal tools are not that.

Is cheaper just worse?

Sometimes. Cheap can mean a template with your logo dropped on it, no testing and no support. What it means here is fewer people between you and the work: no project manager relaying messages, no account manager, no internal handoffs. That is a structural cost difference, not a quality one — but you should check which kind of cheap you are being offered.

Who owns the work?

You do. All the code, the repository, and every account in your name — domain, hosting, app stores. Ask this before signing anything with anyone: if the domain or hosting sits in the supplier's account, the site is not really yours, and moving it later is a conversation you do not want to have.

If this sounds like your situation

Starting prices for every service are published — see the pricing page. Describe the project in a few lines and you get a price and a timeline within 24 hours.

Describe your project → See pricing