Last week someone reached out through an ad I was running. He wanted two websites built, one for each of his businesses.
The first few messages were normal. He asked good questions. He seemed like he actually wanted the work done. I was already thinking about how I'd scope it, what the timeline would look like, what I'd need from him to get started.
Then he told me he'd been scammed by another developer before. So before we went any further, he wanted me to send some money to his bank account. To build trust, he said. To prove I was real.
I read that message a couple of times.
The Part That Actually Got Me
The whole thing was flipped. He was the one asking for the work. I was the one about to do it. And somehow I was supposed to pay him first, so he'd feel safe.
If you slow down and look at it plainly, it makes no sense. Nobody hiring someone for a job pays that person upfront just so the person doing the hiring feels secure. That's backwards. But in the moment, wrapped in a normal conversation, with a sympathetic story attached to it, it almost didn't register as backwards at all.
That's the part that stuck with me. Not the scam itself, the fact that it almost worked, for a second, because he built it so carefully.
How the Setup Worked
He didn't open with the ask. He opened with something completely ordinary, a real project, real questions, real interest. That's what disarms you. By the time the actual request showed up, I was already treating him like a legitimate client, because up to that point, everything about him had been legitimate.
Then he made himself the victim first. "I got scammed before" isn't just an excuse, it's a preemptive move. It reframes the request before you've even heard it. Instead of thinking "why is he asking me to pay him," you're thinking "he's been through something bad, I should be understanding." He made paying him sound like the reasonable thing a trustworthy person would do.
I stopped responding after that. Blocked him. Didn't think twice about it once I saw it clearly. But I keep coming back to that first read, when it almost landed.
Who This Actually Catches
It wasn't built for someone in my position. I've been doing this long enough, and I've heard enough stories, that the moment it clicked, it clicked hard. I could afford to just walk away.
I keep thinking about the people this does work on. Someone new to freelancing, hungry for their first real client, who reads "I got scammed before" and feels sympathy for the guy instead of suspicion. Someone for whom two websites of work sounds like exactly the break they've been waiting for. For that person, the story isn't a red flag, it's a reason to want to help.
That's who this is designed to catch. Not the person who can afford to say no. The person who can't afford not to say yes.
What I'm Actually Taking From This
I don't think there's a clean lesson here, the kind you can turn into a checklist. But there's one thing I keep coming back to: anyone who asks you to pay them so they can trust you is telling you exactly what they are. Not through what they say, through the shape of the request itself. Real clients don't need that. Real trust doesn't get built by moving money first.
If something like this happens to you, especially early on when every lead feels important, it's worth pausing on the exact moment the ask stops making sense in either direction. That pause is the whole thing. It's the only part of the interaction that's actually yours to control.
I build websites for small businesses and MVPs for early-stage founders. If you're dealing with something that feels off in your own client search, I'd rather you ask than second-guess it alone. Reach out.