What Red Flag Do I Look For in a Client's First Email?

What do I look for in a potential client's first email?

Whether they can describe the problem in their own words. Budget, timeline and scope all matter, but they can be negotiated. A person who cannot say what is actually wrong, in a sentence, is usually a person who has not decided yet, and deciding is not something I can do for them.

I have done more than seventy projects for over twenty five clients across six years, and this is the signal that has held up best. It is not the one I would have guessed early on. Early on I was watching for budget, which turns out to be the least predictive thing in the email.

So here is the flag, why it matters, and the ways I get it wrong.

Which red flag actually matters most?

Vagueness about the outcome, paired with certainty about the solution. An email that says we need a new website, can you send a quote, tells me the sender has skipped the part where somebody worked out what the website is failing to do. That missing step does not disappear. It arrives later, during the build.

The dangerous version is confident. It is not somebody saying they are unsure. It is somebody who has converted an undiagnosed problem into a specific solution and now wants a price for it. Nobody in that conversation is uncertain, and that is exactly what makes it expensive.

What happens next is predictable. We build the thing that was asked for, it does not fix the unnamed problem, and the project quietly becomes a search for the real issue on my time. I have learned to notice that shape before I quote, not after.

Why is urgency in a first email a warning rather than an opportunity?

Because genuine urgency usually comes with context, and manufactured urgency comes without it. Someone with a real deadline tells you what it is and why. Someone using urgency as leverage just says they need it fast, and the speed is doing the work that clarity should be doing.

Real deadlines are workable. A conference, a funding announcement, a contract ending, a product launch: those are constraints I can plan around, and they often make a project sharper because they force decisions. I am not against deadlines at all.

What I watch for is urgency with no anchor. That usually means either a decision made under pressure, which will be revisited, or an expectation that speed is free. Neither is a reason to say no on its own, but both change how I scope, and it is part of why I stopped replying to every enquiry immediately.

What does a good first email actually look like?

Short, specific about the problem, and honest about what is unknown. The best enquiries I get describe a situation rather than a shopping list. Something is not working, here is what they have tried, here is what they are unsure about. That email tells me more in four lines than a detailed brief often does in four pages.

Notably, the good ones frequently do not mention a budget, and the ones that do are not automatically better. What makes an enquiry strong is evidence of thinking, not evidence of money. Thinking is the part I cannot supply from outside.

The other marker is that they say what they want from me specifically. Not flattery, but a reason they wrote to me rather than to anyone. That tends to correlate with people who have actually looked at what I do, and those relationships start much further along.

Am I screening people out unfairly?

Sometimes, and I take that seriously. A vague email can mean somebody is busy, writing in a second language, or simply not practised at describing technical problems. Treating vagueness as automatic disqualification would be both unkind and bad for business.

So the flag is not a rejection rule. It is a signal to change my next move rather than to stop. When I see it, I ask one specific question instead of sending a proposal, and the answer to that question resolves the ambiguity almost every time.

That distinction matters. A screen that filters people out costs you good clients. A screen that changes how you respond costs you nothing and improves the conversation. The single question I ask at that point does more work than any qualification form I have tried.

What do I do when the flag is there but the project is interesting?

I propose a small paid piece of work first. Not a free consultation, because free work attracts exactly the undecided energy I am trying to resolve. A short, properly priced diagnostic that produces something useful whether or not we continue.

This works because it converts the ambiguity into a project rather than a risk. If the problem turns out to be different from the stated one, we both find out in week one, at a price we both agreed to, instead of in month two on a fixed fee I quoted blind.

It also respects the client. Nobody sending a vague email is being careless on purpose. They usually know something is wrong and do not have the vocabulary for it yet, and paying somebody to help find the words is a completely reasonable thing to buy.

How has this changed how I write my own site?

I try to do the screening before the email exists. If my site clearly states what I work on, how I price and who I am a bad fit for, then a lot of the mismatched enquiries never get sent, which is better for everyone including the people who do not write.

Publishing pricing does much of this. I work fixed fee, most projects land between one thousand and ten thousand dollars, and saying so filters more accurately than any qualification question I could ask afterwards. People self select, quietly and without an awkward conversation.

The contact page does the rest. Asking for the problem rather than the requirements changes the emails I receive, and that is mostly a copywriting decision rather than a form design one, which is why I care about what a contact page actually asks for.

Why did it take me years to start screening at all?

Because when you are building a practice, every enquiry feels like the last one you will ever get. Saying no, or even slowing down to ask a question, feels like a luxury you have not earned yet. That fear is real and I do not think people should be lectured out of it.

What changed it was not confidence. It was noticing that the projects which went badly shared a pattern that was visible in the very first message, and that I had read that message and proceeded anyway. The information had been there each time. I was choosing not to act on it.

Screening did not reduce the amount of work I get. It changed which work I get, and it made the projects calmer. That is a less dramatic outcome than the advice usually promises, and it is the honest one.

What should you do next?

Go back through your last ten enquiries and mark which ones described a problem and which described a solution. Then check how those two groups actually turned out. You will find your own version of this flag, and yours may not be mine.

Then write down the one question you would ask when you see it. Having the question ready is what turns a vague feeling into a usable process, and it takes about five minutes to decide once and years to keep improvising.

If you want to compare notes on what you screen for, I am genuinely interested. This is the part of running a practice that nobody talks about honestly enough. Let's chat.