A client you have worked with for two weeks suddenly says the logo "doesn't feel right", asks for a fourth round of changes, and mentions they will pay "once everything is perfect". Nothing in your agreement covers this, and you need the money. This is the most common way a freelance job goes sour, and most of it can be prevented or managed with a few habits.
This guide covers how to spot trouble early, what to say in common situations, how to protect your payment, and when walking away is the right call. It applies whether you work through a platform or directly with a client abroad. Competition for remote work is real, and losing a client hurts, but a bad client costs you time you could spend finding a better one.
First, work out what kind of difficult you are dealing with
Different problems need different responses. Before you reply to an annoyed message, name the problem.
| Problem | What it usually looks like | Best first move |
|---|---|---|
| Unclear brief | Client says "I'll know it when I see it" | Ask structured questions, share a sample or outline before full work |
| Scope creep | "Can you just also..." repeated | Point to the agreed scope, quote the extra work separately |
| Endless revisions | Same deliverable reworked again and again | Refer to the revision limit, then offer paid extra rounds |
| Slow or silent | Weeks to approve work or reply | Set deadlines for feedback in writing |
| Late or non-payment | Excuses, "next week", disputed invoices | Pause work, send a firm reminder, use platform protections |
| Disrespect | Rude messages, unreasonable hours demanded | Set boundaries once; end the contract if it continues |
Many "difficult" clients are simply inexperienced at hiring freelancers. They are not bad people, and a clear process fixes them. A smaller group will never be fixable, and you should learn to recognise them.
Prevent most problems before you start
Nearly every conflict traces back to something that was never written down. Before any paid work begins, put these in writing, even if it is just a message the client replies "agreed" to:
- Deliverables: exactly what you will hand over (for example, "one 1,200-word article" or "five social media graphics in PNG").
- Revisions: how many rounds are included, and what counts as a revision versus a new request.
- Timeline: delivery date, and how many days the client has to give feedback.
- Price and payment terms: total amount, currency, deposit, and due dates.
- What happens if the project stops: for example, the deposit is not refundable once work has started.
If you are still working out what to charge, see our guide to pricing your freelance services in dollars. And a clear proposal sets expectations from the first message, as covered in how to write a freelance proposal that gets replies.
Ask for a deposit
For direct clients, asking for a portion upfront filters out people who are not serious. A common approach is part before starting and the balance on delivery, or splitting a large job into milestones. On a platform, check how its escrow or milestone feature works on its own help pages, since rules differ between platforms.
Early warning signs worth taking seriously
- They refuse to define the scope but promise "lots of work later".
- They have fired several freelancers already and blame all of them.
- They push you to move off the platform before any work starts.
- They haggle hard on price, then expect more than the price covers.
- They want a free "test project" that is actually a real piece of work.
- They send urgent messages at odd hours and expect instant replies.
One red flag is a reason to ask questions. Three is a reason to decline politely. Also be careful of offers that look too easy or ask you to pay money first; our post on spotting paid programs that are not worth it uses a similar checking mindset, and fake job offers are a separate risk worth reading about on this blog.
Scripts for common situations
Keep your tone calm and factual. Short messages work better than long defensive ones. Adapt these to your own voice.
When the client keeps adding work
"Happy to help with this. It's outside the original scope we agreed (three landing page sections). I can add it for an extra fee of $X and it would extend delivery to Thursday. Shall I go ahead?"
You are not refusing. You are pricing. Many clients drop the extra request once it has a cost; others pay gladly.
When revisions never end
"We've completed the two revision rounds included in the project. I'm glad to do another round at $X, or we can wrap up here with the current version. Which do you prefer?"
When the feedback is vague
"To make the next version closer to what you want, could you point to two things you'd change and one example you like? That will save us both a round."
Examples are the fastest way out of "I'll know it when I see it".
When the client goes silent
"I haven't received feedback on the draft sent on the 5th. If I don't hear back by Friday, I'll need to move your project to the next available slot, which is in two weeks."
When payment is late
"Invoice 004 for $X was due on the 10th and is still unpaid. Please confirm the payment date today. I'll pause further work until it's settled."
Protect your payment
Money problems are the ones that really hurt, so build safeguards.
- Send proper invoices with a number, date, amount, due date and your payment details.
- Do not hand over final, unwatermarked files before payment where the setup allows it. For writing or design, share previews or low-resolution versions until the balance clears.
- Keep everything in writing on one channel. If a call happens, send a recap message afterward.
- Use platform dispute tools if you work through a marketplace. Read the dispute process on the platform's site before you need it, and confirm what evidence it accepts.
- Know your payout route. Confirm which payment methods the client can use and which ones work with your Nigerian, Ghanaian, Kenyan or South African account. Check with the payment provider directly for fees and supported countries.
For direct clients across borders, enforcing payment through courts is rarely practical for small amounts. That is why deposits and milestones matter more than any legal threat.
A hypothetical example
Imagine you agree to write four blog posts for a US startup for $200 total. You ask for $50 upfront, and the agreement allows two revisions per post. After post two, the client sends a long list of changes that amount to a full rewrite and says the tone is "off".
You first ask for two examples of the tone they like. They send a competitor's article. You rewrite once, free, because the brief was unclear and that was partly your miss. When they ask for another full rewrite, you cite the revision limit and offer a paid extra round at $15. They agree, and the posts three and four go through smoothly because you now have a style reference.
Now imagine the client refuses and also delays the balance. You stop at the delivered posts, invoice the completed work at the agreed rate, and keep the $50 deposit. You have lost some time, but not the whole project. Compare that with having no deposit, no revision limit, and four finished articles unpaid.
When to end the relationship
Some clients cost more than they pay. Consider ending the contract when:
- They have missed payments more than once.
- They are abusive or demand work outside any reasonable hours.
- They keep changing the goal after you deliver.
- Your effective hourly earnings have dropped far below what you could earn on other work.
Do it professionally. Finish or hand over what is paid for, send a short message such as "I won't be able to continue after this milestone. All completed work is attached once the outstanding invoice is paid," and do not argue. Avoid public rants or negative posts about the client; clients talk, and so do platforms.
Also be honest about your own part. Late delivery, missed instructions and poor communication cause plenty of conflicts. Power cuts and patchy data are real in many African cities, so tell clients early if you need extra time, keep a backup (power bank, mobile data hotspot, a nearby co-working space) and set deadlines with a buffer.
Common mistakes to avoid
- Starting work with no written agreement. Even a short email thread is better than nothing.
- Reacting angrily in writing. Wait an hour before replying to a harsh message.
- Quietly absorbing extra work. It teaches the client your boundaries do not exist.
- Taking the job at a very low price to win it. Underpriced work attracts the most demanding clients.
- Moving off the platform too early and losing its payment protection.
- Depending on one client for all your income, which makes it hard to say no.
Frequently asked questions
Should I give a refund if a client is unhappy?
It depends on the cause. If you did not deliver what was agreed, a partial refund or a free fix is reasonable. If the client simply changed their mind, offer paid revisions rather than a refund. Check your platform's refund rules if you use one.
What if the client disappears after I deliver?
Send two or three polite reminders with the invoice, then a final notice. On a platform, open a dispute using your saved messages and delivery proof. For direct clients, recovery is hard, which is why milestones and deposits matter.
Is it okay to fire a client mid-project?
Yes, if you handle it professionally and respect what has been paid for. Review your agreement for any notice terms first.
Do I need a formal contract?
For larger or ongoing jobs, a written contract is wise. For small jobs, a clear written scope and payment terms in an email or message can do. For legal questions about your specific case, speak to a qualified lawyer in your country.
Your next step
Open your current or most recent client project and check whether you can find the deliverables, revision limit and payment terms in writing. If not, send a short message today confirming them. That one message prevents more disputes than any script above.
Results from any side hustle or online work vary widely, and nothing here is a promise of income. Be wary of anyone who asks you to pay upfront to start earning.