The Currency Hedge: Pricing Cross-Border Work for Solo Devs

You land a client in San Francisco. The project scope is tight, the timeline is real, and the rate feels fair—$8,000 USD for three weeks of focused work. You shake on it (digitally), invoice in USD, and feel good about the deal.

Then the invoice sits unpaid for 45 days. By the time the money hits your Australian, UK, or EU bank account, the exchange rate has shifted. What was $12,000 AUD is now $11,400. That's $600 you didn't plan for—a small margin erosion that stings when you're running on a thin solo operation.

This is the currency hedge problem every cross-border freelancer faces. It's not dramatic like a market crash, but it's real, it's frequent, and it compounds. Over a year of international projects, FX swings can cost you 5–15% of projected revenue without you changing a single line of code.

The good news: you don't need a PhD in forex or a complicated hedging strategy. You need a clear pricing framework that absorbs currency risk upfront, keeps your clients happy, and turns "how much should I charge?" into a repeatable decision.

Let's build that framework together.

Why Currency Matters More Than You Think

If you're a solo developer in Australia, the UK, or Europe, the majority of your high-paying work comes from the US. That's not coincidence—it's market reality. US tech companies and startups pay 30–50% more than local equivalents, and they're willing to work with remote contractors worldwide.

But that premium comes with a catch: you're paid in USD, and you spend in local currency. That gap is your exposure.

Consider the numbers. Over the past five years, the Australian dollar has swung from 0.72 to 0.68 USD. The British pound has ranged from 1.20 to 1.35. The euro has moved from 0.95 to 1.10. These aren't tiny blips—they're 5–10% shifts that directly hit your bottom line.

Now imagine you're forecasting revenue for next quarter. You've got three projects lined up, all in USD. You project $30,000 in revenue. But if the FX rate moves 5% against you by the time invoices clear, you're actually looking at $28,500. That's not a rounding error when you're a solo operator—that's the difference between hitting your quarterly goal and falling short.

This is where most solo devs go wrong: they price in USD and hope the rate stays stable. Or they price too low to "be safe," leaving money on the table. Or they price aggressively and get blindsided by FX swings.

The real move is to price strategically from the start, building in a buffer that protects you without making your clients feel gouged.

The Two Pricing Levers: Rate and Currency

When you quote a client, you're actually making two decisions at once:

The rate: How much you charge per hour, per project, or per deliverable. This is what you and the client negotiate.

The currency: Whether you invoice in USD, AUD, GBP, EUR, or something else. This determines your FX exposure.

Most solo devs focus only on the rate and ignore the currency lever entirely. That's a missed opportunity.

Let's say a US client wants to hire you for $5,000 USD. You have three options:

Option 1: Invoice in USD, absorb the FX risk. You quote $5,000 USD, invoice in USD, and accept whatever the exchange rate is when the client pays. If you're in Australia and the AUD drops 5% against the USD, you lose $300 of purchasing power. Simple, but risky.

Option 2: Invoice in local currency at a fixed rate. You quote $5,000 USD, but you convert it to AUD/GBP/EUR at today's rate and invoice in local currency. The client pays in local currency, and you eliminate FX risk entirely. The downside: if the currency strengthens after you quote, you've left money on the table. If it weakens, you're protected but you've already baked in a buffer.

Option 3: Invoice in USD but price higher to absorb FX volatility. You quote $5,200 USD instead of $5,000 USD, invoice in USD, and accept the FX risk on the extra $200. The client pays in USD, you receive USD, and the extra 4% covers your expected FX drift over 30–60 days. You're protected, the client's rate is still competitive, and you're not left guessing.

Each option has trade-offs. The key is choosing deliberately, not by accident.

Understanding FX Volatility: How Much Buffer Do You Actually Need?

Before you can price strategically, you need to know: how much do currencies actually move?

The answer depends on your timeframe. Over a single day, FX rates might move 0.5–1%. Over a week, 1–2%. Over 30 days, 2–5%. Over a quarter, 5–10%. Over a year, 10–20%.

For solo devs, the relevant window is usually 30–60 days: the time from when you quote a project to when the invoice actually clears and hits your bank account.

Historical data from XE Currency Charts shows that USD/AUD volatility averages around 2–4% per month. USD/GBP is slightly lower (1–3% per month). USD/EUR is similar (2–4% per month). These aren't worst-case scenarios—they're normal market behavior.

So if you're quoting a $10,000 USD project and expecting payment in 45 days, a reasonable buffer is 3–5%. That means pricing at $10,300–$10,500 USD to absorb expected FX drift.

Now, you might be thinking: "But my clients will balk at a 5% premium." Here's the thing—they won't, if you frame it right. And more importantly, your clients in the US don't know what you're doing. They see a competitive rate, they see your portfolio, they say yes.

The Three Pricing Strategies for Cross-Border Work

Let's get concrete. Here are three frameworks you can use immediately, depending on your situation and client base.

Strategy 1: The Fixed USD Quote with FX Buffer

This is the simplest and most common approach. You quote in USD, invoice in USD, and bake a small FX buffer into your rate upfront.

How it works:

1. Calculate your base rate in local currency. Let's say you want to earn $80 AUD/hour.
2. Convert to USD at today's rate. At 0.65 USD/AUD, that's $52 USD/hour.
3. Add a 4% FX buffer. That's $54.08 USD/hour, which you round to $54/hour.
4. Quote the project at $54/hour (or lump-sum equivalent). Invoice in USD.
5. When the client pays, you receive USD, convert to AUD at whatever the rate is, and your actual earnings are protected by that 4% buffer.

Pros:

• Simple to execute. No currency conversion tricks or client confusion.
• Competitive. US clients see a straightforward USD rate and don't worry about FX.
• Predictable. You know your downside risk before you quote.

Cons:

• If the currency strengthens (AUD rises), you've left money on the table.
• The buffer is an estimate. In volatile markets, 4% might not be enough.
• You're still carrying some FX risk if the currency moves more than expected.

When to use it: You have a steady stream of US clients, you're comfortable with a small margin of error, and you want simplicity over optimization.

Strategy 2: The Dual-Currency Quote

With this approach, you offer clients a choice: pay in USD or pay in your local currency at a locked-in rate. This shifts some FX risk to the client but gives you optionality.

How it works:

1. Calculate your base rate in USD. Let's say $60/hour.
2. Convert to your local currency at today's rate. At 0.65 USD/AUD, that's $92.31 AUD/hour.
3. Quote both: "$60 USD/hour or $95 AUD/hour." The 3% premium on the AUD side compensates you for the FX risk of invoicing in local currency.
4. Let the client choose. US clients typically pay in USD (their home currency). Australian or UK clients might prefer local currency.
5. Invoice and receive payment in the currency the client chose.

Pros:

• Flexibility. You're not locked into one currency.
• Client-friendly. Clients see options and feel like they have control.
• Hedged. If a client chooses USD, you're protected. If they choose local, you've baked in a premium.

Cons:

• More complex to explain and track.
• Clients might always choose the cheaper option (usually USD), defeating the purpose.
• You need to update the local-currency rate regularly as FX moves.

When to use it: You work with a mix of US and local clients, you want to offer flexibility, and you're comfortable managing multiple currencies on invoices.

Strategy 3: The Monthly Rate Lock

This is the most sophisticated approach. You lock in a monthly FX rate for all projects quoted that month, protecting both you and your clients from mid-month surprises.

How it works:

1. On the first of each month, check the current USD/AUD (or your relevant pair) rate.
2. Lock in a "working rate" for the month. For example, if the spot rate is 0.65, you might use 0.63 as your working rate (adding a 3% buffer).
3. For all projects quoted in that month, use the locked rate. So $60 USD/hour becomes $95.24 AUD at your locked rate, not $92.31 at the spot rate.
4. Invoice in AUD (or your local currency) at that locked rate.
5. When payment arrives, convert at the actual FX rate and pocket the difference if the rate moved in your favor. If it moved against you, you're still protected by the buffer you baked in.

Pros:

• Predictable for both you and the client. Everyone knows the rate for the month.
• Optimized. You're not guessing at FX volatility—you're locking it in.
• Professional. Clients see that you've thought through FX risk and aren't nickel-and-diming them mid-project.

Cons:

• More administrative. You need to track and update your working rate monthly.
• Requires client buy-in. Some clients will push back on invoicing in local currency.
• If the currency strengthens significantly, you've left money on the table.

When to use it: You have a regular flow of projects, you want to minimize FX surprises, and you're willing to invest a bit of admin work for peace of mind.

Real-World Example: The $15,000 Project

Let's walk through a concrete scenario. You're a UK developer. A US client wants to hire you for a four-week project. The scope is clear, the timeline is tight, and you estimate 160 hours of work. Your target rate is £45/hour (about £7,200 total). The current USD/GBP rate is 1.27.

Here's how each strategy plays out:

Strategy 1 (Fixed USD with buffer):

• Base rate: £45/hour = $57.15 USD/hour at spot rate (1.27).
• Add 4% FX buffer: $59.44 USD/hour.
• Round to $59/hour.
• Quote: $9,440 USD for 160 hours.
• Client pays in 45 days. If the rate drops to 1.22 (a 4% move), you receive £7,734. You're protected by your buffer.
• If the rate strengthens to 1.32, you receive £7,151. You've left money on the table, but you're still close to your target.

Strategy 2 (Dual-currency):

• Base rate: $59/hour USD or £46.46/hour GBP (3% premium on the GBP side).
• Quote both options.
• If the client chooses USD, you invoice $9,440 and receive £7,434 at the spot rate (assuming 1.27). You're exposed to FX risk.
• If the client chooses GBP, you invoice £7,433.60 and receive exactly that. You're protected.

Strategy 3 (Monthly rate lock):

• Lock in a working rate of 1.23 for the month (3% buffer from spot of 1.27).
• Quote $9,635 USD (£7,835 at the locked rate).
• Client pays in 45 days. If the rate is 1.22, you receive £7,897 (you win a bit). If the rate is 1.32, you receive £7,308 (you're still protected by the buffer).

In all three cases, you're hitting close to your £7,200 target while protecting yourself from FX volatility. The strategy you choose depends on your comfort level, client expectations, and how much admin work you want to handle.

The Invoice-to-Cash Timeline: Where FX Risk Actually Lives

Here's something most solo devs don't think about: FX risk isn't constant. It concentrates at specific moments in your cash cycle.

When you quote a project (Day 0), you're exposed to FX risk for the entire period until the money clears your bank account. Let's say that's 60 days:

• Days 1–7: You're negotiating and scoping. FX risk is low because the deal isn't final.
• Days 8–14: You start work. The deal is locked in, but you haven't invoiced yet. FX risk is building.
• Days 15–45: You're working. You invoice at the end of the project (Day 45). FX risk peaks here—you're locked into a USD rate, but the client hasn't paid yet.
• Days 46–60: The invoice is outstanding. FX risk is still high. You're waiting for payment.
• Days 61+: The money clears. FX risk is gone.

The key insight: your exposure window is from when you quote to when the money clears. For most projects, that's 45–90 days.

This is why the FX buffer matters. You're not hedging against a single moment—you're protecting yourself across a 60–90 day window where currency volatility is the norm, not the exception.

If you're working with clients who pay slowly (net-60 or net-90 terms), your exposure window stretches to 120–150 days. In that case, you might want to increase your FX buffer from 4% to 5–6%.

Conversely, if you have clients who pay upfront or within net-15, your exposure window is shorter, and a 2–3% buffer might be enough.

How to Choose a Payment Platform That Minimizes FX Costs

Once you've priced your work, the next critical decision is how you actually receive payment. This is where most solo devs leave money on the table.

When a US client pays you, they have options: bank transfer, PayPal, Wise, Stripe, or a dozen other platforms. Each has different FX rates and fees.

Bank transfer: Your client's bank converts USD to your local currency at the interbank rate, then adds a 2–4% markup. You lose 2–4% right there.

PayPal: PayPal adds a 2.5% markup on top of the interbank rate. Plus, if you're receiving international payments, there's an additional 1–2% fee. Total: 3.5–4.5% gone.

Wise (formerly TransferWise): Wise uses the real interbank rate with a tiny 0.5–1.5% fee. This is the cheapest option for most currency pairs.

Stripe: Stripe's international payout fees are around 1% plus a fixed fee. Competitive, especially if you're already using Stripe for invoicing.

Here's the practical move: when you quote a client, ask them how they prefer to pay. If they say "bank transfer" or "PayPal," suggest Wise as an alternative. Frame it as "easier for both of us"—which it is. Wise is faster, cheaper, and more transparent.

If the client insists on their preferred method, factor the FX loss into your pricing. If you know PayPal will cost you 4%, add 4% to your quote. The client sees the same USD rate; you're just accounting for the real cost of receiving international payments.

According to guidance on How to Choose a Platform to Pay Freelance Contractors Across Borders, the platform you choose can save or cost you 2–5% per transaction. Over a year of projects, that's significant.

Building a Pricing Dashboard: From Guesswork to System

Once you've got a pricing strategy, the next step is to automate it. You shouldn't be recalculating FX buffers in your head every time you quote a project.

Here's what a simple pricing dashboard looks like:

Column 1: Your target hourly rate in local currency. This is non-negotiable. Let's say £50/hour.

Column 2: Today's USD exchange rate. Pull this from OANDA Currency Converter or XE Currency Charts. Update it daily or weekly.

Column 3: Your FX buffer (as a percentage). Default to 4%. Adjust based on market volatility or your payment terms.

Column 4: Your quoted USD rate. This is Column 1 converted to USD at Column 2's rate, plus Column 3's buffer. Formula: (Target Rate / Exchange Rate) × (1 + FX Buffer).

Column 5: Your lump-sum quotes for common project sizes. 40 hours, 80 hours, 160 hours, 320 hours. Multiply Column 4 by the hours.

Now, every time you get a project inquiry, you just look at the dashboard. A 160-hour project? That's Column 5's 160-hour figure. Done. No guessing, no spreadsheet fumbling, no leaving money on the table.

If you're using Cashierr to track your revenue and forecast your quarterly goals, you can feed this pricing dashboard into your revenue projections. Instead of guessing "I'll do three $10K projects this quarter," you can model "three projects at $10,200 USD each, which nets me $18,900 AUD after FX and payment fees." Now you're forecasting with real numbers, not hopes.

The Psychological Side: Why Clients Accept Higher Rates

Here's something counterintuitive: clients don't actually care about your FX buffer. They care about value.

If you quote $60/hour and deliver great work, the client is happy. If you quote $62/hour (a 3% buffer) and deliver the same great work, the client is still happy. They're not comparing your rate to other developers in Australia—they're comparing you to other developers in the US or globally.

This is backed by research on The International Price of Remote Work from Harvard Business School, which shows that remote work rates are determined by global labor market competition, not local currency considerations. A US client hiring a developer in Australia is comparing your rate to developers in Eastern Europe, India, and the US itself. They're not thinking about your FX exposure.

So here's the move: price confidently. Build in your FX buffer, your payment platform fees, your taxes, and your profit margin. Quote a rate that makes sense for the work, the client, and your business. Don't apologize for it.

The clients who balk at your rate were never going to be great clients anyway. They're optimizing for price, not quality. You want clients who optimize for results.

Pricing Across Different Project Structures

So far, we've talked mostly about hourly rates. But solo devs often work on different pricing models. Let's cover the main ones:

Hourly rates: This is what we've been discussing. Quote in USD, add a 4% FX buffer, invoice in USD. Simple and common.

Fixed project fees: You quote a lump sum for the entire project. Example: $8,000 USD for a 10-day build. Here's the move: estimate your hours (80 hours), multiply by your hourly rate with FX buffer ($62/hour × 80 = $4,960), then add a 30–50% premium for project risk, scope creep, and the fact that fixed-fee projects are harder to manage. Total: $6,400–$7,400. Round to $7,000. This is your fixed quote.

Why the premium? Because with fixed-fee projects, you're bearing the risk that the project takes longer than expected. That risk is worth 30–50% extra, especially internationally.

Retainer agreements: You charge a monthly fee for ongoing support, maintenance, or availability. Example: $3,000 USD/month for 20 hours of availability. Here's the move: quote in USD, but build in a 6% FX buffer (retainers are longer-term, so FX volatility compounds). So $3,000 becomes $3,180 USD/month. Bill monthly, and you'll have less FX exposure per billing cycle.

Value-based pricing: You charge based on the value you deliver, not the hours you work. Example: "I'll rebuild your API and it'll save you $50K/year in infrastructure costs. I'll charge $10K." This is the holy grail—no FX concerns because you're pricing based on impact, not currency. But it requires trust and a clear value story.

For more context on different pricing methodologies, The Freelancer's Smorgasbord of Pricing Methods covers the full range of approaches and when to use each one.

Common Mistakes and How to Avoid Them

Let's talk about the mistakes I see solo devs make repeatedly:

Mistake 1: Pricing too low to "be safe." You think, "I'll undercut the market a bit, and then FX won't hurt as much." Wrong. You're just giving away money. Price confidently. The FX buffer is separate from your rate.

Mistake 2: Ignoring payment platform fees. You quote $10,000 USD, but PayPal takes 4%, and you net $9,600. You didn't account for this, so you're already 4% behind. Always factor in payment fees.

Mistake 3: Locking in a quote for too long. You quote a project in January, the client approves in March, and you start work in May. By then, FX has moved 5%, and your buffer is gone. Keep quotes valid for 30 days max. After that, re-quote.

Mistake 4: Not tracking actual FX outcomes. You quote with a 4% buffer, the client pays, and you receive money at a different rate. Did you actually need the buffer? Did you lose money anyway? You don't know because you didn't track it. Start logging: quoted rate, actual rate, difference. After 10–20 projects, you'll see your real FX exposure and can adjust your buffer accordingly.

Mistake 5: Quoting in local currency for US clients. You're an Australian dev, you quote in AUD, and the client says "no thanks, too confusing." Just quote in USD. That's what the client expects.

Tying It All Together: Pricing, Forecasting, and Revenue Planning

Here's where it gets interesting. Once you've got a solid pricing strategy, you can actually forecast your revenue accurately.

Most solo devs wing it: "I'll do three projects this quarter, probably $25K USD each, so I'll make $75K USD, which is like $115K AUD." But they're not accounting for FX, payment delays, or project overruns.

Instead, use real numbers:

• Project 1: 160 hours at $62 USD/hour (with FX buffer) = $9,920 USD. Client pays net-30. Expected FX at payment: 0.67 USD/AUD. Expected AUD: $14,791.
• Project 2: 120 hours at $62 USD/hour = $7,440 USD. Client pays net-45. Expected FX: 0.66. Expected AUD: $11,273.
• Project 3: Fixed $8,000 USD. Client pays net-30. Expected FX: 0.67. Expected AUD: $11,940.

Total projected revenue: $38,004 AUD (not $115K, but realistic).

Now you can answer the two questions every solo dev secretly worries about:

1. "How much should I be making this quarter?" Based on your pricing, your available hours, and your pipeline: $38K AUD.
2. "How's the business actually doing?" You've got three projects locked in, payment terms are reasonable, and FX is accounted for. You're on track.

This is where Cashierr comes in. Instead of guessing, you can feed your real pricing, your pipeline, and your FX assumptions into a revenue forecasting tool. Cashierr's AI agents track your goals, project your revenue, and flag gaps before they hurt. You're not spreadsheet-wrestling—you're actually forecasting.

Moving Forward: Your Pricing Checklist

Let's wrap this up with a practical checklist you can use today:

Before you quote your next project:

• [ ] Know your target hourly rate in local currency (not a guess—a real number based on your cost of living, taxes, and profit goals).
• [ ] Check today's USD exchange rate on XE Currency Charts or OANDA Currency Converter.
• [ ] Decide on your FX buffer. Default to 4%. Adjust based on payment terms (longer terms = bigger buffer).
• [ ] Calculate your USD rate: (Target Rate / Exchange Rate) × (1 + FX Buffer).
• [ ] Factor in payment platform fees. If using PayPal, add 4%. If using Wise, add 1%.
• [ ] Quote confidently. Don't apologize for your rate.
• [ ] Specify payment terms (net-30, net-45, etc.) and preferred payment method (ideally Wise).
• [ ] Log the actual FX rate when you get paid. Track whether your buffer was enough.

For your quarterly revenue planning:

• [ ] List your current and pipeline projects with USD amounts and expected payment dates.
• [ ] Apply your pricing formula to each project (FX buffer + payment fees).
• [ ] Convert to AUD/GBP/EUR using realistic FX assumptions (not spot rate—use a conservative estimate).
• [ ] Total your projected revenue.
• [ ] Compare to your quarterly goal. Are you on track? Do you need more projects?
• [ ] Use Cashierr to track this automatically. Let AI agents monitor your goals and flag gaps.

The Bigger Picture: Why This Matters

Pricing cross-border work isn't just about protecting yourself from FX swings. It's about taking control of your business.

When you price strategically, you're not reacting to the market—you're planning for it. You know how much you need to earn, you know what that looks like in USD, and you know how to protect yourself when currencies move.

You stop leaving money on the table. You stop getting surprised by FX losses. You stop guessing at your quarterly revenue.

Instead, you quote with confidence, track your outcomes, and forecast your future accurately. You answer "how much should I make this quarter?" with real numbers, not hopes. You answer "how's the business actually doing?" with data, not gut feel.

That's the currency hedge. It's not fancy, it's not complicated, and it works.

Start with one project. Price it using the framework here. Track the actual FX outcome. Adjust your buffer based on what you learn. Do it again next quarter. After a few cycles, you'll have a pricing system that's tailored to your specific situation, your client base, and your risk tolerance.

And that system will be worth thousands of dollars a year in protected revenue and reduced stress.

Now go quote that next project.