Contracts with freelancers versus companies: the practical differences

What changes in continuity, liability, capacity and paperwork when an individual does your web work, and how to protect yourself.

3 minread 742words last updated

The short answer

Engaging a freelancer and engaging a company are different arrangements with different risks, and both can be excellent. A freelancer is one person: often highly skilled, usually charging less per hour, directly accountable, and a single point of failure for continuity, capacity and availability. A company brings continuity across people, capacity for larger work, formal liability and processes, at a higher price and with the risk that the person you met is not the person who does the work. The protections you need are the same in both cases: everything in your name, code in your repository, documentation, a written scope and exit terms. They simply matter more with a freelancer, because there is no one behind them. And engaging individuals carries employment and tax rules in most jurisdictions that place obligations on you as the client; check them with an advisor.

The practical differences

AspectFreelancerCompany
Who does the workThe person you hiredWhoever the company assigns; ask
ContinuityDepends on one person’s availabilityAcross people, if the company runs properly
CapacityLimited; larger work takes longer or needs subcontractorsScales with the team
PriceUsually lowerHigher; includes overhead and process
AccountabilityDirect and personalContractual and organisational
Liability and insuranceOften limited; check professional insuranceUsually formal; check the cap
Processes: testing, review, pipelineDepends entirely on the individualShould exist; verify
Exit and hand-overCritical to define; nobody else holds the knowledgeShould be routine; verify
Legal and taxRules on engaging individuals apply to youStandard supplier contract

Protecting yourself in each case

  1. Accounts in your name for domain, hosting, repository and services, with the supplier as a collaborator. Non-negotiable with anyone; vital with an individual.
  2. Code in your repository from day one, with history.
  3. Documentation that passes the stranger test, delivered as part of the work.
  4. A written scope, acceptance criteria and exit terms, however friendly the relationship.
  5. A continuity plan with a freelancer: who could take over, on what notice, from the documentation.
  6. With a company: the named people doing the work and a clause about changes to them.
  7. Check the rules for engaging individuals in your jurisdiction and use an agreement drafted for them.

Choosing between them

For a defined project with a clear scope, a strong freelancer with proper ownership terms and documentation is often the best value available. For ongoing work where continuity, capacity and response times matter, a company or a small partner with more than one person is safer, provided you know who does the work. The choice matters less than the conditions; a well-protected freelancer engagement beats a badly protected company one, and the reverse is also true.

What this means for you

Choose a freelancer or a company for the work and the relationship you need, and protect yourself the same way in both cases: your accounts, your repository, documentation, written scope and exit terms, with a continuity plan for an individual and named people for a company. Check the legal rules for engaging individuals. The arrangement that goes well is the one where the conditions were set before anyone needed them.

Written by the CivSec S.M.A.R.T team

We build and run websites, software and AI systems for businesses. We write about what we see in that work, in plain language, and we update articles when things change.

Last checked . Spotted something outdated? Tell us.

Frequently asked questions

Is it risky to have our whole website built by one freelancer?

The build itself is often excellent. The risk is afterwards: one person's availability, health, holidays and career decide your continuity, and there is no team behind them. Mitigate it the way you would with any supplier and more strictly: accounts in your name, repository in your account, documentation that passes the stranger test, and a plan for who takes over if they are unavailable.

Are companies always more reliable?

No. A company can assign a junior to your project, change the team without telling you, or close. What a company can offer is continuity across people, capacity and formal processes; whether it does is a matter of the specific company. Judge on the same evidence either way: ownership terms, documentation, references, and who exactly will do the work.

What about the legal side of engaging a freelancer?

Rules on self-employment, tax and liability for engaging individuals differ by country and can place obligations on the client. Use a written agreement that sets out the independent nature of the work, deliverables, intellectual property assignment and liability, and check the rules that apply in your jurisdiction with an advisor. Getting this wrong is a risk for you, not only for them.