How to Build the Business Case for Nearshoring When Your CFO Only Sees the Rate Difference

Your CFO is looking at two numbers: $30 an hour and $50 an hour. Everything you say after that is noise unless you change the unit of comparison. The honest version of the nearshore argument is that it probably costs more per hour, and the case only works if cost per accepted, production-ready feature comes out lower once you count coordination, rework, compliance, delay, management, and transition.

Directory data shows why the rate gap is real. Per Offshore.dev listing data, 62.1% of the 6,658 companies with rate bounds advertise the $25 to $49/hr band. In Poland (1,324 records), the median company's band is $50 to $99/hr, and 59% of records sit in bands with a midpoint of $50 or more. Czech Republic and Costa Rica look similar. These are advertised bands, not quotes or contract rates, and they say nothing about what a project ends up costing. But the gap your CFO sees is not imaginary, so don't pretend it is.

Start with your own offshore data

Assumptions get shot down. Measurements from your current projects are much harder to argue with. Pull these from Jira, GitHub, and your time records: blocker-to-resolution time, escalations per sprint, sprint carryover percentage, reopened or rejected pull requests, and the hours your product managers, architects, and QA leads spend untangling misunderstandings.

Then convert each to dollars. Blocked time is blocked hours times affected people times blended internal cost. Twelve blockers a month, 18 hours of waiting each, four engineers, $75 an hour: that's $64,800 a month in waiting alone. Escalations: 20 a quarter, four senior people, three hours each, $100 blended, comes to $24,000 a quarter. Carryover is simpler. If a team carries 22% of a 1,000-hour quarterly commitment, that's 220 hours of delayed capacity, about $15,400 at $70 an hour.

One discipline matters here. Don't attribute all carryover or rework to communication. Split causes into requirements, dependencies, technical complexity, staffing, and vendor execution, and count only what the data supports. Also skip the often-quoted industry claim that avoidable rework eats 40 to 50% of project effort. Use your own baseline, and assume a modest improvement, say measured rework dropping from 24% to 15%, not elimination.

Build the side-by-side on accepted output

Here's an illustrative six-month project. Offshore at $30/hr, nearshore at $50/hr, 10,000 planned hours each. Offshore carries 18% coordination overhead and 24% rework; nearshore carries 10% and 15%. Compliance and security run $120,000 offshore versus $60,000 nearshore. Delay is eight weeks versus three, at $25,000 a week.

• Offshore: 14,630 adjusted hours, $438,900 labor, plus $120,000 compliance and $200,000 delay, for $758,900.
• Nearshore: 12,650 adjusted hours, $632,500 labor, plus $60,000 compliance and $75,000 delay, for $767,500.

Nearshore loses by about $8,600. Show that to your CFO. It builds more credibility than any slide claiming a clean win. The case only turns positive if you can demonstrate something more: for example, a 15% reduction in required base hours drops nearshore to roughly $672,600, an $86,300 advantage. But that 15% has to be validated through a pilot or matched historical data, not assumed.

Keep the rules tight. Compare accepted output, not raw story points across teams. Model conservative, expected, and optimistic cases. Normalize scope and definition of done. Don't count unpaid overtime as free capacity. Include transition costs: onboarding, architecture transfer, travel, vendor due diligence, ramp time. And don't double-count: if productivity is measured on accepted output, rework is already in it.

Some market analyses put offshore time-zone and language friction at a 10 to 20% productivity hit versus 5 to 10% for nearshore, and some vendor comparisons claim 30% faster delivery. Treat all of that as scenario ranges to test, not facts to import.

The compliance argument, and where it breaks

For banking, healthcare, insurance, and government work, the question isn't whether offshore engineers can access data securely. It's whether you can prove, continuously and cheaply, that access is controlled, auditable, legally permitted, and contractually governed. Cross-border transfer assessments, subprocessor reviews, segregated environments, masking, audit evidence collection, and multi-jurisdiction incident response all cost money.

Model it as recurring control cost plus probability of failure times financial impact. A defensible example: $180,000 a year in offshore-specific controls versus $95,000 nearshore, plus $75,000 of expected incremental remediation exposure, for a $160,000 annual advantage. Keep speculative fines out of the base case and put them in a sensitivity run.

The catch: "nearshore" doesn't equal compliant. The benefit exists only if the team sits in your regulatory region and legal and security confirm it simplifies the operating model. If you'd need the same controls regardless of location, they don't belong in the savings column.

The objections you should concede

Some CFO pushback is simply correct. Take the rate gap: at $50 versus $30, nearshore needs about 67% more effective output to offset labor rate alone, which is rarely credible. So the case has to rest on measurable rework, compliance, management, or time-to-market gains. Time-to-market counts only as contribution margin times weeks accelerated. A feature earning $40,000 a month in margin, launched six weeks earlier, is worth about $60,000, not the revenue figure.

Two other objections deserve straight answers. Nearshore vendors have quality problems too, so make the case conditional on acceptance criteria, turnover, test automation, and references. And "why not fix the current offshore team?" is often the best alternative. Nearshoring has to beat the best realistic offshore improvement plan (better requirements, more overlap, stronger QA, stable staffing), not a badly managed baseline.

Settle it with an 8 to 12 week pilot on a bounded product area and a pre-agreed rule: at least 10% lower cost per accepted feature, or the same scope four weeks earlier with no rise in defect escapes, or a documented compliance cost reduction. If the numbers don't clear the bar, the right call may be to stay offshore or go hybrid. A CFO who sees you willing to reach that conclusion will trust the rest of the model.

To see who's actually advertising in the regions you're considering, browse the directory, check Poland or Brazil, and use the comparison tool to shortlist vendors for a pilot.