22 million Americans usually worked from home in 2023, according to the Census Bureau's own American Community Survey data, more than double the roughly 9 million who did in 2019. That's the domestic baseline an agency owner already lives inside. So when the same owner treats a Lahore-based engineer as the riskier version of a Denver-based one who works from a spare bedroom three states away, the border isn't actually what's driving that instinct. The Census numbers say remote already won at home. What's left to vet in a subcontract isn't distance. It's everything a portfolio review doesn't ask about.
What the Census data actually shows
The Census Bureau's American Community Survey found that home-based work "more than tripled between 2019 and 2021," from 5.7% of workers (about 9 million people) to 17.9% (about 28 million), a release the Bureau published under its own "Home-Based Workers and the COVID-19 Pandemic" report. By the 2023 ACS, the Bureau's own follow-up story reported the share had settled back to 13.8%, still over 22 million workers, more than double the pre-pandemic rate even after the return-to-office push that followed. That settling-back matters: this isn't a pandemic spike that fully unwound. It's a new, smaller-than-peak, still-permanent floor.
The 2021 data also breaks out which industries adopted it first and hardest. Finance, insurance and real estate hit close to 40% home-based. Professional, scientific, management and administrative services, the bucket that includes most software and agency work, cleared more than 36%. Those are the client industries an agency's own staff already sit inside, and the numbers say more than a third of the people doing that work were already doing it from somewhere the client couldn't see.
The industries that normalized this first are the ones already hiring your bench
An agency that quotes projects for finance or professional-services clients is quoting for buyers who, by the Census Bureau's own count, already let more than a third of their own workforce work unsupervised from home. That's the same trust an agency extends to a US-based contractor it has never met in person: a laptop, a Slack channel, and a deliverable schedule standing in for the daily glance across an office that stopped happening years ago. Nobody calls that arrangement risky anymore. It's just how professional services work now.
What changes when the same arrangement crosses a border isn't the working style. It's that a US-based remote hire comes with defaults an agency doesn't have to think about: enforceable IP assignment under law the agency already understands, a shared legal system if a dispute ever needs one, and a currency and banking rail that don't need explaining to a client. An offshore subcontract needs those things stated on purpose, in writing, because nothing defaults them in automatically. That's a real difference. It's a paperwork and contract-terms difference, not a some-people-can't-be-trusted-with-remote-work difference, and the two get treated as the same objection far too often.
A worked example
Picture a 14-person marketing-tech agency in Denver that already runs half its own delivery team remote, spread across four states, and has for years. The owner has never once run a background check on where an employee actually sits when they're on a call. Now a client wants a six-week integration built at a price the agency's US rate card can't hit without losing money on the job. The owner is offered a subcontract pilot with a Lahore-based partner house at a rate that makes the job profitable again, and hesitates, not because the pilot task looks weak, but because the idea of work happening somewhere the owner has never physically stood feels different from a contractor in Ohio the owner has also never physically stood next to.
The distance is identical in practice: a call, a ticket, a pull request. What actually differs is whether the agency asked the four questions that matter for an offshore arrangement specifically: is there a named, accountable lead on the other side, not a rotating account manager; is there a written IP assignment enforceable under US law; is there a contracted daily overlap window, not a vague promise of availability; and has the team proven itself on a small paid pilot before anything client-facing rides on it. None of those four questions are about where someone lives. All four are skippable with a domestic hire, because the legal and cultural defaults quietly cover them, and none of them are skippable without those defaults in place.
What actually predicts whether a subcontract engagement works
- A named lead, not a shared inbox. The person who owns the relationship should be identifiable, reachable, and the same person from the pilot through the renewal, not whoever answers first.
- IP assignment in writing, under law the client's own counsel recognizes. A verbal understanding that "of course the code belongs to you" is not a contract term, and it's the first thing a client's own legal review will ask to see.
- A contracted overlap window, stated as hours per day rather than "we're flexible," so a blocked ticket has a real window to get unblocked instead of waiting for the next calendar flip.
- A small paid pilot before anything real rides on the relationship. Judge the code, the communication, and whether the demo landed on time, before a client deadline depends on any of it.
- Disclosed staffing, stated plainly. A client who finds out later that work happened somewhere they weren't told loses more trust than one who was told upfront and decided it was fine.
Where this doesn't apply
None of this is an argument that every engagement should go offshore, and an honest list names where it doesn't fit. A scope that contractually requires work performed only by personnel in a specific location, which shows up in some public-sector and defense-adjacent contracts, isn't a vetting problem a good pilot fixes. That's a contract term, and the answer there is simply not to offer offshore staffing against that scope, not to disclose around it.
What this means for your agency
The Census Bureau's own numbers say the market you're selling into already accepted remote work as normal years ago, at scale, across the exact client industries most likely to hire an agency in the first place. The objection an owner still feels toward a subcontracted offshore bench isn't really about distance once you look at what the data already shows about domestic remote work. It's about whether the four things that don't default in automatically, a named lead, written IP assignment, a real overlap window, and a proven pilot, were ever actually put in place. Treat those four as the vetting checklist, and the border stops being the variable that decides whether the arrangement works.
We staff our own subcontract engagements against exactly that checklist, because we'd want a partner to hold us to it too: a named lead from day one, IP assignment under US law, a contracted overlap window, and a paid pilot before anything client-facing depends on it. If you're quoting a job your rate card can't hit alone, tell us the scope and we'll walk through whether a subcontract pilot makes the math work, or whether a dedicated team of your own is the better fit. Either way, the questions in our guide to vetting a global development partner and the margin math in the economics of white-label development are worth running before the next bid, not after you're already committed to one.
Sources
- U.S. Census Bureau: Home-Based Workers and the COVID-19 Pandemic (American Community Survey, 2023 press release covering 2019-2021 data)
- U.S. Census Bureau: New Data Show Detailed Characteristics of Home-Based Workers (American Community Survey, 2023 estimates, published January 2025)