How to Ask for More Money at Work

8 min read

You don't need a speech about rent. You need the right folder in your manager's head. Companies don't have one "more money" button. They've got merit, promotion, equity refresh, and retention buckets that don't talk to each other.

When you can't name the route, you'll get "we'll look at it in review season" and won't know if they meant no or wrong workflow.

Check your resume for free before the meeting so bullet one proves the level you're pricing. Managers discount vague asks when the file still reads one title down.

Below you'll match symptoms to the four routes, fix the proof gap for each, and copy a meeting opener that won't get misrouted.

Four ways more money shows up on payroll

Raise: same level, higher base inside the band after scope growth or strong year.

Promotion: new level, new band, often committee timing.

Market adjustment: title and duties unchanged, pay lags external hires or band midpoint.

Bonus: one-time payout for project delivery, not a permanent base lift.

Symptom you picked wrong: you argued scope but HR heard "retention" with no offer on the table, or you asked for promotion while the JD still matches your current title.

Listen for the words leaders use in town halls: merit, calibration, leveling, equity refresh. Mirror those nouns in your subject line so your ticket lands in the workflow they already funded.

If you're returning from leave, re-anchor scope before comp. Managers sometimes forget projects you finished pre-leave; your doc should reopen those wins so the route isn't dismissed as timing.

Read asking for a raise vs asking for a promotion when title and pay both feel off, and how to negotiate when you're underpaid when you're choosing stay vs leave paths.

Diagnose the route, then fix proof

Route A, raise: scope grew, title still accurate. Fix by tying outcomes to current level expectations.

Before: "I need a raise because costs went up."
After: "Since March I own client onboarding end-to-end; error rate on my accounts dropped after I rebuilt the checklist (illustrative project metric)."

Route B, promotion: duties match next level for months. Fix with JD mapping and dates, not adjectives.

Before: "I'm basically a manager already."
After: "Three direct reports since January; I run weekly 1:1s and hiring loops per the Lead guide."

Copy-paste opener you can drop into email:

{`I'd like time to discuss a [raise / promotion / market adjustment / bonus] tied to [one sentence outcome].

Since [date], I've [metric-backed result]. Which cycle or approver owns this path on our side?`}
            

Route C, market adjustment: peers hired recently earn more for the same title. Fix with role-matched ranges you collected, not coworker gossip names.

Before: "Everyone on the team makes more than me."
After: "External postings for [Title] in [metro] cluster around [range you researched]; I'd like alignment to band midpoint for retained scope."

I've routed internal comp tickets where the employee labeled a market gap as a raise; HR closed it in a day because the workflow didn't match. The relabeled ask moved on the retention track the next week.

Route D, bonus: you delivered a finite project and accept that base may stay flat. Fix by naming deliverables, dates, and prior bonus precedent if you know it.

Symptom: you got a strong review but base didn't move. Check whether the company paid a bonus instead. If total comp rose only in variable pay, your next ask is base or market, not another project bonus.

Symptom: new hire cohort earns more. That's market adjustment territory unless your scope also jumped. Collect role-matched postings and internal job codes before the meeting so you're not arguing from frustration alone.

Symptom: you're doing manager work without manager pay. Promotion first, then raise to midpoint if the promotion lands low in-band. Reversing the order leaves money on the table when the band resets.

Off-cycle triggers that work: retention risk with documented offer, material scope change with signed charter, or location tier change after a move. Off-cycle triggers that flop: cost of living alone with flat output.

Hourly workers: ask whether overtime eligibility changes with reclassification before you celebrate a base bump. A raise that moves you exempt can lower take-home even when the salary number looks larger.

Tell which comp gap is blocking you

• Route gap: you're using raise language for a promotion problem.
• Proof gap: no metrics in bullet one or in the meeting doc.
• Timing gap: committee already met; you needed the packet six weeks earlier.
• Total comp blind spot: bonus looks fine while base lags; you never split the parts.

Before: Mixed bonus ask with base demand in one paragraph.
After: Asked for project bonus now and scheduled base review at promotion effective date.

Emotion gap: venting to peers feels productive but doesn't create an approvable packet. Translate frustration into dated outcomes before you knock on your manager's door.

Manager gap: your boss may agree you're underpaid but lack budget. Ask what executive sponsor or HR partner owns exceptions. A routed ticket beats a sympathetic nod.

Career changers internal to a new lane: you're often priced on old-band logic until promotion catches up. Use market adjustment language tied to the new JD, not last year's title in another department.

Align the file with the dollar ask

Internal mobility and external search both read bullet one. Update scope language before you argue band.

Score your job match against a posting at the level you want paid for. Gaps show whether promotion or market language fits better.

Generate a cover letter only if you're running a quiet external backup while internal routes process. Keep scope facts identical across channels.

Update your internal profile and resume the same night you change bullet one. HR systems sometimes pull the stale internal PDF into calibration packets if you don't upload the new version yourself.

Send one labeled ask

How to ask for more money at work isn't one script. It's picking raise, promotion, market adjustment, or bonus, then giving HR the folder they can actually approve.

Name the route in the subject line, attach three dated outcomes, and ask which approver owns the path. You'll get a real yes, no, or date instead of review-season fog.

If the answer is no, ask what evidence would flip it next cycle. That's not weakness; it's a test of whether the route was real or polite deferral.

Keep a one-page comp log: date, route, outcome, next step. You'll stop relitigating the same hallway conversation every six months without paperwork.