Client phrase pattern
Client Asking for a Free Test Project — Red Flag or Reasonable?
Clients want to know who they're hiring. That's legitimate. A portfolio shows past work — a test shows current capability on their specific brief.
The phrase
"Can you do a quick test first?" / "We'd like to see a sample before we commit" / "Just a small trial piece to see if it's a fit" / "We don't pay for test work, but the project is significant."
Why it sounds reasonable
Clients want to know who they're hiring. That's legitimate. A portfolio shows past work — a test shows current capability on their specific brief.
Some freelancers accept test work, especially early in their career or when breaking into a new niche. The logic: a small unpaid piece leads to a large paid project.
Sometimes that's true. Usually it isn't.
What it actually signals
The work has value — that's why they want it. If the test is genuinely low-stakes, the client can afford to pay for it. "We don't pay for tests" is a policy choice, not a financial constraint. It signals that the client has decided your time isn't worth paying for until they've decided they like you.
The follow-through rate is low. Clients who ask for free tests are often running the same request across multiple freelancers simultaneously. They'll collect several pieces of work, use the best one, and pay nobody — or pay one person a fraction of what the work is worth.
It sets the tone for the project. A client who starts by asking you to prove yourself for free has already established the power dynamic. Every subsequent negotiation — rates, revisions, scope — will happen from that position.
The difference between a test and a paid trial
A paid trial is reasonable. A short piece of work at your standard rate, scoped clearly, with payment on delivery — that's a legitimate way for both sides to assess fit.
An unpaid test is different. It transfers all the risk to you: your time, your ideas, your work — with no commitment from the client.
If a client won't pay for a trial piece, they've told you how they value your time.
When it's a harder call
Some industries have norms around spec work — advertising and design have long histories of unpaid pitches. If you're in one of those industries and the opportunity is genuinely significant, the calculus is different.
But even then: know what you're agreeing to. A test with no defined scope, no feedback commitment, and no clear path to a paid project is just free work.
What to say
"I don't take on unpaid test work, but I'm happy to do a paid trial piece at my standard rate — [X for Y deliverable]. That gives us both a clean way to assess fit without either side carrying all the risk."
A good client will either agree or show you their portfolio of work from the test request. A client who pushes back hard is confirming the red flag.
What to clarify before deciding
- Is there a defined scope for the test, or is it open-ended?
- How many freelancers are being asked for the same test?
- What happens after the test — is there a specific project, or is it "we'll see"?
- Has the client worked with freelancers before, and how did those relationships go?
Scan the full message
The test request rarely appears in isolation. The rest of the message usually contains scope signals, budget language, and relationship red flags that tell you more about what this project will actually look like.
Paste the full inquiry into FreelancerGuard and see the complete risk picture before you reply.
Scan the full client message
This phrase matters more when it combines with urgency, vague deliverables, missing budget, or pressure to start. Paste the full message to see the complete risk pattern.
Check a client message freeRelated patterns