🚩 When You Hear This From Clients, Act Fast

Ever had a client say, “It shouldn’t take too long”? That is your cue to gently push back in your chair and re-evaluate your life choices.

Or this classic:

“My last developer couldn’t get it done.”

That is not a fun fact. That is a warning label.

Personal Story

A while back, I built a subscription-based content drip system for a client. Pretty standard setup. You subscribe, you get a new chunk of the game each month. You cancel, the content disappears. Clean, simple, predictable.

Or so I thought.

A few weeks after launch, the client came back with what they believed was a tiny request.

 “Hey Wil, can we make it so customers get to keep all the games they unlocked, even if they cancel the subscription? Shouldn’t be too hard. Can’t you just enable that option?”

Mate.

Enable what option? In what universe is that a checkbox?

“Every time someone says ‘shouldn’t take long,’ the universe adds another plugin conflict to a WordPress site.”

What sounded small to them was actually a complete architectural shift. We’re talking new entitlement logic, new access rules, rewiring how content is stored, rewriting user permissions, and basically rebuilding the entire foundation from subscription logic to product-ownership logic.

And of course, to the client, it all looked like one tiny switch labelled “Let them keep the stuff.”

Meanwhile, I’m sitting there trying to explain that their “quick fix” was actually the development equivalent of turning a bicycle into a motorbike. Sure, they both have wheels. That doesn’t make it a tweak.

That moment was a good reminder.

Clients don’t see the complexity. They visualise the outcome.

And that’s where the trouble starts. 

Freelancer Challenge

If you have been freelancing for more than 15 minutes, you have run into one of these deceptively simple client requests.

The dreaded:
🤪  “It shouldn’t take long.”
🤪  “Can we just add one tiny thing?”
🤪  “No developer seems interested.”
🤪  “My last developer couldn’t get it done.”

These jobs are dangerous because they pretend to be harmless. They look small on the surface, but underneath, they are tangled in tech debt, unknown plugins, messy databases, and logic that was never designed to do what the client suddenly wants.

Here is the real pain:

When you take on these jobs, you risk blowing your schedule, derailing bigger projects, burning mental energy, and ending up underpaid because the client never understood how deep the rabbit hole went.

Most importantly, these jobs are usually not tasks at all. They are strategy problems. They need framing, scoping, planning and diagnostics before anyone even touches the code.

Actionable Goodies

The Quick Job Red Flag Scorecard

Before you say yes to any “quick fix,” run it through this simple checklist. It gives you instant clarity on whether the job is harmless, risky or a full-blown time-eater dressed as a favour. Think of it as your early-warning system for trouble.

Give each red flag 1 point.

1. The client says, “It shouldn’t take too long.”
2. They mention that another developer could not or would not touch it.
3. The request affects core logic, subscriptions, payments, animations or user access.
4. The client already tried something and broke things.
5. There is urgency with no clear reason.
6. They resist a call to explain the actual problem.
7. Your gut does the uncomfortable squirm.

☑️ 0 to 1: Probably safe. Quote normally.

🔶 2 to 3: Proceed with caution. Scope before quoting.

🚩 4+: Run for the hills! Or schedule a paid strategy session first.

The Boundary Script Library

When a client hits you with a sneaky red-flag request, having the right words ready makes everything easier. These scripts help you hold your boundaries, stay professional and redirect the conversation without burning bridges. Copy, paste and soften as needed.

1. The Referral Method
“Thanks for reaching out. I cannot take this on right now, but here are a couple of great people who may be a better fit.”

2. The Strategy-First Method
“This type of request looks small, but usually indicates a bigger structural issue. Before I quote, I recommend a short digital strategy session to map everything clearly.”

3. The Kind but Firm Method
“This request is more complex than it appears. It is not something I can take on as a quick, standalone task.”

4. The Protect-the-Client Method
“Doing this without understanding the wider setup can cause issues elsewhere in the site. A strategy session is the safest next step.”

Your Turn

Have you ever been handed a “quick fix” that turned into a monster? Hit reply and tell me your best one. I might include it in a future newsletter.

Until next time, keep thriving!

Wil.