The worst project of your freelance career won't be the hardest one technically. It'll be the one you should never have taken on. The vague client who changes their mind every week, the one who "didn't realize it was paid work," the one who vanishes for three months and then demands delivery in eight days. All these projects share one thing: the warning signs were there from the first contact, and nobody took thirty minutes to look at them.
After years as an independent developer in Switzerland, I've boiled it down to one simple rule: a 30-minute qualification call is enough to tell a serious client from a tire-kicker. Not a two-hour meeting, not three endless email exchanges. Thirty minutes, a script, and a decision at the end. Here's how I do it.
Why you filter before you work for free
When a request comes in, the beginner's temptation is to jump on it: reply within the hour, send ideas, sketch a proposal, sometimes even a mockup, "to show what we can do." I've done that. Result: hours of work given away to people comparing five providers before ordering nothing, or walking off with my ideas in their pocket.
Free work before qualification is a double mistake. Economically first: every hour given to a prospect who never signs is taken straight out of your paying projects. Psychologically second: a client who gets free work immediately learns that your time costs nothing, and they'll remember that for the whole relationship.
The qualification call flips the dynamic. You're not begging for a project, you're evaluating whether this project deserves a slot on your calendar. That shift changes everything, including how the client sees you. Good clients respect a professional who asks structured questions. Tire-kickers hate it, and that's exactly the point.
The script: five topics, in order
My call always follows the same script. Five topics, about five minutes each, and I keep control of the pace.
Context. Who is this person, what do they do, how do they currently manage without the website or app they're asking for? Two minutes of answers tell you more than ten emails.
The real need behind the request. This is the heart of the call. The client shows up with a solution: "I need an app." Your job is to trace it back to the problem: "what's costing you time or money today?" A tradesperson asking for "an app" often just needs a well-built quote request form. Someone willing to talk about their problem instead of their solution is already a good sign.
Budget, asked without flinching. This is the question beginners are afraid to ask, and the one that saves the most time. I ask it plainly: "What budget have you set aside for this project?" No apology, no dancing around it. A serious client has a range, even a vague one. A client who answers "no idea, just send me a proposal" usually simply has no budget. You can then throw out a ballpark figure and watch the reaction: it's a test in itself.
Timeline. By when, and above all: why that date? A trade show in October is a real constraint. "As soon as possible" isn't one, it's the absence of any thought.
Decision-making. Who signs? Who pays? Is there a partner, a board, a "brother-in-law who knows about this stuff" to convince? If the person on the phone doesn't decide, your next meeting needs to include the one who does, or you'll be pitching twice.
A real conversation, condensed
Here's what the decisive moment of an actual call looks like, condensed:
"So you want a booking platform for your yoga studio. Right now, how do your clients book? » Through WhatsApp. I spend an hour a day managing it. » Okay, the problem is clear. What budget have you set aside to fix that? » Uh... I don't know, I was thinking a few hundred francs? » I'll be honest: a custom, reliable booking tool with online payment runs into the thousands of francs, not hundreds. There might be off-the-shelf subscription tools that would work for your case. Want us to look at whether custom really makes sense first?"
Two possible outcomes. Either the client says "oh, I didn't realize, but tell me what I'd gain," and the conversation turns serious. Or she hangs up disappointed, and you just saved yourself weeks. Either way, the call did its job. Notice also what I did: offer a cheaper alternative when one exists. It's surprising, and it's exactly what brings people back years later with a real budget.
The red flags that don't forgive
Some signals, heard during the call, should trigger extreme caution, or even a polite refusal.
Permanent vagueness. A client unable to say what they want, for whom, or why, even after your questions. Vagueness on a call becomes chaos on a project.
Artificial urgency. "I need it by next week," with no concrete reason behind it. Manufactured urgency is designed to make you skip your process: proposal, deposit, mockups. Refuse the shortcut, not necessarily the client.
"It's simple, it's a two-day job." A client who has already estimated your work for you is telling you two things: they don't respect your expertise, and they'll contest every line of your invoice. My reply: "If it's that simple, why isn't it already done?", said with a smile, but said.
Immediate haggling. Negotiating before even knowing the price, asking for "your best rate" by minute two, comparing you to a nephew or a cut-rate platform. A client who starts with the price will end with the price, at every step. And if, later, they want to leave: let them leave. Never try to hold on to a client who's heading for the door, it only buys you trouble at a discount.
The golden rule: the proposal first, everything else after
One last rule, the most important one, the one that cost me the most to learn: nothing deliverable leaves your desk before a proposal is accepted. No free requirements document, ever. No free mockup, ever. A requirements document is days of structured thinking; a mockup is design work. Both are written after a proposal is accepted and a deposit paid, never before, never "to help you decide."
The qualification call, on the other hand, is free, and it's the only gift you give: thirty minutes of your attention. That's more than enough for a serious client to notice, and for a tire-kicker to walk away.
This call is just the first step of a full journey: proposal, contract, payment milestones, requirements document, approved mockups, development, testing, launch, maintenance. Every step has its own pitfalls and paperwork, and I walk through them one by one, with real dialogues and real amounts, in my course Design a full-stack project from A to Z. If you want to live off this trade instead of enduring it, that's exactly where it starts.