What nearshore lean actually costs, and where the money goes

Every nearshore conversation starts with the rate card, because it is the one number that is easy to compare. It is also the number least correlated with what you will eventually spend. Two teams at the same hourly rate routinely differ by a factor of two in cost per delivered feature, and nothing on the rate card predicts which is which.

Here is a more useful way to model it.

The rate is a floor, not a price

Senior engineering rates across Europe have converged far more than the marketing suggests. Western Europe sits meaningfully above Central and Eastern Europe, but the gap is a multiple of well under two at senior level — not the four or five that offshore pitches were built on a decade ago. Anything dramatically below the regional band is buying you either juniors billed as seniors or a rotating cast.

So the rate narrows your options and then stops being informative. What actually moves the total is everything the rate does not describe.

The three multipliers that decide the bill

Rework. Code written against a misunderstanding, then written again. This is the largest single line item in most failed engagements and it never appears as a line item. It is driven almost entirely by feedback loop length — which is why timezone overlap is a cost variable, not a comfort variable. A misunderstanding caught the same afternoon costs an hour. The same misunderstanding caught next week costs the week.

Coordination overhead. Communication paths grow roughly with the square of team size. Five people have ten pairwise channels; twelve people have sixty-six. Past a certain point each additional person adds more coordination cost than delivery capacity, which is why a five-person team frequently out-delivers a twelve-person one on the same product. You are not paying twelve people to build; you are paying seven of them to stay synchronised.

Handover risk. The cost of leaving. If the repository, infrastructure and deployment pipeline are not in your name, switching supplier or bringing work in-house is a project of its own, and its price gets discovered exactly when you can least afford it. Price this at the start: it is the difference between a handover conversation and a three-month migration.

A rate card tells you what an hour costs. It tells you nothing about how many hours the same outcome will take, and that ratio is where the entire difference lives.

A model you can run in a spreadsheet

Compare suppliers on cost per delivered outcome, not per hour:

• Take one real feature from your backlog, specified identically for each supplier.
• Ask each for an estimate with assumptions written out.
• Multiply the estimate by your own rework factor guess based on loop length: same timezone, small team, direct engineer contact — assume low. Twelve-hour offset with a relay layer — assume substantially higher.
• Add the coordination tax: what fraction of the quoted team is producing versus synchronising.
• Add the exit cost: what would it take to move this elsewhere in year two.

The winner on this model is frequently not the winner on rate, and the gap is usually large enough that the rate difference stops mattering.

Where lean actually saves money

It is worth being precise about the mechanism, because "lean" is often just a word attached to a discount.

• No bench. You are not funding idle capacity between other clients' contracts.
• No account layer. Every person you pay for is producing something you can open. The coordination that remains is done by the people doing the work.
• Limited work in flight. Two finished features beat six half-finished ones, and finished features produce the feedback that stops you building the wrong third one.
• Late commitment on scope. Features specified in month one for a market you will understand differently in month four are the purest form of waste. Deciding later costs nothing and saves a great deal.
• Ownership from commit one. Removes the exit premium entirely.

What it does not save: it is not cheap per hour. Senior people working directly with you, with no juniors hidden in the blend, will not be the lowest quote you receive. The saving is in the multiplier, not the rate.

Budgeting honestly

Two practical rules we hold ourselves to and recommend regardless of who you hire.

Buy the first slice small. Two to four weeks, one real feature, deployed to your environment. You learn the actual velocity of this specific team on your specific codebase, which no estimate can tell you, and you can re-plan the rest of the budget on real numbers.

Refuse fixed prices for unfixed scope. A fixed price for a two-year roadmap is either heavily padded or a plan to bill every change. Fix the price of a bounded, well-understood slice; keep the rest on a model that lets both sides re-decide.

For how to check a supplier against these ideas, read how to evaluate a nearshore development team, and for the shortlist itself, nearshore lean software development companies in Europe, 2026. If you want a written estimate with its assumptions attached, tell us what you are building.

A free companion to this piece: our 42-point nearshore lean evaluation checklist — an eight-page PDF covering the team, the commercials, IP ownership, delivery rhythm, engineering practice and the exit. Send it to every supplier you shortlist, including us.