Remote Salary Adjustment Calculator — Hub-Based vs Location-Based vs National Pay Bands

What This Calculator Does

The Remote Salary Adjustment Calculator answers the most common question employees and HR teams collide on when remote work moves somebody between cities: what is the right salary for this person at the new location, given our company’s pay-band policy? Drop your current salary, current city, proposed remote city, your employer’s pay-band policy (national / hub-based / location-based), and how much negotiation leverage you have. The calculator computes the salary your employer’s policy will produce, brackets a fair-market range using cost-of-living indices, and gives you an open-ask + settle- for target so you walk into the conversation with both anchor and walk-away point already crisp.

Most online “cost-of-living converters” stop at the index ratio — “your $150K SF salary equals $108K in Austin” — without modeling the policy that actually determines what your employer will pay, the leverage you bring to the negotiation, or the fair-market band that defines your walk-away. CalcBold’s version is honest: it surfaces the policy-specific offer, brackets the fair range with researched ±5%/+15% bands, and gives you negotiation scripts (open at $X, settle at $Y) instead of just a number to memorize.

The Math — Three Policies, One Salary

The headline number is the salary your employer’s explicit policy will produce. National = full preservation, no reduction; offered by Basecamp, GitLab pre-2020, fully-async startups, and a handful of cost-of-living-blind firms. Hub-based = your salary anchors to the nearest major office with a cap on how far it can drop — typical FAANG: max 15% reduction even if the COL ratio is 0.5×. This is the most common 2026 policy because it preserves a meaningful remote-work bonus while letting employers avoid paying SF rates to someone in Mexico City. Location-based= full COL pass-through, your salary tracks the actual cost of your new city; this is Meta and Google’s standard for approved relocations.

The fair-market range brackets the index-equivalent salary at ±5%/+15% because real-world salary surveys (Levels.fyi, Payscale, BLS OEWS) show the same role in the same city varies roughly ±10-15% across employers. Below fair-low you’re being underpaid for the local market; above fair-high you’re overpaid relative to peers. Within the band you have legitimate negotiation room. The leverage tilt scales the open-ask: each step above 5 adds 2%; each step below 5 subtracts 2%. At leverage ≥7, fair-high is floored at your current salary because full preservation becomes a credible ask when you have other offers in hand.

Worked Example — SF $150K to Austin Under Three Policies

Take a $150K salary in San Francisco (index 105) moving to Austin (index 76), with leverage 5 (standard back-and-forth, no other offers in hand). Index ratio = 76 ÷ 105 = 0.7238. National policy: $150,000 unchanged — full preservation. Hub-based: $150,000 × max(0.85, 0.7238) = $150,000 × 0.85 = $127,500 (the 15% floor binds because the COL ratio is below 0.85). Location-based: $150,000 × 0.7238 = $108,572 (full COL pass-through). Fair-market low = $150K × 0.7238 × 0.95 = $103,143. Fair-market high = $150K × 0.7238 × 1.15 = $124,856. Open-ask at leverage 5 = $124,856 × 1.0 = $124,856. Settle target = ($127,500 + $124,856) / 2 = $126,178.

Reading the verdict: under hub-based, the employer is offering $127,500 which is above both the fair-market high and the settle target. That’s a generous offer — the 15% floor is doing meaningful work. Under location-based, the offer drops to $108,572 which is just above fair-market low; that’s the bottom of the negotiable band. Under national, $150,000 is well above fair-market high — you’re getting full geo-arbitrage benefit, which is why national policies are rare and prized. The lesson: policy choice dominates the outcome. Negotiate to land at hub-based when location-based is on the table; negotiate to keep national when hub-based is the proposed switch.

Hub-Based vs Location-Based — Why the Spread Matters

Hub-based is the dominant policy in 2026 because it splits the difference between two extremes. National policies are too generous for employers (paying SF rates everywhere is a $50-100K annual premium per remote worker); location-based is too punishing for employees (full COL pass-through means moving to a cheaper city is functionally a pay cut for the same job). Hub-based with a 15% floor captures the middle: the employee gets a meaningful preservation bonus, the employer caps their cost exposure, and the math is defensible to both finance and HR.

The spread between hub-based and location-based is your negotiation leverage. SF → Austin under hub-based = $127,500; under location-based = $108,572. The $18,928 spread is what you’re negotiating to capture. If your employer proposes location-based, push for hub-based with the framing: “industry standard for remote moves at our peer companies is hub-based with a 15% reduction floor.” Document the policy in writing before accepting any contingent relocation offer — verbal commitments often shift to location-based at offer time when the legal team sharpens the contract language.

For international moves, hub-based becomes even more valuable because the index spreads are larger. SF (105) → Lisbon (44): location-based produces $62,857 (a 58% pay cut on the same job); hub-based with the 15% floor produces $127,500 (only a 15% cut). The $64,643 annual spread is roughly two years of mortgage in Lisbon — the difference between hub-based and location-based at large index spreads is the entire financial case for the move. If your employer won’t commit to hub-based for international moves, that’s a strong signal to walk and find a remote-friendlier employer.

Negotiation Leverage — What 1-10 Actually Means

Leverage 1-3 is “take what they offer.” You have no other offers in hand, you’re locked in by visa or family or fear, and any aggressive ask is non-credible. The open-ask is tilted down by 2-8% to reflect that your starting position is the realistic target, not the high end of the fair-market range. Use this level honestly — if you’re actually at leverage 1, opening at fair-market high will result in the employer walking, and you have no fallback.

Leverage 4-6 is the standard back-and-forth. You can ask for the high end with reasoning (“I’ve looked at Levels.fyi for this city, the market rate is X”), but you’ll probably settle near the middle after one round. The open-ask is the fair-market high, the settle target is the midpoint of employer offer + fair-high, and either party can walk if the math doesn’t close.

Leverage 7-10 unlocks the “current salary floor” on fair-market high. You have other offers in hand or you’re willing to walk. At this level, “don’t reduce my salary at all” becomes a credible ask — you’re anchoring at full preservation rather than at COL equivalence. Each step above 5 tilts the open-ask up by 2%, so leverage 10 produces an open-ask 10% above fair-market high (or 10% above current salary, whichever is greater). Use this level when you genuinely have alternatives; bluffing without alternatives leads to losing the offer entirely.

Common Mistakes

• Negotiating without documenting the policy first. Many employers verbally commit to hub-based then quietly apply location-based at offer time. Get the policy in writing — either in the original offer letter or in an HR-confirmed email — before accepting any contingent relocation. The cost of asking is zero; the cost of finding out post-signing that the policy you negotiated isn’t the policy in your contract is tens of thousands of dollars.
• Anchoring at the settle target instead of the open-ask. If you lead with the settle target, the negotiation re-centers on something between settle and the employer’s offer — and you’ve given up the upper half of the fair-market range before the conversation started. Always anchor at the open-ask. The settle target is for round two.
• Treating hub-based and location-based as the same policy. They’re not. Hub-based has a 15% floor that protects you on large index spreads; location-based has no floor and produces pure COL equivalence. The difference is small for moves between similar-cost cities (NYC → Boston) but enormous for moves between very-different-cost cities (SF → Mexico City, NYC → Karachi). Always confirm which policy applies before negotiating.
• Using your current salary as the negotiation anchor instead of the local market rate. Your employer’s policy isn’t about preserving your historical salary — it’s about paying you fair-market for the new city. Frame the ask around city-specific market data (Levels.fyi for tech, Glassdoor / Payscale for non-tech, BLS OEWS for occupational averages), not around what you used to make. The calculator’s fair-market range gives you the local benchmark.
• Bluffing leverage you don’t actually have. Setting leverage to 10 when you have no other offers in hand produces an open-ask the employer will reject — and they may walk away entirely if they suspect you’re bluffing. Honest leverage assessment is more valuable than aspirational leverage. If your real leverage is 4, anchor at fair-market high (not above) and settle for the midpoint; you’ll capture most of the available value without risking the offer.
• Forgetting that taxes can flip the “take-home” outcome. A move from California to Texas under hub-based at $127,500 can actually beat a $150,000 California salary on take-home because California’s 9.3% state tax + commute / housing differentials eat the gap. Always run take-home pay separately for both cities and compare net after-tax purchasing power, not gross salary. The remote-adjustment calculator gives you the gross negotiation target; the take-home calculator gives you the lifestyle reality.
• Ignoring international visa + employer-of-record costs. A US employer typically can’t legally pay you in Germany without a German Employer-of-Record service that adds $5-10K/yr overhead. Some employers pass that through to you (lower offer); others absorb it. Always ask explicitly: “Will the EOR overhead be deducted from my offer or absorbed by the company?” The answer materially shifts the math, sometimes by 5-10% on the gross.

Related Calculators

For the full geo-relocation picture, pair this calculator with three adjacent tools. First, run geo-arbitrageto decide whether the move is financially worth it after taxes, climate, and social cost — that’s the “move or don’t” verdict. This calculator gives you the “what salary to negotiate” script. Then run cost-of-living for the raw COL-equivalent number without policy or leverage layers — useful for ballpark sanity-checking. Layer the negotiation package shape with salary-negotiation-counter, which handles bonus / signing / equity / vesting on top of the base salary this calculator produces. Finally, run take-home payfor both current and proposed cities to surface the after-tax delta — often more material than the gross-salary delta when crossing tax jurisdictions.

How to Read the Verdict

Three numbers walk into the negotiation: the policy-implied salary (what your employer will likely offer), the fair-market band (your defensible counter-anchor), and the open-ask vs settle-for targets. Take the open-ask in; settle no lower than the fair-market floor.

• Hub-based policy + low leverage. Expect a 15-25% haircut. Walk in with the fair-market range as counter-anchor; settle for the open-ask number, not the policy default.
• National pay-band employer.Negotiate from your current salary, not the new city’s COL. National policy companies (Buffer, GitLab, 37signals) explicitly do NOT cut for relocation; the policy is your friend.
• Strategic role + high leverage.Push to same-pay or better. Hub-based formulas have exception lanes for senior IC and leadership; ask for the “senior IC override” explicitly.
• New city COL is HIGHER than current.Almost no employers raise salary for COL increases — frame instead as “market rate adjustment” tied to local hiring comparables, not COL math.