TRV-2026-1508Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-1508 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-15T22:03:02.486466Z status: published lens: g_space sector: labor headline: Make or buy AI? Evidence on AI sourcing decisions and workforce outcomes dek: We examine how firms acquire artificial intelligence (AI) capabilities and how their AI sourcing decisions relate to workforce outcomes. Using Swedish enterprise surveys from 2019 and 2021 linked to financial statements and employer–employee data, we directly observe whether firms adopt AI and whether they outsource AI-related activities. AI adoption is concentrated among larger firms. Among adopters, pre-existing cost pressure is associated with outsourcing. Relative to non-adopters, both in-house adopters and… gain_title: Swedish firms that adopted AI, whether building it in-house or outsourcing it, had higher subsequent employment and persistently higher shares of university-educated and CS-educated workers than non-adopters. problem_title: (none) trace_subject: (none) gain_reading: Swedish firms that adopted AI, whether building it in-house or outsourcing it, had higher subsequent employment and persistently higher shares of university-educated and CS-educated workers than non-adopters. gain_evidence: both in-house adopters and outsourcers have higher subsequent employment and persistently higher shares of university-educated and computer-science (CS)-educated workers problem_reading: (none) problem_evidence: (none) quick_read: The study uses Swedish enterprise surveys from 2019 and 2021 linked to financial statements and employer–employee records. This lets the authors observe directly which firms adopt AI and which outsource AI-related activities, then compare their later workforce outcomes with non-adopters. The findings suggest that how a firm sources AI, by building it or buying it, matters little for who it employs afterward. Adopters did better on employment and skill composition than non-adopters. The abstract does not establish whether adoption caused these differences, and it reports only a short window after adoption. limitation: The source reports associations rather than proven causal effects, and it observes workforce composition only for the year after adoption, so longer-term effects remain unknown. tag: Evidence-backed gain key_points: AI adoption is concentrated among larger firms in the Swedish data. | Among adopters, pre-existing cost pressure is associated with a choice to outsource AI activities. | Both in-house adopters and outsourcers have higher subsequent employment than non-adopters. | Adopters keep persistently higher shares of university-educated and CS-educated workers. | Workforce outcomes are statistically indistinguishable between in-house adopters and outsourcers. rundown: The data combine Swedish enterprise surveys from 2019 and 2021 with financial statements and employer–employee data. Because the surveys directly record AI adoption and outsourcing, the authors do not need to infer AI use indirectly. Adoption is concentrated among larger firms. Among those that adopt, firms already under cost pressure are more likely to outsource AI-related activities instead of developing them in-house. Relative to non-adopters, both groups of adopters show higher subsequent employment and persistently higher shares of university-educated and CS-educated workers. In the year after adoption there is no further change in workforce composition, and in-house adopters and outsourcers cannot be statistically distinguished. sources: - peer_reviewed | Applied Economics Letters | https://doi.org/10.1080/13504851.2026.2749673 | 2026-10-14 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 175661a49f87c27b3788934276b594db03e8800105fe7b1ac3428b3466e267b1
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1508 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace