How to Negotiate Salary Using Cost of Living Data
Turn BEA Regional Price Parities into a compelling, data-backed case for the compensation you actually deserve.
Your purchasing power depends on both your salary and where you live. The BEA's Regional Price Parities let you convert any salary into a single comparable number regardless of location. Use the formula: Real purchasing power = (Nominal salary ÷ Local RPP) × 100. This converts your salary into "national-average dollars" — the most credible way to present location-adjusted compensation in negotiations.
Real Wages vs. Nominal Wages
Most salary discussions focus on nominal wages — the number on your offer letter. But what that number can actually buy depends entirely on where you spend it. A $90,000 salary in Knoxville, Tennessee has more purchasing power than a $110,000 salary in Boston, Massachusetts, even though the nominal difference looks substantial in Boston's favor.
This is the distinction between nominal wages (the dollar amount) and real wages (purchasing power after adjusting for local prices). Economists and policymakers use real wages to compare living standards across geographies and time. You should use them in salary negotiations.
The BEA's Regional Price Parities (RPPs) are the best available tool for this conversion. They measure the price level in a metropolitan area relative to the national average (set to 100), covering all goods, services, and housing. An RPP of 88 means the local price level is 12% below the national average; an RPP of 115 means 15% above average.
The RPP Purchasing Power Formula
Converting a nominal salary to real purchasing power is simple:
Real purchasing power = (Nominal salary ÷ Local RPP) × 100
This gives you what your salary is worth in "national-average dollars" — a common currency that lets you compare offers in different cities fairly. Examples:
- $85,000 in Memphis, TN (RPP ~86): $85,000 ÷ 86 × 100 = $98,837 in real terms
- $105,000 in Washington, DC (RPP ~116): $105,000 ÷ 116 × 100 = $90,517 in real terms
- $75,000 in Amarillo, TX (RPP ~85): $75,000 ÷ 85 × 100 = $88,235 in real terms
- $120,000 in San Jose, CA (RPP ~131): $120,000 ÷ 131 × 100 = $91,603 in real terms
The Washington and San Jose numbers illustrate a common trap: high nominal salaries in expensive metros often translate to lower real purchasing power than moderate salaries in affordable cities. Use the PlainCost salary calculator to run these conversions for any metro automatically, or browse all metro area RPP data to find the numbers for your city.
Using RPP Data in Salary Negotiations
Bringing data to a salary negotiation reframes the conversation from opinion to evidence. Here's how to present RPP data effectively:
Scenario 1: You're moving from a cheaper market to an expensive one. Calculate your current real purchasing power and show what nominal salary you'd need in the new city to maintain the same living standard. If you currently earn $80,000 in a metro with RPP 88 (real value: $90,909), and the new city has RPP 118, you'd need $80,000 × (118 ÷ 88) = $107,273 just to break even. This is a defensible, data-based counterpoint to an offer that ignores location.
Scenario 2: You're asking for a raise and have received competing offers from other markets. Show that your real compensation is below market even if your nominal salary looks competitive. If your $95,000 local salary converts to $87,000 in real terms, but competing offers in similar-cost markets are at $100,000, you have documented evidence of undercompensation.
Scenario 3: Your employer wants to cut your pay for relocating to a cheaper city. Acknowledge that prices are lower in your destination metro, but demonstrate using RPP data exactly how much lower — and negotiate a proportional cut rather than an arbitrary one. If the destination RPP is 92 vs. your current 105, prices are 12.4% lower, so a proportional cut would be $92,000 ÷ $105,000 = 12.4% — not the larger cut your employer may propose.
Where to Find Supporting Wage Data
RPP data shows what things cost locally; you also need data on what people in your role earn locally. The best sources:
BLS Occupational Employment and Wage Statistics (OEWS). The Bureau of Labor Statistics publishes median and percentile wages for hundreds of job categories at the metro area level. This is the most official source for local wage benchmarks. Search by occupation and metro at the BLS website.
Census Bureau's American Community Survey. The ACS provides median household and individual income data for metro areas and counties. Useful for understanding local income context.
H-1B Disclosure Data (if applicable). The Department of Labor's Foreign Labor Certification data shows actual wages paid for H-1B positions by employer and occupation, which can reveal what companies actually pay (vs. what they advertise).
Combining BLS wage data with BEA RPP data gives you a complete picture: what the market pays in your target location in nominal terms, and what that translates to in real purchasing power. See our state-level RPP overview for a starting point, then drill into specific metros.
Remote Work: Should Salary Adjust for Location?
This is one of the most contested questions in modern employment. Two broad approaches exist, and understanding both helps you negotiate from a position of knowledge:
Location-based pay. Some employers (notably Google, Meta, and many large tech companies) adjust salaries based on where the employee lives, using cost of living indices to maintain roughly equal real purchasing power across geographies. Under this model, relocating to a cheaper city means a salary reduction — but your purchasing power stays roughly constant.
Role-based pay. Other employers pay the same salary regardless of employee location, typically anchored to their headquarters market or the national labor market. Under this model, moving from San Francisco to Omaha while keeping your salary is a large real raise — your nominal pay stays the same but your purchasing power increases substantially.
When negotiating with a location-based-pay employer, RPP data is your primary lever. If they propose cutting your salary by 20% for relocating to a city where prices are 12% lower, you have a quantitative case that the proposed cut is disproportionate. Show the math:
- Current city RPP: 115. Your salary: $120,000. Real value: $104,348.
- New city RPP: 92. To maintain real value: $104,348 × 92 ÷ 100 = $96,000.
- A proportional cut would mean: $120,000 × (92 ÷ 115) = $96,000 — not the $85,000 they proposed.
This kind of structured, data-backed argument is harder to dismiss than a general objection to pay cuts.
Common Mistakes to Avoid
Using housing costs only. Relying solely on rent comparisons overstates cost differences in some cases and understates them in others. RPP includes all expenditure categories — use the comprehensive figure.
Using private cost-of-living calculators uncritically. Sites that publish cost-of-living comparisons use varying methodologies and may have incentives to exaggerate differences. BEA RPPs are derived from government survey data with transparent methodology, making them far more defensible in a professional negotiation.
Forgetting state income tax. RPP measures price levels, not tax rates. Moving from a no-income-tax state (Texas, Florida) to a high-income-tax state (California, New York) significantly affects your net take-home even if nominal salaries are similar. Always layer tax analysis on top of RPP analysis.
Anchoring too hard on cost of living alone. A well-rounded negotiation considers market wages, your specific skills, career trajectory, and company performance — not just RPP math. Cost of living data strengthens your case; it doesn't replace all other factors.
Frequently Asked Questions
What is the difference between real wages and nominal wages?
Nominal wages are the dollar amount on your paycheck. Real wages adjust for purchasing power — what those dollars can actually buy in your local market. A $90,000 salary in a city with RPP 85 has greater real purchasing power than a $100,000 salary in a city with RPP 110.
How do I calculate purchasing power using RPP?
Divide your nominal salary by the metro's RPP and multiply by 100. For example: $85,000 ÷ 92 × 100 = $92,391 in national-average purchasing power. This lets you compare offers across different cities on a true apples-to-apples basis.
Should remote workers accept lower salaries for living in cheaper areas?
This depends on your employment agreement and the company's compensation philosophy. Some companies practice location-based pay; others pay uniformly by role. If you're asked to accept a pay cut for relocating, RPP data gives you objective grounds to negotiate — your productivity does not change with your zip code.
What data sources should I cite in a salary negotiation?
The most credible sources are: BEA Regional Price Parities (cost of living), BLS Occupational Employment and Wage Statistics (local wages by occupation), and the Census Bureau's American Community Survey (median household income). These are official government data that cannot be dismissed as biased advocacy.
Sources: U.S. Bureau of Economic Analysis, Regional Price Parities by State and Metro Area; U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
Last updated: February 2026
A worked example
Consider a household earning $75,000 per year facing an annual cost of $18,000 for the service this guide covers. Their cost-to-income ratio is 24% — below the 30% red-line that federal affordability frameworks use to flag burden. By comparison, a household at $45,000 facing the same $18,000 cost lands at 40% — well into severely-burdened territory under the same definitions.
Where to dig deeper
The methodology page documents exactly which federal series we draw from, how we weight regional differences, and the reference period for each metric. The research section publishes original analyses derived from the same underlying database — useful when you want to see year-over-year shifts or peer-jurisdiction comparisons that the per-page detail views don't surface.
| Threshold | Federal definition | Practical meaning |
|---|---|---|
| Below 7% | Affordable | Comfortable margin for unexpected expenses |
| 7-30% | Moderate burden | Manageable but constrains discretionary spending |
| Above 30% | Burdened | HUD definition — qualifies for federal subsidy programs |
| Above 50% | Severely burdened | Trade-offs with food, healthcare, savings |
Frequently asked questions
Where does this data come from?
All figures on this page derive from official federal data — primarily the U.S. Bureau of Labor Statistics, U.S. Census Bureau, U.S. Department of Health and Human Services, and U.S. Department of Labor. We cite the underlying agency and series in the methodology section. No proprietary aggregators are used.
How often are figures updated?
Each series follows its own publication cadence. We refresh our database within 30 days of each upstream release. Specific update timestamps appear in the page footer where available; the methodology page documents the cadence per data series.
Can I use this data for my own analysis?
Yes. The underlying federal data is public domain. Our presentation, calculations, and editorial commentary are licensed for individual reference. For commercial republication or large-scale data extraction, contact us at the email listed on the contact page.
What if the figures here disagree with another source?
Different sources use different methodologies, definitions, geographic boundaries, and reference periods — disagreement is normal and informative. Our methodology page documents exactly which series and reference period we use for each metric, so you can reproduce or audit the figures against the upstream agency directly.