What if you paid more?

The expectation conversation, held too late

Every role starts with a version that pays what was budgeted, sits in the home city and asks for exactly the experience the team had in mind. Sometimes the market agrees. When it does not, the usual way to find out is a thin shortlist a few weeks in, followed by a conversation about pay and location that both sides would rather have had at the start.

A market map tells you where the role stands. This post is about the next question, the one you actually ask when you see it: what would change if we moved?

A waterfall you can argue with

The market read does not hand over a single pool number and ask to be trusted. It narrows the talent pool filter by filter, from a broad base down to the realistic addressable pool, and shows an estimated pool after each step, with a confidence on each rung and a note where one is thin. Alongside it sit a pay band, low, middle and high, and the single biggest constraint working against the search.

That structure matters for the conversation. When the pool collapses, the waterfall shows which filter did it, so the discussion lands on one requirement rather than on the whole role.

Nobody objects to the market. People object to a number with no working shown. The waterfall is the working.

The levers

When EmployLabs takes on a role with you, you get a Company Room for it, where you work through the role with Meera, and there the market read comes with a what-if playground. Each lever is something you can realistically offer:

• Pay.Raise the offer, or lower it, and the projected pay band moves with it. Asking what happens if you paid more is the question in this post’s title.
• Geographic scope. Open the role to remote work, or widen it beyond the base city to tier-two cities or nationally.
• Experience. Shift the experience requirement down or up by a few years.

Each lever carries its own pool factor, and the factors combine when several are pulled at once. The playground shows the pool before and after, how much it changed, and whether competition for that talent is likely to ease or tighten as a result.

What the numbers are, and what they are not

Every projection is labelled directional, and it should be read that way. The layer counts in the waterfall are research estimates, shown as ranges. The only figure that can come from a real search is the headline pool: once the role has been searched, it can be read from that search’s count of matches, and the map records that it came from that search.

• It costs nothing to explore. The playground works on the market read already on the role. Pulling a lever never runs a paid search.
• It says when it cannot answer. If the pool or the pay band could not be read as numbers, the projection is marked unavailable rather than approximated.
• There is no lever for dropping a must-have. The levers are pay, location and experience. Removing a specific requirement is a change to the brief, made with Meera, not a slider.

From a what-if to the search

Once you settle on a combination, the pay and location levers can be applied, which records them as corrections to the role’s market read; an experience change is agreed as a change to the brief. The conversation that started with what if ends with a read of the role you have agreed with EmployLabs, before anyone is contacted.

How to use it

1. Walk the waterfall with everyone who signs off the role first. Agree which filter is doing the damage before talking about money.
2. Pull one lever at a time. A combined move hides which concession actually bought the pool.
3. Treat the projection as a direction, not a promise, and let the first real search settle the headline number. There is more on how Meera builds the read from the brief.