For three weeks, the draft has lived in your notes app. It starts "Hi Dana, hope you're well! I wanted to touch base about possibly, if the timing works, discussing compensation." You've deleted it four times. Each time you reread it, your stomach drops a little, because you know what it sounds like: someone apologizing in advance for a number they haven't even said yet.

Here is the uncomfortable part. While you wait for the perfect moment, the number is being set anyway. It's just being set without you.

The number that gets there first

In negotiation research, one of the sturdiest findings is the anchoring effect. When a number is put on the table, every later number gets pulled toward it, even when people know the first figure is arbitrary. In a well-known set of experiments, Adam Galinsky and Thomas Mussweiler (2001) found that negotiators who made the first offer ended up with outcomes closer to their own target than those who waited. The first figure becomes the reference point the other side adjusts from, and the adjustment is usually smaller than it should be.

Now look at your email through that lens. If you write "I'd love to discuss compensation" and leave it there, you haven't avoided anchoring. You've handed the anchor to your manager. Their budget, their memory of what you earn now, and the 3% pool HR announced in January all become the starting line. You then negotiate upward from a spot you didn't choose.

This is the one idea worth carrying out of this article: in a raise request, the first concrete number does more work than the best argument that follows it. That doesn't mean being aggressive. It means being specific and early.

Why we write the vague version

The vague draft isn't a failure of intelligence. It's protection. Naming a figure feels like exposure, because you're putting a price on yourself and inviting a verdict. Hedging words ("possibly," "if the timing works," "I was just wondering") are a way of lowering the stakes of rejection before it arrives.

But hedges cost something. They signal that you don't fully believe the request yourself, and a reader skimming between meetings will take that cue at face value. A request that sounds apologetic is easier to defer. "Let's revisit this after Q1" is the natural response to a question that was asked as if it were already optional.

There's also a quieter mismatch. You've been living inside your own contribution for months, so it feels obvious. Your manager hasn't. Most managers carry a fuzzy, recent-weighted picture of each person on their team, and your best work from eight months ago may have faded. The email isn't bragging. It's supplying the memory they don't have time to build.

What a strong raise request actually contains

A good written request is short and has four parts, in this order.

1. A plain ask. Say what you're asking for in the first two sentences. "I'd like to discuss adjusting my salary to $92,000, effective next quarter." The number is the anchor, so it shouldn't be buried in paragraph four.

2. Evidence of value, not need. Rent going up is true and human, and it's the weakest argument you can lead with, because it's about you, not the company. Your manager has to justify this to someone above them. Give them the material: the project you led, the revenue or time it saved, the responsibilities that grew since your title was set. Two or three concrete facts beat ten adjectives.

3. A reference point beyond your own opinion. Where you can, ground the figure in something external: published salary ranges for the role, a posted range for similar jobs, or what the market pays for the scope you now cover. Use only data you can actually point to. A made-up benchmark is worse than none.

4. A clear next step. End by proposing a conversation, with a time frame. "Could we find 30 minutes this week or next?" removes the easiest way out, which is silence.

One caution from the research on this topic: how the ask lands can differ by who is asking and how it's framed. Work by Hannah Riley Bowles, Linda Babcock, and Lei Lai (2007) found that women who negotiated were sometimes penalized more than men who did the same, and that framing a request in terms of the organization's interests, or a shared goal, softened the reaction. You shouldn't have to manage other people's biases, but it's useful to know that "here is what this lets me do for the team" is both truthful and tends to travel well.

Choosing the number

Because the first figure pulls the outcome, aim slightly above what you'd be happy with, as long as you can defend it. If your honest target is $88,000 and the market data supports a range up to $95,000, naming $92,000 leaves room for a counter that lands where you wanted.

Two practical details help. Precise-sounding numbers ("$92,500") can read as better researched than round ones, and there's some research suggesting precise first offers anchor more strongly, though I'd treat that as a nudge, not a trick. And whatever you pick, don't attach an apology to it. "I know this might be a stretch, but" undoes the anchor in six words.

Say it before you write it

The hardest part of this email isn't the logic. It's the sentence where you type the number. Typing invites the editor in your head: you write it, flinch, soften it, bury it, and the confident version never survives.

Speaking tends to skip that flinch. Imagine your manager sitting across from you and say the request out loud, start to finish, the way you'd say it in a one-on-one. You'll hear where you rush, where you apologize, and where the number finally comes out plainly. The spoken version is usually shorter and more direct than the typed one, because you can't hedge for four paragraphs to someone's face.

Then you tidy it. The point is to capture the version of you that already believes the ask, before the cautious drafter gets to it.

Your next moves

  • Today, write down three results with numbers or outcomes. "Cut onboarding time from two weeks to one," "took over the vendor relationship when Sam left." Facts you can attach to a name, a project, or a date.
  • Find one external reference point. Check published pay ranges for your role and city, or posted salaries for comparable openings. Write down the source so you can cite it truthfully.
  • Decide your number and your floor, in writing, before you draft. Your target goes in the email. Your floor stays private.
  • Say the ask out loud, once, as if your manager were in the room. Record it or dictate it, and keep the sentence where the number appears exactly as it came out.
  • Cut every hedge, then send or schedule it. Delete "just," "possibly," "I was wondering if," and "sorry to bother you." End with a specific request for a time to talk, and put it on your calendar to send, so it doesn't sit in drafts for a fourth week.

A last word on where this gets said

The raise conversation is one of those moments where the words you'd say aloud are better than the ones you'd type. That's the reason we built Quill, a dictation tool that works in any app, on your device, so what you say stays private. You speak the request the way you'd say it to Dana, get clean text back, and use the one-tap rewrite if you want it a little more formal. It won't pick your number or write your results for you. But it can get the honest, unhedged first draft out of your head and onto the page. If that sounds useful, you can take a look at Quill.