Upwork’s revenue hit $769.3 million in 2024, up 12 percent year-over-year, with Q1 2025 bringing in $193 million—maintaining growth even as it slows. Yet in the same window, freelancers exposed to generative AI experienced a 5 percent drop in earnings and a 2 percent decline in contracts, according to research from Brookings Institution. Writing work—once a staple of freelance marketplaces—contracted 33 percent between November 2022 and February 2024. Translation declined 19–24 percent. Customer service fell 16 percent. Meanwhile, a separate analysis of 2.2 million projects found that 11 of 12 job categories on Upwork shrank year-over-year, with overall platform volume down 9 percent.
The paradox is not a paradox. The platform is capturing more value per transaction while the total addressable market for commodity contract work is collapsing. Businesses are spending 77 percent less on labor marketplaces today than they were in 2021—dropping from 0.66 percent of total vendor spend to 0.14 percent. In the same period, they increased spending on AI model providers to 2.85 percent of budget. The work that remains on platforms is not moving to premium freelancers or specialized shops. It is being absorbed by AI-augmented in-house teams that can now execute tasks previously outsourced. And for developers, the mechanism matters because it determines whether this is a temporary market dislocation or a structural floor.
The Problem
What is collapsing is not freelancing—it is the market for execution-interchangeable work below a certain price point. The floor is moving up, and it is moving fast.
Start with the direct measurement. Brookings researchers studying generative AI’s impact on online labor markets found that workers in occupations most exposed to AI tools—writing, translation, coding tasks, customer support—are losing both volume and rate. The income decline (5 percent overall, reaching 9.4 percent for the most exposed categories) is being driven by both fewer contracts and lower bids on remaining ones. Separately, analysis of Upwork’s actual job postings shows writing fell from a baseline to 67 percent of that baseline in roughly 15 months. Entry-level projects—the traditional on-ramp for building freelancer reputation and earning history—now comprise less than 9 percent of all Upwork postings, down from a far higher share before 2023.
But here is where the mechanism diverges from the common narrative. Freelancers are not getting replaced by other freelancers on the platform. Upwork itself is reporting sustained revenue growth even as client numbers contracted 7 percent year-over-year. The platform is monetizing fewer, higher-value contracts. The work that vanished—the writing, customer service tickets, basic coding tasks—is not appearing in a visible alternative market. It is not being posted to competitor platforms. It is not being listed on job boards. It is being internalized into companies’ own operations, handled by existing employees augmented with Claude, GPT-4, Copilot, or specialized tools.
Ramp’s analysis of corporate spending patterns provides the clearest evidence for this shift. Spend on labor marketplaces collapsed from 0.66 percent of total vendor budget in Q4 2021 to 0.14 percent by Q3 2025—a 77 percent contraction. In the same period, spending on AI model providers and integrated AI tools rose sharply, reaching 2.85 percent of budget. This is not theoretical. This is how companies are actually reallocating money when generative AI becomes available. The effect has been validated independently: an arXiv working paper analyzing firm-level spend patterns found the same substitution dynamic—businesses are replacing marketplace labor procurement with direct AI tooling procurement.
For a developer positioned to bid on Upwork or Fiverr, this means the economic equation has fundamentally shifted. The work available at $25–50 per hour (typical Upwork rates for commodity tasks) is now being done for a $20 monthly Claude subscription or a $200 one-time Cursor license. The client never posts the job. The employee completes it in-house.
Why This Is Happening
Three forces are converging, and they are not in conflict—they are reinforcing.
The first is substitution at the execution layer. Generative AI tools are not narrow; they work across writing, coding, customer communication, documentation, data analysis, and a hundred other tasks that made up the bulk of freelance volume. Unlike previous waves of automation that required task-specific tooling, these tools are general. A client evaluates the make-or-buy decision for a writing task and discovers that ChatGPT 4o or Claude can produce passable output in seconds for $3 per million tokens. The freelancer charging $40 per hour (or $1.33 per minute of their time) is not competing on cost—they have already lost. They are competing on judgment, reputation, and craft, which means they are competing in a category that has shrunk from commodity work to specialist work. The contract volume reflects that contraction.
The second is selection effect. As simpler work disappears from the platform, the remaining contracts skew toward higher complexity and higher budgeted projects. This raises the average contract value—which is why Upwork’s revenue can grow while client count and freelancer earnings fall. The platform is not saturated with more work at higher quality. It is saturated with less work that pays more to those who can capture it. Entry-level freelancers, who used to build skill and portfolio through low-cost gigs, now face a market with fewer entry-level posts and fiercer competition for the few that remain. The 9 percent figure for entry-level projects represents an effective exit from the on-ramp. Someone graduating a coding bootcamp looking to build Upwork credibility faces a market that has partially closed.
The third is the economic incentive reversal for companies. Outsourcing used to be cheaper than in-house hiring because you paid only for capacity when you needed it, avoided benefits and payroll overhead, and could tap global labor at lower rates. Generative AI has rewritten that equation. A $100 per month subscription to multiple AI tools is now cheaper than the delta between employing someone at $60k per year and the all-in cost of a junior contractor at $40 per hour ($83k annualized, with payment friction and vetting cost). Add to that the friction of explaining requirements, reviewing work, iterating—and suddenly the in-house + AI route is not just cheaper, it is faster and requires less coordination. The business can iterate internally and reduce its surface area of external dependency.
What makes this different from previous freelance market contractions is the lack of a visible alternative. When manufacturing moved offshore, factories opened elsewhere. When customer service centralized, call centers appeared. When design work became commoditized, lower-cost markets emerged. But AI-displaced freelance work is not moving to a cheaper labor market. It is not appearing in a new platform category. It is vanishing into in-house workflows. There is no visible supply-side adjustment because the supply no longer needs to exist.
What Developers Are Actually Doing
The practitioners who are hanging on fall into distinct adaptive categories, and the data from their forums and hiring patterns tells you something important about what the market is actually selecting for.
First group: specialization upmarket. Developers with specific domain expertise—financial modeling, healthcare compliance coding, academic research infrastructure, security-critical systems—are reporting stable or rising rates because the work cannot be safely automated or handed to a junior with a script. These are categories where the cost of error is high, where judgment matters, and where the barrier to entry is domain knowledge, not just coding ability. On r/BEFreelance and r/freelance, the consistent pattern from higher-earning practitioners is “I stopped competing on availability and price, started competing on specificity.” This is not sentimental advice; it is survival data. The work available to someone without a defensible specialization has contracted visibly.
Second group: platform internalization. Developers are increasingly building internal tools and SDKs for clients rather than completing finite projects. This is not a new phenomenon, but the economics have accelerated it. A company that used to hire contractors to build one-off features now hires a developer to build a framework that their AI-augmented team can work within. The contract is longer, the rate is higher, and the client avoids rehiring. This is a response to the substitution problem: if AI can handle the execution, companies will pay more for someone who can structure the execution layer so AI works reliably within it. It is architectural work instead of execution work.
Third group: moving off-platform. Several sources track this indirectly through job board data and Upwork’s own shrinking client base. The developers who are still active in freelancing are increasingly sourcing work through direct client relationships, referral networks, and niche communities rather than open marketplaces. This is partially a quality-of-life choice (fewer algorithmic constraints, better rates), but it is also an economic inevitability. If you are competing in a category where AI is a viable substitute, your brand and direct reputation become your actual product. The platform takes 8–18 percent of revenue for the privilege of algorithmic visibility. If you have established credibility in your niche, that tax is uncompetitive.
The unspoken adaptation at the floor of the market is retreat. Developers who were treating Upwork or Fiverr as a primary income source have been forced into a choice: go deeper into specialization (which requires a coherent build across months or years), move into in-house roles (which means accepting the stability and constraints of employment), or exit to a different income tier entirely. The Brookings data on 5 percent earnings decline represents the developers still active in the market, trying to maintain volume by lowering rates. For every person adapting upmarket, there is someone in this category—bidding lower to compete, working longer hours for the same income, or both.
The Build Opportunity
If the work is not visible, it cannot be efficiently priced or matched. This is where infrastructure becomes the actual problem.
The foundational insight is that AI-displaced work is moving from public marketplaces (where it is visible and measurable) to private procurement (where it is invisible). There is no “what are companies actually buying” layer for in-house AI-augmented teams the way there is for public freelance platforms. This creates several specific build problems:
Market segmentation and transparency: The current freelance platforms are structured as undifferentiated marketplaces. You filter by category and rate and get a pool of similar-looking bids. But the market has stratified. There is now a floor below which work cannot be economically viable (because AI is cheaper), a middle band where you are competing directly with AI tooling and losing, and a tier above where human judgment, specialization, and reputation command premium rates. None of the existing platforms have a navigation layer for this segmentation. A developer trying to understand whether they should be bidding $50, $80, or $150 per hour has no real-time feedback from the market. They are guessing. A platform or tool that explicitly surfaced market-clearing rates by specialization, complexity, and risk level would let developers price accurately instead of racing to the bottom.
Direct relationship infrastructure: The developers adapting successfully are building direct client relationships, but there is no tool designed for this at the freelance tier. There is Stripe for payments and Notion for contracts, but nothing that bundles the workflow of proposal writing, rate negotiation, scope documentation, delivery, feedback, and invoicing the way platforms do—while keeping fees and friction minimal. A lightweight infrastructure for direct contracts (think: Upwork’s workflow without Upwork’s take rate or algorithmic gatekeeping) would capture the developers who are already moving off-platform but are doing it manually right now. The build opportunity is low overhead, high transparency, and structured around specialization rather than search.
Rate discovery and competency mapping: Developers need to know what their actual market rate is in their specific specialization, geography, and experience tier. This exists for full-time employment (Levels.fyi, Salary.com) but not for contract work. A dataset and interface that tracked “senior Python with AWS expertise, B2B SaaS context, $X per hour with $Y average project size in Q4 2025” would let practitioners price rationally instead of posting, getting undercut, and lowering their bid. This requires data aggregation (difficult but not impossible—surveys, opt-in logging, API integrations with platforms that allow it), validation (filtering spam and outliers), and real-time publishing. The hard part is not the technology; it is getting enough data sources to be authoritative. But the problem is real enough that practitioners would likely participate if the infrastructure existed.
AI-augmented team assessment: For developers who are positioning themselves as the architectural layer above AI tooling, there is an unanswered question: how do you prove that you have built something that is actually structured for AI augmentation rather than just being a regular system? A certification or assessment framework—something that evaluated code structure, documentation, test coverage, and API design specifically for “can an AI augment this efficiently?”—would let developers credibly signal a key skill. This could be an open-source validation tool or a community standard. It would be most valuable if it could integrate with existing code review and hiring systems (GitHub checks, portfolio websites) so it becomes a visible signal rather than a claim.
The adjacent technical work is substantial but not novel. Rate aggregation has been done for employment and housing. Lightweight contract infrastructure exists in various forms (and the open-source contract-management space is reasonably mature). The hard problems are coordination—getting developers and platforms to share data—and authority—making the data credible enough to shift behavior. These are not problems that evaporate with more code. They require community participation and governance, which is slower but sometimes more durable.