Friday, November 20, 2026 • 08:43 AM
  • Home
  • /
  • HR Outsourcing
  • /
  • Outsource Expertise, Not Ownership: How Remote-First Companies Should Decide What to Hand Off
HR Outsourcing
Insights

Outsource Expertise, Not Ownership: How Remote-First Companies Should Decide What to Hand Off

By Charles Wong, Global Head of Human Resources, ELSA

Post Image

Many HR leaders are facing the same problem. Their workforce is spreading across more countries, but their HR team is not growing with it.

Today, 73% of leaders expect more than half of their new hires to be international by 2026, yet 87% of companies have HR teams of fewer than 10 people (Remote, 2025).

With so few people covering so much ground, many HR teams turn to outsourcing. A good partner brings expertise you don't have in-house, without adding permanent headcount.

But deciding what to hand over is harder than it looks.

Most HR leaders make that decision based on expertise and cost. Both matter, but they only tell you whether a partner can do the work today. They don't tell you whether the function will keep getting better, or what happens to everything the partner has learned about your business once the engagement ends.

I've led people functions for 15 years in private equity–backed, Fortune 500, and startup companies. Today I lead HR at ELSA, a technology company with a largely remote team across Asia, Europe, and North America. We take a selective approach to outsourcing. External partners support us in areas such as legal services, event marketing, KOL (key opinion leader) marketing, website engineering, and reliability engineering.

Our decisions depend on the nature of the work, the level of specialization it needs, and whether the capability genuinely has to be built and kept in-house. One factor I weigh heavily is context: how much someone needs to understand about our business to do the work well.

Context Is the Hidden Cost in Every Outsourcing Decision

Some capabilities are important to the business but don't warrant a full-time employee. For us, legal, compliance, and website engineering fit that description. They need specialized expertise, but the work can be clearly scoped in a well-constructed brief.

Legal work shows this well. ELSA operates across multiple jurisdictions, and requirements can vary significantly between countries, even on similar matters. A company our size can't keep deep expertise for every market in-house. So when a specific matter comes up, we bring in a local specialist who knows that jurisdiction and that issue.

That's the test I apply. If a specialist can do high-quality work without having to understand the intricacies of our business, technology, or internal processes, outsourcing becomes much more attractive. We get the expertise without the fixed cost of building every capability ourselves. More importantly, our own people can focus on functions where institutional knowledge, continuous collaboration, and long-term ownership make a real difference.

Where Outsourcing Breaks Down: Ownership, Continuity, and Incentives

Some capabilities I would be reluctant to hand over at all. For a technology company like ELSA, that means ownership of anything at the heart of our proprietary technology or critical technology stack. These capabilities are fundamental to our competitive advantage. They require deep familiarity with our systems and access to sensitive information. Adding external dependencies and continuity risks there generally doesn't make commercial sense.

Outsourcing has also been harder for us in data, core software engineering, DevOps, and performance marketing. People in these roles need to understand our technology, our proprietary data, our internal processes, and how different teams interact. In performance marketing, that extends to our target audiences, customer segments, and ideal customer profiles. Being technically competent isn't enough. People need to connect the dots across the organization to make good decisions.

Continuity is another problem. A consultant may be redeployed or move to their next engagement just as they've built the knowledge to be truly effective. The organization then has to build that context all over again.

Then there are incentives. Consultants are generally good at discrete, well-defined assignments. Operationally intensive functions need someone who spots recurring problems, challenges existing processes, and fixes the hundreds of small inefficiencies that build up over time. Those improvements are rarely glamorous, but together they have an enormous impact on how well an organization runs. When an engagement is structured around billable hours or specific outputs, there's little incentive to do that work. A full-time employee who owns the function has a much stronger reason to.

For these roles, it isn't enough to know whether someone can execute the work. What matters is whether they're embedded enough in the organization, and motivated enough, to make the whole function better over time.

Remote-First Raises the Price of Context

One of the most underestimated challenges of a globally distributed team is communication latency. People don't always appreciate how much coordination they get for free when they work in the same office or time zone.

Across time zones, that changes. A misunderstanding that a co-located team would sort out in minutes might take another 24 hours to correct. Multiply that across several teams and stakeholders, and you can end up operating at a fraction of the pace of a team in a single time zone. Research from Harvard, Rice, and Georgetown, which studied more than 12,000 employees at a large multinational, found that every extra hour of time difference between colleagues reduced real-time communication by 11%.

Language adds to the challenge. Most global teams work in English, often as a second language. Harvard Business School professor Tsedal Neeley has put it simply: "Without appropriate levels of language skills, communication and performance suffer." In a remote company, much of the context a partner or new hire needs is communicated in English. If that communication isn't clear, the context doesn't get through. I see clear English as part of the operating model, like systems and processes.

The biggest lesson I've taken from this is that organizational design is one of the most important levers for making remote-first work succeed. Being remote-first doesn't mean every function has to be spread across the globe. When closely interdependent teams sit in compatible time zones, you keep many of the benefits of remote work and cut down much of the coordination it demands.

Four Questions to Answer Before You Sign

If you're about to outsource a major function for a distributed team, I'd suggest starting with organizational design rather than the contract. The question isn't simply whether an external partner can perform the work. It's whether the operating model allows that function to perform consistently and improve over time.

  1. How much context does the function need? If the work depends on deep institutional knowledge and frequent collaboration with other teams, outsourcing is unlikely to be the most effective model.
  2. How complex are the time zones? Going from two time zones to three isn't a linear increase in complexity, especially when working hours barely overlap.
  3. How mature is the workforce? Junior employees often learn by watching experienced colleagues, which takes deliberate effort remotely. Factor that into what you outsource and how senior the people delivering it need to be.
  4. Who is accountable? Be clear about who owns the function's long-term performance and who makes sure institutional knowledge isn't lost.

The Advantage Is in the Design

I believe remote-first operating models are here to stay. They give companies access to specialized capabilities that might otherwise be unavailable or prohibitively expensive. But access to talent and effective use of talent are two very different things. Remote organizations have to be much more deliberate about how they communicate, share knowledge, and assign accountability, because weaknesses in systems, processes, and governance show up much faster when teams are dispersed. Companies will need to think harder about which capabilities they hand off, which they keep, and how they organize people around both. Many have already started: over the past five years, 70% of executives have brought some outsourced work back in-house (Deloitte, 2024).

For me, the distinction is between buying expertise to solve a problem and building internal capability to keep improving a function.

In the end, the competitive advantage won't come from being able to reach talent anywhere. It will come from designing organizations where that talent can work well together.

Charles Wong is Global Head of Human Resources at ELSA, where he leads people, culture, and organizational development across Asia, Europe, and North America. He has 15 years of experience leading HR functions in private equity–backed, Fortune 500, and startup companies across real estate, dental technology, and education technology.

  • By Charles Wong
  • 2026-11-20 12:06:46

Latest News

News Image
Press Release

Chief Nursing Officers to Conv...

By Editorial Panel, Editor, HRM O...

News Image
Press Release

PharmaMarketing Summit 2027 to...

By Editorial Panel, Editor, HRM O...

News Image
AI

Alibaba Sells Gaming Arm in $1...

By Editorial Panel, Editor, HRM O...

News Image
Workforce Solutions

Michigan’s Employee Ownership...

By Editorial Panel, Editor, HRM O...

News Image
Strategy Execution Planning

New Era Energy & Digital Stren...

By Editorial Panel, Editor, HRM O...

HRM Outlook

HRM Outlook magazine contains all the latest information about the workforce that is necessary to improve the performance of businesses. We hand over various topics, such as talent management, employment law, HR technology, recruitment, diversity, leadership, well-being, etc.