How to hire a freelancer in Nepal safely
Most bad freelance hires fail for the same three reasons — an unclear brief, paying up front, and no written scope. Here is how to avoid all three.
By The Nepal Can Work team · Updated
Hiring a freelancer online is mostly a trust problem. You are asking someone you have never met to do work you cannot verify until it is finished, and they are asking you to pay for it. Almost every horror story — the developer who vanished, the logo that never arrived, the writer who wanted half up front and was never heard from again — comes down to one of the two sides carrying all the risk.
This guide is about removing that risk structurally rather than hoping for a good person. It is written for clients hiring in Nepal, but most of it applies anywhere.
1. Never pay a freelancer directly before the work exists
This is the single most important rule and the one most often broken. A direct bank transfer, an eSewa payment, a Khalti transfer — once the money leaves your account it is gone, and your only recourse is asking nicely.
The alternative is escrow: you pay, but the money is held by a third party and does not reach the freelancer until you approve the delivered work. The freelancer can see the money exists and is committed, so they start work confidently. You keep control of the release. Neither side has to trust the other's good intentions.
How escrow works here
On Nepal Can Work your payment is held by the platform, never forwarded to the freelancer on receipt. You trigger the release when you approve the delivery. After approval there is a short hold — 6 hours by default — before the payout is queued, which is the window for raising a problem you spot immediately after clicking approve.
If a freelancer pressures you to pay outside the platform — 'it is cheaper without the fee', 'just send it to my eSewa' — treat that as the end of the conversation. Off-platform payment is not a discount, it is the removal of every protection you have. There is no dispute process for a bank transfer.
2. Write a brief that can be judged finished
The second most common failure is not dishonesty, it is ambiguity. 'Design me a logo' cannot be completed, because there is no state of the world where it is objectively done. 'Three logo concepts, final one delivered as SVG and PNG at 1000px, in the two brand colours below' can be.
A brief that works has four parts:
- The deliverable, as a file list. Not 'a website' — 'a five-page Next.js site, source in a Git repo, deployed to a URL I can open'.
- The definition of done. What has to be true for you to approve it. Be specific enough that a stranger could check.
- The revision count. Two rounds is normal. Unlimited revisions is not generosity, it is an argument waiting to happen.
- The deadline, with your own dependencies named. If you owe them copy or logins, say when.
Fifteen minutes writing this saves days later, and it is the document a dispute is judged against if one ever happens.
3. Check the things that are actually checkable
Profile photos and confident messages tell you nothing. These do:
- Portfolio work in the same category as your job. A brilliant illustrator is not evidence for a brilliant React developer.
- Completed orders on the platform, not follower counts or years-of-experience claims. Platform history is the part nobody can self-declare.
- Reviews with substance. 'Great work!' is noise. A review describing what was delivered and how the revisions went is signal.
- How they respond to your brief. A freelancer who asks two sharp clarifying questions before quoting is worth more than one who says yes to everything immediately.
That last one is the most underrated. Someone who agrees to every requirement without a single question has usually not read them.
4. Understand what you are actually paying
Be clear on the total before you commit. On Nepal Can Work the freelancer's price is what they receive; a platform service fee is added on top at checkout, currently 20%, and the exact figure is always itemised on the checkout screen before you pay.
That fee is what pays for escrow, the dispute process, and support. It is worth knowing one thing about it in advance: the service fee is not refundable, including when an order is cancelled or refunded. The escrowed work amount comes back to you; the fee for handling it does not. Every honest marketplace works this way, but not all of them say so before you pay.
5. Keep the whole conversation in one place
Move to WhatsApp or Viber and you have quietly opted out of the record. If a dispute happens, the messages, the files, and the delivery timestamps are the evidence — and evidence that lives on someone's phone is not evidence anyone else can see.
Keep the brief, the revisions, and the delivery in the order thread. It costs nothing and it is the difference between a resolvable disagreement and your word against theirs.
6. Know what happens when it goes wrong
Sometimes the work is genuinely not what was agreed. A good platform has a process for that, and you should know it before you need it:
- Ask for a revision first. Most problems are a misunderstanding, and most freelancers would rather fix it than fight.
- Propose a settlement. If it is partly right, offer a partial release — say 60% for work that is 60% there. Both sides walk away and it resolves immediately, with no staff involved.
- Open a formal dispute. If you cannot agree, staff review the brief, the delivery, and the thread, and decide. The money stays in escrow the entire time.
The order in which you try these matters. Going straight to a dispute over something a revision would have fixed wastes days for everyone.
The short version
- Pay into escrow, never directly. Refuse off-platform payment requests.
- Write a brief someone else could mark as done or not done.
- Judge portfolios and completed orders, not confidence.
- Know the total, including the fee, before you pay.
- Keep everything in the order thread.
- Revision, then settlement, then dispute — in that order.