Last month a UI/UX freelancer told me about her worst client ever.
He sat in her Figma file. All day. Watching her cursor move. He'd ping her on Slack when she stopped designing for more than ten minutes. He'd paste AI-generated mockups from Midjourney and demand pixel-exact recreations, then change direction the next morning because he "saw something better on Dribbble."
Three weeks in, she'd done six versions of the same homepage. Her effective hourly rate had halved. She was messaging me at 11pm asking how to fire him without losing the deposit.
Here's the thing: every red flag was visible in the discovery call.
He'd said "I like to be hands-on." He'd said "I move fast and I expect my team to keep up." He'd shown three reference sites and said "I want it to look like all of these, mixed together." None of this was hidden. She just didn't have a script for what to do with the signal.
That's the dirty secret of nightmare clients. They aren't ambushes. They're failed onboardings.
The patterns were all there
- Hands-on = wants to supervise mid-process.
- Move fast = will change direction without warning.
- Three reference sites = doesn't actually know what they want.
These aren't bad people. They're people with normal anxieties about spending money on something they can't fully evaluate. Your job in onboarding isn't to filter them out — it's to install the operating system you're going to use together. Skip that step and they install theirs by default. Theirs always involves watching your cursor.
The conversation that needed to happen in the kickoff call had three pieces.
1. Process agreement: phases and feedback windows
You don't show work continuously. You show it at defined gates: Discovery → Wireframes → Visual Direction → High-Fidelity → Handoff. Each gate has a 48-hour feedback window where the client consolidates input from their team and sends one structured response.
Outside that window, you're heads-down. No live commentary. No "just checking in" Slacks. No watching the cursor.
This isn't rigidity — it's how the work gets good. Continuous feedback creates Frankenstein designs, because every passing thought gets the same weight as a considered opinion.
2. Change policy: approval is approval
Once a phase is signed off, going back costs extra. Not as a punishment — as a reflection of reality. Reopening visual direction after wireframes are approved means redoing the wireframes. That's new work. New work has a price.
Standard rate: your hourly × 1.5, billed in advance, on a new mini-SOW. Write this into the proposal. Reference it cheerfully when it comes up: "Totally doable! That's a Phase 2 change, so I'll send the addendum over and we'll slot it in next week."
The cheerful part matters. You're not punishing them. You're showing them the menu.
3. Supervision norms: review gates, not shoulder surfing
Your Figma file is not a livestream. Edit access is for the people doing the work. View access for stakeholders comes with a note: "This is a working file. What you see between review gates is in-progress and will look broken. Please save reactions for our scheduled review."
Most clients have never been told this. They assume the default is "watch everything." When you set a different default, they relax. Watching designers work isn't actually fun for clients — it's anxiety management. Replace the anxiety with predictability and they'll happily stay out.
Three copy-paste phrases for kickoff
Steal these. Send them in writing before kickoff, then say them out loud on the call.
"I work in phases with 48-hour review windows. Between reviews I'm heads-down — that's where the quality comes from. Sound good?"
"Once we sign off a phase, going back is totally fine but it triggers a Phase 2 addendum at 1.5×. I'll always quote it before doing the work, so there are no surprises."
"I'll share the Figma in view-only between reviews so you can peek if you want, but please save reactions for our scheduled gate — the in-between is messy on purpose."
Three sentences. Five minutes. They prevent every version of the nightmare client.
The reframe
Nightmare clients aren't a hiring problem. They're a system problem. The same client, onboarded properly, becomes a normal client. The same client, onboarded by default, becomes the person Slacking you at 11pm about Dribbble.
If your last three projects had scope creep, supervision creep, or direction whiplash — your onboarding is the leak. Not your client filter.
Want the full kickoff script, the change-order template, and the review-gate email I send before every project? Grab the free Agency Onboarding Checklist:
Top comments (0)