After a Pay Freeze, Build Your Raise Case Around Named Costs

A pay freeze names the budget lines

A pay-freeze memo can feel like a rejection. It is usually a budget line. When a company names cost pressure, it is telling you which decisions are open: spend, headcount, risk, capacity, or revenue enablement. Rebuild your promotion or raise case around those decisions, not performance.

On October 13, 2026, Zoho forwent the standard yearly salary increases for staff. A fourfold rise in data-center server prices was one cost factor behind the decision. Fast-growing AI use pushed up expenses, which the company was trying to restrain. Zoho had cut its marketing budget and informed staff that the normal salary increase could not be provided that year. The company had gone 18 months without increasing headcount and was trying to prevent large-scale job cuts. Zoho was undergoing a reinvention, and the following 3-5 years would show whether that transformation succeeded.

A pay freeze can be selective. The 2027 federal pay plan left most civilian employees on a pay freeze while providing pay increases for law enforcement and military personnel starting in January. President Donald Trump's plan proposed a 3.8% pay increase for law enforcement personnel and a 5% to 7% pay increase for military members. A 3.5% inflation rate was linked to the argument that a federal pay freeze would reduce real pay.

Build the case on the company's cost lines

• Name the company's cost drivers from the memo, company meeting, or budget note: servers, AI use, marketing, headcount, customer acquisition, or revenue enablement.
• Map your work to savings, risk, capacity, or revenue enablement. Tie server spend to lower usage or prevented waste; headcount to work you absorbed or stable delivery; risk to prevented failures or customer loss; revenue enablement to the work that lets sales close, renew, or expand without adding cost. Build a table with columns: company cost line, your action, and the business result.
• Quantify it in the company's units: cost saved, hours returned, incidents avoided, delivery time cut, or revenue protected. If you cannot produce a number, state the direction and size in plain terms, then ask for a review that can measure it. A finance person should be able to test the claim without asking you to re-explain your job.
• Ask for level, scope, or a dated review.

The mistake is to lead with fairness. Treat the freeze as a budget decision. A raise request that ignores the budget line and the org chart will read as a demand. Put the cost line first, then your evidence, then the ask.

Match the ask to the constraint

A freeze may block a percentage, but it may not block a level change, a broader title, a bigger project, or a written commitment to revisit pay. Transformation calls for scope. Headcount protection points to level. Uncertainty points to a dated review with the cost lines that must move before pay can move. The output is a calendar entry, a scope change, or a level recommendation, not a promise of a number.

Keep the human part visible. Your manager can carry a cost case, but they also need to know what the freeze is doing to you. Say what you need: clarity, a path, or a date. Kindness keeps the case from sounding like a grievance. You are done when you can repeat the sentence in a review without flinching.

Leave a written record. Send a short note after the conversation: the cost lines you used, the evidence you attached, and the ask you made. If the answer is no, the note becomes the basis for the next review. If the answer is yes, it becomes the record that the change was tied to the company's stated constraints. The finished note stands if the conversation gets fuzzy.