The Vetting Call Goes Both Ways: Six Questions That Saved Me From My Worst Projects

I used to think vetting was something clients did to freelancers. Then I tallied up the projects that went sideways over the years — the one that ran nine months over, the one with the committee that appeared in week six, the one where the check cleared but the client did — and realized every single catastrophe had announced itself in the first phone call. I just hadn't asked the right questions.

What follows is the list I now work through before saying yes to anything. Each one has a scar attached.

"Who gives the final approval, and is that person in this conversation?"

The scar: a rebrand project where I presented to my friendly day-to-day contact four times before learning that her boss's boss had veto power and strong opinions. Four rounds of work, discarded on preferences I never heard directly.

The red-flag answer is hesitation, or a vague "we'll all weigh in." What you want to hear is a named person, present on the call, with authority to say yes. If the real decision-maker won't take a discovery call, the project isn't ready to start.

"What does success look like in six months, specifically?"

The scar: a website redesign for a regional restaurant group that I delivered exactly to spec — and exactly to nothing, because nobody had defined what the site was supposed to accomplish. The client's disappointment was real, and so was my innocence. We had both been building toward a fog.

Listen for a concrete answer: more reservations, fewer support tickets, a launch date tied to an event. If a client can only offer adjectives — modern, clean, elevated — that fog will eventually condense into a revision cycle you pay for.

"What is the budget range you've set aside for this?"

I resisted this question for years because it felt indelicate. The scar that fixed me: six weeks of unpaid discovery for a startup whose entire budget, I later learned, was what they hoped the project might cost.

Asking about budget first is not aggressive; it is respectful of everyone's time. The red flag is not a small number — small budgets can be honest budgets. The red flag is deflection. A client who won't share a range either hasn't done the planning or doesn't want you to know the gap between their number and yours. Both are disqualifying.

"What happened with the last person who did this work?"

The scar, briefly: I once became the fourth designer on a project in two years and found out only when I inherited the fourth set of contradictory files.

This question is a gold mine. A client who answers honestly — "we outgrew him," "the scope changed," "we didn't communicate well" — is telling you how they behave under stress. A client who answers with pure villain narrative, where every previous professional was incompetent, is showing you the script they're already writing about you.

"How do you prefer to make decisions — quickly, or with deliberation?"

This sounds like a soft question. It is not. It is a gut-check dressed as logistics, and it is the one that has saved me most often.

The scar: a client who described himself as "decisive" and then took five weeks to approve a homepage, ghosting in between. What I've learned to listen for is whether the client's self-description matches their behavior in the call itself. Did they respond to my emails promptly? Did they show up on time? The vetting call is a sample of the working relationship, in miniature, and I trust the sample over the sales pitch every time.

"Is there anything about this project you're worried about?"

The last question is the one clients never expect, and it works because it invites honesty you couldn't extract any other way. I have heard budget anxieties, internal politics, doubts about the project's own premise — all volunteered, all things I would otherwise have discovered at the worst possible moment.

The red flag is not the worry itself. It's the client who has none, because either they aren't being candid yet, or they haven't thought carefully enough to worry. Both predict a bumpy road.

A Shorter Yes List

Here is the uncomfortable summary: the questions take fifteen minutes, and the projects they've saved me from would have cost me months. I have walked away from four prospective clients since adopting this list, and every single one, based on industry gossip, lived down to my expectations.

Saying no is a skill. These questions are just the instrument that makes the no — and the yes — honest.