35
Employees across 10 countries
40%
Less admin time on compensation
20%
Retention increase year-over-year
92%
Employee satisfaction with pay fairness
In early 2023, CloudVista, a B2B SaaS company with 35 employees spread across the US, Europe, and Asia, faced a looming crisis. Their pay strategy was a patchwork of local salary surveys, ad-hoc adjustments, and gut feelings. The result? Pay disparities, grumbling on Slack, and a 15% annual turnover rate. The CEO, Sarah, knew something had to change.
"We were losing great people because they felt undervalued compared to peers in other locations," she recalls. "And our finance team was spending 25 hours a month just on compensation calculations." The problem wasn't unique—but the solution they built was.
The Situation
CloudVista had grown quickly, hiring wherever top talent lived. But their pay bands were based on a single location (San Francisco), which meant a junior developer in Poland earned the same as one in Austin—except when it didn't, because managers would negotiate exceptions. The result:
- Salary ranges were inconsistent (e.g., same role varied by 40% across regions)
- Employees in high-cost areas felt underpaid; those in low-cost areas felt overpaid and at risk
- HR spent hours reconciling market data from disparate sources
- Managers dreaded compensation conversations, leading to delayed negotiations and resentment
The breaking point came when two senior engineers (one in Berlin, one in Bangalore) simultaneously resigned for better offers. Exit interviews revealed a common theme: "I don't trust that my pay is fair."
The Approach
Sarah assembled a task force: the Head of People, three engineering managers, and a finance analyst. They decided to build a location-agnostic, market-based pay framework. The core principles:
- Base salary anchored to industry benchmarks for each role, regardless of location
- Cost-of-living adjusters for geo-differentials (not full location pay)
- Transparent pay bands published internally for all roles
- Annual review with automatic adjustments for inflation and market changes
But the biggest challenge was human, not mathematical. Managers and employees had to trust the system. That's where they used Negotiation Simulator—to practice conversations about pay adjustments before rolling them out. "We ran simulations for every manager," explains Maya Chen, the People Ops lead at the time. "They role-played explaining why someone's pay didn't change, or why it went down. It made the actual rollout 10x smoother."
The Execution
Over three months, the team did the following:
Step 1: Market Data Collection
They bought salary data from Radford and Payscale, plus used Levels.fyi for tech roles. For each role, they identified a 50th percentile target for total compensation. (Note: This is a composite case; data sources are referenced for realism.)
Step 2: Define Pay Zones
Instead of location-specific pay, they created four zones based on cost of living:
| Zone | Example Locations | Geo-Differential |
|---|---|---|
| 1 | San Francisco, New York, London | +20% over base |
| 2 | Seattle, Austin, Berlin | +10% |
| 3 | Remote US, most EU capitals | +0% (base) |
| 4 | Remote Asia, Eastern Europe | -10% |
The base itself was set at the 50th percentile for each role nationally (US benchmark). So a Senior Engineer in Zone 1 would get 120% of that base; in Zone 4, 90%.
Step 3: Communicate the Change
They held a company all-hands explaining the philosophy: "We want to pay fairly for the role, not for where you sit. But we acknowledge location cost differences." Then each employee received a personalized letter with their new band and where they fell within it. Managers held one-on-ones to discuss.
"The simulations we did earlier really paid off," says Maya. "Managers who had practiced on the Negotiation Simulator were calm and prepared. They could handle pushback without getting defensive."
Step 4: Implement Auto-Adjustments
Using Workings.me's compensation tracking tools (integrated with their HRIS), they set up quarterly market reviews. If the market moved, bands updated automatically—and employees were notified via email with a clear rationale.
The Results
After six months, the impact was clear:
| Metric | Before | After |
|---|---|---|
| Time spent on compensation admin (per month) | 25 hours | 15 hours (-40%) |
| Annual voluntary turnover | 15% | 12% (projected to 8% year-end) |
| Employee pay satisfaction (survey) | 63% favorable | 92% favorable |
| Number of pay equity complaints | 5 per quarter | 0 in last quarter |
"We didn't just save time; we transformed trust," says Sarah. "People now believe the system is fair, so they focus on their work."
"The pay zone model gave us a simple, defensible framework. And using the Negotiation Simulator to prepare our managers was a game-changer—it turned potentially awkward conversations into empowering ones."
— Maya Chen, former People Ops Manager (Composite)
Key Takeaways
- Base pay on role, not location. Let geo-differentials be a small percentage (10-20%) rather than full location salaries. This simplifies administration and reduces perceived inequity.
- Publish your bands internally. It's scary but powerful. At CloudVista, it eliminated 'whisper comparisons' and forced managers to justify disparities.
- Invest in manager training. The Negotiation Simulator at Workings.me was instrumental. Practicing difficult conversations means fewer mistakes and more consistency during rollouts.
- Use a composite of market data sources. Relying on one survey is dangerous. Cross-reference at least three to set credible bands.
- Build in automatic adjustments. Manual reviews get postponed. Automating quarterly refreshes ensures bands stay current without extra effort.
- Communicate the 'why' relentlessly. Every employee should understand the philosophy behind the pay structure. Repeat it in all-hands, emails, and one-on-ones.
- Measure satisfaction frequently. CloudVista surveyed every quarter. Early data showed skepticism, which they addressed by clarifying band assignment.
Apply This to Your Situation
Whether you're a 10-person startup or a 100-person scale-up, the principles apply. Here's a step-by-step framework:
Step 1: Audit Your Current State
Export all salaries, roles, and locations. Calculate the spread (max/min) for each role. If it's >30%, you likely have a problem.
Step 2: Define Your Philosophy
Are you paying for role value or for location? There's no wrong answer, but be consistent. CloudVista chose role value with location adjusters. Document it.
Step 3: Choose Market Sources
Use at least two of: Radford, Payscale, Levels.fyi, or Glassdoor. Get a 50th percentile for each role in your primary market (often US).
Step 4: Create Location Zones
Group countries/cities into 3-5 bands based on cost of living (use data from Numbeo). Assign +/-% adjusters.
Step 5: Simulate the Rollout
Before talking to employees, test your messaging. The Negotiation Simulator is perfect for this. Run role-play scenarios with your managers so they can handle objections like "Why did my pay stay the same?" or "Why am I in a lower zone?"
Step 6: Communicate and Iterate
Roll out in phases: first to leadership, then all-hands, then one-on-ones. Collect feedback weekly and adjust if needed (but stick to the principles).
Common Pitfalls to Avoid
- Over-relying on a single survey. One data point is not a trend. Use multiple sources.
- Ignoring equity compensation. Stock options or RSUs can offset small salary differences. Include them in total comp comparisons.
- Changing bands too frequently. Quarterly is fine; monthly causes confusion. Set a cadence.
- Forgetting to train managers. They are your frontline communicators. If they stumble, trust erodes.
- Not benchmarking against your specific industry. A SaaS company's pay differs from retail. Use industry-specific surveys.
CloudVista's experience is a proof point: a structured, transparent pay strategy not only saves admin time but builds a culture of fairness that retains top talent. And it doesn't require a full-time compensation analyst—just clear methodology and the right tools.