Freelancer or agency — which actually fits

It depends on three variables: how parallel the work is, how much process you want between you and the code, and budget. One codebase with a clear owner → a senior freelancer. Multiple workstreams (brand, site, app, campaigns simultaneously) → an agency. The decision framework, with edge cases, is the comparison guide.

On rate, usually — agencies typically run 30–60% above independents for comparable calibre because you fund project management, QA and bench capacity. On total cost, not always: agencies bundle services a freelancer would bill separately or you would manage yourself. Cheaper-per-hour and cheaper-overall are different questions; price the outcome, not the hour.

The person who sold you the project builds it — no account-manager telephone game. Direct communication, faster decisions, senior attention (agencies staff juniors after seniors close), and no markup funding overheads. For one codebase with a clear owner, the senior-freelancer structure is hard to beat.

Parallel capacity — designers, developers, content and marketing working simultaneously; process rails (PM, QA, procurement-ready contracts); and resilience — an agency has a bench if someone leaves mid-project. For multi-workstream programmes and enterprise buying requirements, those rails are worth the premium genuinely.

Honest ones: capacity ceiling (one person, one queue), bus-factor of one (illness moves your timeline), and breadth limits outside their stack. Mitigations: written scopes, staged payments, and independents who maintain a vetted specialist network instead of pretending to be infinite.

The senior who pitched rarely does the work; layers add cost and dilute signal; and smaller clients get the B-team while the A-team serves the anchor accounts. Mitigations: name the team in the contract, demand direct developer access, and check who your day-to-day contact actually is before signing.

Usually a senior freelancer on a proven CMS: the scope is one site, the budget is better spent on quality than process, and one accountable contact beats a rotating pod. An agency earns its premium when the site is one piece of a simultaneous rebrand-plus-marketing programme.

For an MVP or marketing site: a senior freelancer, decisively — speed and direct iteration matter more than process at that stage. Move toward agency or in-house when workstreams multiply faster than one person can sequence them. The staging logic is laid out in the in-house vs freelance guide.

Three genuine triggers: you need several specialists in parallel within one programme; procurement requires enterprise contractual rails; or the project is large enough that a single point of failure is unacceptable. Outside those, a direct senior covers most business builds with less overhead — the structural comparison is here.

Reliability comes from structure, not org form: written scopes, staged payments, reference-checked history and clean handover terms. A disciplined freelancer with those beats an agency without them — and vice versa. Ask both the same question: "show me a project that went wrong and what you did." The answer tells you more than the letterhead.