Negotiation
The person negotiating with you usually cannot say yes
Understanding who holds the authority changes what you ask for and how long you wait.
This is less a set of instructions about approval authority than an argument, and it is worth saying so at the start.
The argument in brief
- Hiring managers often need approval from finance or HR to exceed a set point.
- Requests that fit an existing exception route are approved faster than novel ones.
- Silence after a request usually means it is being escalated, not refused.
Authority sits above the conversation
A hiring manager or recruiter typically has discretion up to a defined point and needs approval beyond it. That approval usually involves someone in finance or human resources who has never met you and is looking at consistency across many hires. What persuades them is comparability to other people in the same role, not your account of your own strengths.
Giving your contact a case they can forward is more useful than giving them a case they must summarise.
Exceptions have routes
Most organisations have established ways to pay more than the standard point: a market supplement, a higher starting position in the band, a signing payment or an earlier first review. Requests that map onto one of these are far easier to approve than requests that require inventing something. Asking what mechanisms exist, rather than only asking for more, often produces the better outcome.
On an ordinary week, the recruiter usually knows the answer and will frequently tell you.
Delay is usually process
A pause after a request is more often an approval chain than a decision to refuse. Chasing daily during that period can damage the relationship without accelerating anything.
Asking at the outset how long approvals take, and agreeing a date to speak again, removes the ambiguity. A request that has been escalated is a request being taken seriously.
One request beats a sequence
Approvals are usually sought once, so raising a second point after the first is settled means starting the process again. Putting everything you want in a single, prioritised message is faster and reads better. Ranking the items makes it easy for the other side to give you the cheap ones when the expensive one is refused.
This is ordinary practice rather than a tactic, and experienced recruiters expect it.
The constraint may genuinely be real
Approved headcount budgets, published band structures and internal relativities are real limits, not always negotiating positions. An employer that would break its own structure for you would break it for others, which is worth knowing about a workplace.
In practice, where the limit is genuine, the productive question is what else is available and when the next review point falls. Treating a real constraint as a bluff usually costs goodwill without changing the number.
Some of this will suit you and some will not, and that is the point.
Know when the constraint is not yours to solve
Where the pay for a role is simply too low for the local cost of living, no amount of negotiation technique fixes it. That is a market and policy problem, and the honest response is to weigh the role against alternatives rather than to negotiate harder. Collective bargaining exists precisely because individual negotiation has limited reach on general pay levels.
For most people, where a sector is systematically underpaid, a union is more likely to move it than any individual conversation.
The takeaway
Ask what approval routes exist. A request that fits an existing mechanism gets answered faster.
The version you keep doing is the version that works.
Questions readers ask
Should I chase if I hear nothing after asking?
Agree a date to speak again when you make the request. A pause usually means the request has been escalated for approval.
Is it better to ask for several things at once?
Yes, in one prioritised message. Approvals are typically sought once, so a sequence of separate requests is slower and lands worse.
