Set pay for a new office location
Draft ranges for a city you've never hired in, in local currency.
The prompt
We're opening an office in Toronto. For our 12 most common jobs, show the market differential against our San Francisco ranges and draft Toronto ranges in CAD.
Then try
- Which of these jobs have thin market data in Toronto?
- Compare Toronto to Vancouver.
What you get back
Sample output with illustrative data
Toronto runs well below San Francisco for engineering and somewhat closer for go-to-market roles. Draft ranges below are in CAD at your 50th percentile target.
The problem
Leadership is opening an office in a new city. You need ranges for your most common jobs before recruiting starts posting roles.
The old way
- Buy or borrow a survey for that country
- Map every job again
- Convert currencies and sanity-check by hand
Why it works in Pave
Global benchmarks built in
No extra survey to buy for a new country.
Starts from your bands
Ranges are drafted relative to what you already pay, so they fit your structure.
Flags thin data
It tells you when a job has too little market data to trust.
Data it uses
Your data
- Current ranges
Your San Francisco bands - Headcount by job
To find your most common roles - Comp philosophy
Target percentiles
Pave intelligence
- Market Data benchmarks
Canada, by job and level - Geographic differentials
City-level adjustments
What you need
See it on your data
We'll run this prompt in your Pave instance before we ever meet.
Book a demo
