Technote

Development workflow Practical

Series What to know before you hire a developer Part 7 of 8

Freelancer or agency: the real difference is continuity

Neither is better. They carry different risks, and the contractual moves that cover those risks are different too.

“Freelancers are cheap and agencies are expensive” explains almost nothing about this decision. Good independents are not cheap, and small studios are frequently not expensive. What actually separates the two is continuity — what happens to the work when that person is not there.

Either can be an excellent choice. What matters is knowing which risk each carries and using the contract to cover only that risk.

Where the two genuinely differ

Not better and worse — different blanks, and a contract is the document that fills them

Working with an individual has obvious advantages: the person deciding and the person building are the same, so communication is fast and the context lives whole in one head. It also lives only in one head, which is why documentation and repository ownership matter most in this arrangement. The handover list from part five earns its keep here.

Working with a company buys continuity. Work carries on when staff change, and several specialisms come through one point of contact. In exchange, who is actually building it can become unclear and there is an additional step in every conversation. Asking “who will do this work, and how will we be told if that changes” before signing is the direct answer to that risk.

Choose on the checks, not the size

Whichever you meet, the things to look for are the same. Judge the way of working rather than the shape of the business.

What to look for in a supplier — the same list whether they are one person or forty

Not one line on that list has anything to do with size. There are solo practitioners who write scope and exclusions immaculately, and there are sizeable firms that would rather start first and sort it out later. The judgement rests on documents, not on shape.

Using both

One arrangement comes up often in practice: the build with one supplier, ongoing care with another. Building is project-shaped work and maintenance is repeating work, and the people who are best at each are not always the same people.

It works on one condition: the handover has to have been done properly. With account ownership settled and documentation in place this arrangement runs very well; without them, responsibility blurs between the two. Part five is effectively the prerequisite.

We frequently occupy one side of exactly that arrangement — the original builder stays, and we take on the upgrade and optimisation work separately. Accounts stay in the client’s name and the work is recorded either way. Scope is on the optimization program page and the procedure on our process page.

Next part

The last part is about operating instinct. You do not have to read code to notice the signals of technical debt.

More on this topic

All technotes

Development workflow Practical

Turning taste arguments into rule checks

"It feels a bit cramped" can be neither argued with nor fixed. Spacing off the scale, colour off the palette, contrast below threshold, missing states — four rules…

Designers 9 min read

Development workflow Practical

Do not swap everything at once

A full swap makes every problem appear at the same moment — which means none of them can be attributed. So you switch one template at a time.

Designers 6 min read

Development workflow Practical

Adding an SCSS build, and whether to commit the output

WordPress themes are expected to deploy without a build step, which leads to the opposite conclusion from ordinary application code — and to its own costs.

Developers 7 min read

₩270,000 · Join the program