HomeJournalNegotiation
NegotiationCareerSalary

How to Negotiate Like You Have Options (Even When You Do Not)

Most salary negotiations are lost in the first email, before an "ask" is even on the table. The tone gives it away — desperate, grateful, relieved to be offered anything. This post teaches a very simple shift: how to negotiate from a position of calm optionality, what to say and not say, and the five moves that tend to get a 15–30% bump even when you genuinely have no other offer in hand.

Siddharth PuriJanuary 26, 20267 min read
Career Growth

How to Negotiate Like You Have Options (Even When You Do Not)

January 26, 2026 · 7 min read · Siddharth Puri

Most salary negotiations are lost in the first email, before anyone has asked for a number. The tone gives it away — desperate, grateful, relieved to be offered anything at all. That tone costs people between ten and thirty percent of their next salary.

The fix is not a complicated playbook. It is a small internal shift: negotiate as if you have other options, whether or not you actually do. The company does not know either way.

The shift

You do not have to be arrogant. You have to be unreadable. A candidate who seems like they are weighing things carefully, who says "let me think about it," who comes back in 48 hours with a counteroffer instead of a grateful yes — that candidate is negotiating like they have options. Hiring managers respond to that behaviour with higher numbers. It is almost automatic.

You do not have to lie about other offers. You have to stop signalling that this is your only one.

Five moves that work

  • Never give a number first. "What is the range for this role?" is a complete sentence
  • When they give a range, assume the top of the range is the starting point, not the ceiling
  • Always take 48 hours to respond to an offer. Always. Even if you know you will say yes
  • Come back with a specific counter, not a vague "can we do better." Numbers anchor
  • Negotiate components, not just base. Signing bonus, equity, start date, title, learning budget, remote policy — all of these are levers

What to say when you do not have another offer

Do not lie. Do not say "I have another offer" if you do not. Liars get caught and it costs you the role plus the reputation. Instead, say true things that imply optionality.

  • "I am in the final stages with two other teams"
  • "I am evaluating a few directions for my next role"
  • "I want to make a careful decision, so I would like 48 hours"
  • "I was hoping for X, based on the market and the scope of this role"

Every one of these sentences is true for almost any candidate. None of them are lies. All of them shift the dynamic.

What to never do

  • Say "yes" in the first email. Always a 48-hour minimum
  • Accept the first number. Always counter, even if the counter is small
  • Apologise for negotiating. "Sorry to ask but…" leaves money on the table
  • Compare yourself downward ("my current salary is…"). Compare yourself to the role and the market
  • Accept components you do not actually understand. Ask about the equity, the vesting, the refresh

The mental model

The company has already decided they want to hire you. That is why there is an offer at all. Every day they do not close the offer is a day the role stays open and costs them. You have more leverage than you feel like you have, at the exact moment you feel like you have the least.

Negotiate from that reality. Not from the panic. One good negotiation pays more than a year of raises. Treat it accordingly.

Never give a number first. Never say yes in the first email. Never apologise for asking.
All postsSiddharth Puri

Keep reading

View all →
AI & Future of Work

Claude 3 vs GPT-5: What Changed and Why It Matters

March 26, 2026 · 9 min

Claude 3 vs GPT-5: What Changed and Why It Matters

They both claim to be the smartest thing ever built, and both demos look suspiciously similar. This is a ground-level look at how Claude 3 and GPT-5 actually differ in reasoning depth, long-context reliability, code quality and tool use — plus a blunt cheat sheet for which one to pick for which job. Written in English, without the benchmarks theatre.

AI & Future of Work

Will AI Really Replace Developers or Just Upgrade Them?

March 18, 2026 · 8 min

Will AI Really Replace Developers or Just Upgrade Them?

The internet has been burying developers every year since 1998 and we keep showing up for breakfast. Here is the honest split — which parts of the job AI genuinely eats (boilerplate, docs, test scaffolding, Stack Overflow archaeology) and which parts quietly get harder and more valuable (product judgement, architecture, ambiguity). Short answer: it replaces the parts of your job you hated, and the parts that pay you get more fun.

AI & Future of Work

Jobs That Will Survive the AI Revolution (And Why)

March 8, 2026 · 9 min

Jobs That Will Survive the AI Revolution (And Why)

Forget the "creative vs repetitive" framing — the real line is "work customers trust a machine with vs work they do not." This post maps three tiers: jobs that will stay deeply human (health, founding sales, investigative journalism, skilled trades), jobs that will transform rather than disappear (design, engineering, teaching, support), and jobs that are quietly becoming the best bets of the decade. A calmer, less LinkedIn-flavoured take on the next ten years.