To hire a freelance developer directly: shortlist people whose shipped work you can open and use, send a brief that states the scope and the budget, check that the person matches the work, then start with one small paid slice before committing to the whole project. It takes an afternoon.
Here is why that beats the usual route. Most advice assumes you will post a job on a marketplace, sort through fifty proposals written by people who did not read it, and pick whoever seems least risky. That process exists because it is easy to run at scale, not because it works. What follows is the alternative, step by step.
Start from work you can open
A CV tells you what someone says they did. A shipped product tells you what they finished. Those are very different claims, and only one of them can be checked in ninety seconds.
Before you talk to anyone, get a short list of people whose work you can actually open: a live site, an App Store listing, a tool you can sign up for. Then use it:
- Open the thing. Use it for five minutes like a real user.
- Look at what happens when you do something wrong. Empty states and error messages are where care shows up.
- Check it on a phone.
- If it is a paid product, look at the pricing page. Someone who shipped billing has dealt with real edge cases.
You will learn more from that than from any interview, and you will walk into the conversation able to ask specific questions.
Write a brief that can be said no to
The most useful brief is one a good developer can read and decline. That means it contains enough to be evaluated. Four things:
- What exists now. Nothing, a Figma file, a half-built app, a live product with 400 users. Say which.
- What "done" means. One paragraph. Not a feature list. An outcome. "Customers can pay with a card and get a receipt by email."
- Constraints that are real. A deadline that matters, a stack you cannot leave, a platform you must ship to.
- Budget, as a number or a range. This is the part people leave out, and it is the part that wastes the most time.
If you do not know your budget, say what the work is worth to you. "This unblocks about $2k/month of revenue" is a useful sentence. "Let's discuss budget" is not.
The first message
Short, specific, and human. Reference the work you looked at. Say what you need and what you can pay. Ask one question.
Hi, I used [their app] this morning, the onboarding is genuinely good. I have a Next.js app with auth and a dashboard already built, and I need Stripe subscriptions plus a billing page. Budget is around $1,500 and I would like it live in three weeks. Have you done Stripe billing before?
That message gets answered. "Hey, are you available for a project?" does not, because answering it costs the reader more effort than sending it cost you.
Check that the person is real
Not in a paranoid way. In a five-minute way.
| Check | What you are looking for |
|---|---|
| A permanent home for their work | Their own domain or a store listing, not a temporary preview link |
| A public trail | GitHub, X, a blog, a changelog: anything with dates on it |
| The same name across places | Profile, repo commits, domain, invoice |
| A specific answer to a specific question | Ask about a trade-off in their own product |
None of these are proof on their own. Together they are usually enough.
Structure the first job so it can fail cheaply
The mistake is not hiring the wrong person. The mistake is finding out three months and one lump-sum payment later.
- Make the first engagement small. A week, a defined slice, its own price.
- Pay in stages. Something up front so they can start, the rest on delivery. For a first job with someone new, a 30/70 or 50/50 split is normal and neither side should be offended by it.
- Get access sorted on day one. Repo, hosting, domain, third-party accounts. In your accounts, with them invited. This is the single most common source of pain later, and it costs nothing to get right at the start.
- Agree how you talk. One channel, one weekly checkpoint. Not four tools.
If the first slice goes well, the second one is easy and you have a person you can call again. If it goes badly, you are out one week, not one quarter.
What a fair rate looks like
There is no single number. An independent developer in a low-cost country charges differently to a studio in London, and both may be right for you. But two things are generally true:
Cheap is expensive when the work has to be redone. And an experienced person who quotes a bigger number often finishes in less time, so the total is closer than the day rates suggest.
Ask for a quote for the outcome, not for hours. Then you are comparing prices for the same thing.
Where Shipfolks fits
Shipfolks is a directory of independent builders and the products they shipped. Every profile leads with real work you can open, and there is a green dot on the people currently open to freelance work.
Contacting them is free, the message goes straight to the builder, and we take no cut of whatever you agree. We are not a middleman: we do not vet the work, hold the money, or mediate the job. That is deliberate, because it keeps the price at zero for both sides, but it does mean the checks above are yours to run.
If that trade is the one you want, browse the builders who are open right now.