Why quick question kills your email

"Quick question" was clever once. Now it's the loudest signal in the inbox that a stranger wants something.

Senior buyers see it a dozen times a week. They know what follows. A question that isn't quick, isn't a question, and usually ends with a request for thirty minutes. So they delete it without opening it.

How it got here

The idea made sense at the start. A subject line that looks like it came from a colleague gets opened. "Quick question" sounds casual and internal. It borrows the tone of a coworker leaning over a desk.

Then everyone copied it. Sequencing tools put it in email marketing templates. Sales trainers taught it. Within a few years, the phrase stopped looking internal and started looking like outbound. The trick wore off, and what's left is a cliche that marks you as a seller before the email is even open.

Why it fails senior buyers in particular

Executives are protective of their time and allergic to manipulation. "Quick question" is a small manipulation. It pretends the ask is smaller than it is, and pretends a relationship that doesn't exist.

When a CFO opens it and finds a pitch, they feel tricked. That's a bad first impression for a firm hoping to sell a $200K engagement. Trust is the whole game in services, and you just spent some of it on a subject line.

And the question that follows is rarely quick. "Who handles your data strategy?" "Are you the right person to talk to about cloud costs?" These are questions that ask the buyer to do your research for you.

The deeper problem

The subject line is a symptom. The real issue is a note with nothing specific to say.

"Quick question" gets used when the seller has no hook. No research, no observation, no reason this buyer should care. The subject line is trying to do the job the content should do.

Fix the content and the subject line fixes itself. If you have something real to say about their company, say it plainly up top. The subject line can just name the topic.

What to write in its place

Start with what you found. A subject line that names the event or the problem is honest and specific. "Your claims platform migration." "The new hiring push in data engineering." "Margin note in the last 10-Q." Short, plain and only relevant to them.

Then open the email with the same thing. No warm-up. No question yet.

Say a VP of IT at a regional bank just posted four roles for core banking engineers, a month after the bank announced it was moving to a new core.

Saw the four core banking roles you posted right after the conversion announcement. Running a core move and hiring people who know the old system at the same time is rough, and my guess is the timeline already feels tight. Is that the pressure, or is the harder part somewhere else?

That's a real question at the end, but it isn't a trick. It's a binary the buyer can answer in a line. And it only comes after you've earned it with something specific.

Questions that earn a reply

Questions work in cold notes when they come last and they're easy to answer. Yes or no. Right or wrong. This or that.

They fail when they come first, when they're vague, or when they ask the buyer to explain their org chart to a stranger. "Who's the right person for X?" isn't quick. It's homework.

Good questions invite correction. You guess at a problem, and you ask whether you're close. That's the binary exit, and it's the only question a cold note needs.

The rule to keep

Never let the subject line promise something the email doesn't deliver. If it says quick, be quick. If it says question, ask one real one.

Better yet, skip the tricks entirely. Name something true about their world, guess at what it means, and let them tell you if you're wrong. That's harder to write than "quick question." But it's the kind of note a senior buyer actually answers.