Increase Your Salary. Build the value you can prove, then negotiate the number.

You're the one the team leans on when something breaks. Somehow that has made you too valuable to move. Two years of strong reviews and the same band, while the people who talk more get moved up around you.

There's a mechanism behind this and it isn't personal. Reliable people generate no incidents, and organisations allocate attention to incidents. Being the reason nothing went wrong is genuinely invisible in every system a company uses to decide who gets paid more.

So the work is making the invisible thing legible, and it's more mechanical than it sounds. Thirty-odd impact statements covering the last two years, each translating what you did into what changed: money saved, time recovered, scope absorbed, risk removed before it became an incident. Most people find this excruciating for the first hour and then can't stop.

What you end up holding is a case a decision-maker can't wave away, and specifically one your manager can carry into a room you're not in. That's the actual bottleneck: not whether they rate you, but whether they can prove it to somebody else at short notice.

You genuinely don't know what your role pays at the top of your market. So you anchor low, or you dodge the question, and either way the money is gone before the conversation properly started.

We calibrate against real data rather than the averages that come up first: Levels.fyi for the global picture, Platy.cz for Czech roles, and my own network of tech-leadership comp across CEE, which is the part you can't google. You walk out with a band you can defend line by line and one specific number inside it.

The number matters less than being unbothered when you say it. That's the bit we rehearse.

In the review, or the interview, it comes out as task language. I led the migration. I managed the team. You could feel it land flat and you don't know how to say it better without sounding like you're bragging, so you undersell it again, and the CFO in the room stopped listening about forty seconds in.

Two separate skills are missing here and they need different work. One is a vocabulary problem: leaders buy outcomes, tradeoffs and unit economics, and you're describing activity. The other is a permission problem, which is the one that takes longer, because you were probably trained somewhere that describing your own impact accurately is immodest.

We build the differentiator sentence first, the one that says what you're for in a way a CTO respects and a CFO understands. Then the business vocabulary underneath it so it survives a follow-up question. Then we record you saying it, repeatedly, until the outcome language comes out automatically and the cringe has worn off, which usually takes about three sessions and is the least dignified part of the work.

Every time you raise comp it's budgets are tight, or next review. You don't want to threaten to leave, because you genuinely like the place. And you're finished with being the cheapest senior person in the building while training people who out-earn you.

The thing that unlocks this is rarely a better argument. It's a deadline that exists whether or not anybody agrees to it, because next cycle works as an answer precisely as long as it costs nothing to say.

So we build the case, which is the impact log plus the market band plus one specific number. Then we write the if-not-X-by-Y-then-Z, in advance, on paper, where Z is something you'd genuinely do. Then I play your manager in the dry run, including the deflection you've heard three times, so the real conversation isn't the first time you've said any of it out loud.

You come out of it with the conversation held, a number on the table, and a documented fallback if the answer is still no. The fallback is the part that changes how the first two land.

An offer lands, somebody said yes, and the relief is so strong you accept on the spot. Weeks later you find out one question would have been worth 20%. You don't know how to push without spending the goodwill you just earned.

You can't spend it, in practice. Companies expect a negotiation and quietly price for one, which means the candidate who doesn't negotiate simply funds the one who does. Nobody rescinds over a well-mannered ask, and if anyone ever did, you learned something important about them for free.

So we run mock negotiations with me as the hiring manager: the anchor, the silence after it, the second ask, the walk-away, and what your BATNA genuinely is rather than what you'd like it to be. For an internal move we work scope and title alongside the number, because those compound and a one-off bump doesn't. It's a thirty-minute skill that pays for about a decade.