Interviews

Salary negotiation practice for IT consultants

An IT consultant's compensation conversation looks different depending on the engagement structure, a billing rate to negotiate as an independent contractor, or a base salary and bonus to negotiate as a firm employee, and sometimes a title change from senior to principal consultant. Intervieux's salary negotiation type runs both new-offer and internal-raise modes as a spoken conversation with an AI that pushes back.

Neither version of this conversation gets much rehearsal anywhere else. Independent consultants often set a rate once and rarely revisit how to defend it out loud, and firm employees frequently avoid asking for a title bump until the conversation is already happening for real.

The scenario: two different money conversations

One version of this scenario is a consultant who's been quoting the same hourly rate for a year and just got handed a project scope that's clearly bigger than what that rate was set for. The other is a senior consultant at a firm who's carried the workload of a principal for two quarters without the title or the pay bump to match, and now has to make that case to a practice lead who controls the budget.

Both are real IT consulting negotiations, and both benefit from saying the actual ask out loud before it has to land in front of the person who can say no.

What each mode covers

New-offer mode fits the rate negotiation, stating a specific number for a project's scope and holding that position when a client or staffing firm pushes back with a lower counter or a request to bundle in extra work at no additional cost.

Internal-raise mode fits the title and compensation conversation with a practice lead, framed around the actual scope of work being carried rather than a general request for more money. Both modes have the AI on the other side respond the way a real client or manager would, with hesitation, a counter, or a request for more justification, rather than agreeing right away.

Scoring

How the report reads this conversation

The abrupt-ending penalty is worth watching specifically in the rate-negotiation scenario, since a consultant who states a number and then goes quiet once pushback starts is a common failure mode this session is built to surface. Holding the conversation through a counter-offer, restating the number with the reasoning behind it, matters more than getting the client to agree on the first try.

The written reasoning in the report explains what specifically held up in the ask, the pushback, and the close, which matters more here than a single pass or fail on the number itself.

Frequently asked questions

Which mode fits negotiating a project billing rate?

New-offer mode fits that scenario, practicing stating a rate for a specific scope and holding that position when a client or staffing firm counters lower.

Which mode fits asking for a title change from senior to principal consultant?

Internal-raise mode fits that conversation, since it's built around the exchange an employee has with a manager about current compensation and scope of work.

Does the AI actually push back during this practice, or just agree?

It pushes back. The AI on the other side of the conversation responds the way a real client or manager would, with hesitation or a counter, rather than accepting the first number stated.

Can I practice this before I have an actual offer or scope change in hand?

Yes. Both modes can be used ahead of a real conversation, whether a specific project scope or title decision is already on the table or not.

Related pages

Rehearse the rate or raise conversation before it happens for real

Practice negotiating a project billing rate or an internal title and pay conversation out loud, then review a scored report on how it went.