Coweb·Hub
← All postsFreelancing

How to hire a freelance developer without getting burned

Coweb Hub · 17 November 2026 · 3 min read

Most bad freelance experiences are not caused by bad freelancers. They are caused by an unclear brief, a payment structure that suits nobody, and nobody owning the accounts.

Check what they have done, not what they claim

A portfolio of pretty screenshots proves a designer existed. Ask for live links you can open, and ask which parts they personally did.

Ask what went wrong on a recent project and how it was handled. Anyone with real delivery experience has an answer. Someone who says nothing ever goes wrong has either not shipped much or is not being straight with you.

If the work is code, ask to see some. You do not need to read it; you need to see that it exists and that they are comfortable showing it.

Write the brief that prevents the argument

Most disputes come from a difference about what was included. Write these down before any money moves.

What exactly is being delivered, listed as things, not adjectives.

What is explicitly not included. This section saves more relationships than any other.

How many rounds of revision are included, and what counts as a revision versus a new request.

What you will supply and by when. Late content from the client is the most common cause of a late project, and it should be on paper.

Who owns the accounts and the code at the end. The answer should be you.

Structure payment so neither side carries all the risk

Nobody should be fully exposed. A deposit of twenty to fifty percent, then payments tied to milestones you can actually see.

Avoid paying everything up front. Avoid expecting a stranger to do everything before being paid anything. Both arrangements attract the wrong people.

For hourly work, agree a cap, or agree to review at a set number of hours. Open-ended hourly with no checkpoint is how budgets quietly double.

The warning signs

A quote that arrives without a single question being asked. Anybody who can price your project without understanding it is pricing a template.

Reluctance to put the scope in writing.

A price far below everyone else. It is rarely generosity; it is usually a misunderstanding of the scope that you will pay for later, in a different currency.

Communication that is already slow before any money has changed hands. It does not improve after.

Resistance to you owning the domain, hosting or code.

Keep the keys

This is the one that costs the most when it goes wrong. The domain, the hosting account, the code repository and the email administration should be in your name, with your logins.

Grant your freelancer access. Do not receive access to your own business.

You can trust someone completely and still hold the keys. A professional will expect it.

Starting small is not an insult

A small paid first piece of work tells you more than any interview. How they communicate, whether they hit a date, whether they ask good questions.

It is a cheap way to find out, and good freelancers prefer it too, because working with an unclear client is its own risk.

Keep reading

Comments

Comments from guests are checked before they appear. Logged-in comments post straight away.

One hub

8 services, one team

24-hour quote

On every inquiry

AI-native delivery

Built in, not bolted on

No lock-in

Project or retainer, your call