The Resale Chain Nobody Shows You: How the Final Price of a Nearshore Engineer Gets Built

The price you pay for a nearshore Data or Cloud engineer through a US intermediary is rarely the provider's price plus one clean markup. It is frequently the sourcing provider's rate, marked up once to cover the intermediary's margin, and sometimes marked up again if a second layer is involved in the chain. Each layer adds cost without adding engineering capability, because the actual sourcing, vetting, and management still happens at the bottom of the chain, not at the top. NearCore's pricing model skips this stack entirely: one all-inclusive price per role, set by the company actually doing the sourcing, with no hidden intermediary margin baked in, and no other way to build it. Here is how the chain forms, and how to see it.

How a resale chain actually forms

Nearshore staffing chains form for a structural reason, not a conspiracy: a US buyer wants a single vendor relationship, a specific vendor does not have direct sourcing capacity in every LatAm market, and so it subcontracts to a provider that does. The buyer sees one contract and one invoice. What they do not see is how many margins each layer stacks between their payment and the engineer's actual compensation. Each layer in that chain typically adds its own percentage on top of the layer below it: not a flat fee, but a multiplier, which compounds the further removed the buyer is from the source. NearCore sources every one of its 10 roles directly, so there is no second layer left to stack a margin onto.

This is not unique to nearshore. It mirrors traditional staffing agency economics broadly, where contingency fees run 11-21% of annual salary and retained fees run 21-31%, except that in a resold nearshore chain, a subcontracted layer can stack that kind of margin on top of an already-discounted LatAm rate, partially erasing the savings the buyer thought they were getting.

Buyers rarely notice because the arrangement is presented as a feature: one throat to choke, one vendor scorecard, one renewal meeting. The simplification is real on the procurement side. It is the pricing side where the simplification quietly reverses, because nobody in the chain is incentivized to show you the arithmetic.

A simple illustration of how the stack compounds

Picture a Senior Data Engineer role priced at a base LatAm rate. A first-layer vendor adds a contingency-style margin somewhere in that 11-21% range to cover its own sourcing and account management. If that vendor then subcontracts to a second provider because it lacks direct sourcing capacity in the engineer's market, that second provider adds its own margin (potentially in the same 21-31% band typical of retained arrangements) on top of the first, not the original base.

Neither layer discloses its margin to the buyer as a separate line item; both fold into one quoted rate. The buyer never sees the arithmetic, only the total, which is exactly why the resale chain is hard to spot from the outside and easy to spot once you know to ask how many parties touched the price before it reached you. NearCore's quote skips both steps: one team sets one margin on the base rate, and that is the number on your invoice.

What gets lost in the stack, not just what gets added

The cost is not the only casualty. Every layer between the buyer and the sourcing provider is a layer that did not run the search, does not manage the engineer day-to-day, and is not the one accountable when something goes wrong. That distance shows up in outcomes: 57%+ of failures in distributed-team projects trace back to communication problems, not technical gaps, and a longer resale chain is, structurally, more communication hops between the buyer's requirements and the engineer doing the work.

A few things typically get diluted as a chain gets longer:

• Context about the buyer's actual architecture and business goals, re-explained at each layer.
• Accountability for a bad fit, harder to trace to a single responsible party.
• Speed, since approvals and change requests route through more intermediaries.
• Price transparency, since each layer's margin is invisible to the buyer.
• The replacement guarantee's real teeth, if it is not backed by the entity that vetted the candidate.

None of this applies inside NearCore's model, because the same team that talks to you about your architecture is the team that stays accountable for the placement afterward.

Why communication failures cluster at the top of the chain

It is worth dwelling on that 57%+ figure, because it is easy to assume communication problems are mostly about time zones or language, and for LatAm nearshore specifically, they usually are not. The more common failure mode is a requirement that three different parties re-explain, one after another, losing detail at each retelling before it ever reaches the engineer doing the work. A chain with more layers has more retellings by definition, which is a structural cause of communication breakdown that has nothing to do with the engineer's actual English proficiency or working hours. NearCore removes those retellings by design: the team that scopes your architecture with you is the same team the engineer hears the requirement from.

Where NearCore sits in this picture

NearCore is not a layer in someone else's chain. It is the sourcing provider itself, selling directly to the end client: one price per role, all-inclusive, with no hidden seniority tiers and no replacement fees, because there is no second margin to protect and no upstream vendor's pricing to justify. The price you see is the price for the actual work: understanding your business, running a genuinely selective search, and standing behind the placement.

This also explains why NearCore's savings versus onshore hiring land in a specific, moderate range (around 30-35%) rather than an implausibly steep discount. That number reflects one real margin on top of a real LatAm cost base, not a chain of markups disguised as a single number, and it is the number NearCore stands behind on every role.

Asking the right question about your own vendor

If you are currently working with a US staffing partner for Data or Cloud roles, the useful question is not what is my rate: it is how many parties are between me and the person actually running this search. A single, direct answer is a good sign. Multiple hand-offs, vague answers about who does the vetting, or an inability to name the sourcing entity are signs you are several layers removed from where the actual value is created.

If you would rather see the chain removed entirely, talk to NearCore about the Data and Cloud roles you are hiring for. We will walk you through exactly how our pricing is built, because there is no chain behind it to hide, and there never will be.