It happens to every freelancer. Sometimes it's subtle: "Can you just throw together a quick mockup so we can see if you're a good fit?" Sometimes it's brazen: "We don't have budget right now, but this would be great exposure for your portfolio."
Either way, someone is asking you to work for free. And you need to respond without torching the relationship or caving to a request that devalues your work.
This is one of the trickiest situations in freelancing. Not because the answer is complicated (don't work for free), but because the delivery matters. There's a difference between firmly declining and burning a bridge.
Recognize What Free Work Actually Looks Like
Free work isn't always obvious. It comes in a lot of disguises:
Some of these sound reasonable on the surface. That's what makes them dangerous. A "test project" might seem like a fair ask until you realize they're getting usable deliverables without paying for them. "Quick revisions" that go beyond the agreed scope are free work with a polite wrapper.
The common thread is someone getting value from your labor without compensating you for it.
Why You Shouldn't Do It
Let's get the obvious reason out of the way: you deserve to be paid for your work. Your skills took years to develop. Your time has value. Working for free tells the client that your time isn't worth paying for.
But there are practical reasons too. Clients who start a relationship expecting free work tend to continue expecting discounts and favors throughout the project. You're setting a precedent. If you do free work to "prove yourself," you're training the client to believe they can always negotiate you down.
There's also the signal problem. A client who asks for free work before hiring you is telling you something about how they value creative work in general. Pay attention to that signal.
How to Say No to Spec Work
Spec work is when a client asks you to create actual deliverables as part of the selection process. "Design us three homepage concepts and we'll choose our favorite (and our favorite designer)."
Here's a response that works:
"Thanks for considering me for this. I don't do spec work, but I'd be happy to walk you through my process and show you similar projects I've done for other clients. That way you can get a feel for my approach and quality without either of us committing to unpaid work. Would a 20-minute call work for you this week?"
This does a few things. It says no clearly. It offers an alternative that still addresses their underlying concern (can this person do the work?). And it stays professional without being preachy about it.
How to Handle "Test Projects"
Test projects are a gray area. Some companies genuinely use paid test projects to evaluate freelancers, and that's fine. The issue is when the test project is unpaid.
"I'd love to do a test project. My rate for a small trial project like this would be [rate]. I find that paid test projects lead to better results for both sides because I can give it the same attention I'd give any client work. Want me to send a quick scope and estimate?"
If they push back and insist it needs to be free, that tells you everything you need to know.
How to Respond to "It's Good Exposure"
This one's a classic. It implies that the client's platform or name is so valuable that you should be willing to work for the privilege of being associated with them.
Keep it light: "I appreciate the offer, but I'm not in a position to take on unpaid projects right now. My rate for something like this would be [rate]. If that works with your budget, I'd love to be involved."
Don't argue about whether exposure has value. Don't explain your rent situation. Just state your rate and let them decide.
How to Handle Scope Creep Disguised as "Quick Favors"
This one is different because it happens with existing clients, not prospects. You're in the middle of a project and the client starts asking for things that weren't in the original scope.
"That sounds like a great addition. It's outside the current scope, so let me send over a quick estimate for adding it. Shouldn't take long to price out."
This language is important. You're not saying "no, that's extra." You're saying "yes, and here's what it costs." You're still being collaborative. You're just making sure you get paid for the additional work.
For more on handling scope changes, check out how to write a scope change email and how to stop scope creep with email scripts.
When Free Work Might Be Worth It
I want to be honest here. There are rare situations where working for free (or at a discount) makes strategic sense.
Pro bono for a cause you care about. Volunteering your skills for a nonprofit or community organization you believe in is different from doing free work for a for-profit company that just doesn't want to pay you.
A genuine portfolio gap. If you're pivoting to a new niche and have zero samples, doing one discounted project to build your portfolio might be worth it. One. Not five.
A referral relationship. If a client who's sent you $50,000 in work over the years asks you to do a $200 favor, the math probably works out. Relationships have value too.
The key distinction is agency. If you're choosing to work for free because it serves your goals, that's a business decision. If someone is pressuring you to work for free because they don't want to pay, that's exploitation with a friendly face.
Scripts You Can Copy
Here are a few responses you can adapt for different situations:
For spec work requests: "I don't take on unpaid spec projects, but I'm happy to share my portfolio and walk you through my process so you can evaluate the fit."
For unpaid test projects: "I'd love to do a trial project. My rate for a small-scope engagement like this is [rate]. That way you can see my work and process before committing to anything bigger."
For exposure offers: "I appreciate the opportunity, but I'm not able to take on unpaid work at this time. My rate for this type of project is [rate]. Happy to discuss if there's flexibility in the budget."
For scope creep: "Great idea. That's outside the current scope, so I'll send over a quick estimate for adding it on."
For "it's a quick thing": "Even quick projects involve research, revisions, and communication time on my end. I can turn this around fast for [rate]. Want me to put together a mini scope?"
The Bigger Picture
How you handle requests for free work shapes your entire freelance career. Every time you say yes to unpaid work, you make it slightly harder to charge full price next time. Every time you politely but firmly say no, you reinforce your value, both to the client and to yourself.
The freelancers who earn the most aren't necessarily the most talented. They're the ones who've gotten comfortable saying "my rate for that is [rate]" without flinching. That comfort comes from practice.
Start now. The next time someone asks for free work, respond with your rate. See what happens. You might be surprised how often they say yes.