A freelancer is not a bad option. For point tasks it is often the best choice: cheaper than a studio, quicker to agree. The problem is not freelancers as a class but how little of the arrangement protects the client: no contract, no process, no guarantees — meaning all the risks are on you by default. We regularly pick up “abandoned” projects and know these pitfalls firsthand — here is where clients usually lose money and deadlines, and what actually works as protection.
Pitfall one, before the start: a vague specification
“We need a website like our competitor's, only better” — with that brief, any argument about the results is lost in advance. What is in scope, what counts as “done”, how many pages, what logic — without answers, every edit turns into haggling and every deadline into a negotiation.
Protection: a written specification, even half a page: the list of pages/screens, what must work, what is not included. If a freelancer is against a specification — that is not saving paper, that is a forecast for the whole project.
Pitfall two, payment: 100% prepayment
A hundred percent prepayment means you are lending to the contractor at zero percent with no collateral. The most common “the freelancer disappeared” story starts exactly there.
Protection: stages paid against results — for example 30% to start, 40% after the design/intermediate demo, 30% after acceptance. Every payment is tied to a concrete visible result, not to a promise.
Pitfall three, process: disappears for two weeks
A week of silence, then “I was swamped, this week for sure”, then another week of silence. A freelancer runs several projects in parallel — and yours always burns less for them than it does for you.
Protection: agree on regularity (a short status update every 2–3 days) and fix it in writing at the start. Three missed updates are a reason to revisit the arrangement before the deadlines are lost. Intermediate demos per stage: watching the work live is cheaper than sorting it out at the end.
Pitfall four, rights and access: nothing is registered in your name
The most expensive mistake: the domain is registered to the contractor's personal email, the hosting is their account, the repository is their profile. While relations are good, none of it matters. In a conflict you discover that the website is legally and technically their property, and “moving it” becomes a separate conversation — sometimes a separate development project.
Protection: the domain, hosting and all accounts are registered to you or your company before work starts. The contractor works under your access. Rights to the design and code transfer to you by contract. The code lives in your repository from the first commit.
Pitfall five, quality: “it works, so it works”
The website opens on the contractor's laptop — and falls apart on a phone. Forms never reach the inbox. A month later a vulnerability turns up, and your client database leaks. A solo worker physically has nobody to review their code — nobody to double-check.
Protection: include a checkable list in acceptance: responsiveness on real phones, all forms working, loading speed, basic SEO setup, backups. Plus a warranty period: bugs found after delivery get fixed for free.
Pitfall six, after delivery: no documentation, no author
The project is delivered, the contractor is “on vacation, out of reach”, and six months later you need to fix a form or move to different hosting. The next specialist opens the code and sees an unstructured wall with no description — the price of changes suddenly doubles, because “first we need to figure it out”.
Protection: put the handover of sources and minimal documentation (how it is deployed, where the admin panels are, what lives where) into the contract as a condition of final payment. Cheaper to demand it at the start than to pay for “archaeology” later.
When a freelancer is the right choice
- The task is limited and clear: a landing page from a ready-made design, edits, an integration, a small improvement
- There are proven recommendations — live ones, from people whose projects you have seen
- The scope fits a single “payment → acceptance” cycle, or two
When you need a team: the project is part of the business (a store, a service), deadlines are critical, several specialists are required at once, or you are not ready to be the project's “technical director” yourself.
In short
Almost all losses in freelance work come from three things: the scope is not fixed, payment is not tied to results, and the rights and access are not yours. The protection is simple and works with any contractor: a written specification, staged payment against visible results, the domain and accounts in your name, the code in your repository, a warranty period. And if the project is critical to the business — choose a contractor whose process protects you automatically.