When companies evaluate nearshore partners, the conversation follows a predictable script. What's the rate? What stacks do your engineers cover? How quickly can you get someone started?
These are reasonable questions. But they're the wrong ones to lead with because none of them predict whether the engagement will still be working six months from now.
There's one metric that does. Almost nobody asks about it.
It's talent continuity rate.
Talent continuity rate measures what percentage of the engineers working inside a nearshore model are still there after a defined period - typically 12 months.
It's harder to fake and harder to spin than rates or timelines. And it's a direct measure of something that rates and timelines can't tell you: whether the people you're counting on will still be there when you need them.
Because when an engineer leaves, the cost is not just a hiring problem. It's a delivery problem.
The engineer who has been working inside your team for four months isn't just filling a seat. They know the codebase. They know the decisions that were made and the ones that got deferred. They know which parts of the system are fragile and why. They've built working relationships with your team - the kind that make code reviews faster and architecture conversations more honest.
When they leave, all of that leaves with them. You don't just lose an engineer. You lose the accumulated context that made that engineer valuable.
And then you start again. New onboarding. New ramp-up. New uncertainty about whether this one will still be there in four months.
The instinct is to assume this is a compensation problem. Pay engineers more, keep them longer. It's a clean, transactional explanation.
It's also wrong - or at least, incomplete.
Engineers leave nearshore engagements for a different set of reasons. They leave when they feel disconnected from the work: doing tickets without understanding the product, shipping code without knowing whether it matters.
They leave when their career trajectory is unclear: no growth, no progression, no sense of where this is going.
They leave when they feel unsupported in the day-to-day: problems that don't get addressed, friction that nobody acknowledges, a quiet sense that nobody is paying attention until something breaks.
These are cultural and operational failures, not compensation failures. And they're not visible at the rate negotiation stage.
The question to ask a nearshore partner isn't "what do you pay your engineers." It's "what do you do, operationally, to keep them engaged and integrated?"
At KWAN, the answer to that question is a dedicated People Experience Partner for each engineer.
This isn't a manager. Managers handle performance and process.
A People Experience Partner does something different: they monitor integration, motivation, and alignment - continuously, not at an annual review or a quarterly check-in.
If an engineer starts showing signals of disconnection - less engagement in standups, hesitation about a client relationship, ambiguity about their next step - the PEP sees it early and acts on it. Not reactively, after the engineer has already decided to leave. Proactively, while there's still something to work with.
The practical effect is that problems get addressed before they become departures. The engineer stays engaged. The client gets continuity. The delivery doesn't restart.
The business case for continuity isn't complicated.
A high talent continuity rate means the engineer who shipped a feature in month one is still there in month six, with full context and growing investment in the product. They're not just executing tasks anymore - they're making better decisions because they understand the system. They're faster because they know the codebase. They're more valuable to your team because the relationship has had time to develop.
That compound effect is real, and it's the difference between nearshore that genuinely extends your team's capability and nearshore that keeps your team in a permanent onboarding loop.
A low talent continuity rate doesn't just cost time. It costs the compound interest on the time you've already invested.
Ask for the number. Not a range, not a benchmark, not a "we have very low churn" - the actual talent continuity rate, over the past 12 months, across active engagements.
Unlike employee retention in permanent hiring, there's no single industry-wide benchmark for talent continuity in IT staffing. The closest comparable metrics - contractor retention rate and assignment completion rate - vary significantly by model, market, and how individual partners define and measure them. Which makes the conversation with your potential partner more important than any external number.
A few things to probe when you get the figure:
How do they define the period? Continuity calculated over 6 months looks very different from continuity calculated over 18. Make sure you're comparing the same window across partners.
What's excluded? Internalizations - engineers hired directly by the client -— should not count as departures. If a partner doesn't make this distinction, their number is artificially deflated.
What happens when someone does leave? The answer tells you whether the partner has a real transition process - context preservation, structured handover, replacement coverage - or whether it becomes your problem the moment the engineer decides to go.
KWAN's talent continuity rate, excluding internalizations, is 70% over a 12-month period. We use it not as a comparison against an external benchmark, but as a measure of the delivery stability we're able to sustain for clients, and as a forcing function for the People Experience Partner model that drives it.
Rates tell you what you'll pay. Stacks tell you what the engineers can build. Talent continuity rate tells you whether the engagement will still be working when you need it most.
It's the number that predicts everything else. Ask for it.
KWAN engineers are supported by a dedicated People Experience Partner model designed to keep integration high and continuity strong. Our talent continuity rate, excluding internalizations, is 70%. If you're evaluating nearshore partners and want to understand how this works in practice talk to us →