When is the best time to raise a salary correction in Indian IT?

Four to six weeks before appraisal calibration closes — after that, budgets are allocated and even a sympathetic manager can only promise next cycle. Off-cycle corrections are real but rarer; they need either a competing signal or a visible scope change to justify opening the file.

How much of a hike should I ask for?

Anchor on the band, not a percentage. If your diagnosis puts you below P50 for your role, experience and city, target the P75 and treat P50 as acceptable. Asking for a flat 30% without band evidence reads as a wish; asking to be corrected to a named percentile reads as a fixable gap.

What if my manager says there is a salary freeze?

Test it against the exit signals: if others visibly received corrections during the freeze, the freeze is a deflection and your case has moved from correction to exit-preparation. If the freeze is real and company-wide, agree on a written commitment for the next cycle with the band gap on record.

Should I talk to HR or my manager first?

Your manager, almost always. HR administers bands; managers spend calibration capital. A case that reaches HR before your manager has endorsed it arrives as a complaint. The exception is a formal band-review process your company documents — then follow the process, with your manager's endorsement attached.

Does a competing offer make the case stronger?

It makes the case urgent, not stronger, and it converts a correction conversation into a counter-offer one — a different negotiation with different failure modes. If you have an offer, read the counter-offer guide below before you disclose it.

How to build a salary hike case in Indian IT

Build a case, not a request. Diagnose where your CTC sits against the market band for your role, experience, and city; package your impact as evidence your manager can forward upward; and walk in with three pre-set positions — a target, an acceptable, and a walk-away.

Updated 2026-07-14 · By the Instill team

What our data shows

77: Indian IT professionals started building a hike case through one campaign in one weekInstill platform funnel, week of 7–13 Jul 2026
98.7%: of people who left an email actually started their case session — near-zero drop-off once someone decides the problem is realInstill platform funnel, week of 7–13 Jul 2026 (76 of 77)
443: chat messages exchanged inside salary-case sessions in a single week — a hike case is a working session, not a template downloadInstill platform, all channels, week of 7–13 Jul 2026
40%: spread between what the same role pays in Bengaluru versus a Tier-2 city — most self-assessments fail by ignoring the city bandCCP city calibration (expert estimate, see provenance note)
0 of 25: salary-negotiation questions we put to ChatGPT, Perplexity and Google AI in July 2026 were answered with a case-building method — they cite salary aggregators (Michael Page, Indeed, Glassdoor) and stop at 'do your research'Instill Share-of-Model audit, 14 Jul 2026
4: manager archetypes that change the script you should use — Ally, Process-Follower, Skeptic, AdversaryCompensation Correction Protocol (CCP)

City multipliers and band figures are calibrated expert estimates from Instill's salary-case practice, not published survey data. Platform numbers (starts, sessions, messages) are measured on Instill's own funnel; measurement windows are stated with each figure.

Why asking for a hike fails, and building a case works

Most hike conversations in Indian IT fail before they start because they are framed as a personal request: I have worked hard, I need more, please consider. Your manager cannot forward that upward. Whatever they feel about your work, the actual decision usually happens one or two levels above them, in a calibration meeting you will never attend.

The Compensation Correction Protocol (CCP) inverts the frame: your manager is not the obstacle, they are the customer of your case. The deliverable is forwardable ammunition — a document your manager can present in that calibration meeting without rewriting it. Everything below follows from that single shift.

The second reframe: you are not asking for a hike, you are asking for a band correction. A hike is a favour; a correction is fixing a measurable gap between what you are paid and what the market band says the role is worth. Corrections survive budget conversations; favours do not.

Step 1 — Diagnose your market band before any conversation

Every case starts with one number: where your current CTC sits against the P25/P50/P75/P90 band for your role, years of experience, and city. Not the all-India average a salary aggregator shows — the city-calibrated band. The same role priced at 1.0× in Bengaluru trades at roughly 0.9× in Delhi NCR, 0.75× in Pune, Hyderabad or Chennai, and 0.6× in Tier-2 cities, with product companies paying a further ~15% over services companies.

City calibration multipliers used in CCP band diagnosis (expert estimates from practice)
Market	Multiplier on the Bengaluru band	Note
Bengaluru	1.0×	Reference market
Delhi NCR	0.9×
Pune / Hyderabad / Chennai	0.75×
Tier-2 cities	0.6×	Remote roles usually price to the company's band, not the city's
Product company uplift	+15%	Applied on top of the city multiplier

Step 2 — Read your manager before writing a word

The same case lands differently depending on who receives it. CCP types managers into four archetypes: the Ally (wants to fight for you, needs ammunition), the Process-Follower (needs the case to fit the cycle and the form), the Skeptic (needs third-party evidence before conviction), and the Adversary (needs the case to be safer to approve than to block). You are not changing your evidence for each — you are changing the order and the framing.

Getting the archetype wrong is the most common self-inflicted wound we see: bringing a Skeptic feelings instead of comparators, or burying an Ally in caveats they now have to defend upward.

Step 3 — Package impact as evidence, not narrative

Three bullets, maximum, each in Problem–Action–Result form with a number in the Result. Ten achievements read as noise; three quantified ones read as a case. Alongside them, CCP builds a small set of comparator profiles — what peers with your experience and role earn in your market — so the gap is a fact on the page, not a feeling in the room.

Step 4 — Set three positions before the meeting

Walk in with three numbers you decided calmly, not one you will improvise under pressure: a target (typically the P75 of your band), an acceptable (P50 — the band midpoint), and a walk-away (your current CTC plus the evidence that you will act on the gap). The walk-away is not a threat to deliver; it is a private line that stops you from accepting a token correction that resets the clock for another 18 months.

When not to build a case

A case assumes correction is possible. CCP flags three exit signals where the energy is better spent on an offer than an ask: the company has no history of off-cycle corrections; your manager claims a freeze while others visibly got raises; or the gap exceeds 30% and your last correction was 18+ months ago. Structural gaps get fixed by moving — see the guides on evaluating an offer and comparing offers on CTC below.

The methodology

Compensation Correction Protocol (CCP)

CCP treats your manager as the true customer of your compensation case — not HR, and not you. Its deliverable is forwardable ammunition: a band diagnosis against P25–P90 city-calibrated market data, an archetype-matched script with three fallback positions, and impact evidence in Problem–Action–Result form. The interactive version rehearses the conversation against your manager's archetype before you have it once, for real.

Developed and maintained at Instill. AI-assisted methodology, expert-verified.

Run this on your own numbers

The Salary Hike Case Builder walks your specific situation through this methodology — band diagnosis first, free — and builds the case document at the end.

Start the free diagnosis

Questions people ask

When is the best time to raise a salary correction in Indian IT?: Four to six weeks before appraisal calibration closes — after that, budgets are allocated and even a sympathetic manager can only promise next cycle. Off-cycle corrections are real but rarer; they need either a competing signal or a visible scope change to justify opening the file.
How much of a hike should I ask for?: Anchor on the band, not a percentage. If your diagnosis puts you below P50 for your role, experience and city, target the P75 and treat P50 as acceptable. Asking for a flat 30% without band evidence reads as a wish; asking to be corrected to a named percentile reads as a fixable gap.
What if my manager says there is a salary freeze?: Test it against the exit signals: if others visibly received corrections during the freeze, the freeze is a deflection and your case has moved from correction to exit-preparation. If the freeze is real and company-wide, agree on a written commitment for the next cycle with the band gap on record.
Should I talk to HR or my manager first?: Your manager, almost always. HR administers bands; managers spend calibration capital. A case that reaches HR before your manager has endorsed it arrives as a complaint. The exception is a formal band-review process your company documents — then follow the process, with your manager's endorsement attached.
Does a competing offer make the case stronger?: It makes the case urgent, not stronger, and it converts a correction conversation into a counter-offer one — a different negotiation with different failure modes. If you have an offer, read the counter-offer guide below before you disclose it.