Not every compensation project is a multi-month overhaul. Sometimes you just need to know what one role is worth, and you need the answer this week.
I recently ran exactly that engagement. One position. Four days, start to finish. $1,000. I want to walk through what actually happened in those four days, because the value here isn't a magic number — it's the process that makes the number defensible.
Day one: understand the role, not the title
The conversation starts with the job, not the job title. A title tells you almost nothing about scope. I need to know what the person actually does: the decisions they own, who they report to, who reports to them, the complexity of the work, the expectations.
I work from a job description when one exists, and from a conversation when one doesn't. By the end of day one, I have a working summary of the role that I can match against survey benchmarks. That summary is the foundation everything else sits on. Get this wrong and the rest of the work is precise nonsense.
Day two: match to survey benchmarks
Once I understand the role, I match it to the right benchmark jobs in the salary survey sources I work with. This is not a title-matching exercise. It's a content-matching exercise — comparing the actual work to the actual benchmark job description.
Most roles match cleanly to one benchmark. Some sit between two, which means I'm using judgment to weight them. I document which benchmarks I used and why, because the client is going to need to explain this later.
Day three: level, age, and adjust
Raw survey data is a snapshot from a point in time. Before it means anything, three things happen.
Leveling: confirming I've matched to the right level of the benchmark. An individual contributor and a manager of that same function are different benchmarks with different data.
Aging: moving the data forward to today. Survey data reflects a collection date, and markets move. I age the data to the effective date using standard market-movement assumptions.
Premiums and adjustments: where warranted, I apply adjustments — a hot skill premium, a geographic differential, a size-of-organization factor. These aren't invented. They come from the survey methodology or from documented market conditions, and I note every one I apply.
Day four: land on a range and document it
By day four, the work converges. I'm not handing the client a single number. I'm handing them a defensible range — typically a 50th-percentile anchor with context around it — plus the full logic of how I got there.
That documentation is the deliverable. The client walks away owning the range and the reasoning behind it. If their CFO asks why the number is what it is, they can answer. If they want to revisit it next year, they have the method, not just the output.
Who this is right for
A single-position engagement like this fits a specific need: you have one role you're unsure about — maybe you're about to make an offer, maybe you're responding to a pay concern, maybe you're sanity-checking a number before a budget conversation — and you don't need a full market pricing project to get there.
If you're pricing a full set of roles, that's a bigger project. Full market pricing engagements run $5,000–$10,000 depending on organization size and are scoped to the full role set. The single-position engagement exists for the moment when one role matters right now and the rest can wait.