OLD SCRIPT DETECTED
“I can't say no to spec work or I'll lose the client”
Try this response:
“Spec work proves I’ll work for free. That is not the proof I’m selling.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I can't say no to spec work or I'll lose the client”
YOUR RECORDED RESPONSE
“Spec work proves I’ll work for free. That is not the proof I’m selling.”
ONE PRIVATE MOVE
Open a blank note and write two columns: "paid work" and "free proof." Move three current tasks, asks, or sample ideas into the column they belong in, then save and close the note without changing any client message.
When free work starts looking like safety
- The unpaid mock-up on your deskThe client has not said yes yet, but the ask is already on your plate: a quick concept, a sample layout, a little proof that you can do the job. You tell yourself this is how freelance design works. If you push back, they will move on to someone hungrier, someone easier, someone willing to do the first round for free.
- What that bargain actually costsYou say yes before the rate conversation is even settled, and now the rest of the project inherits that logic. A “small” request becomes another sample, then another revision, then scope that keeps stretching because the original price never had a chance to stand on its own. The work is visible; the fear is not, but it is doing the steering.
A cleaner way to handle the ask
You do not have to pretend spec work is a favor you owe in order to be taken seriously. You can leave the draft unfinished, label what belongs to paid work, and keep your options open without volunteering proof that comes before payment. That is a decision you can make privately, with no speech to rehearse for anyone else.
TRACE · 01/04
How this script runs you
- You accept unpaid test projects because you picture the client disappearing the moment you hesitate.
- A rate objection makes you soften your price immediately, before anyone has actually challenged it.
- A request for “just a little extra” turns into free labor because you do not want the project to feel fragile.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Spec Work Trap
The hidden rule says your value has to be demonstrated in unpaid work first, because payment is something you earn by lowering the risk for the client. Under that rule, saying no to spec work feels like saying no to the job itself, so you keep offering proof, revisions, and extras in advance.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- Spec work proves I’ll work for free. That is not the proof I’m selling.
- My rate is the number that keeps this work sustainable.
- "That’s outside the scope" is a professional sentence, not a threat.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“I can't say no to spec work or I'll lose the client”
I say
“Spec work proves I’ll work for free. That is not the proof I’m selling.”
Then I do one thing
Open a blank note and write two columns: "paid work" and "free proof." Move three current tasks, asks, or sample ideas into the column they belong in, then save and close the note without changing any client message.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I can't say no to spec work or I'll lose the client". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
What if the client only wants to see I can do the job?
Then the issue is the process, not your worth. You can notice that a free sample is being used as a gate, and still decide not to treat that gate as your only route in. The point is to separate evidence of skill from unpaid labor.
Isn’t refusing spec work just risky if I need the project?
It can feel risky because the old rule ties refusal to loss. But saying yes to unpaid proof also carries risk: it trains the project to expect labor before terms are clear. You are allowed to notice both risks without pretending one is harmless.
What if I already said yes to one free round?
Then the next move does not have to be dramatic. You can privately name which parts are already volunteered and which parts will need a paid scope if they continue. That distinction helps you stop carrying the spec-work logic into the rest of the job.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- AIGA Design Census 2022 — AIGA, 2022
- Graphic Artists Guild Handbook: Pricing & Ethical Standards — Graphic Artists Guild, 2022