Know Your Worth Means More Than Salary

Most people negotiate the base salary and accept the rest of the offer as if it were weather.

It isn’t. Nearly every other line in an SAP offer is written by someone, which means it can be written differently. The professionals who understand that leave with a materially better position than colleagues who won the same argument about base pay.

This is not about squeezing an employer. It is about knowing what you are actually being offered — and what you are actually being asked to deliver.

The package is the offer, not the salary

Base pay is the most visible number and rarely the most valuable one. Before you compare two offers, price the whole thing:

Variable pay — bonus or commission. What is the target, who sets it, how has it actually paid out in the last three years, and is it discretionary or contractual? A generous target that nobody has ever hit is a decoration.
Pension and employer contribution. Often the largest number in the package after base, and the one people forget entirely.
Car, allowance or mobility budget — and whether it survives a policy change next year.
Time. Holiday, flexibility, the four-day option, the realistic travel expectation. Travel is compensation in reverse: an SAP role at 70% on-site costs you something that never appears on the payslip.
Training and certification — budget, but more importantly time and the right to choose. In a market where skills reprice this fast, the employer who funds your next capability is paying you in a currency that compounds.
Notice period and severance terms — both directions. They set your negotiating position for the next move.

Two offers with identical base pay routinely differ by a wide margin once these are on the table. You cannot evaluate what you have not itemised.

The mandate matters more than the money

Here is the part that experience teaches late: the scope of the role determines your next role. Compensation is a one-year decision; mandate is a five-year one.

Ask what you will actually own:

What decisions can you make without asking?
Who do you report to — and how far is that from where the transformation is really decided?
Is there a budget attached to your responsibility, or only accountability without authority?
Will you be running something, or supporting someone who runs it?

A well-paid role with no decision rights is a comfortable way to stand still. In SAP work particularly — where the value has moved toward judgment and ownership — a mandate that lets you decide, defend and own outcomes is worth more than the delta you were going to argue about.

Title versus scope

Titles inflate at different rates in different companies. “Lead”, “Principal”, “Head of” mean genuinely different things at a consultancy, a software vendor and an end customer.

Do not negotiate a title you cannot substantiate — you will have to justify it at the next interview. Do negotiate one that does not undersell what you run, because the market reads titles before it reads you. If the scope is bigger than the title on offer, name that gap explicitly. It is one of the cheapest things an employer can fix, which makes it one of the easiest asks to win.

Permanent versus contracting

Neither is universally right, and the honest comparison is not day rate versus salary.

Contracting pays a premium for carrying risk: no notice protection, no paid bench, no pension unless you build it, and income that stops when the project does. That premium is real — and it is payment for that risk, not free money. It suits people with a deep, in-demand specialism, a financial buffer and a network that keeps the next contract close.

Permanent buys stability, employer-funded development, pension and the chance to own something over multiple years — which is how you build the kind of track record that makes you an obvious hire later.

The mistake is comparing gross day rate to gross salary and declaring contracting the winner. Compare after utilisation, unpaid time, benefits you now self-fund, and the value of a mandate you can hold long enough to point at.

What “know your worth” actually requires

You cannot benchmark yourself against a number you found in an article — including this one. Do the harder, more accurate thing:

Establish the market range for your specific combination — domain, seniority, industry, region, and whether the demand is genuinely scarce. Specialist recruiters who work your domain daily know this; so do peers who have moved recently. Ask directly, and ask more than one.
Separate scarcity from seniority. Years of experience are not the driver. A capability the employer cannot buy elsewhere is.
Write down your evidence before the conversation. Not responsibilities — outcomes. What you decided, what it changed, what it was worth. Most people underprice themselves because they arrive with a job description instead of a record.
Know your walk-away, and know your must-haves — and make sure at least one of them is not money.

The conversation itself

Negotiate once, late, and on the whole package. Fragmented asks over several weeks read as indecision; a single, well-reasoned “here is what would make this an easy yes” reads as senior.

Two things worth saying plainly:

Silence is a position. You are allowed to consider an offer without filling the pause.
The first offer is a proposal, not a verdict. Employers expect a response. Not making one is a choice you pay for in every subsequent year of that role.

And if an employer treats a reasonable, evidence-based conversation as an affront — that is information about how they will treat you when the project is late.

The bottom line

Know your worth means: know the whole package, know the mandate, know the market for your specific scarcity, and know which parts you actually care about. Then have one clear conversation.

The raise is a year. The mandate is a career.

— Andreas BORN

Read The Talent Brief — the SAP skills, careers and hiring decisions that matter, once a month. Subscribe →