The mistake isn’t the word, it’s the mismatch
Two ESL writers can make the opposite mistake with the exact same phrase. One writes “I want the contract signed by Friday” to a client and sounds like they’re issuing an ultimatum. The other writes “I would like to kindly request that you might possibly review the contract at your earliest convenience” to a coworker on Slack and sounds like a customer service bot apologizing for existing.
Neither “I want” nor “I would like” is the polite one. Both are correct English, and both are wrong in the wrong context. The skill isn’t memorizing that “would like” = polite and “want” = rude — it’s matching the phrase to two things: who has more power in the exchange, and what channel you’re writing in.
Why “I want” isn’t rude
Native speakers use “I want” constantly, without a second thought, in sentences like these:
I want to flag one risk before we move forward. I want to make sure everyone’s aligned on scope before Thursday. I want your take on this before I send it out.
None of these sound demanding, because “want” here describes what’s motivating you to speak — not an order to someone else. It reads as direct and confident, which is exactly the tone you want among peers, or when you’re the one holding context or authority in the conversation.
The trouble starts when “I want” attaches to something the other person has to do for you, especially if they outrank you or you’re asking a favor:
I want the deck finished by tomorrow. (sent to your manager) I want a refund, today. (sent to a support rep who didn’t cause the problem)
English reserves bare “I want + [action from someone else]” for situations with a clear power imbalance in your favor — a customer to a vendor, a boss to a report. Say it to a peer or a superior and it lands as tone-deaf, not just informal.
Why “I would like” isn’t automatically polite
“I would like” is a hedge — it puts distance between you and the request, which softens it. That’s useful exactly once per message. Stack the hedge on every sentence and it stops reading as courtesy and starts reading as anxiety, or as a direct translation of a much more formal phrase from your first language.
Compare these two Slack messages to a teammate:
I would like to know if you have had the opportunity to review the document I sent yesterday. Did you get a chance to look at that doc I sent yesterday?
The first is grammatically flawless and instantly marks the writer as someone who doesn’t write Slack messages in English very often. Chat tools run on spoken register — the same register you’d use leaning over someone’s desk to ask a question out loud. “Would like” belongs to written, formal register: cover letters, contracts, emails to someone you’ve never met.
The register scale, roughly
Ordering the options from bluntest to most cushioned is more useful than any single rule:
Need it → Want it → I’d like → I would like → I would appreciate it if
Each step down adds distance between you and the ask. Pick your spot with two questions in mind: Does the other person have to do something for me? and Do I outrank them, are we equals, or do they outrank me? The bigger the ask, and the more they outrank you, the further down the scale you go — but usually one or two steps, not all the way to the bottom.
Same message, three channels
Take one real request — you need a deck finished by tomorrow — and watch how it should shift by channel and audience, not by some abstract “politeness level”:
To a peer, on Slack: Can you get me the deck by tomorrow? Tight, I know. To your manager, by email: Would it be possible to have the deck ready by tomorrow? Happy to help with any section if it’s too much. To a client, in writing: We’d need the deck finalized by tomorrow to stay on schedule for Friday’s launch.
Notice the client version doesn’t use “I would like” at all — it uses “we’d need,” which is direct but frames the deadline as a shared project constraint, not a personal preference. That reframe is often the better move in client-facing writing generally: state the requirement as a fact about the project, not a want you happen to have.
The double-hedge that gives you away
The single most common tell in ESL business writing isn’t “I want” — it’s stacking politeness markers until the sentence collapses under its own courtesy:
I would like to kindly request that you please send the invoice at your earliest convenience.
That’s four hedges doing the work of one. A native speaker writes:
Could you send the invoice when you get a chance?
Pick one softener — “would,” “could,” “kindly,” or “please” — and let it carry the whole sentence. Adding a second one doesn’t double the politeness; it just signals the writer isn’t sure how much softening is enough, which reads as more effortful, not more respectful.
A quick check before you send
Before sending anything longer than a one-line chat message, ask yourself: is this the register I’d use if I said it out loud to this person’s face? If “I would like to formally request your assistance with this matter” would sound absurd said aloud to the colleague at the next desk, it’s the wrong register for a chat message to them too — even when the grammar is flawless. And if “I want that fixed today” would sound like an order coming from you to your own manager, it’s too far the other direction.
Copynote’s tone presets are built around exactly this mismatch — rewriting the same draft for a client, a manager, or a teammate — but the underlying check works with or without a tool: match the channel, match the power dynamic, and never hedge the same sentence twice.
