Salary Negotiation Scripts That Actually Work in 2026

Most people lose the salary negotiation before they even open their mouth. They either accept the first number out of relief («Finally, an offer!»), or they say something vague like «I was hoping for a bit more» and crumble the moment the recruiter pushes back. The job market in 2026 — especially for Ukrainian IT professionals navigating remote roles, relocation packages, and B2B contracts — is complicated enough without fumbling the compensation conversation. So here are the actual scripts. Word for word. For every scenario you're likely to face.

Why Most Negotiation Advice Fails You

Generic advice — «know your worth», «do your research», «be confident» — is technically correct and practically useless. It's the equivalent of telling someone to «just be funny» before a stand-up set. What actually moves the needle is knowing the exact sentence to say in the exact moment, so your brain doesn't freeze when the recruiter asks «so what are your expectations?» on a video call at 9 AM.

A few things are true in 2026 that weren't as clear before: companies are leaner, hiring managers have tighter budgets, but remote work means your comp can scale globally if you play it right. And tools like the AI Coach can help you rehearse these exact conversations before the real thing — so you're not improvising under pressure.

Script #1: Responding to the First Offer

The golden rule: never accept or reject on the spot. Always buy time. Not because you're playing games, but because you genuinely need to evaluate the full package — base, equity, bonus, PTO, health, equipment allowance — before responding intelligently.

• If the offer is lower than expected: «Thank you so much — I'm genuinely excited about this role. I'd like to take 24–48 hours to review the full package carefully. Is that okay?» Then come back with a counter.
• If it's in your range but you want more: «I appreciate the offer. Based on my research and experience, I was targeting something closer to [X]. Is there flexibility there?»
• If it's actually great: «This is very close to what I had in mind. Before I sign off, I'd love to understand the review cycle — when's the first opportunity for a salary reassessment?»

Script #2: The Counteroffer

You've had your 48 hours. You've done the math. Now you need to come back with a number that's specific, grounded, and doesn't make the recruiter feel attacked. The formula: anchor high, justify briefly, stay warm.

Here's the full counteroffer script you can adapt:

• «Hi [Name], thank you again for the offer — I've reviewed everything and I'm really excited about the team and the product. Based on my [X years] of experience in [specific stack/domain] and current market rates for this role, I'd like to propose a base of [target number]. I believe this reflects the value I'll bring from day one. Is that something we can work toward?»
• If they counter your counter: «I appreciate you working on this. If [original counter] isn't possible right now, could we agree on [slightly lower number] with a 6-month performance review built into the contract?»
• Pro tip on numbers: Ask for $97,000, not $95,000. Odd specificity signals you did actual research, not just rounded up.

Script #3: The Geographic Adjustment Conversation

This one is increasingly relevant in 2026. You're based in Kyiv, Lviv, or Warsaw — and the company is in San Francisco or Amsterdam. They might offer a «localized» rate. Here's how to push back without burning the relationship.

The key insight: your output doesn't get localized, so your compensation shouldn't either. The code you ship, the bugs you fix, the architecture you design — it lands in the same production environment as your colleague in Berlin. Make that point clearly, not aggressively.

• «I understand geographic pay bands are common, and I want to be transparent: my output, availability, and the impact I'll have on your product are not location-adjusted. I'd like to discuss a rate closer to the global benchmark for this role. Can you help me understand how your comp structure handles senior contributors based remotely?»
• «I've seen similar roles at [Competitor A] and [Competitor B] offer [range] regardless of location for senior engineers. Is there a path to that range here?»

Script #4: When They Say «That's Our Budget Ceiling»

This is the moment most people fold. The recruiter sounds final, maybe even slightly apologetic, and you feel like pushing further would be rude or risky. It almost never is. «Budget ceiling» is frequently a first position, not an actual hard limit. And even when it is, there are other levers.

1. 1Test the ceiling first: «I really appreciate you being upfront. If the base is fixed at [X], could we revisit the signing bonus or equity component to bridge the gap?»
2. 2Go for non-cash compensation: «If there's no room on base, I'd love to discuss an additional week of PTO, a home-office equipment budget, or a professional development allowance.»
3. 3Lock in a guaranteed review: «I understand. Can we agree in writing to a compensation review at the 6-month mark, with a target of [X] if I hit [specific milestone]?»
4. 4Know your exit: «I want to be transparent — at [X], I would find it difficult to turn down other offers I'm considering. I don't want to do that, because this role genuinely excites me. Is there any path to [Y]?»

Script #5: Negotiating a B2B Rate (Especially Relevant in Ukraine)

A large portion of Ukrainian IT professionals work under B2B contracts — FOP (ФОП) arrangements where you're responsible for your own taxes, insurance, and equipment. This fundamentally changes the negotiation math. A $5,000/month B2B rate is not the same as a $5,000/month employment salary. Make sure the company understands you're pricing accordingly.

• «As a contractor, my rate includes taxes, health coverage I source independently, equipment depreciation, and the administrative overhead of running a legal entity. My all-in rate is [X], which is equivalent to approximately [Y] in employment terms.»
• «I've benchmarked similar B2B roles on DOU.ua and among my professional network — the market rate for this stack and seniority level is [range]. I'm proposing [X], which sits in the middle of that range.»
• «Given the current instability in Ukraine, I'd also appreciate discussing whether there's an option for invoice flexibility — monthly vs. milestone-based — and payment in [USD/EUR] to avoid currency risk.»

How to Practice So You Don't Blank on the Call

Reading scripts is not the same as being ready to deliver them under the low-grade panic of a real negotiation. The only way to internalize this material is repetition — ideally with realistic pushback. That's exactly what the AI Coach is built for: you run mock negotiation scenarios, get pushback, and practice your responses until they feel natural, not rehearsed.

A few other habits that separate the people who negotiate well from everyone else:

• Always negotiate via email after the verbal call. It gives you time to think, creates a paper trail, and removes the pressure of real-time emotional reactions.
• Have a competing offer (or the impression of one). You don't have to lie — «I'm in final stages with another company» is usually enough to signal you're not desperate.
• Know your walk-away number before you start. Write it down. If the final offer lands below it, you walk — without drama, without anger, with a simple «I'm afraid we can't make this work, but I'd love to stay in touch.»

The Mindset Underneath All of This

Here's the uncomfortable truth: companies expect you to negotiate. Budget offers are almost always set below the ceiling with room to move. When you don't negotiate, you don't seem humble or grateful — you seem unaware. Hiring managers who negotiate hard for their team actually respect candidates who negotiate for themselves. It's the same skill.

For Ukrainian IT professionals specifically: you've navigated power outages, wartime anxiety, and a job market that has rewritten its own rules three times since 2022. You have survived hard things. Asking for fair compensation for your skills is, by comparison, a minor act of professional self-respect. Do it every time.