The org chart shows your team. The work tells a different story: a designer billing by the day, a development shop three time zones away, a temp covering a parental leave, and an engineer in another country who feels like a full employee but is technically on a third party's payroll. That blended workforce is normal now, and it asks the leader to manage two things at once: the work, and the legal and human boundary around who is actually an employee.

The quick version

  • The contingent workforce is everyone doing your work who isn't a permanent employee, independent contractors, freelancers, gig and platform workers, temp-agency staff, and consultants. The global workforce adds people hired across borders, often via an intermediary.
  • The classic way to think about it is core and periphery: a stable core of employees you invest in, surrounded by a flexible ring you scale up and down with demand. Useful as a map, risky if "periphery" becomes a polite word for disposable.
  • Two traps do most of the damage: misclassification (treating someone as a contractor when the law says they're an employee) and permanent establishment (creating an accidental taxable presence by hiring abroad). Both surface late and cost a lot.
  • People choose flexible work for very different reasons, and that mix decides how you should lead them. Treat a free agent and a "reluctant" the same way and you'll lose both.

The idea in depth

Start with how big this actually is, because the number is smaller than the hype and larger than most payrolls admit. In the United States, the Bureau of Labor Statistics ran its long-awaited update on contingent and alternative work using a July 2023 supplement to the Current Population Survey (released November 2024). It found that 4.3% of workers, about 6.9 million people, held contingent jobs (work they don't expect to last), and separately that 11.9 million people, 7.4% of employment, were independent contractors on their main job, alongside smaller groups of on-call, temp-agency and contract-firm workers (BLS, "Contingent and Alternative Employment Arrangements," 2023). Those are conservative, main-job figures; broader counts that include side gigs run much higher, which is exactly why you should treat any single headline percentage with suspicion. The honest summary: contingent work is a meaningful and durable slice of how work gets done, not a temporary blip, and the supplementary, occasional gig is far more common than someone's sole livelihood.

Which is the case for stopping treating contingent labour as an exception you handle case by case, and starting to treat it as a category you have a deliberate strategy for. Who decides when a role is a contract versus a hire? Who owns the relationship once the contract is signed? If the answer is "whoever happened to need the help," you have a workforce by accident.

Core and periphery: the model under the practice

The most durable lens here predates the gig economy by decades. In 1984, John Atkinson described the flexible firm: a core of skilled, permanent employees the organisation invests in and cross-trains (what he called functional flexibility), surrounded by a periphery of workers it expands and contracts with demand (numerical flexibility), with pay and contract structures used to flex cost (financial flexibility). The peripheral ring, temps, contractors, outsourced and on-call staff, absorbs the shocks so the core stays stable. The model is descriptive and widely taught precisely because firms behave roughly this way whether or not they've named it (overview of Atkinson's flexible-firm model).

flowchart TB
  C(["Core
permanent, skilled
functional flexibility"]) --> P1(["Peripheral 1
full-time but lower security"])
  C --> P2(["Peripheral 2
temps, contractors,
part-time, on-call"])
  C --> P3(["External ring
outsourced, freelance,
agency, EOR-employed"])
  P2 -.->|"absorbs demand shocks"| C
  P3 -.->|"buys skills you don't keep"| C
Atkinson's flexible firm, a stable core ringed by layers that flex with demand. A map of how the work is structured, not a verdict on who matters. Leaders Loop

Be explicit, then, about what belongs in the core. Atkinson's own logic gives you the test: keep inside the things that carry your distinctive capability and that you want to compound over years; buy from the ring the things you need only occasionally, can't justify employing full-time, or genuinely don't want to own. A specialist you use four weeks a year is a textbook periphery decision. The product judgement that defines your company is not.

An honest limitation. The core–periphery model is a description, not a recommendation, and it has a well-known dark side. Critics have long pointed out that real firms often use it to push risk and insecurity onto the periphery, lower pay, no progression, no voice, while the language of "flexibility" makes that sound like neutral design. The empirical picture is also messier than the diagram: many firms never built a clean two-tier structure, and peripheral workers don't reliably convert into core ones. Use the model to decide what to keep in-house, not to justify a two-tier culture where half your workforce is treated as expendable.

The two traps that surface late: classification and country

Most of the real damage in contingent and global work comes from two boundaries leaders cross without noticing. The first is worker misclassification, labelling someone a contractor when, on the facts of how they actually work, the law treats them as an employee. The tests differ by jurisdiction (and this is genuinely regulated territory, check your own and take advice rather than rely on a generic rule), but they tend to circle the same questions: who controls how and when the work is done, how integrated the person is into your operation, and whether they really run their own business. Get it wrong and the bill is retroactive, back taxes, unpaid benefits and penalties, and it lands long after the saving was banked (Deel, on misclassification and EOR risks).

The second trap appears the moment you hire across a border: permanent establishment risk. If your activity in another country looks substantial enough, people there generating revenue, signing contracts, running operations, the tax authority may decide your business has a taxable presence locally, triggering corporate tax and reporting obligations you never planned for. This is why the employer of record (EOR) exists: a third party that legally employs the worker in their country on your behalf, handling local payroll, tax and compliance so you don't need your own entity there. It's the fastest compliant way to hire one engineer in a country you're not established in, though providers are clear it reduces, rather than automatically erases, permanent-establishment exposure (Oyster, on EORs and permanent establishment).

The savings from "just use a contractor" are visible immediately. The cost of getting the boundary wrong arrives later, with interest.

Make the classification and country call before the work starts, then, with someone who knows the rules, not after a tax authority or an aggrieved worker raises it for you. The cheapest version of this problem is the one you catch at the contracting stage.

Lead for the reason they're flexible, not against it

Here's the part leaders most often miss: contingent workers are not one group. The McKinsey Global Institute's study "Independent Work: Choice, Necessity, and the Gig Economy" (October 2016), based on a survey of around 8,000 people across Europe and the US, estimated that up to 162 million people, 20–30% of the working-age population, did some form of independent work, and sorted them into four groups: free agents who choose it and live on it, casual earners who top up income by choice, reluctants who'd rather have a traditional job, and the financially strapped who do it out of necessity. The headline finding that matters for leaders: roughly 70% were independent by choice, and those who chose it reported markedly higher satisfaction than those who didn't.

Lead each group for its actual motivation, then. A free-agent specialist wants interesting work, autonomy, and to be paid promptly and fairly. Micromanage them and they'll simply take the next contract. A reluctant contractor covering a gap wants something different: stability and a path. If you value them, the kindest and smartest thing may be to offer a real role rather than string out a series of contracts. The single worst approach is to treat the whole ring identically and assume "flexible" means "doesn't care about the work." For most of them, the research says the opposite.

And mind the line that quietly corrodes blended teams: the two-tier culture, where contractors and EOR-employed staff are excluded from the things that signal belonging, context, recognition, the all-hands, the roadmap. You can't (and for classification reasons sometimes shouldn't) treat a contractor identically to an employee. But you can make sure no one doing your work feels like a stranger to it. That's leadership, not compliance, and it's the part no intermediary will do for you.

A worked example

Take a mid-sized software company, call it Meridian, that needs to ship a data-migration feature it has no in-house expertise for, plus a back-end engineer it would love to hire but can't, because the best candidate lives in a country where Meridian has no legal entity. (Illustrative scenario; not a real company.)

Run it through the lens above. The migration work is genuinely peripheral: a specialist skill needed for one project, not a capability Meridian wants to own forever. So it goes to a contractor, but the contract is written carefully, with a defined deliverable and the contractor controlling their own methods and tools, so the classification holds up rather than looking like a disguised employee. The back-end engineer is different. This is core capability the company wants to keep and grow, and the only reason it can't simply employ her is geography. So Meridian uses an employer of record in her country: she's legally employed there, fully compliant, while doing the work and getting the belonging of any core engineer, same standups, same roadmap, same recognition.

flowchart TD
  A{"Is this a capability
we want to own
and compound?"}
  A -->|"No, one project,
specialist skill"| B(["Contractor
scoped deliverable,
their methods → classification holds"])
  A -->|"Yes, core, but
they're in another country"| C{"Do we have a
legal entity there?"}
  C -->|"No"| D(["Employer of record
compliant local employment,
full team belonging"])
  C -->|"Yes"| E(["Direct hire
onto local payroll"])
The same two questions, own-it-or-rent-it, and where are they, route most contingent and global hiring decisions. Leaders Loop

The point of the example is the order of reasoning. Meridian didn't ask "what's cheapest?", it asked "is this core or peripheral?" and "what's the compliant way to do it?" The contractor saved money and survived a classification test because the call was made deliberately. The engineer felt like a full team member and created no permanent-establishment surprise. Cheapness reversed, decide what to own first, then make it compliant, would have produced a misclassified contractor and a half-included colleague.

Frequently asked questions

What's the difference between a contingent worker, a contractor and a gig worker?

They overlap. "Contingent workforce" is the umbrella for anyone doing your work who isn't a permanent employee. An independent contractor (or freelancer) is a self-employed person you engage for defined work. A gig worker usually means someone getting short tasks through a platform. Temp-agency and contract-firm staff are contingent too, but employed by the agency, not by you. The labels matter less than one question: who is the legal employer, and have you classified the relationship correctly?

How do I avoid misclassifying a contractor as an employee?

Look at how the work actually happens, not what the contract is titled. The more you control when, where and how someone works, the more integrated they are into your operation, and the less they look like an independent business, the more likely the law treats them as an employee, regardless of the label on the agreement. The tests vary by country and even by state or province, so this is a check-your-jurisdiction-and-take-advice situation, not a do-it-from-a-blog one. The cheap fix is getting it right before the work starts.

What is an employer of record (EOR), and when do I need one?

An EOR is a company that legally employs someone in their country on your behalf, handling local payroll, tax, benefits and compliance, so you can hire there without setting up your own legal entity. It's the standard route when you want to employ one or a few people in a country where you have no presence and don't want the cost and time of incorporating. It reduces compliance and permanent-establishment risk, but it doesn't make you immune to it, and it isn't free, so it suits a handful of hires more than a whole local operation.

Are contingent workers really cheaper than employees?

Often less than it looks. The headline rate hides what you don't get: institutional knowledge that walks out the door, ramp-up time on every new engagement, management overhead, and the tail risk of misclassification penalties. Contingent labour earns its place when you genuinely need flexibility or a skill you can't justify employing, not as a blanket way to shave cost. Used as the latter, it tends to cost more once you count the things that don't appear on the invoice.

How do I keep contractors and remote global hires feeling part of the team?

Give them the context and recognition employees get, even when their legal status differs. Include them in the standups and channels where the work is actually discussed, tell them why the work matters and not just what to do, and credit their contribution publicly. Mind the classification line, a contractor genuinely shouldn't be managed identically to an employee, but belonging isn't the same as control. Most disengaged contractors aren't poorly paid; they're poorly connected to the purpose of what they're building.

Related in the Toolkit

How you bring in flexible and cross-border talent is shaped by how you present the work in the first place, your employer brand reaches contractors and global hires too, and by how rigorously you choose them, which is where a structured selection process earns its keep just as much for a six-week contractor as for a permanent hire.

Where to go next