You made your case, and the answer was: there's no budget right now. Most people hear a no, say "I understand", and leave. Twelve months later nothing has changed, and the conversation starts from zero.
The sentence is rarely a rejection of your value. It's a statement about a calendar you can't see.
Treat it as a scheduling problem
Budgets are decided in cycles, and by the time most people ask, the current one is already allocated. That means the useful response isn't to argue about your worth — you may have already won that part — but to attach yourself to the next allocation before it closes.
The question that does this: "I understand this cycle is set. When is the next budget decision made, and what would need to be true for this to be included?"
You've just converted a soft no into two concrete things: a date and a condition.
Get the condition in writing — carefully
Vague agreements evaporate. Managers change, priorities move, and nobody remembers a hallway conversation from March. But "put it in writing" can sound adversarial, so make it administrative instead:
"Just so I'm working on the right things — can I summarise what we agreed in an email so we're aligned?"
Then send a short, unemotional message: what was discussed, what you'd deliver, when it would be revisited. You're not creating a contract. You're creating a shared memory that survives a reorganisation.
Make the condition measurable
If the answer is "show more leadership" or "grow into the role", you don't have a condition — you have a mood. Push once, politely, for something observable: a project owned end to end, a metric moved, a responsibility formally transferred. Anything you can point at later without needing your manager to agree from memory.
A useful test: could a different manager, reading only your email, tell whether you'd met the bar? If not, it's still too vague.
Ask what else moves
Cash is often the most constrained thing in the building while other levers are wide open. A title change carries no immediate salary cost but changes your market rate at the next move. A training budget, a conference, a formal mentor, a shift to four days, a review scheduled at six months instead of twelve — these frequently get approved when money can't.
Title is the underrated one. It costs the company little today and follows you for the rest of your career, because your next employer prices the role you held, not the raise you didn't get.
When to believe it, and when not to
Once is a budget cycle. Twice, with a specific commitment that was met and still produced nothing, is information — not about your performance, but about the organisation. At that point the honest question stops being "how do I ask better?" and becomes "is this a place where pay moves at all?"
That's uncomfortable, but it's also useful. The most expensive outcome isn't a declined raise. It's three years of annual increases below inflation while waiting for a cycle that was never going to come.
This guide is general education, not personalized career advice.