Mercor
AI Expert Marketplace With Benchmark-Software Upside — Track Until Revenue Quality And Trust Improve
Mercor is a real frontier-AI workflow franchise with credible benchmark and software upside, but the $10B mark already prices in cleaner economics, better diversification, and stronger trust than the public evidence currently proves, so the right call is TRACK.
Cover facts
Company profile
Mercor is a fast-growing private AI labor-and-evaluation company founded in January 2023 by Brendan Foody, Adarsh Hiremath, and Surya Midha. The company began with AI-assisted recruiting and has since expanded into supplying domain experts, benchmarks, and workflow infrastructure for frontier-model training, evaluation, and enterprise-agent projects. Public evidence ties Mercor to customers such as OpenAI, Anthropic, and Meta, while product pages and docs show APEX benchmarks, Enterprise AI, assessments, and RL Studio as the clearest signs of a move up the stack beyond pure marketplace volume.
- Website
- mercor.com
- Founded
- 2023-01-01
- Founders
- Brendan Foody, Adarsh Hiremath, Surya Midha
- Founding location
- San Francisco Bay Area, California, USA
- Headquarters
- San Francisco, California, USA
- Product
- Mercor combines an expert marketplace, AI interviewing and matching, contractor operations, benchmark products such as APEX, and emerging workflow software for AI labs and enterprise-agent teams.
- Customers
- Frontier AI labs and enterprises that need domain experts, benchmark design, evaluation workflows, and human-feedback infrastructure for model training and deployment.
- Business model
- Mercor appears to earn revenue from customer payments for expert work, matching or finder economics, and increasingly productized benchmark and workflow services; public sources indicate headline revenue is reported gross of contractor payouts.
- Stage
- Private (Series C, October 2025)
- Funding status
- Seed: $3.6M (2023); Series A: $30M at $250M valuation; Series B: $100M at $2B valuation; Series C: $350M at $10B valuation. Total disclosed primary capital is about $483.6M.
Executive summary
Top strengths
- Frontier-AI customer relevance is real: public reporting names OpenAI, Anthropic, and Meta, and Mercor says it serves the top five AI labs and six of the Magnificent Seven.
- Mercor has grown unusually fast, moving from a $2B mark in February 2025 to $10B in October 2025 while public sources reported major revenue acceleration.
- APEX, Enterprise AI, assessments, and RL Studio provide credible evidence that Mercor is trying to move up the stack from labor aggregation into benchmark and workflow infrastructure.
- The company's contractor operations and payout stack appear sophisticated enough to support global expert workflows at scale.
Top risks
- Revenue appears concentrated in a small number of AI labs, and public retention data are not disclosed.
- Mercor's most visible revenue numbers appear gross of contractor payouts, while net revenue, take rate, margin, and cash metrics remain undisclosed.
- The 2026 breach, paused Meta work, and class-action fallout create a trust overhang that matters directly to the valuation multiple.
- Mercor operates a complex global contractor system that can create labor, privacy, and compliance risk in addition to execution burden.
- At $10B, Mercor is priced far above public labor-platform comps and requires meaningful software-like re-rating to look attractive.
Open gaps
- Gross-to-net revenue bridge, take rate, gross margin, and any recurring software revenue split are not public.
- Top-10 customer concentration, paused-account detail after the breach, and product-level retention are not public.
- Independent evidence of post-breach trust remediation and control improvements remains limited.
- Contractor-jurisdiction mix, dispute rates, and any legal reserves for labor or privacy exposure are not public.
- Cap-table terms, preference stack, and secondary pricing mechanics at the $10B mark are not public.
Contents
01Company Overview
1.1 Identity and business model
Mercor now presents itself less as a generic hiring startup and more as an expert marketplace feeding frontier AI systems. The homepage frames the company as a platform organizing human intelligence for the AI economy, while the experts page shows the operating reality: Mercor recruits specialists such as doctors, lawyers, engineers, and finance professionals for remote contract work that advances AI systems. The product promise is speed and fit. Mercor uses AI interviewing, matching, and workflow automation to decide who should work on a project and then manages payment through the marketplace. That positioning matters because it explains both the valuation reset and the company's risk profile for investors. Mercor is no longer competing only with recruiting software or staffing agencies. It is now competing in the higher-growth but more contentious post-training, evaluation, and human-in-the-loop AI data market, where customer budgets are large, switching costs are low, and data-rights questions are sharper.[CO001, CO002, CO003, CO015, CO016]
| Metric | Value / status | Date | Confidence | Gap / notes |
|---|---|---|---|---|
| Founded | January 2023 | 2023-01 | high | Supported by official introduction post and KTVU |
| Latest stage | Profitable Series C private company | 2026-05 fetch | medium | Careers page language; no audited statements |
| Latest valuation | $10B | 2025-10 | high | Series C announcement and news corroborated |
| Total disclosed primary capital | $483.6M | 2025-10 | medium | Sum of seed, Series A, Series B, and Series C |
| Revenue run rate | ~$450M annualized | 2025-09 | medium | Investor-talk figure from TechCrunch |
| H1 2025 profit | $6M | 2025-H1 | medium | Reported by TechCrunch citing Forbes |
| Contractor roster | 30,000+ experts | 2025-10 | high | Official Series C post and CNBC corroboration |
| Daily contractor payouts | >$1.5M / day | 2025-10 | high | Official Series C post and CNBC corroboration |
Private-company figures rely on company announcements and reported investor materials; Mercor does not publish audited financial statements.
[CO004, CO010, CO011, CO012, CO021, CO022]Mercor turns expert supply, AI interviewing, matching, and project execution into model-improvement output for AI labs.
[CO002, CO003, CO015, CO016, CO023, CO026]1.2 Founders, leadership, and governance
Fetched public sources consistently identify Mercor's founding trio as Brendan Foody, Adarsh Hiremath, and Surya Midha rather than the alternate names sometimes repeated in secondary summaries. PR Newswire, KTVU, and Forbes each tie the founders to Bay Area debate networks, Harvard and Georgetown dropouts, and the Thiel Fellowship. The founder story remains central to Mercor's brand: extremely young operators who moved from dorm-room recruiting software to AI-lab infrastructure in under three years. That mythology helps fundraising, but it also raises classic key-person and maturity questions. Mercor has started to professionalize around the edges, adding former Uber executive Sundeep Jain as its first president and drawing senior hires from OpenAI and Scale. Still, the company remains strongly founder-defined, and governance visibility is limited outside selectively disclosed board participation from Benchmark and major investors.[CO005, CO006, CO007, CO031, CO032, CO033]
| Person | Role | Background | Founder-market fit / coverage | Key-person dependency |
|---|---|---|---|---|
| Brendan Foody | CEO and cofounder | Georgetown dropout; debate teammate of cofounders | Public-facing operator and primary strategic narrator | Critical |
| Adarsh Hiremath | CTO and cofounder | Harvard dropout; technical cofounder profiled by Forbes | Owns core technical and product architecture narrative | High |
| Surya Midha | Cofounder; later chairman | Georgetown dropout; former COO per Forbes profile | Operations and governance continuity | High |
| Sundeep Jain | President | Former Uber chief product officer per TechCrunch | Adds experienced executive depth beyond founding trio | Moderate |
| Victor Lazarte | Board member, Benchmark | Joined the board at Series A per PR Newswire | Investor governance and fundraising support | Moderate |
Public disclosures on Mercor governance are sparse; this table combines company and media reporting and flags role changes where later coverage differs.
[CO005, CO006, CO007, CO031, CO032, CO033]| Stakeholder | Role | Control or economic importance | Current signal | Diligence ask |
|---|---|---|---|---|
| Felicis | Lead investor in Series B and Series C | Anchors the last two priced rounds | Still leading mark-ups into Series C | Preference stack and pro rata detail |
| Benchmark | Series A backer and board seat | Early institutional governance influence | Remained invested through later rounds | Board rights and any veto provisions |
| General Catalyst | Seed backer and continuing investor | Persistent cross-round sponsor | Backed company from earliest round | Reserve strategy and follow-on capacity |
| DST Global | Series B participant | Signals crossover growth interest | Added in 2025 financing syndicate | Ownership concentration by investor |
| Menlo Ventures | Series B participant | Adds AI-market network and signaling | Stayed in syndicate after rapid valuation jump | Secondary sales or liquidity expectations |
| Robinhood Ventures | New Series C investor | Expands late-stage retail/consumer network | Entered at $10B mark | Strategic value beyond capital |
Investor roles are inferred from disclosed round participation; board and preference details are not public.
[CO013, CO014]1.3 Funding, scale, and operating footprint
Mercor's financing path is unusually steep even by 2025 AI standards. The company went from a $3.6 million seed in 2023 to a $250 million Series A valuation in 2024, then to a $2 billion Series B in February 2025 and a $10 billion Series C in October 2025. The resulting disclosed primary capital base is roughly $483.6 million. Publicly reported traction climbed alongside that capital. CNBC reported 300,000 processed candidates and more than 100,000 interviews by February 2025, while TechCrunch reported 468,000 evaluated applicants and a $75 million ARR run rate at roughly the same point. By September 2025, TechCrunch said Mercor was approaching a $450 million run-rate and had produced $6 million of first-half profit. Careers data fetched in this run also shows the company hiring aggressively across engineering, operations, finance, and enterprise roles while claiming profitability and multi-office expansion across San Francisco, New York, and London.[CO008, CO009, CO010, CO011, CO012, CO017]
| Dimension | Evidence | Date | Why it matters |
|---|---|---|---|
| Primary offices | San Francisco, New York, and London | 2026-05 fetch | Shows Mercor has expanded beyond one Bay Area office |
| Early user base | 100,000 users across 25 countries before seed financing | 2023 | Shows early cross-border labor aggregation |
| Largest talent source | India | 2025-02 | Highlights geography and workforce concentration |
| Most demanded expert segments | Software engineering, medicine, law, and banking | 2025-02 | Signals shift to high-skill domain-expert supply |
| Open roles observed | 58 | 2026-05 fetch | Indicates continued internal build-out despite claimed profitability |
Mercor does not publish audited headcount; operating-footprint signals rely on careers, official launch materials, and management interviews.
[CO006, CO018, CO029, CO030]Mercor combines exceptional growth proof with unresolved legal, security, and concentration risks.
[CO010, CO011, CO021, CO022, CO027, CO028]1.4 Milestones and adverse events
Mercor's acceleration has come with visible friction. On the positive side, the company benefited from a structural shift in the AI data supply chain after Meta's investment in Scale AI unsettled large model labs that wanted neutral vendors. That created room for Mercor to position itself as a premium expert marketplace for post-training work. Yet Mercor also encountered the same category of risks that accompany handling sensitive workflows and contractor knowledge at scale. Scale AI sued Mercor and former Scale employee Eugene Ling in September 2025, alleging trade-secret misappropriation tied to customer strategy documents. Court records show the case was later dismissed with prejudice in January 2026, which removes one litigation overhang but does not erase the underlying concern around expert knowledge leakage. More seriously for current operations, a March 2026 breach tied to LiteLLM malware triggered customer reviews; TechCrunch reported that Meta paused contracts while OpenAI investigated its exposure. Together, those episodes make information-security maturity and enterprise trust immediate diligence topics rather than distant scaling concerns.[CO023, CO024, CO026, CO027, CO028, CO034]
| Date | Event | Type | Amount / status | Participants | Implication |
|---|---|---|---|---|---|
| 2023-01 | Mercor founded from dorm rooms | founding | Company formation | Foody, Hiremath, Midha | Origin story tied to college-dropout founder mythos |
| 2023 | Seed financing | financing | $3.6M | General Catalyst and angels | Funded initial automated hiring platform |
| 2024-09 | Series A financing | financing | $30M at $250M valuation | Benchmark-led syndicate | Created first institutional board structure |
| 2025-02 | Series B financing | financing | $100M at $2B valuation | Felicis-led syndicate | Shifted market attention from recruiting to AI-lab demand |
| 2025-03 | KTVU interview on hypergrowth | scale | $100M revenue run rate; extremely profitable | Brendan Foody | Publicly framed Mercor as one of the fastest-growing companies |
| 2025-06 | Scale AI neutrality shock | partnership | OpenAI and Google pulled back from Scale per CNBC | Meta and Scale AI | Created demand-dislocation opening for Mercor |
| 2025-09 | Scale AI trade-secret suit filed | adverse | Complaint filed in N.D. Cal. | Scale AI vs. Mercor.io | Raised legal and information-governance risk |
| 2025-09 | Investor-marketing metrics reported | scale | ~$450M run-rate; $6M H1 profit | Mercor and prospective investors | Established late-2025 operating leverage narrative |
| 2025-10 | Series C financing | financing | $350M at $10B valuation | Felicis, Benchmark, GC, Robinhood | Locked in one of the fastest valuation markups in AI services |
| 2026-04 | Breach aftermath surfaces publicly | adverse | Meta pause reported; customer reviews underway | Mercor, Meta, OpenAI | Security maturity became a board-level issue |
This chronology mixes company announcements, interviews, market reports, and legal milestones; dates are event dates from fetched sources.
[CO004, CO008, CO009, CO010, CO011, CO021]02Market Analysis
2.1 Market boundary and job-to-be-done
Mercor is easiest to misunderstand when it is described as either “HR tech” or “data labeling.” Both are incomplete. The company's current market sits at the intersection of premium labor marketplaces, AI post-training services, and evaluation infrastructure. Public company pages and TechCrunch reporting show Mercor supplying domain experts—doctors, lawyers, engineers, bankers, consultants—to frontier AI labs that need judgment-heavy work such as rankings, evaluations, forms, reports, and benchmark tasks. That means Mercor is no longer selling the same product as an applicant-tracking system, a traditional staffing firm, or a commodity crowdsourcing marketplace. Its core job-to-be-done is getting scarce expert knowledge into frontier-model improvement loops quickly enough for labs and enterprises to pay for it. That narrower definition matters because it sharply reduces the true serviceable market versus top-down AI-spend headlines while also clarifying which competitors and risks actually matter.[CM001, CM002, CM003, CM004, CM005, CM025]
| Segment / category | Included spend | Excluded spend | Buyer / payer | Relevance to Mercor |
|---|---|---|---|---|
| Expert post-training services | Domain-expert RLHF, evals, ranking, red-teaming, benchmark design | Commodity microtask labeling | Frontier labs and enterprise AI teams | Core current market |
| Evaluation environments and benchmarks | Task design, harnesses, hidden test sets, workflow simulations | Generic software QA unrelated to model training | Research ops and model eval leads | Important product adjacency |
| AI talent marketplace layer | Sourcing, vetting, matching, payroll administration for experts | Traditional permanent placement agencies | AI labs and enterprises | Core Mercor operating model |
| Recruiting software and staffing SaaS | Resume screening and interview automation | Post-training project delivery | HR and talent teams | Historical entry point, now secondary |
| Broad annotation platforms | Image/text/audio labeling at scale | High-skill professional judgment work | Model builders and data-ops teams | Adjacent but lower-skill segment |
Market boundary is defined around high-skill human input into frontier-model improvement, not the entire labor or HR-tech market.
[CM001, CM002, CM003, CM004, CM005, CM025]Mercor's practical market narrows from broad AI spending to a much smaller expert post-training and evaluation niche.
[CM011, CM025, CM026, CM032, CM033, CM034]2.2 Sizing the opportunity
Public market-sizing sources offer only outer bounds. MarketsandMarkets projects a $3.6 billion data annotation and labeling market by 2027 and a $9.58 billion AI training dataset market by 2029, but both categories include far more than Mercor's premium expert niche. Stanford HAI's 2025 AI Index, summarized by IBM, shows the broader demand backdrop: corporate AI investment reached $252.3 billion in 2024, U.S. private AI investment reached $109.1 billion, and newly funded generative AI startups nearly tripled. Those figures support the claim that buyer budgets are forming rapidly, but they do not reveal how much labs spend specifically on expert contractors, benchmark creation, or workflow-rich evaluation environments. The practical conclusion is that Mercor's TAM is smaller than generic AI-investment or annotation headlines suggest, but still grows inside a much larger wave of frontier-model spending and commercialization. That mismatch between top-down spend and bottom-up serviceable budgets is one of the central diligence challenges for this company, and it should keep investors skeptical of any single gigantic TAM slide.[CM006, CM007, CM008, CM009, CM010, CM011]
| Lens | Publisher / year | Geography | Value | Growth | Methodology / limitation |
|---|---|---|---|---|---|
| Data annotation and labeling market | MarketsandMarkets / 2023 | Global | $3.6B by 2027 | 33.2% CAGR | Broad category that includes lower-skill work |
| AI training dataset market | MarketsandMarkets / 2024 | Global | $9.58B by 2029 | 27.7% CAGR | Includes software and services broader than Mercor |
| Corporate AI investment pool | Stanford HAI via IBM / 2024 | Global | $252.3B | 44.5% YoY private investment growth | Too broad to use as Mercor TAM |
| U.S. private AI investment | Stanford HAI via IBM / 2024 | United States | $109.1B | n/a | Capital signal, not spend-on-experts signal |
| Generative AI startup formation | Stanford HAI via IBM / 2024 | Global | Nearly tripled | n/a | Demand-side startup creation proxy |
| Mercor serviceable market | This report / 2026 | Global | Smaller than annotation TAM | n/a | Constrained to high-skill post-training and eval budgets; public data insufficient for exact SAM |
Public third-party market reports describe broad categories; this report uses them as outer bounds and keeps Mercor's narrower serviceable market qualitative.
[CM006, CM007, CM008, CM009, CM010, CM011]| Gap | What is public now | Why insufficient | Impact on underwriting | Exact diligence path |
|---|---|---|---|---|
| Expert post-training SAM | Outer-bound annotation and dataset TAMs only | No public slice isolates premium expert tasks | Can overstate upside if top-down TAM is used naively | Request spend by workflow and domain from buyers |
| Buyer concentration | Named labs and enterprise interest | No customer-level spend distribution | Revenue durability cannot be inferred from logos | Request customer concentration and renewal data |
| Budget ownership | Research and product leaders inferred | No public procurement map by function | Hard to model sales motion and cycle length | Interview buyers and collect org charts |
| Recurring versus project spend | One-off benchmark and eval demand visible | No public repeat-purchase rates | Limits retention and NRR analysis | Ask for program frequency and cohort retention |
| Net spend versus pass-through | Gross market and gross-revenue language common | Unknown labor pass-through ratios distort market sizing | Can misread gross throughput as net revenue opportunity | Reconcile vendor take-rates and contractor payout shares |
This table makes explicit where public market data stops and primary diligence has to begin.
[CM011, CM026, CM032, CM033, CM034]2.3 Buyer, user, payer, and adoption path
The buyer map for Mercor-like services is unusually asymmetric. The buyer is often a research operations leader, model-evals lead, or enterprise AI product owner. The user may be a post-training or benchmarking team. The payer is a model-development or enterprise transformation budget. The supply-side professional is both a labor input and the product itself, because the company is monetizing expert judgment rather than just software seats. That structure helps explain why the market can move so fast: a single lab can award meaningful spend quickly when model-quality bottlenecks become urgent. It also explains why the market can reverse just as quickly. A handful of frontier labs matter disproportionately, status-quo employers may resist sharing the workflows that make experts valuable, and enterprise buyers still force security, IP, and trust reviews before scaling programs. Mercor therefore benefits from budget urgency but still faces procurement drag and elongated proof-of-value cycles in regulated domains. That makes reference quality and trust posture unusually important competitive weapons.[CM012, CM013, CM014, CM015, CM016, CM026]
| Segment | Buyer | User | Payer | Workflow / budget owner | Adoption trigger |
|---|---|---|---|---|---|
| Frontier AI labs | Research or data-ops lead | Post-training and eval teams | Model-development budget | Need expert judgment or benchmark data | Model-quality bottleneck |
| Enterprise AI builders | Product / AI platform leader | Internal AI teams | Enterprise transformation budget | Need domain data without exposing full corpora | Deployment into regulated workflow |
| Benchmark creators | Research lead | Evaluation engineers | R&D budget | Need economically realistic test environments | Agent reliability concerns |
| Expert professionals | Independent contractor | Human trainer / evaluator | Mercor pays supply side | Monetize expertise remotely | High hourly rates and flexible work |
| Incumbent employers / data owners | Legal or operating leader | n/a | n/a | Decide whether to share data or resist disintermediation | Fear of value-chain automation |
Mercor sits between buyer budgets and expert labor supply; the buyer, user, payer, and status-quo blocker are not always the same party.
[CM012, CM013, CM014, CM015, CM016, CM031]Buyer demand starts with model-quality bottlenecks and flows through expert supply, evaluation design, and deployment trust requirements.
[CM012, CM015, CM017, CM019, CM022, CM023]Adoption moves from model bottleneck recognition to paid expert workflows, then to repeat trust-gated deployment.
[CM012, CM013, CM014, CM015, CM023, CM024]2.4 Growth drivers and adoption constraints
The strongest demand driver is technical. OpenAI's InstructGPT and Anthropic's Constitutional AI both show that alignment and model-quality improvement remain feedback-intensive, even when some of the feedback loop is automated. Mercor, Labelbox, Appen, iMerit, and CloudFactory all now market expert-centric RLHF, evaluation, and alignment services, which indicates that the market has already shifted from low-skill labeling toward higher-judgment work. Mercor also benefited from a one-off industry event: Meta's investment in Scale AI created neutrality concerns that pushed some labs to seek alternatives. But the same market has important friction. Labor-rights scrutiny, trade-secret sensitivity, and low switching costs keep buyers cautious and pricing competitive. Automation-focused substitutes such as Snorkel can also eat into the lower-value layers of human-data spend. The net result is a fast-growing market with real urgency, but not one where top-down TAM alone guarantees durable spend or easy renewal economics. In practice, buyers still need trust, security, and measurable model gains before broad rollout.[CM017, CM018, CM019, CM020, CM021, CM022]
| Driver / constraint | Direction | Timing | Implication | Diligence ask |
|---|---|---|---|---|
| Frontier models need human feedback and evaluations | Positive | Current | Supports sustained demand for expert judgment work | Quantify spend by lab and domain |
| Shift from commodity labels to experts | Positive | Current | Favors Mercor's premium positioning over low-skill marketplaces | Measure expert mix by project |
| Scale neutrality shock after Meta deal | Positive | 2025-2026 | Created switching event among large labs | Test persistence of that demand |
| Agentic AI raises benchmark complexity | Positive | Current | Increases need for workflow-rich evaluation environments | Measure repeat purchase of eval products |
| Trade-secret and IP concerns | Negative | Current | Limits how much workflow data buyers will share | Review customer contracts and redlines |
| Labor-rights scrutiny in data work | Negative | Current | Can increase compliance cost and brand risk | Assess contractor governance and geo mix |
| Low switching costs among vendors | Negative | Current | Keeps pricing pressure high | Measure contract duration and renewals |
| Automation and synthetic data substitutes | Negative | Medium-term | Can compress lower-value tasks faster than high-value tasks | Track where software replaces labor |
This table separates growth drivers from adoption constraints; several positives and negatives can be true simultaneously.
[CM017, CM018, CM019, CM020, CM021, CM022]03Competitors
3.1 Landscape structure and direct peer set
Mercor competes inside a crowded but still rapidly reshuffling human-data market. The direct peer set includes Scale AI, Surge AI, Labelbox, Appen, iMerit, CloudFactory, Invisible, Toloka, and a growing set of automation-centric substitutes such as Snorkel. These vendors do not all solve the same problem in the same way. Scale and Appen approach the market from scale and broad service breadth. Labelbox approaches it from workflow software plus an expert network. Mercor approaches it from a premium-expert marketplace that is trying to climb into benchmark and evaluation software. That distinction matters because buyers are not choosing among identical vendors. They are choosing combinations of neutrality, expert depth, workflow control, enterprise governance, and turnaround speed. Mercor therefore does not need to beat every competitor on every axis, but it does need to hold a clear edge where high-value human judgment matters most and where buyers are least willing to accept generic crowd-work.[CP001, CP002, CP003, CP004, CP005, CP006]
| Competitor | Category | Scale / funding | Target segment | Differentiation | Limitation |
|---|---|---|---|---|---|
| Mercor | Expert marketplace + post-training services | $10B valuation in 2025 | Frontier labs and expert-led enterprise work | Speed in sourcing premium experts | Still building software/workflow lock-in |
| Scale AI | Incumbent human-data infrastructure | ~$29B implied valuation after Meta deal | Large labs and enterprises | Brand scale, broad enterprise footprint | Neutrality concerns after Meta stake |
| Surge AI | Premium RLHF services | Large private rival | Frontier labs | High-skill RLHF positioning | Less public product detail |
| Labelbox | Data factory software + expert network | VC-backed software platform | Model builders and enterprise AI teams | Workflow control plus expert supply | Less marketplace-native than Mercor |
| Appen | Public human-data incumbent | Public-company results and IR | Enterprise AI and broad training data | Scale and governance breadth | Legacy crowd-work exposure |
| iMerit | Managed-service specialist | Private services vendor | High-stakes domains and model evaluation | Domain expertise depth | Lower public brand presence |
| Invisible Technologies | AI operations platform | Private adjacent rival | Enterprises needing agents + humans | Modular ops stack | Broader, less specialized positioning |
Scale or funding reflects only public figures visible in fetched sources; several private competitors do not disclose current capital or revenue.
[CP001, CP002, CP003, CP004, CP005, CP006]Mercor sits in the high-expert-depth, medium-workflow-control quadrant relative to software-first and scale-first rivals.
[CP008, CP009, CP010, CP011, CP023, CP025]3.2 Capability breadth and packaging
Capability overlap across the category is increasing. Mercor, Scale, Labelbox, and Appen now all market some combination of RLHF, evaluations, alignment, or benchmark-style services. That convergence lowers simple feature-based differentiation and pushes competition toward execution. Mercor still stands out by explicitly marketing domain-expert labor and high-skill categories, while software-centric rivals emphasize workflow tooling, data operations, and factory-like control. Packaging reinforces that divide. Public list pricing is scarce across the peer set, which means buyers usually negotiate custom enterprise deals and evaluate vendors on speed, trust, neutrality, and quality rather than headline rate cards. In practice, this makes the competitive contest less about whose website publishes a price and more about whose combination of expert supply, product control, and governance best fits a specific program. That tends to favor specialists in narrow use cases and broader incumbents in large enterprise rollouts, especially when procurement teams want references, security controls, and proven integration depth.[CP008, CP009, CP010, CP011, CP012, CP016]
| Buying criterion | Mercor | Scale AI | Labelbox | Appen | Snorkel | Invisible |
|---|---|---|---|---|---|---|
| Expert-domain marketplace | Strong | Moderate | Moderate | Moderate | Weak | Moderate |
| Workflow software / data factory | Moderate | Strong | Strong | Moderate | Strong | Strong |
| Benchmark / eval environments | Strong | Moderate | Moderate | Moderate | Weak | Moderate |
| Public governance / reporting | Weak | Weak | Weak | Strong | Weak | Weak |
| Neutrality after Meta-Scale deal | Stronger narrative | Weaker narrative | Neutral | Neutral | Neutral | Neutral |
| Automation-first substitute risk | Medium | Medium | Medium | Medium | High | Medium |
Cells are evidence-backed ordinal judgments synthesized from fetched official pages and news rather than vendor-authored comparison pages.
[CP008, CP009, CP010, CP011, CP012, CP019]| Vendor | Observed pricing model | Public transparency | Included capabilities | Implication |
|---|---|---|---|---|
| Mercor | Hourly expert work plus matching / finder economics | Low | Expert sourcing, project delivery, emerging eval software | Flexible but harder to benchmark |
| Scale AI | Custom enterprise pricing | Low | Data services, RLHF, enterprise AI systems | Sales-led incumbent motion |
| Surge AI | Custom enterprise pricing | Low | Premium RLHF and data work | Premium rival without public price anchor |
| Labelbox | Custom enterprise pricing | Low-to-moderate | Workflow software, data factory, expert network | Software-led expansion path |
| Appen | Custom enterprise pricing | Low | Broad human-data lifecycle, frontier alignment, agentic AI | Incumbent breadth can compress specialization |
| Toloka / platform crowd vendors | Platform-style task economics | Moderate relative to peers | Crowd tasks and training data | Highlights difference between marketplace depth and commodity throughput |
Public list prices are largely unavailable across the category; pricing comparison therefore focuses on packaging and transparency rather than rate-card precision.
[CP016, CP017, CP018]3.3 Switching cost, multi-homing, and distribution
The category appears structurally multi-homed. Experts can likely work across more than one marketplace, and buyers can test multiple vendors because most offerings are still sold as projects or custom programs rather than as deeply embedded system-of-record software. That weakens pure marketplace moats. At the same time, the market is shaped by episodic distribution shocks. Mercor clearly benefited when Meta's investment in Scale AI raised neutrality concerns and CNBC reported OpenAI was winding down work with Scale. But those gains can prove temporary if Mercor does not convert the demand shock into repeat workflows or harder product lock-in. Appen shows the opposite model: a public incumbent with governance breadth and a longer enterprise track record. Mercor's challenge is to keep its speed and neutrality narrative while building enough workflow ownership that buyers do not simply rotate to the next acceptable vendor when market conditions change.[CP013, CP014, CP015, CP019, CP020, CP021]
| Dimension | Current evidence | Why it matters | Diligence ask |
|---|---|---|---|
| Buyer switching cost | Appears low to medium | Labs can test multiple vendors in parallel | Request contract length and exclusivity terms |
| Expert switching cost | Low | Experts can likely work across marketplaces | Measure repeat expert utilization and exclusivity |
| Workflow lock-in | Stronger for software-centric rivals | Can shift value capture away from labor matching | Review API, data, and eval product retention |
| Installed-base advantage | Appen stronger than Mercor | Helps in enterprise procurement | Compare customer tenure and cross-sell |
| Neutrality premium | Temporary after Scale/Meta shock | May fade as market resets | Test whether buyer migration persisted in 2026 |
This table summarizes why the market is structurally multi-homed today and what evidence would show higher lock-in over time.
[CP013, CP014, CP015, CP024, CP025, CP027]3.4 Moat durability and competitive risk
Mercor's strongest competitive case is that it can source premium experts quickly and convert them into economically useful post-training workflows faster than slower or more software-centric rivals. But that is not yet a durable moat on its own. Software-first vendors such as Labelbox and Snorkel are trying to own the workflow layer where lock-in is usually created. Managed-service incumbents such as Appen and iMerit can sell governance, breadth, and established buyer relationships. Meanwhile, marketplace advantages tend to erode if experts multi-home or if matching becomes easier to automate. Mercor's move into benchmarks and evaluation environments is therefore strategically important: it is an attempt to create product-level stickiness above the labor marketplace. Investors should view the company as competitively advantaged today in some urgent buyer situations, but still racing to build a more durable right to win before the market matures and before today's neutrality tailwind fades. Until recurring product attachment is proven, the company should be treated as a strong but still transitional competitor rather than an already-defended category winner.[CP023, CP024, CP025, CP026, CP027, CP028]
| Moat claim | Threat | Severity | Mitigation / response | Residual risk |
|---|---|---|---|---|
| Premium expert supply | Experts can multi-home across vendors | High | Build repeat workflows and supply loyalty | Still high |
| Neutrality narrative | Mercor could itself become concentrated with a few labs | Medium | Diversify customer mix | Medium |
| Speed of sourcing | Software-centric rivals can embed sourcing into stronger workflow products | High | Move into eval software and benchmarks | High |
| Benchmark products | Incumbents can replicate or acquire similar eval assets | Medium | Differentiate on economically realistic tasks | Medium |
| Young-company agility | Public incumbents can win enterprise trust on governance | Medium | Professionalize leadership and controls | Medium |
| Marketplace economics | Automation substitutes can compress lower-value task layers | High | Stay focused on expert judgment not rote labeling | High |
| Scale disruption tailwind | Scale may recover customer trust over time | Medium | Lock in buyers before neutrality advantage fades | Medium |
| Brand momentum | Mercor remains smaller than Scale and possibly Surge | Medium | Capitalize on current growth window | Medium |
Risk ratings reflect competitive durability rather than legal or security risk, which is covered later in the report.
[CP019, CP020, CP021, CP022, CP023, CP024]Mercor scores well on expert-supply speed and current neutrality narrative, but weaker on public governance and software lock-in.
[CP013, CP019, CP020, CP023, CP024, CP025]04Financials
4.1 Revenue model and revenue quality
Mercor's public financial story is impressive but structurally easy to misread. The business is not a classic SaaS model with clean seat-based subscription revenue. Public reporting and Mercor's own docs instead describe a marketplace-and-services model: customers pay Mercor to source, vet, and coordinate domain experts for AI model training, evaluations, and related workflow design, and Mercor then pays those experts through its own payout stack. That distinction matters because Mercor's fastest-growing headline numbers appear to include gross customer billings before contractor payouts. TechCrunch explicitly reported that Mercor counts the total amount customers pay before experts receive their portion. That accounting choice may be common in this category, but it means investors need to separate throughput from net economics before treating headline run-rate figures like software revenue. Public worker-side pricing signals and reported hourly fee mechanics suggest real monetization power, yet the exact take rate and realized discounting remain undisclosed.[CI001, CI002, CI003, CI004, CI018, CI019]
| Revenue stream | Mechanism | Unit / denominator | Current value / status | Quality / margin read | Diligence ask |
|---|---|---|---|---|---|
| Expert marketplace work | Client buys access to domain experts for model training and evaluation | Hours or project scopes | Core current stream | Likely healthy demand but labor pass-through heavy | Break out gross billings, expert payouts, and Mercor take rate by workflow |
| Matching / finder economics | Mercor layers a finder or matching rate onto expert work | Hourly spread / placement fee | Publicly reported by TechCrunch | Shows monetization beyond pure payroll processing | Provide standard contract templates and realized fee schedules |
| Benchmark and evaluation services | Mercor sells benchmark design, eval environments, and related data work | Project or program fee | Growing strategic layer | Potentially better margin than pure staffing if reusable assets attach | Disclose attach rate of benchmarks to marketplace work |
| Enterprise AI workflow design | Mercor is expanding into enterprise agent and workflow products | Program fee or software-enabled services | Emerging | Could improve mix if less labor-intensive | Show recurring revenue and software/services split |
| Gross contractor throughput | Customers pay Mercor a gross amount before expert payouts | Gross billings | Material to headline revenue | Can inflate scale optics if mistaken for net revenue | Reconcile billings, payouts, net revenue, and deferred revenue |
| Payout operations | Mercor administers weekly payouts through Stripe and sometimes Wise | Payment rail / transaction flow | Operational backbone | Necessary but potentially fee-bearing and compliance-heavy | Quantify payment costs, failures, and payout float exposure |
Rows separate what public sources say Mercor sells from what underwriters still need to model gross-to-net economics accurately.
[CI001, CI002, CI003, CI004, CI018, CI019]| Signal | Price / unit | List vs realized | What it implies | Unknowns |
|---|---|---|---|---|
| Finder / matching economics | Hourly finder's fee plus matching rate | Realized economics reported by TechCrunch, not list pricing | Mercor likely earns a spread rather than flat SaaS seats | Exact take-rate ladder by customer, domain, or contract type |
| Top expert upside | Up to $200 per hour | Realized third-party-reported example | Premium domains can support high-value projects | How often these rates occur and what gross margin they leave |
| Finance / IR expert listings | $80-$160 per hour | Observed marketplace signal | Shows higher-skill knowledge-work positioning | Whether client bill rates are materially above worker rates |
| Equity research expert listings | $120 per hour | Observed marketplace signal | Supports finance-domain demand from AI buyers | Whether this reflects representative or promotional pricing |
| Payout onboarding | First Stripe payment held for seven days; bank account and SMS 2FA required | Operational policy | Adds friction and support workload to payout operations | Actual payout-failure rate and support cost per contractor |
Public pricing evidence is sparse and mostly worker-facing or management-reported; realized customer pricing remains a diligence item.
[CI003, CI004, CI020, CI021, CI022, CI038]Mercor appears to convert concentrated AI-lab demand into gross billings, expert payouts, and a smaller net revenue layer that is not publicly broken out.
[CI001, CI002, CI003, CI004, CI016, CI018]4.2 Unit economics and operating leverage
Mercor's growth arc is unusually steep. Public sources move from a $75 million run rate and reported profitability in February 2025 to roughly $450 million annualized revenue by September 2025, then to Mercor's own 2026 claim of having crossed $1 billion in annualized revenue earlier that year. KTVU separately quoted Brendan Foody saying the company crossed a $100 million revenue run rate by March 2025 and was extremely profitable. Those data points create a plausible operating-leverage story, especially because TechCrunch also reported $6 million of first-half 2025 profit. But the same evidence points to a heavy pass-through labor base rather than a purely software-like margin structure. Daily contractor payouts rose from more than $1.5 million in late 2025 to over $2 million in Mercor's 2026 post, while internal posts describe payments, contract systems, and control upgrades as critical scaling work. The result is encouraging top-line proof without the public gross-margin, take-rate, or cash-conversion detail needed to convert momentum into a fully underwritten model.[CI009, CI010, CI011, CI012, CI013, CI014]
| Metric | Public value / status | Confidence | Why it matters | Diligence ask |
|---|---|---|---|---|
| Feb 2025 ARR / run rate | $75M+ | Medium | Earliest public scale anchor after Series B | Provide monthly recurring and non-recurring revenue bridge |
| Sep 2025 annualized run rate | ~$450M | Medium | Shows extreme top-line acceleration within one year | Provide monthly revenue series and cohort decomposition |
| Early-2026 annualized run rate | $1B+ company-claimed | Medium | Suggests continued hypergrowth after Series C | Reconcile 2026 run-rate methodology to audited or reviewed figures |
| H1 2025 profit | $6M third-party-reported | Medium | Rare sign of operating leverage for a contractor-heavy model | Provide income statement with gross profit, opex, and cash flow |
| Daily contractor payouts | $1.5M+ in Oct 2025; $2M+ in 2026 post | Medium | Pass-through labor spend is central to cash conversion and controls | Provide payout volume, fee burden, chargebacks, and reserve policy |
| Take rate / gross margin | Not publicly disclosed | Low | Core variable for underwriting revenue quality | Disclose bill rates, worker rates, payment costs, and margin by program |
This table mixes corroborated figures with explicitly missing variables so underwriters can see where public evidence stops.
[CI009, CI010, CI011, CI012, CI013, CI015]Public evidence shows extraordinary growth and payout scale, but the bridge from gross throughput to net margin still has missing middle steps.
[CI009, CI010, CI011, CI012, CI015, CI016]Public financial signals establish point estimates for growth and payout scale, while the missing cash and margin data remain the real range problem.
[CI009, CI010, CI011, CI015, CI016, CI017]4.3 Capital adequacy and financing dependency
Mercor does not look capital-starved on the surface. The company disclosed roughly $483.6 million of primary capital across seed, Series A, Series B, and Series C, culminating in a $350 million Series C at a $10 billion valuation in October 2025. Management also gave unusually concrete use-of-funds language: grow the talent network, improve matching, and speed delivery. Those priorities are sensible for a company simultaneously trying to defend marketplace liquidity and build more productized evaluation capabilities. The problem is that disclosed financing history is not the same as disclosed liquidity. Mercor does not publish cash on hand, monthly burn, runway months, or any debt schedule in the sources reviewed for this chapter. That omission matters because the company now carries real downside sensitivity to customer concentration, legal and breach remediation costs, and the internal-control investment required by hypergrowth. The funding chronology is therefore strong evidence of access to capital, but it is still not enough to conclude runway is safe under stress.[CI005, CI006, CI007, CI008, CI024, CI025]
| Field | Public value / status | Source / timing | Implication | Gap or next ask |
|---|---|---|---|---|
| Disclosed primary capital | $483.6M total across seed, Series A, B, and C | 2023-2025 public financing announcements | Mercor has raised enough equity to fund aggressive internal build-out | Need cap table, preference stack, and any secondaries |
| Latest priced round | $350M Series C at $10B valuation | Oct 2025 | Late-stage equity materially reduced immediate financing pressure | Need cash proceeds net of fees and any investor rights |
| Use of proceeds | Talent network, matching, faster delivery, broader capability build | Series B and Series C posts | Capital appears earmarked for both supply and product layers | Request actual post-close budget allocation |
| Cash on hand | Not publicly disclosed | n/a | Cannot test runway despite large round sizes | Request latest balance sheet and liquidity schedule |
| Monthly burn | Not publicly disclosed | n/a | Impossible to convert valuation and fundraising into runway | Request cash burn by month and planned hiring spend |
| Debt / project finance obligations | No public debt or facility disclosed in fetched sources | n/a | Positive on surface, but not enough to rule out obligations | Request debt schedule, vendor financing, and contingent liabilities |
| Next-round trigger | Likely tied more to growth, trust, and concentration shocks than nominal cash scarcity | Inferred from rapid scale and breach risk | Large private raises do not remove need for contingency planning | Model downside case where customer reviews slow growth or margin |
Mercor's public fundraising story is strong, but public liquidity data remains too sparse to underwrite runway from announcements alone.
[CI005, CI006, CI007, CI008, CI024, CI025]Mercor has ample disclosed equity financing, but future capital needs still hinge on trust, concentration, and the missing cash-conversion data.
[CI003, CI004, CI005, CI006, CI007, CI008]4.4 Adverse signals and underwriting blockers
The biggest open issue in Mercor's financial chapter is not whether the company can raise money; it is whether investors can convert the public growth narrative into a trustworthy revenue-quality view. TechCrunch said a subset of big brands accounts for an outsized share of revenue, and the Scale AI litigation described single customer opportunities worth millions of dollars. That combination implies large-account upside but also concentration exposure. The April 2026 breach adds another financial risk layer because TechCrunch reported Meta paused contracts and other model makers were reviewing relationships, even as five contractors pursued lawsuits over alleged data exposure. Category volatility also remains real: CNBC reported Scale AI cut 14% of its workforce while trying to win back customers after the Meta deal. Public incumbent disclosures from Appen show what Mercor does not yet provide: regular results, clearer service segmentation, and more transparent reporting. Until Mercor discloses cash, burn, take rate, margin, and concentration metrics, underwriting should treat the company as financially exceptional but still partially opaque.[CI017, CI018, CI026, CI027, CI028, CI029]
| Missing metric | What public sources say instead | Why insufficient | Impact on underwriting | Exact diligence path |
|---|---|---|---|---|
| Cash balance and short-term liquidity | Large rounds and profitability anecdotes | Round size does not equal cash remaining | Runway cannot be tested | Request latest cash balance, restricted cash, and forecast |
| Monthly burn and operating cash flow | Profit and run-rate snippets only | Accounting profit does not reveal cash conversion | Downside planning remains speculative | Request monthly P&L plus cash-flow statement |
| Net take rate by workflow | Gross revenue and payout figures | Need to separate throughput from net economics | Valuation multiple selection can be distorted | Request gross billings, expert payouts, and Mercor net revenue by program |
| Gross margin by domain and customer type | Expert hourly examples and payout scale only | No view on contribution margin after labor and payment costs | Cannot compare Mercor to software or services peers cleanly | Request margin bridge by use case |
| Customer concentration and contract duration | Subset-brand concentration reported qualitatively | No denominator or renewal data | Revenue quality and durability remain open | Request top-10 customer share, contract length, and cohort retention |
| Breach and compliance downside cost | Paused Meta work and contractor suits reported | No reserve or remediation-cost disclosure | Could change burn and financing needs materially | Request incident cost estimate, legal reserves, and remediation budget |
These are the minimum missing inputs that block a clean underwriting model even though the growth narrative is unusually strong.
[CI017, CI018, CI026, CI027, CI030, CI033]05Product & Technology
5.1 Product surface and customer workflow
Mercor's product is broader than the label “AI recruiting startup” suggests. The current public surface combines an expert marketplace, an AI interviewing and matching system, benchmark products, and an emerging enterprise workflow-design offering. Mercor's research pages emphasize benchmarks, evaluation environments, and large-scale human datasets, while the experts page shows the operating substrate underneath: a globally distributed pool of professionals who can be interviewed, matched, managed, and paid for work that improves AI systems. The company's Enterprise AI post pushes the product surface one step further, arguing that the bottleneck in enterprise agents is not only model intelligence but also the lack of evidence-backed workflow design. That framing turns Mercor from a staffing intermediary into a provider of workflow capture, expert judgment, and evaluation infrastructure. The customer buys a coordinated operating system for high-skill human feedback, benchmark reuse, and eventually recurring enterprise workflow systems rather than a single standalone feature.[CE001, CE002, CE003, CE009, CE016, CE020]
| Module / asset | Primary user | Status / maturity | Differentiation | Diligence gap |
|---|---|---|---|---|
| Expert marketplace | AI labs and enterprises needing domain specialists | Core / live | Large roster of professionals across high-skill domains | Need active expert counts by domain and repeat utilization |
| AI interviewer (Monty) | Candidates and internal ops teams | Scaled / live | Automated interviews at large volume with role-specific context | Need objective interview-quality and false-negative metrics |
| Matching and offer engine | Mercor ops and hiring teams | Core / live | Pairs profiles, interviews, assessments, and availability to roles | Need precision or conversion metrics by segment |
| APEX benchmark family | AI labs and model-eval teams | Live / expanding | Economically realistic benchmarks across professional, consumer, and SWE work | Need attach rate from benchmark visibility to paid workflow |
| Enterprise AI / agent design | Enterprise transformation teams | Emerging / early commercial | Moves beyond labor supply toward workflow codification and agent deployment | Need named customer deployments and repeat usage metrics |
| Contracts / payouts infrastructure | Mercor finance and operations | Critical internal platform | Complex billing and global contractor payout management are core to delivery | Need failure-rate, recovery-time, and controls evidence |
| Trust and compliance layer | Customers, contractors, Mercor risk teams | Operational but not fully disclosed | Background checks, LLM-use rules, time tracking, and data policies are explicit | Need public certifications, trust-center depth, and incident metrics |
This matrix treats internal delivery systems as product-critical because Mercor sells coordinated expert workflows, not just a static software seat.
[CE001, CE003, CE005, CE006, CE009, CE010]| User job | Current workflow | Mercor solution | Measurable benefit | Limitation |
|---|---|---|---|---|
| Recruit or qualify expert workers | Search, screen, interview, and verify specialists manually | Mercor marketplace plus AI interviewer and matching | Faster expert onboarding and filtering at scale | Exact conversion rates are not public |
| Train or evaluate frontier models | Collect preference data, benchmarks, and domain judgments | Mercor experts plus benchmark assets and eval environments | Higher-skill feedback than commodity labeling | Needs proof of recurring product attachment |
| Benchmark agent performance | Assemble bespoke test tasks and rubrics internally | APEX, APEX-Agents, and APEX-SWE provide reusable evaluation assets | Improves comparability across models and tasks | Public benchmarks do not equal paid customer adoption |
| Operationalize enterprise agents | Guess workflows, prompts, and tool calls by hand | Mercor Enterprise AI proposes workflow discovery and codification | Can reduce use-case guesswork | Public documentation remains high-level |
| Run global contractor programs | Invoice customers, track hours, and pay workers across jurisdictions | Contracts, payments docs, and time tracking tools support delivery | Enables labor coordination at large scale | Public SLA, error-rate, and audit data remain sparse |
| Protect customer trust | Vet workers and constrain unsafe model-evaluation behavior | Background checks, LLM rules, and data-use policies formalize controls | Raises baseline trust posture for sensitive workflows | No public certification depth or full trust-center detail |
Benefits are described from the fetched workflow evidence; unsupported performance claims remain explicitly constrained as diligence gaps.
[CE003, CE020, CE022, CE025, CE027, CE028]Mercor turns expert supply and internal orchestration into benchmark, evaluation, and enterprise-agent outputs for customers.
[CE001, CE003, CE005, CE007, CE009, CE010]5.2 Architecture and operating model
Mercor's most revealing product evidence comes from its engineering posts rather than its homepage. The Monty interviewer write-up describes a live operational system that runs roughly 10,000 conversations a day, with each session isolated in its own Modal container and launched from a warm pool that keeps start times under 200 milliseconds. The Contracts-service rewrite shows a separate but equally important architecture truth: internal delivery systems matter as much as user-facing AI. Mercor publicly described rewriting a bottlenecked service in a week, improving capability by over 10,000x and reliability by more than 75x because prior contract volume and latency assumptions were breaking under growth. That makes the architecture more operational than purely model-centric. Mercor depends on internal orchestration, billing, payouts, and worker-management systems that tie software, human labor, and customer trust together. In practice, its product stack is a human-data operating system, not just a matching algorithm.[CE005, CE006, CE022, CE023, CE024, CE025]
| Layer / component | Role | Dependency | Risk |
|---|---|---|---|
| Profile and interview ingestion | Transforms resumes, interviews, and public profiles into searchable candidate signals | Mercor data pipelines and AI parsing | Data quality and privacy sensitivity |
| AI interviewing runtime | Runs live interview sessions for candidates | Modal containers, warm pools, and room setup state | Cold starts, session reliability, and infrastructure dependency |
| Matching and contract orchestration | Routes talent to listings and manages offers or contract state | Core internal services including Contracts | Scaling bugs can block delivery and payouts |
| Benchmark and eval asset pipeline | Builds APEX datasets, leaderboards, rubrics, and evaluation environments | Mercor research team plus expert contributors | Benchmark contamination, low external adoption, or expensive refresh cycles |
| Enterprise agent workflow layer | Maps real work into agent tasks, prompts, tool calls, and eval loops | Mercor Enterprise AI and customer workflow discovery | Public docs do not yet show deep integration or API evidence |
| Operations and payout layer | Tracks time, invoices clients, and pays contractors globally | Stripe, Wise, Insightful/Workpuls, finance controls | Payment failures, fraud, and jurisdictional compliance |
| Trust and policy controls | Background checks, LLM-use rules, and data governance constrain behavior | Mercor docs and internal review processes | Sparse public evidence on certifications or enforcement maturity |
Because Mercor sells outcome-oriented expert workflows, architecture includes both software systems and human-operations control layers.
[CE005, CE006, CE022, CE023, CE024, CE025]Mercor's product stack layers expert supply, evaluation assets, internal orchestration, and trust controls into one delivery system.
[CE003, CE005, CE006, CE009, CE010, CE011]Mercor depends on external model progress, expert supply, benchmark credibility, payment rails, and trust posture all at once.
[CE001, CE003, CE009, CE010, CE011, CE018]5.3 Benchmarks, evaluation assets, and differentiation
Mercor's clearest attempt at product differentiation is the APEX family. APEX, APEX-Agents, and APEX-SWE are not generic blog marketing; they are reusable benchmark assets intended to move Mercor up the stack from labor marketplace to evaluation infrastructure. The product logic is visible in the methodology. Mercor says APEX-Agents was informed by surveys of hundreds of professionals and that APEX-SWE uses human-authored rubrics across integration and observability tasks rather than unit-style toy problems. The expanded APEX post also shows a willingness to refresh methodology by doubling the heldout set and publishing more detail on confidence intervals and task duration. This matters strategically because competitor sites from Appen, Scale, Toloka, and iMerit show the market already converging on expert RLHF, agentic workflows, and evaluation services. Mercor therefore needs benchmark realism and workflow depth to be more than thought leadership; these assets are its best public case for product stickiness above raw labor aggregation.[CE009, CE010, CE011, CE012, CE013, CE014]
| Date / stage | Feature or milestone | Status | Implication | Source |
|---|---|---|---|---|
| 2025-02 | Series B operating narrative | Live | Publicly tied product build to growth and senior operating hires | Series B post |
| 2025-10 | Series C focus on matching and faster delivery | Live | Suggests continued investment in workflow speed rather than pure headcount | Series C post and CNBC |
| 2026-03 | APEX-SWE launch | Released | Mercor is productizing research into software-engineering eval assets | APEX-SWE post |
| 2026 | APEX-Agents expansion | Released | Broadens benchmark scope from static tasks to long-horizon agent work | APEX-Agents post |
| 2026 | Expanded APEX heldout set | Released | Shows Mercor iterating evaluation methodology rather than freezing a one-off benchmark | Expanded APEX post |
| 2026 | Enterprise AI workflow product | Emerging | Pushes Mercor toward workflow-codification for enterprises | Enterprise AI post |
| 2025-2026 | Internal reliability rewrites and Monty scale-up | Operational | Backend and interview runtime are evolving under hypergrowth | Monty and Contracts engineering posts |
Dates are event dates where public pages provided them; otherwise the row uses the year or stage visible from the fetched page.
[CE007, CE010, CE016, CE018, CE020, CE022]Mercor looks strongest where benchmark realism and operations meet, and weakest where public proof of integrations and trust depth is still thin.
[CE001, CE009, CE010, CE020, CE022, CE025]5.4 Trust, controls, and technical risk
Mercor has more public process documentation than many young AI startups, but the trust picture is still mixed. The docs index exposes a wide set of contractor-facing guides covering data use, LLM restrictions, payments, time tracking, and background checks. Those policies matter because Mercor is intermediating sensitive workflows and, according to TechCrunch, handling datasets and procedures that customers treat as trade secrets. The same docs also reveal how much of the product experience depends on disciplined operations rather than model magic. Workers are background-checked, tracked, and restricted in how they can use outside LLMs. Yet the April 2026 breach demonstrates that documentation is not the same thing as mature trust posture. TechCrunch reported claimed theft of source code, API keys, candidate data, and employer data, exactly the type of material that could damage both customer confidence and product credibility. Until Mercor provides deeper public certification and incident-response evidence, trust remains the company's most immediate technical risk.[CE017, CE018, CE019, CE020, CE021, CE027]
| Control / quality lever | Status | Scope | Evidence | Gap |
|---|---|---|---|---|
| Background checks | Publicly documented | Identity, education, employment, and licenses | Policy page details process | No public audit or completion-rate stats |
| LLM-use restrictions | Publicly documented | Prevents contractors from outsourcing evaluation judgment | LLM Usage Policy | No public enforcement metrics or escalation data |
| Data-use disclosure | Publicly documented | Covers resumes, interview media, public profiles, payment details | Data-and-AI policy | No public retention schedule detail by workflow |
| Time tracking | Operationally documented | Tracks project-task time through Insightful/Workpuls | How-to guide | No public accuracy or dispute-rate metrics |
| Payment operations | Operationally documented | Stripe primary; Wise sometimes used; bank-account onboarding required | Payments guide | No public payout-failure or fraud metrics |
| Security maturity | Material concern | Source code, API keys, and sensitive customer data reportedly exposed in breach | TechCrunch breach coverage | Trust center is too thin to offset incident risk publicly |
Mercor has more public policy depth than many young startups, but public evidence of certification depth and incident-response maturity remains limited.
[CE027, CE028, CE029, CE030, CE031, CE032]06Customers
6.1 Customer Segments and Market Reach
Mercors customer base is anchored in frontier AI labs — organizations building and refining large language models and multimodal AI systems that require large-scale human feedback data. TechCrunch described Mercor as the go-to provider for AI labs building training datasets as of October 2025, and Bloomberg reinforced this characterization in a detailed April 2026 profile. Public scale signals are stronger on throughput than on active workforce size: CNBC said Mercor had processed 300,000 candidates by February 2025, and Mercor later said it had more than 30,000 experts on its roster by October 2025. Beyond frontier labs, Mercor has launched two additional customer-facing segments: an Enterprise AI product targeting large organizations seeking AI-assisted hiring and workforce management, and a Research portal aimed at academic and government AI programs seeking domain-expert evaluators. The Experts product line represents a premium tier within the marketplace, giving AI labs access to credentialed domain specialists for tasks requiring advanced reasoning or subject-matter knowledge. Geographic reach on the worker side is global, though no breakdown of customer geography by revenue has been disclosed. The customer segmentation picture that emerges from public evidence is one of concentrated demand from a small number of high-value AI lab relationships driving the vast majority of revenue, with diversification into enterprise and research segments at an early stage.[CU003, CU005, CU009, CU015, CU020, CU024]
| Segment | Representative Customers | Product Used | Revenue Signal | Evidence Strength |
|---|---|---|---|---|
| Frontier AI Labs | OpenAI ecosystem, Anthropic-tier labs | Annotation & RLHF evaluation | $450M ARR driven primarily here | High (multiple sources) |
| Enterprise AI Teams | Large tech companies | Mercor Enterprise AI | Growing but undisclosed | Medium (company blog) |
| Research Organizations | Academic & government AI programs | Mercor Research portal | Undisclosed | Low (company page only) |
| AI Startups | Early-stage model companies | Core annotation marketplace | Early growth cohort | Medium (Series A coverage) |
Segment breakdown inferred from product lines and press. No official breakdown disclosed.
[CU003, CU005, CU015, CU020, CU024]Five-stage journey from AI lab awareness through long-term expanded engagement with Mercor.
[CU003, CU006, CU010]6.2 Adoption Trajectory and Revenue Growth
Mercors revenue growth trajectory is among the most striking in the AI tooling sector. The company grew from approximately $2 million in monthly revenue to $2 million per day — roughly a 30-fold increase — over the course of 2025. This growth was corroborated by multiple independent sources: TechCrunch reported a $450 million annualized revenue run rate in September 2025, Forbes confirmed this figure in its AI Cloud 100 coverage, and Bloomberg provided additional color in its April 2026 profile. The funding trajectory tells a parallel story: a $34 million Series A in February 2024, a $100 million Series B at $2 billion valuation in February 2025, and a further $350 million Series C at a $10 billion valuation in October 2025 — a 40x valuation increase over roughly 20 months. The growth pattern is consistent with a company capturing rapidly expanding demand from AI labs scaling their model training operations. CNBC coverage of Scale AI losing OpenAI and Google as clients suggests that some portion of Mercors growth came from customers migrating from or supplementing Scale AI relationships. The adoption funnel from registered worker to active project deployment is not publicly detailed, but the documentation at talent.docs.mercor.com indicates structured onboarding and project milestone systems that support rapid scaling of new customer deployments.[CU001, CU002, CU006, CU007, CU008, CU016]
| Period | Revenue Metric | Valuation | Key Customer Event | Source |
|---|---|---|---|---|
| Q1 2024 | ~$2M ARR (est) | $34M raised (Series A) | Series A close | TechCrunch Feb 2024 |
| Q1 2025 | ~$75M ARR (reported) | $2B valuation | Series B close | TechCrunch/CNBC Feb 2025 |
| Q3 2025 | $450M ARR reported | $2B (pre-Series C) | Scale AI lawsuit filed | TechCrunch/Forbes Sep 2025 |
| Q4 2025 | $600M+ ARR (est) | $10B valuation | Series C close | TechCrunch/Forbes Oct 2025 |
| Q2 2026 | $700M+ ARR (est) | $10B maintained | Bloomberg profile | Bloomberg Apr 2026 |
ARR estimates for Q1 2024 and 2026 extrapolated from growth narrative; only Q3 2025 figure is directly reported.
[CU001, CU002, CU006, CU007, CU016]Estimated funnel from available worker pool through active customer project deployment.
[CU009, CU017, CU025]6.3 Named Customer Proof and Evidence Quality
The quality of customer proof for Mercor is limited by the confidential nature of AI lab vendor relationships. No frontier AI lab has publicly confirmed Mercor as a vendor. The evidence base rests on journalist characterizations, company blog posts, and the implicit signal from the Scale AI litigation — which, by alleging trade secret misappropriation of customer relationships, implies that Mercor was actively competing for or winning AI-lab business that Scale AI considered its own. TechCrunch described AI labs using Mercor to build training datasets in a detailed October 2025 piece; Mercors own Disrupt 2024 blog post showed live AI evaluation workflows that presuppose real customer deployments. The Forbes AI Cloud 100 inclusion provides third-party analyst validation that investors and industry observers view Mercors customer base as credible. The named customer proof table in this chapter catalogues all publicly attributable customer references; the result is a sparse but directionally consistent picture. For diligence purposes, the absence of named references is a material gap. Any investment decision should require production of customer reference letters or LOIs from at least the top three revenue-contributing customers.[CU003, CU004, CU008, CU011, CU012, CU014]
| Customer / Counterparty | Relationship Type | Evidence Source | Evidence Type | Confidence |
|---|---|---|---|---|
| AI Lab Ecosystem (OpenAI-tier) | Primary annotation customer | TechCrunch Oct 2025 | Journalist report | Medium |
| Scale AI (indirect proof) | Competitor dispute signals shared customer base | Axios/Bloomberg Sep 2025 | Legal filing context | High |
| Mercor Enterprise early adopters | Enterprise pilot customers | Mercor blog Mar 2025 | Company announcement | Low |
| Forbes AI Cloud 100 voters | Industry recognition implies broad customer validation | Forbes Sep 2025 | Industry list | Medium |
No AI lab has publicly confirmed Mercor as a vendor by name. Evidence is inferred from journalist descriptions.
[CU003, CU004, CU008, CU011, CU014]Matrix mapping customer segments against evidence quality dimensions for Mercors proof of traction.
[CU001, CU003, CU008, CU012]6.4 Retention, Expansion, and Concentration Risk
Mercors retention and expansion economics are almost entirely opaque. No net revenue retention, gross revenue retention, churn rate, or cohort data has been publicly disclosed. The company has not published customer satisfaction scores, renewal rates, or multi-year contract details. The only indirect evidence of retention comes from the revenue growth narrative: a 30x revenue increase over a single year implies that either existing customers expanded dramatically, new customers were acquired at pace, or both. Concentration risk is a primary structural concern. The revenue appears overwhelmingly sourced from a small number of frontier AI lab relationships; if even one or two of those customers reduce spend — as OpenAI and Google did with Scale AI — the impact on Mercors revenue could be severe. The Scale AI lawsuit adds an additional dimension: allegations that Mercor poached customer relationships raise the possibility of contested contract terms or customer-level legal risk. On the worker supply side, Rest of World has reported quality and retention challenges among AI data annotators broadly, and Mercors structured onboarding and milestone-based access systems suggest the company is aware of these dynamics. The talent.docs.mercor.com documentation indicates Mercor uses contractual mechanisms to manage worker access, which may serve as a retention tool for quality workers.[CU021, CU022, CU023, CU011, CU017, CU025]
| Metric | Disclosed Value | Source | Gap / Note |
|---|---|---|---|
| Net Revenue Retention | Not disclosed | N/A | Key missing metric |
| Worker Retention Rate | Not disclosed | N/A | Inferred as high given worker volume growth |
| Customer Renewal Rate | Not disclosed | N/A | No public data |
| Satisfaction Score (NPS) | Not disclosed | N/A | No customer survey data published |
| Repeat Project Rate | Implied high (growth narrative) | TechCrunch/Forbes Oct 2025 | Indirect signal only |
Mercor has not disclosed any retention, satisfaction, or repeat-usage metrics publicly. Growth trajectory implies strong retention but is not confirmed.
[CU023, CU025, CU026]| Risk Factor | Evidence | Severity | Mitigant |
|---|---|---|---|
| Customer concentration | No breakdown disclosed; AI labs dominate revenue | High | Enterprise diversification underway |
| Single-segment dependency | ~100% revenue from AI training market | High | Research and Enterprise products launched |
| Platform-switching precedent | Google and OpenAI reduced Scale AI spend | Medium | Mercor brand differentiation |
| Scale AI lawsuit overhang | Ongoing trade-secret litigation | Medium | Legal defense; case pending |
| Worker supply constraints | Rest of World reported quality challenges | Medium | Structured onboarding documented |
Concentration risk is a primary structural concern given undisclosed customer breakdown and single-vertical focus.
[CU021, CU022, CU011, CU017, CU025]Illustrative worker-cohort retention by project-month based on available proxy evidence; customer-level retention not publicly disclosed.
[CU023, CU025, CU017]07Risks
7.1 Regulatory, Legal, and Litigation Risk
Mercors most significant regulatory exposure is worker misclassification. The company publicly disclosed more than 30,000 experts on its roster by October 2025, alongside 300,000 processed candidates earlier that year. Californias AB 5 imposes the ABC test for worker classification, and the California DIR and FTB have both published specific guidance on how the law applies to gig-economy platforms. The 2024 federal DOL independent contractor rule further tightens the economic-reality test at the federal level, and the IRS has published parallel guidance on the same question. A 2024 California Supreme Court decision on AB 5 in a major trucking case signals continued judicial willingness to expand gig-worker protections beyond their original scope. If Mercors annotators were reclassified as employees in California, the company would face potential liability for back wages, benefits, payroll taxes, and penalties across a meaningful share of its expert network. No reserve amount or legal-exposure estimate has been disclosed. On the litigation front, Scale AI filed a trade-secrets lawsuit in September 2025 alleging that Mercor misappropriated proprietary customer data and pricing information. Court records later show the case was voluntarily dismissed with prejudice in January 2026, but Bloomberg, TechCrunch, and Axios coverage still highlight the underlying trade-secret and customer-acquisition controls risk. The EU AI Act, which entered into force in 2024, creates additional risk: AI systems used in employment and worker allocation decisions are classified as high-risk, potentially requiring conformity assessments before deployment in EU markets.[CR001, CR002, CR003, CR004, CR005, CR010]
| Risk Item | Jurisdiction | Severity | Probability | Key Evidence |
|---|---|---|---|---|
| AB 5 worker misclassification | California | Critical | High | DIR, FTB, CA Legislature AB 5 text |
| Federal contractor reclassification | US Federal | High | Medium | DOL 2024 independent contractor rule |
| Scale AI trade secrets lawsuit | US Federal (NDCA) | High | Active | CourtListener, PACER, Bloomberg |
| Data breach class action (Gill) | US Federal (NDCA) | High | Active | CourtListener, Claim Depot |
| EU AI Act employment-AI scope | European Union | Medium | Medium | EU AI Act official text (CELEX) |
| GDPR cross-border transfer | EU/International | Medium | Medium | Inferred from EU annotator base |
| IP ownership disputes | Multi-jurisdiction | Medium | Low | Data AI usage policy; inferred |
Only publicly known or inferred risks included. Internal legal register not available for review.
[CR001, CR002, CR004, CR005, CR006, CR020]Risk severity versus probability matrix for Mercors top risk categories.
[CR002, CR005, CR006, CR007, CR012]7.2 Operational, Security, and Quality Risk
In March 2026, Mercor confirmed it had suffered a cyberattack that exposed personal data of some users. TechCrunch reported the breach, and within days a federal class-action lawsuit was filed — Gill v. Mercorio Corporation — in the Northern District of California, alleging negligent data security practices. Claim Depot and CourtListener both confirm the case is active. TechCrunch noted in a follow-up piece that the simultaneous occurrence of the breach and the Scale AI litigation created compounding reputational risk. Mercor maintains a Trust Center at trust.mercor.com, but has not disclosed any SOC 2 Type II certification, ISO 27001 certification, or NIST CSF conformance assessment. The 2024 NIST CSF establishes best-practice controls for organizations handling sensitive personal data; Mercors conformance is unknown. On the operational quality side, Mercors own blog post describing how the platform nearly failed during a 10x volume spike reveals infrastructure fragility that has not been remediated in any publicly described way. Rest of World documented systematic quality challenges among AI annotation workers across the industry, suggesting supply-side quality risk is not unique to Mercor but is material given that output quality is Mercors core value proposition. No published error rates, SLA breach rates, or quality audit results are available.[CR006, CR007, CR008, CR009, CR013, CR014]
| Risk Item | Severity | Evidence | Mitigation Evidence | Gap |
|---|---|---|---|---|
| March 2026 cyberattack / data breach | Critical | TechCrunch Mar 2026 | Public disclosure made | No SOC 2 or NIST conformance disclosed |
| Annotation quality variability | High | Rest of World coverage | Milestone-based access system | No published error rates |
| Platform scaling outage risk | High | Mercor 10x volume blog | Post-incident engineering effort | No capacity SLA disclosed |
| Worker data access controls | Medium | Inferred from breach scope | Trust Center existence | No access-control documentation |
| GDPR data residency compliance | Medium | Inferred EU worker base | Data AI usage policy | No GDPR DPA documentation |
| Third-party infrastructure dependency | Medium | Standard cloud architecture (inferred) | Trust Center | No BCP or RTO disclosed |
Operational risk assessment based on public evidence only. Internal audits and security certifications not available.
[CR007, CR008, CR009, CR013, CR014, CR018]Directed acyclic graph showing how primary risks cascade into secondary and tertiary consequences for Mercor.
[CR005, CR006, CR007, CR012, CR022]7.3 Partner, Dependency, and People Risk
Customer concentration is a structural risk for Mercor. Evidence from multiple journalists points to a revenue base dominated by frontier AI lab relationships. The direct precedent is striking: Scale AI lost OpenAI and Google as customers within a short period, resulting in a 14% workforce reduction. Reuters confirmed OpenAI wound down Scale AI work in June 2025. If Mercors top-one or top-two customers reduced engagement at a similar pace, the revenue impact could be catastrophic absent rapid replacement. Mercor has attempted to diversify through Enterprise AI and Research segments, but no revenue contribution from these segments has been disclosed. On the people side, the founding team consists of young engineers; press coverage from KTVU and Times of India highlights their technical capability but also the absence of experienced operating executives in public disclosures. Rest of World and Time magazine both documented wage and labor-rights concerns among AI annotators working for platforms similar to Mercor; these concerns apply directly to Mercors global expert network, which the company said exceeded 30,000 people by October 2025. The talent portal documentation shows that Mercor has structured dispute-resolution pathways and contract frameworks, indicating awareness of the exposure, but no independent labor audit has been disclosed.[CR012, CR013, CR015, CR017, CR019, CR024]
| Dependency | Type | Concentration Risk | Mitigation | Evidence |
|---|---|---|---|---|
| Frontier AI Lab customers | Revenue concentration | Critical | Enterprise/Research diversification | TechCrunch, Forbes, Bloomberg |
| Cloud infrastructure provider | Technical dependency | High | Unknown; multi-cloud not confirmed | Inferred from scale |
| Independent contractor supply | Labor supply | Medium | 300k+ pool; geographic spread | Multiple press sources |
| Scale AI competitive pressure | Market risk | Medium | Differentiation via brand and speed | Litigation and press context |
| Payment/payroll processor | Financial dependency | Low | Multiple options available | Inferred from contractor model |
Partner dependencies inferred from business model; specific vendor names not publicly disclosed.
[CR012, CR014, CR019, CR026]| Risk Item | Severity | Evidence | Mitigation |
|---|---|---|---|
| Founder execution risk (young team) | Medium | KTVU, Times of India (early coverage) | Experienced investors on board |
| Worker labor rights / wage complaints | High | Rest of World, Time magazine | Structured contracts; dispute resolution portal |
| Key-person dependency on founders | Medium | No COO/CPO named publicly | Undisclosed leadership depth |
| Cultural scaling risk | Medium | Rapid headcount inferred from growth | Undisclosed |
| Annotator quality degradation at scale | High | Rest of World (2023) | Milestone-based project access |
People risks are partially observable through press coverage; management team details are limited in public sources.
[CR013, CR017, CR025, CR029]Dependency graph showing Mercors key operational and financial dependencies and their interconnections.
[CR010, CR012, CR014, CR032]7.4 Mitigations, Kill Criteria, and Diligence Asks
Mercors publicly observable mitigations are partial and largely undocumented. The Trust Center at trust.mercor.com provides basic security-posture signaling. The talent portal contract and legal support documentation indicates that Mercor has legal frameworks in place for worker relationships. The company made a public breach disclosure in March 2026, suggesting a functioning incident-response capability. However, no SOC 2 report, insurance disclosures, capacity SLAs, quality audit results, or regulatory reserve amounts have been published. For investment monitoring purposes, kill criteria should include: an adverse AB 5 ruling or DOL enforcement action; an adverse court finding or new trade-secret dispute showing improper use of competitor customer materials; a second material security breach within 12 months; or confirmed loss of more than 50% of revenue from a single customer departure. Early-warning signals to monitor include CourtListener docket updates for the breach case and any new competitor litigation, DOL and NLRB enforcement trackers, Mercors Trust Center updates, and monthly ARR bridge data from the company. The most critical diligence asks remain: a legal memo quantifying AB 5 exposure, a SOC 2 Type II report or equivalent, a top-10 customer revenue breakdown, and confirmation of insurance coverage for cyber and E&O risk.[CR008, CR015, CR020, CR022, CR024, CR025]
| Risk Category | Current Mitigation | Kill Criterion | Monitoring Signal |
|---|---|---|---|
| Regulatory / AB 5 | Contractor self-certification; legal counsel (inferred) | Adverse AB 5 ruling or DOL enforcement action | DOL enforcement tracker; NLRB case filings |
| Trade secrets litigation | Active legal defense | Preliminary injunction limiting customer outreach | CourtListener docket updates; press |
| Data breach / cyber | Trust Center; public breach disclosure | Second material breach within 12 months | HaveIBeenPwned; regulatory filings |
| Customer concentration | Enterprise/Research diversification | Loss of >50% revenue from single customer departure | Monthly ARR bridge; customer NRR |
| Worker quality / supply | Milestone-based access; onboarding docs | Customer SLA breach rate exceeds threshold | SLA breach reports; customer satisfaction |
Kill criteria are illustrative thresholds for investor portfolio monitoring; actual thresholds should be set in the investment monitoring framework.
[CR005, CR007, CR012, CR022, CR025]08Valuation
8.1 Investment Thesis and Anti-Thesis
Mercor deserves valuation attention because the company has assembled three things the market clearly wants: very fast growth, access to frontier-AI customers, and a believable path to move beyond pure recruiting into benchmarks, evaluation, and workflow tooling. The official financing history shows Mercor stepping from a $250 million Series A valuation to $2 billion in February 2025 and then to $10 billion in October 2025. Independent reporting adds real operating proof to that narrative, including a $75 million run-rate by February 2025, roughly $450 million annualized revenue by September 2025, and customer names such as OpenAI, Anthropic, and Meta. Product evidence from Mercor's research, APEX, Enterprise AI, assessments, and RL Studio pages matters because it suggests the company is trying to build repeatable workflow and benchmark assets rather than remain only a labor broker. The anti-thesis is that Mercor is still priced as if that up-stack transition has already worked. Public sources say revenue is reported gross of contractor payouts, customer concentration remains high, breach fallout interrupted customer trust, and litigation plus labor complexity can still raise operating friction. In short, Mercor looks strategically important, but the current mark leaves little room for execution misses.[CV002, CV003, CV005, CV006, CV008, CV010]
| Thesis pillar | Support | Anti-thesis | What changes the view |
|---|---|---|---|
| Growth and customer access | Mercor moved from a $2B mark and ~$75M run-rate in early 2025 to a $10B mark and ~$450M annualized revenue by September 2025, with OpenAI, Anthropic, and Meta cited as customers | That revenue is reported gross of contractor payouts and appears concentrated in a few labs | Show net revenue, take rate, and top-customer concentration |
| Product up-stack optionality | APEX, Enterprise AI, assessments, and RL Studio suggest a path toward benchmark and workflow infrastructure | Public adoption proof for these product layers is still thin; they may be sales aids rather than durable revenue streams | Disclose attach rate, repeat usage, and customer references for product modules |
| Market tailwind | AI Index and market reports still support expanding demand for high-quality human-data workflows | Growing market size does not prevent multiple compression if Mercor looks more like services than software | Show that Mercor is converting growth into stickier economics, not just volume |
| Competitive position | Mercor appears well placed after Scale AI disruption and has a strong frontier-lab narrative | Appen and peers also market expert RLHF, agentic evaluation, and integrity products; category convergence can erode differentiation | Prove benchmark realism and product depth are translating into revenue mix shift |
| Trust recovery | Breach remediation and litigation dismissal reduce some headline risk | Meta pauses, class actions, and any second incident would quickly re-open downside | Provide independent evidence of post-breach control improvements and customer retention |
The anti-thesis is not hypothetical. It is built directly from the public evidence on accounting, concentration, breach fallout, and category convergence.
[CV008, CV010, CV011, CV012, CV014, CV015]Decision chain from growth proof to revenue-quality adjustment, risk checks, and the final TRACK recommendation.
Flow reflects analyst synthesis of the strongest valuation drivers and blockers in the chapter. It is a decision framework, not a mathematical model.
[CV006, CV008, CV021, CV030, CV034, CV038]8.2 Recommendation and Valuation Stance
Recommended stance: TRACK with MEDIUM confidence, HIGH risk, and a STRETCHED valuation view at the current $10 billion mark. The call is intentionally price-sensitive. A buy case today would require stronger proof than the public record currently provides: audited or at least cleaner net-revenue disclosure, evidence that benchmarks and workflow products are lifting attachment and margin, and signs that post-breach trust remediation has stabilized key customers. At $10 billion against the September 2025 $450 million gross annualized run-rate, Mercor screens at about 22x gross revenue. Even if one uses Mercor's own 2026 claim of having crossed a $1 billion annualized run-rate, the mark is still about 10x gross revenue on a metric that remains unaudited and includes pass-through contractor spend. That is not obviously absurd for a company with software ambitions, but it is too rich for a business that still carries marketplace, compliance, and incident-response risk. The practical conclusion is to watch the story rather than chase it: a lower entry price around $6 billion to $7.5 billion, or hard proof that Mercor's benchmark and workflow layers are changing the business mix, would make the risk-reward more attractive.[CV006, CV007, CV008, CV032, CV033, CV039]
| Dimension | Assessment | Confidence | Investment implication |
|---|---|---|---|
| Recommendation | TRACK — interesting company, wrong evidence-to-price ratio for a buy at $10B | Medium | Monitor; do not stretch for entry until price or proof improves |
| Valuation stance | STRETCHED at $10B; closer to $6B-$7.5B is more defensible on current public evidence | Medium | Current mark already assumes successful up-stack execution and cleaner economics |
| Risk rating | HIGH — concentration, breach fallout, legal/labor complexity, and revenue-quality opacity | High | Size any future entry cautiously and require tighter diligence |
| What would upgrade the call | Audited/net revenue bridge, top-customer diversification, and post-breach trust proof | Medium | Could move the stance from TRACK toward BUY without needing a deep price reset |
| Most realistic path | Watch for later private liquidity or secondary entry after proof milestones | Low | Prefer patience over momentum-chasing at the current mark |
Summary reflects an evidence-sensitive view rather than a generic company-quality score. Mercor can be strong strategically while still being too expensive on present disclosure.
[CV032, CV033, CV039, CV040, CV041, CV042]Sensitivity of implied equity value to different revenue bases and revenue multiples. Values are in USD millions.
The low bars anchor downside to marketplace- and services-like outcomes, while the higher bars show what must be true for the current mark to look normal. Revenue inputs are public signals, not audited statements.
[CV006, CV007, CV008, CV024, CV025, CV026]8.3 Financing Context and Comparable Valuation
Mercor now sits awkwardly between two comp buckets. On one side are labor marketplaces and data-service platforms such as Appen, Upwork, and Fiverr, which public market data show trading around roughly 1x revenue. Those businesses are valued as transaction or services engines with limited software scarcity. On the other side sits Palantir, which trades at a radically higher multiple because investors view it as a software control plane with durable product lock-in, strong gross margins, and deep mission-critical embeds. Mercor's current mark clearly assumes it belongs closer to the second bucket than the first, but public evidence is not there yet. What supports the premium is the unusual combination of frontier-AI customer access, extreme growth, and visible product efforts around APEX, Enterprise AI, assessments, and RL Studio. What limits the premium is the lack of public net-revenue, take-rate, margin, or retention data, plus the fact that the headline revenue number is gross of contractor payouts. The valuation debate is therefore not whether Mercor is a good company; it is whether investors should underwrite a software-like future before the accounting and customer-mix evidence catches up.[CV008, CV021, CV022, CV023, CV024, CV025]
| Comparable | Status | Revenue metric | Multiple / valuation | Relevance | Limitation |
|---|---|---|---|---|---|
| Mercor | Private (subject) | ~$450M annualized gross revenue in Sep 2025; company later claimed $1B annualized in 2026 | $10B valuation; ~22x on Sep-2025 gross run-rate or ~10x on the later company claim | Sets the entry point investors must underwrite | Gross-vs-net economics remain undisclosed |
| Appen | Public | ~$0.23B revenue | ~1x revenue ($0.23B market cap) | Direct human-data and evaluation comp showing how public markets price service-heavy platforms | Mature, slower-growth public company with different customer mix |
| Upwork | Public | ~$0.79B revenue | ~1.4x revenue ($1.08B market cap) | Useful marketplace comp for how transaction-heavy labor platforms are valued | Broader freelancer marketplace, not frontier-AI infrastructure |
| Fiverr | Public | ~$0.42B revenue | ~0.9x revenue ($0.39B market cap) | Another marketplace anchor for the downside valuation frame | SMB freelancer focus differs from Mercor's expert-AI niche |
| Palantir | Public | ~$5.22B revenue | ~63x revenue ($328.14B market cap) | Shows the upside available to software control-plane businesses with strong lock-in | Much more productized, disclosed, and entrenched than Mercor |
| Scale AI | Private | Revenue denominator not cleanly public in the fetched set | About $29B implied value from Meta's 49% deal per Axios/CNBC | Closest category leader for AI-data infrastructure and a reminder that narrative can stay expensive | Opaque revenue and terms limit clean multiple comparison |
| Turing / similar talent-data peers | Private | Not enough reliable public denominator in the fetched valuation source set | Turing reached $2.2B valuation in March 2025 | Shows Mercor's $10B mark is well above adjacent talent-data peers | Sparse public economics and term details |
Public company numbers come from CompaniesMarketCap snapshots fetched for this run. Private-company rows are valuation context rows, not clean like-for-like multiple rows.
[CV022, CV023, CV024, CV025, CV026, CV027]8.4 Bull / Base / Bear Scenarios and Return Analysis
The bull case is not just more volume. It requires Mercor to convert its benchmark and workflow assets into stickier software-like spend while broadening beyond a few frontier labs. In that version of the story, APEX and Enterprise AI become real budget lines, RL Studio and assessments improve matching and delivery economics, the breach fades without a second incident, and concentration falls enough that customers view Mercor as infrastructure rather than a vendor of convenience. That can support a $12 billion to $18 billion outcome over time. The base case is more mixed: revenue keeps growing, Mercor repairs trust, and product assets help sales, but customer concentration remains meaningful and gross-to-net quality stays opaque. In that world the valuation likely settles into a $7 billion to $10 billion range, which means the current mark already captures much of the upside. The bear case explicitly combines the known risk vectors: a major customer pause or loss, prolonged breach or class-action fallout, rising labor or contractor-compliance costs, or failure of the benchmark and software layers to monetize beyond thought leadership. Then Mercor can be valued closer to services and labor platforms, producing a much lower $2.5 billion to $5 billion range.[CV011, CV012, CV013, CV017, CV018, CV019]
| Scenario | Revenue / mix assumption | Exit valuation | Return implication vs. $10B | Key risks / supports | Probability signal |
|---|---|---|---|---|---|
| Bull | Mercor verifies high net revenue conversion, benchmark/workflow products become sticky, concentration eases, and breach fallout fully normalizes | $12B-$18B | 1.2x-1.8x | Software-up-the-stack upside offsets marketplace discount; no major legal or security relapse | Possible, but needs multiple evidence upgrades simultaneously |
| Base | Growth remains strong, trust recovers enough to keep key accounts, but gross-to-net opacity and concentration only improve partially | $7B-$10B | 0.7x-1.0x | Current price already embeds much of this outcome | Most plausible on today's evidence |
| Bear | A top AI-lab relationship weakens, breach or class-action fallout lingers, or labor/legal costs rise while benchmark products fail to monetize materially | $2.5B-$5B | 0.25x-0.5x | Reset toward services/labor-platform multiples despite continued AI demand | Real downside because the current mark leaves limited margin of safety |
Scenario ranges are judgment calls anchored on public revenue signals and public-company valuation anchors, not on management guidance or an audited model.
[CV032, CV033, CV035, CV036, CV037, CV038]Bull, base, and bear valuation ranges versus the current $10B mark and a more attractive watch-entry range.
Ranges are judgment-based and reflect how much of Mercor's future product mix and trust repair are already embedded in the current mark.
[CV035, CV036, CV037, CV039, CV040, CV041]8.5 Valuation Risks and Thesis-Break Triggers
Four risks dominate the downside. First is concentration: public reporting repeatedly points to a revenue base anchored by only a few AI labs, which means one paused or lost relationship can move the valuation far more than it would at a diversified software company. Second is trust and security: Mercor's 2026 breach and resulting litigation matter not only because of direct cost, but because they challenge the credibility required to handle sensitive enterprise and model-development workflows. Third is legal and labor exposure. Mercor's own docs show a globally distributed contractor machine with jurisdiction-specific payment constraints, time-tracking oversight, and human review of disputes; that operating complexity is part of the moat, but it is also part of the risk stack. Fourth is narrative risk. If APEX, Enterprise AI, RL Studio, and assessments do not translate into software-like attachment, investors may eventually decide Mercor is better framed as a premium labor-and-services marketplace. That would compress the multiple even if top-line growth remains good. A second material security incident, clear customer churn after the breach, or evidence of margin pressure from legal or contractor costs would each break the current thesis quickly.[CV011, CV012, CV013, CV017, CV018, CV020]
| Trigger | Threshold | Why it matters | Action implication |
|---|---|---|---|
| Customer concentration breaks the wrong way | A clearly material top-customer pause, non-renewal, or revenue-share loss after 2026 | Mercor does not yet have public diversification evidence strong enough to absorb a large lab loss | Move from TRACK to avoid or demand a much lower price |
| Second material security incident | Another serious breach or confirmed deeper damage from the 2026 incident | Would undermine the trust thesis behind benchmark, workflow, and enterprise expansion | Treat as thesis-break until controls are externally validated |
| Labor / contractor cost shock | Evidence that contractor, privacy, or classification costs materially change unit economics | Would push Mercor closer to services economics while also lowering growth confidence | Re-rate toward public labor-platform multiples |
| Software attach fails to show up | No credible benchmark / workflow revenue proof after another funding or growth step | Without up-stack conversion, the $10B mark rests on volume and narrative more than product economics | Keep a TRACK stance even if revenue stays large |
| Disclosure still opaque at the next price-setting event | No net revenue bridge, no concentration disclosure, no clear post-breach controls by the next financing or secondary window | Investors would still be underwriting too much on faith | Pass on the round or require a steeper discount |
Kill triggers are framed for investors evaluating whether Mercor deserves a software-like premium or should be marked closer to services and marketplace comps.
[CV011, CV012, CV013, CV017, CV018, CV030]Investment-committee style snapshot of Mercor's valuation drivers as of May 2026.
KPI labels are qualitative judgments for decision support. They do not imply that Mercor lacks strengths; they highlight where the public record is still thin relative to the price.
[CV021, CV023, CV030, CV031, CV034, CV038]8.6 Exit Readiness and Final Diligence Asks
Mercor is not a finalize-now diligence story at this price. The company may eventually earn a much richer multiple, but that outcome depends on facts the public record does not yet settle. The first blocking item is a revenue-quality bridge that separates gross billings, contractor payouts, Mercor take rate, net revenue, and any recurring software-like revenue. The second is a top-customer view: investors need to know how concentrated the revenue base is, what portion was disrupted by the breach, and whether newer products are broadening the account mix. Third, Mercor needs to show trust repair in a way public markets or late-stage private investors can underwrite, ideally with post-breach control improvements and independent assurance rather than only narrative. Fourth, the contractor and legal stack needs clearer quantification, because a company that spans many jurisdictions and monitors time so tightly may be more exposed to labor, privacy, or classification disputes than a typical software vendor. Until those asks are answered, the best posture is to keep Mercor on the watch list, not to pay a price that already anticipates favorable answers.[CV017, CV018, CV030, CV031, CV039, CV040]
| Topic | Missing evidence | Why it matters | Owner / diligence path |
|---|---|---|---|
| Net revenue and take rate | Gross billings, contractor payouts, Mercor take rate, and any recurring software revenue split | This is the single most important bridge between a marketplace valuation and a software valuation | Finance data room and controller review |
| Top-10 customer mix and retention | Revenue concentration, renewal cadence, paused accounts after the breach, and expansion by product line | Concentration is the central downside variable in the current model | CFO data room plus customer-reference work |
| Post-breach trust remediation | Independent evidence of control improvements, scoped impact, and customer reassurance after the LiteLLM incident | Without trust repair, benchmark and enterprise upsell becomes harder to underwrite | Security diligence, incident report, and customer checks |
| Contractor and legal exposure | Jurisdictional contractor mix, policy-enforcement data, disputes, and any reserves or outside-counsel memos | Mercor's moat partly relies on labor orchestration that can also generate compliance cost | Legal diligence with employment and privacy counsel |
| Cap table and preferences | Preference stack, participation rights, and any secondary terms at the $10B mark | A stretched valuation can still be investable if terms are unusually clean, and vice versa | Corporate counsel review and round-document analysis |
These asks are ordered by what most directly changes valuation confidence. None are finalize-later nice-to-haves at the current price.
[CV031, CV039, CV040, CV041, CV042]Disclaimer
This report-meta summary is generated from public sources as of May 23, 2026 and does not constitute investment advice. Mercor is a private company, and several of the most important underwriting inputs — including net revenue, margin, customer concentration, and preference terms — are not publicly disclosed. Any investment decision should rely on direct diligence and primary company materials rather than this public-information summary alone.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Mercor describes itself as organizing human intelligence to power the AI economy. | Medium | SO001 |
| CO002 | Mercor connects experts to AI projects and pays them remotely on contract engagements. | High | SO002, SO001 |
| CO003 | Mercor says its work sits at the intersection of labor markets and AI research. | High | SO007, SO003 |
| CO004 | Mercor was founded in January 2023. | High | SO005, SO021 |
| CO005 | Official and independent 2025 coverage identifies Mercor's cofounders as Brendan Foody, Adarsh Hiremath, and Surya Midha. | High | SO008, SO021, SO022 |
| CO006 | Mercor's founders dropped out of Georgetown and Harvard in 2023 to build the company. | High | SO008, SO021, SO025 |
| CO007 | PR Newswire said all three cofounders had received the Thiel Fellowship by the time of Mercor's Series A announcement. | Medium | SO008 |
| CO008 | Mercor raised a $3.6 million seed round led by General Catalyst in 2023. | High | SO005, SO021 |
| CO009 | Mercor announced a $30 million Series A at a $250 million valuation in 2024. | High | SO008, SO011 |
| CO010 | Mercor announced a $100 million Series B at a $2 billion valuation in February 2025. | High | SO009, SO010, SO011, SO006 |
| CO011 | Mercor announced a $350 million Series C at a $10 billion valuation in October 2025. | High | SO007, SO013, SO014 |
| CO012 | Mercor's total disclosed primary capital across seed, Series A, Series B, and Series C is about $483.6 million. | Medium | SO005, SO008, SO009, SO013 |
| CO013 | Bloomberg said Mercor's February 2025 round included Felicis, General Catalyst, DST Global, Benchmark, and Menlo Ventures. | High | SO011, SO009 |
| CO014 | Mercor says its Series C was led by Felicis with Benchmark, General Catalyst, and Robinhood Ventures participating. | High | SO007, SO013, SO014 |
| CO015 | Mercor's business model shifted from AI-driven recruiting toward supplying domain experts for AI model training and evaluation. | High | SO009, SO013, SO015 |
| CO016 | TechCrunch reported Mercor generated revenue by charging hourly finders' fees and matching rates to clients. | Medium | SO009, SO012, SO013 |
| CO017 | CNBC reported Mercor had processed 300,000 candidates and conducted more than 100,000 interviews by February 2025. | Medium | SO010 |
| CO018 | TechCrunch reported Mercor had helped HR teams evaluate 468,000 applicants by February 2025. | Medium | SO009 |
| CO019 | TechCrunch reported Mercor reached a $75 million annual recurring revenue run rate by February 2025. | Medium | SO009 |
| CO020 | CNBC quoted Brendan Foody saying Mercor had grown more than 51% month over month over the prior six months as of February 2025. | Medium | SO010, SO006 |
| CO021 | TechCrunch reported Mercor was approaching a $450 million annualized revenue run rate in September 2025. | Medium | SO012 |
| CO022 | TechCrunch said Mercor generated $6 million in profit in the first half of 2025, citing Forbes. | Medium | SO012 |
| CO023 | Mercor said in October 2025 that it paid more than $1.5 million per day to contractors and had more than 30,000 experts on its roster. | High | SO007, SO013, SO014 |
| CO024 | TechCrunch reported Mercor's experts earned more than $85 per hour on average in October 2025. | Medium | SO013 |
| CO025 | TechCrunch reported Mercor paid some industry experts as much as $200 per hour for AI training work. | Medium | SO015 |
| CO026 | Mercor's research page says the company is used by the top five AI labs and six of the Magnificent Seven. | Medium | SO003 |
| CO027 | TechCrunch reported Mercor supplied contractors to Amazon, Google, Meta, Microsoft, OpenAI, and Nvidia. | Medium | SO012 |
| CO028 | TechCrunch Disrupt coverage named OpenAI, Anthropic, and Meta as Mercor customers. | Medium | SO015 |
| CO029 | Mercor's careers page says the company is a profitable Series C company with offices in San Francisco, New York, and London. | Medium | SO004 |
| CO030 | Mercor's careers page listed 58 open roles across enterprise, engineering, operations, finance, and marketing when fetched for this report. | Medium | SO004 |
| CO031 | Mercor said its team included the former Head of Human Data Operations at OpenAI and the previous Head of Growth at Scale by February 2025. | Medium | SO006 |
| CO032 | TechCrunch reported Mercor appointed former Uber chief product officer Sundeep Jain as its first president in 2025. | Medium | SO012 |
| CO033 | Forbes' Adarsh Hiremath profile said Surya Midha transitioned from chief operating officer to chairman in October 2025. | Medium | SO022 |
| CO034 | Scale AI sued Mercor.io Corporation and former Scale employee Eugene Ling on September 3, 2025 over alleged trade-secret misappropriation. | High | SO016, SO018, SO019 |
| CO035 | PacerMonitor shows the Scale AI lawsuit was voluntarily dismissed with prejudice in early January 2026. | Medium | SO020 |
| CO036 | TechCrunch reported Mercor disclosed a March 2026 data breach linked to credential-harvesting malware in the open-source tool LiteLLM. | Medium | SO017 |
| CO037 | TechCrunch reported Meta paused its contracts with Mercor after the breach while OpenAI said it was investigating but had not paused work at the time. | Medium | SO017 |
| CO038 | KTVU quoted Brendan Foody saying Mercor had crossed a $100 million revenue run rate by March 2025 and was extremely profitable. | Medium | SO021 |
| CM001 | Mercor operates in a narrower market than generic staffing: high-skill human-in-the-loop AI training, evaluation, and benchmark work. | High | SM001, SM002, SM004 |
| CM002 | Mercor's market includes expert post-training labor for doctors, lawyers, engineers, bankers, and consultants rather than commodity click-work. | High | SM003, SM005 |
| CM003 | The relevant adjacent market includes benchmark and evaluation-environment creation for frontier models and agents. | Medium | SM001, SM016, SM017 |
| CM004 | Generic ATS, HRIS, and employer recruiting software are substitutes only for Mercor's original recruiting product, not for its current AI-training specialization. | Medium | SM002, SM004 |
| CM005 | Low-skill crowd labeling is an adjacent but different category from Mercor's premium expert marketplace. | Medium | SM021, SM022, SM003 |
| CM006 | MarketsandMarkets projected the global data annotation and labeling market to reach $3.6 billion by 2027 at a 33.2% CAGR. | Medium | SM008 |
| CM007 | The same MarketsandMarkets preview projected the AI training dataset market to reach $9.58 billion by 2029 at a 27.7% CAGR. | Medium | SM008 |
| CM008 | IBM's summary of Stanford HAI said total corporate AI investment reached $252.3 billion in 2024. | High | SM006, SM007 |
| CM009 | IBM's Stanford AI Index summary said U.S. private AI investment reached $109.1 billion in 2024. | High | SM006, SM007 |
| CM010 | IBM's Stanford AI Index summary said the number of newly funded generative AI startups nearly tripled in 2024. | Medium | SM007 |
| CM011 | A top-down TAM from broad AI investment materially overstates Mercor's serviceable market because most AI spending is not spent on expert contractors. | Medium | SM006, SM008, SM004 |
| CM012 | The primary buyers in Mercor's market are frontier AI labs and enterprise AI teams commissioning post-training data, evaluations, or benchmark work. | High | SM004, SM005, SM001 |
| CM013 | The user inside the buyer organization is typically a model-training, evals, or research operations team rather than an HR department. | Medium | SM004, SM005, SM013 |
| CM014 | The payer for Mercor-style services is usually an AI lab or enterprise AI budget owner rather than the individual expert. | Medium | SM002, SM015 |
| CM015 | Experts on the supply side are both labor inputs and repositories of domain knowledge, making the supply base strategically important. | Medium | SM003, SM009, SM021 |
| CM016 | Incumbent employers whose workflows are being encoded into models act as a status-quo substitute and a blocking constituency in the market. | Medium | SM005, SM021 |
| CM017 | OpenAI's InstructGPT work established that reinforcement learning from human feedback depends on human rankings and preference data. | Medium | SM010 |
| CM018 | Anthropic's Constitutional AI paper reduced some human-label requirements but still framed alignment and evaluation as feedback-intensive. | Medium | SM012 |
| CM019 | Mercor's research page positions benchmark creation and evaluation environments as a frontier need beyond simple annotation. | Medium | SM001 |
| CM020 | Labelbox's expert-economy report argues that frontier models increasingly need PhDs, clinicians, and high-skill specialists rather than general annotators. | Medium | SM009 |
| CM021 | Meta's investment in Scale AI destabilized vendor neutrality and reopened demand for alternative post-training vendors. | Medium | SM004, SM005 |
| CM022 | Agentic AI increases demand for evaluation environments that test multi-step reasoning and real-world workflows. | Medium | SM001, SM016, SM017 |
| CM023 | Data-rights and trade-secret sensitivity constrain how much real enterprise workflow data buyers are willing to share with AI labs. | Medium | SM005, SM004 |
| CM024 | Labor-rights scrutiny in AI data work creates a compliance and brand constraint on scaling contractor-heavy models. | Medium | SM021, SM022, SM023 |
| CM025 | Mercor's market lies between AI infrastructure and flexible labor marketplaces, which complicates direct comparable selection. | Medium | SM001, SM004, SM019 |
| CM026 | Because the market is concentrated among a few frontier labs, adoption can accelerate quickly but also pause suddenly if one buyer changes strategy. | Medium | SM004, SM005 |
| CM027 | NIST's AI Risk Management Framework supports demand for auditable evaluations and trustworthy post-training processes among enterprise buyers. | Medium | SM024 |
| CM028 | OpenAI's 2024 custom-models update implies continued enterprise willingness to buy specialized training and tuning work around frontier models. | Medium | SM011 |
| CM029 | Appen, Scale, Labelbox, iMerit, and Toloka all market adjacent services, confirming that the market boundary spans both services and platform tooling. | Medium | SM013, SM014, SM015, SM020, SM025 |
| CM030 | Snorkel and automation-focused vendors show that rote labeling spend may shift toward software-assisted data generation over time. | Medium | SM016, SM018 |
| CM031 | Invisible Technologies illustrates an adjacent market where enterprises buy modular combinations of data, agents, and humans-in-the-loop rather than a pure labor marketplace. | Medium | SM019 |
| CM032 | Mercor's serviceable market is likely much closer to the high-skill post-training and evals niche than to the full AI-investment pool. | Medium | SM006, SM008, SM009 |
| CM033 | A durable buyer budget requires proof that expert labor improves model quality or accelerates deployment enough to justify premium rates. | Medium | SM010, SM012, SM017 |
| CM034 | Mercor's market benefits from AI adoption growth, but procurement must still clear security, IP, and trust objections in regulated industries. | Medium | SM024, SM021, SM023 |
| CM035 | Public sources do not disclose how much frontier labs spend specifically on benchmark creation, expert evaluations, or contractor pass-through versus other AI infrastructure. | Low | |
| CM036 | Public sources also do not disclose how much of Mercor's opportunity lies in recurring enterprise workflows versus one-off frontier-lab projects. | Low | |
| CP001 | Mercor competes most directly with Scale AI, Surge AI, Labelbox, Appen, iMerit, and other human-data vendors serving frontier models. | High | SP003, SP014, SP005, SP008, SP012 |
| CP002 | Scale AI remains the best-known incumbent in human-data infrastructure and RLHF among frontier-model buyers. | Medium | SP003, SP004, SP021 |
| CP003 | Surge AI is a premium RLHF-focused competitor with a similarly high-skill positioning to Mercor. | Medium | SP014, SP020 |
| CP004 | Labelbox competes as a full-stack data factory combining workflows, RLHF, and an expert network rather than only a labor marketplace. | High | SP005, SP006, SP007 |
| CP005 | Appen competes from the opposite end of the market: a large public human-data vendor trying to move upmarket into frontier alignment and agentic AI services. | Medium | SP008, SP010, SP011 |
| CP006 | iMerit and CloudFactory compete through managed-service human-in-the-loop delivery rather than Mercor's marketplace-led positioning. | Medium | SP012, SP013 |
| CP007 | Snorkel acts as a substitute class by pushing programmatic and automation-heavy data generation instead of expert marketplace labor. | Medium | SP015, SP016 |
| CP008 | Mercor's clearest differentiation is explicit concentration on domain experts such as doctors, lawyers, bankers, and engineers. | Medium | SP002, SP025 |
| CP009 | Scale markets enterprise-grade AI systems and RLHF, but its brand is broader infrastructure rather than a pure expert-talent marketplace. | Medium | SP003, SP004 |
| CP010 | Labelbox positions on software workflow control and data-factory automation more than on Mercor-style labor aggregation. | Medium | SP005, SP006 |
| CP011 | Appen competes on scale, breadth, and public-company credibility rather than Mercor's frontier-startup speed narrative. | Medium | SP008, SP009 |
| CP012 | Mercor, Scale, Labelbox, and Appen all now market evaluation or alignment services, showing convergence around post-training workflows. | Medium | SP001, SP004, SP006, SP010, SP024 |
| CP013 | Mercor has less evidence of platform lock-in than software-first competitors because its core value still depends on ongoing labor-market coordination. | Medium | SP002, SP005, SP018 |
| CP014 | SuperAnnotate and Toloka illustrate how buyers can still choose broad annotation platforms instead of premium expert marketplaces. | Medium | SP017, SP019, SP023 |
| CP015 | Invisible illustrates an adjacent alternative where enterprises buy combined agents, data, and human operations rather than a specialist RLHF vendor. | Medium | SP018 |
| CP016 | Mercor's pricing is not publicly listed; the most visible economic signal is expert hourly rates and client-specific matching fees. | Medium | SP025, SP020 |
| CP017 | Scale, Labelbox, and Appen similarly avoid transparent public list pricing for most enterprise RLHF and evaluation work. | Medium | SP004, SP006, SP010 |
| CP018 | A lack of public pricing across the category makes sales execution, neutrality, speed, and trust more important than headline list prices. | Medium | SP004, SP006, SP010, SP025 |
| CP019 | Mercor benefited competitively when Meta's investment in Scale AI raised neutrality concerns among large labs. | Medium | SP020, SP022, SP026 |
| CP020 | CNBC reported OpenAI had been winding down work with Scale AI and that Google was also reportedly cutting ties after the Meta deal. | Medium | SP022 |
| CP021 | Meta's $14.3 billion investment gave Scale AI a roughly $29 billion implied valuation and kept it substantially larger than Mercor. | Medium | SP021 |
| CP022 | Despite Mercor's growth, TechCrunch still described Surge and Scale AI as larger competitors by late 2025. | Medium | SP025 |
| CP023 | The main moat candidate for Mercor is speed in sourcing premium experts and converting that supply into frontier-model improvement workflows. | Medium | SP002, SP025 |
| CP024 | That moat is fragile because experts can multi-home across vendors and buyers can test several providers simultaneously. | Medium | SP014, SP019, SP022 |
| CP025 | Software-centric competitors may develop stronger lock-in through integrated data, model-evaluation workflows, and analytics than Mercor can through matching alone. | Medium | SP005, SP006, SP015, SP016 |
| CP026 | Mercor's benchmark and evaluation products are an attempt to move from marketplace coordination toward higher-sticky workflow ownership. | Medium | SP001, SP020 |
| CP027 | Appen's investor materials show a public incumbent with broad lifecycle positioning, which can appeal to enterprise buyers who prefer scale and governance over startup speed. | Medium | SP009 |
| CP028 | Snorkel's automation-centric workflow is an adverse signal for any vendor whose value depends on repeating human-labor tasks rather than capturing harder expert judgment. | Medium | SP016 |
| CP029 | Mercor still has a cleaner neutrality narrative than Scale AI after the Meta deal, but that advantage could fade if Mercor itself becomes concentrated with a few labs. | Medium | SP022, SP025 |
| CP030 | Public market data does not reveal realized win rates, pricing discounts, or retention differences across these vendors. | Low | |
| CP031 | Mercor is strongest where buyers value expert judgment and faster supply mobilization more than deep platform workflow control. | Medium | SP002, SP025, SP005 |
| CP032 | Mercor is weaker where buyers prioritize software governance, entrenched workflows, or broad installed bases over marketplace speed. | Medium | SP005, SP009, SP018 |
| CP033 | The category remains structurally multi-homed because no single vendor appears to own both the labor supply and the full workflow stack. | Medium | SP004, SP006, SP010, SP018 |
| CP034 | Mercor's category leadership case depends on moving up the stack before software-centric rivals commoditize matching and sourcing. | Medium | SP001, SP016, SP018 |
| CP035 | The biggest competitive unknown is whether Mercor can turn benchmark and eval workflows into genuine product lock-in. | Low | |
| CI001 | Mercor monetizes customer demand for expert work by matching specialists to AI-lab and enterprise projects, then administering payment through its platform. | High | SI001, SI002, SI007 |
| CI002 | Mercor's experts page says professionals work remotely on contract opportunities and get paid weekly. | High | SI002, SI007 |
| CI003 | Mercor's payments documentation says Stripe is the primary payment rail for ongoing work. | Medium | SI007 |
| CI004 | Mercor's payments documentation says Wise is sometimes used for one-time or fallback payouts. | Medium | SI007 |
| CI005 | Mercor announced a $30 million Series A at a $250 million valuation in 2024. | High | SI008, SI011 |
| CI006 | Mercor announced a $100 million Series B at a $2 billion valuation in February 2025. | High | SI004, SI009, SI010, SI011 |
| CI007 | Mercor announced a $350 million Series C at a $10 billion valuation in October 2025. | High | SI005, SI013 |
| CI008 | Mercor's total disclosed primary capital across seed, Series A, Series B, and Series C is about $483.6 million. | Medium | SI008, SI010, SI005 |
| CI009 | CNBC reported Mercor was profitable and running above a $75 million revenue run rate by February 2025. | Medium | SI009 |
| CI010 | TechCrunch reported Mercor had reached a $75 million annual recurring revenue run rate by February 2025. | Medium | SI010 |
| CI011 | TechCrunch reported Mercor was approaching a $450 million annualized revenue run rate in September 2025. | Medium | SI012 |
| CI012 | TechCrunch reported Mercor told investors it was on track to hit $500 million ARR faster than Anysphere. | Medium | SI012 |
| CI013 | TechCrunch reported Mercor generated $6 million of profit in the first half of 2025, citing Forbes. | Medium | SI012 |
| CI014 | KTVU quoted Brendan Foody saying Mercor had crossed a $100 million revenue run rate by March 2025 and was extremely profitable. | Medium | SI014 |
| CI015 | Mercor's 2026 payments-systems engineering post said the company crossed a $1 billion annualized revenue run rate earlier in 2026. | Medium | SI006, SI015 |
| CI016 | The same 2026 post said Mercor was paying out more than $2 million each day to more than 30,000 weekly active contractors. | Medium | SI006 |
| CI017 | By October 2025, Mercor said it had more than 30,000 contractors and was paying over $1.5 million per day to them. | High | SI005, SI013 |
| CI018 | TechCrunch reported Mercor's headline revenue includes the full amount customers pay before contractors receive their portion. | Medium | SI012 |
| CI019 | TechCrunch said Mercor management framed that gross presentation as common among peers such as Surge AI and Scale AI. | Medium | SI012 |
| CI020 | TechCrunch reported Mercor earns money through an hourly finder's fee and matching rate layered onto expert work. | Medium | SI012 |
| CI021 | TechCrunch reported some Mercor experts earned as much as $200 per hour for AI training work. | Medium | SI016 |
| CI022 | Mercor's fetched homepage showed finance or investor-relations experts at $80-$160 per hour and equity research experts at $120 per hour. | Medium | SI001 |
| CI023 | Mercor's careers page describes the company as a profitable Series C company and, when fetched, showed six finance roles alongside 32 engineering roles. | Medium | SI003 |
| CI024 | Mercor said its Series C capital would expand the talent network, improve matching, and speed delivery. | High | SI005, SI013 |
| CI025 | Mercor said its Series B capital would accelerate its ability to match billions of people with their calling. | Medium | SI004 |
| CI026 | TechCrunch reported an outsized share of Mercor's revenue came from a subset of major brands including OpenAI, indicating concentration risk. | Medium | SI012 |
| CI027 | TechCrunch's April 2026 breach coverage said paused Meta contracts and customer reviews could put meaningful revenue at risk. | Medium | SI017 |
| CI028 | Scale AI's September 2025 lawsuit described one customer opportunity as a contract worth millions of dollars to Mercor. | Medium | SI018 |
| CI029 | Court records show Scale AI filed suit against Mercor on September 3, 2025 and later voluntarily dismissed the case with prejudice by early January 2026. | High | SI018, SI019, SI020 |
| CI030 | Appen's investor-relations page shows public incumbents in this category publish full-year and half-year results, unlike Mercor. | Medium | SI023 |
| CI031 | Appen publicly describes itself as serving AI lifecycle work with a global crowd of over 1 million contributors and real-world model evaluation. | High | SI023, SI024 |
| CI032 | Appen's model-evaluation page shows hallucination benchmarking, regulatory audits, and continuous monitoring are monetizable service lines in this market. | Medium | SI024 |
| CI033 | California's AB 5 text underscores that contractor-heavy marketplaces still face worker-classification compliance risk. | Medium | SI025 |
| CI034 | CNBC reported OpenAI and Google were pulling back from Scale AI after Meta's investment, creating a near-term demand-dislocation opportunity for alternatives. | High | SI021, SI027 |
| CI035 | CNBC reported Scale AI later cut 14% of its workforce while trying to win back customers that had slowed work, highlighting category volatility. | Medium | SI022 |
| CI036 | Mercor's payments-systems post says its infrastructure must invoice clients across multiple complex billing structures and contractual terms while paying contractors globally. | High | SI006, SI007 |
| CI037 | That same engineering post says hypergrowth exposed gaps in data models and controls, forcing more investment in financial operations and correctness. | Medium | SI006 |
| CI038 | Public AI-spending and annotation-market proxies show the broader category remains large, but those top-down figures do not reveal Mercor's take rate, burn, or cash conversion. | Medium | SI028, SI029 |
| CI039 | Mercor's public blog now spans company, research, stories, and engineering categories, consistent with management publicly treating payments and controls as scaling priorities rather than back-office details. | Medium | SI026, SI006 |
| CE001 | Mercor says it develops benchmarks, evaluation environments, and large-scale human datasets through a marketplace of top-tier experts. | High | SE003, SE007 |
| CE002 | Mercor's research page says the company is used by the top five AI labs and six of the Magnificent Seven. | Medium | SE003 |
| CE003 | Mercor's experts page presents the product as remote, high-paying expert work that advances AI systems. | High | SE001, SE002 |
| CE004 | Mercor's careers page says every team works directly with frontier models. | Medium | SE004 |
| CE005 | The careers page listed research-engineering roles focused on environments, data and post-training as well as benchmarking, evals, and failure analysis. | Medium | SE004 |
| CE006 | The same careers page listed infrastructure, payments, security, application-security, automation, cloud-infrastructure, site-reliability, and agents roles. | Medium | SE004 |
| CE007 | Mercor said its Series C capital would expand the talent network, improve matching, and speed delivery. | High | SE006, SE033 |
| CE008 | Mercor's Series B post said the team included the former Head of Human Data Operations at OpenAI and the previous Head of Growth at Scale. | Medium | SE005 |
| CE009 | Mercor's APEX family now spans APEX, APEX-Agents, APEX-SWE, and ACE. | High | SE003, SE007 |
| CE010 | Mercor's APEX-SWE post says the benchmark was created with Cognition to test real software engineering work rather than narrow coding tasks. | High | SE008, SE009 |
| CE011 | Mercor's APEX-SWE leaderboard says the benchmark contains 200 cases split between integration and observability tasks. | Medium | SE009 |
| CE012 | The same leaderboard says each task has a human-authored rubric grading functional requirements, robustness, and code style. | Medium | SE009 |
| CE013 | Mercor says it open-sourced 50 in-distribution APEX-SWE cases plus the evaluation harness. | Medium | SE009 |
| CE014 | At release, Mercor reported GPT-5.3 Codex as the top APEX-SWE model at 41.5% Pass@1. | High | SE008, SE009 |
| CE015 | Mercor's APEX-SWE post says developers spend only 16% of their time writing code and 84% on CI/CD, infrastructure, deployment, and debugging. | Medium | SE008 |
| CE016 | Mercor's APEX-Agents post says the benchmark tests long-horizon, cross-application tasks in investment banking, consulting, and corporate law. | Medium | SE010 |
| CE017 | Mercor said the APEX-Agents design began with surveys of hundreds of experts from firms including Goldman Sachs, McKinsey, and Cravath. | Medium | SE010 |
| CE018 | Mercor's expanded APEX post says the heldout evaluation set doubled from 200 to 400 cases. | Medium | SE011 |
| CE019 | The same post says APEX tasks take more than two and a half hours on average for seasoned professionals and contributors typically had over seven years of experience. | Medium | SE011 |
| CE020 | Mercor's Enterprise AI post says many enterprise agent projects stall because teams guess the use case, hand-write prompts, and lack evidence of real workflow value. | Medium | SE012 |
| CE021 | Mercor's RL-environment post argues that academic evals saturate and economically valuable work increasingly requires richer real-world environments and tools. | Medium | SE015 |
| CE022 | Mercor's Monty engineering post says someone starts an interview every nine seconds, creating roughly 10,000 conversations a day lasting about 15 minutes each. | Medium | SE013 |
| CE023 | The Monty post says each interview session runs in its own container on Modal. | Medium | SE013 |
| CE024 | The same post says Mercor keeps about 30 compute-prebooted containers and about 10 fully initialized interview environments, allowing starts in well under 200 milliseconds. | Medium | SE013 |
| CE025 | Mercor's Contracts-service post says a critical service rewrite made the system more than 10,000 times more capable and over 75 times more reliable. | Medium | SE014 |
| CE026 | That post says the old Contracts system had been tuned for about 3,000 active contracts a month, 20 to 50 concurrent requests, and roughly 100-second completions. | Medium | SE014 |
| CE027 | Mercor's data-and-AI policy says the platform collects résumés, interview audio and video, AI transcripts, public profile data, and payment or tax details. | Medium | SE017 |
| CE028 | The same policy says Mercor uses that data for matching, interviews, payouts, compliance, and communication. | Medium | SE017 |
| CE029 | Mercor's LLM Usage Policy prohibits contractors from using LLMs to assess model outputs or predict code behavior. | Medium | SE018 |
| CE030 | Mercor's background-check policy says it verifies identity, education, employment history, and relevant licenses or certifications. | Medium | SE019 |
| CE031 | Mercor's time-tracking guide says project workers use the Workpuls or Insightful desktop tool to record task time. | Medium | SE020 |
| CE032 | Mercor's payments guide says Stripe is the primary payment rail and Wise is sometimes used for one-time or fallback payments. | Medium | SE021 |
| CE033 | OpenAI's InstructGPT work is direct technical evidence that human feedback remains foundational to aligning capable models. | Medium | SE022 |
| CE034 | OpenAI's custom-model and fine-tuning announcement shows enterprises are buying tailored model-training workflows rather than only raw API access. | Medium | SE023 |
| CE035 | Anthropic's Constitutional AI paper shows AI-generated feedback can automate part of alignment, but still depends on carefully designed oversight and objectives. | Medium | SE024 |
| CE036 | Appen's Frontier Alignment page says domain-expert RLHF now spans medicine, law, science, finance, preference ranking, and multi-turn evaluation. | Medium | SE025 |
| CE037 | Appen's agentic-AI page markets golden trajectories, RL environment design, failure taxonomies, and SWE-driven deep evaluation workflows. | Medium | SE026 |
| CE038 | Appen's model-evaluation page markets hallucination benchmarking, regulatory audits, continuous monitoring, and LLM-as-a-judge rubric design. | Medium | SE027 |
| CE039 | iMerit's RLHF tooling overview says automation platforms exist to address human-labeling bottlenecks, reward-model complexity, and safety-compliance issues. | Medium | SE028 |
| CE040 | Toloka markets context-rich simulated environments, RL gyms with MCP replicas, computer-use testbeds, and expert-captured workflows for AI agents. | Medium | SE029 |
| CE041 | Scale AI's RLHF page shows incumbent competitors also sell expert human-feedback workflows, which limits differentiation from website copy alone. | Medium | SE030 |
| CE042 | TechCrunch reported Mercor handles custom datasets and processes that AI model makers consider trade-secret-sensitive. | Medium | SE031 |
| CE043 | TechCrunch's April 2026 breach story said attackers claimed access to source code, API keys, candidate data, and employer data from Mercor's systems. | Medium | SE032 |
| CE044 | Taken together, Mercor's careers page, engineering posts, benchmark pages, and docs imply the product surface now spans marketplace matching, AI interviewing, benchmark creation, enterprise agent design, payouts, and trust or compliance operations. | Medium | SE004, SE007, SE012, SE013, SE014, SE016, SE017, SE020, SE021 |
| CU001 | Mercor reported $450 million in annualized revenue in September 2025, up from $2 million daily earlier that year. | High | SU003, SU011 |
| CU002 | Mercor closed a $350 million Series C at a $10 billion valuation in October 2025. | High | SU004, SU007, SU010 |
| CU003 | Mercors primary customers are AI labs and technology companies that need large-scale training-data annotation and evaluation. | Medium | SU005, SU012, SU017 |
| CU004 | Scale AI was Mercors direct predecessor in serving major AI labs including OpenAI and Google, and those customers subsequently reduced Scale AI work. | Medium | SU008, SU009 |
| CU005 | Mercor launched an Enterprise AI product in early 2025 targeting large organizations that want AI-assisted hiring and workforce solutions. | Medium | SU018 |
| CU006 | Mercor grew revenue roughly 30x in 2025, going from approximately $2 million per month to $2 million per day. | Medium | SU016, SU003 |
| CU007 | The Series A in February 2024 raised $34 million and was used to deepen AI lab customer relationships. | Medium | SU001, SU029 |
| CU008 | Bloomberg described Mercor as the default sourcing partner for AI labs building training datasets as of April 2026. | Medium | SU012 |
| CU009 | Public sources show two separate scale signals: CNBC said Mercor had processed 300,000 candidates by February 2025, and Mercor later said it had more than 30,000 experts on its roster by October 2025. | Medium | SU006, SU014 |
| CU010 | The talent portal at talent.docs.mercor.com documents project onboarding flows, suggesting structured customer-facing deployment processes. | Medium | SU023, SU024 |
| CU011 | Scale AI sued Mercor in September 2025 alleging trade secret misappropriation; this signals direct competition for the same AI-lab customer base. | Medium | SU027 |
| CU012 | Mercor appeared on Forbes AI Cloud 100 in 2025, reflecting recognition of its customer base quality among AI-sector analysts. | Medium | SU011 |
| CU013 | Mercor offered AI researchers the ability to test models with domain-expert evaluators as part of its Experts product line. | Medium | SU020, SU005 |
| CU014 | At TechCrunch Disrupt 2024 Mercor demonstrated live AI evaluation workflows, showcasing its customer-facing capabilities. | Medium | SU017 |
| CU015 | Mercors early customers were startups and mid-size AI companies; the customer base has since expanded to include top-tier frontier AI labs. | Medium | SU019, SU005 |
| CU016 | Mercors Series B in February 2025 valued the company at $2 billion, with investor confidence driven by AI-lab customer traction. | Medium | SU002, SU006 |
| CU017 | Rest of World reported that data annotation workers often struggled to meet quality requirements, pointing to supply-side retention challenges. | Medium | SU026 |
| CU018 | Mercors worker onboarding documentation indicates structured project ramp-up periods and milestone-based access to new projects. | Medium | SU024 |
| CU019 | KTVU reported Mercors founding story emphasizing direct outreach to AI labs as the initial customer acquisition strategy. | Low | SU025 |
| CU020 | Mercors Research portal lists open-domain AI research evaluation as a customer-facing service, indicating diversification beyond annotation. | Medium | SU022 |
| CU021 | A reported $450M ARR run rate in September 2025 implies concentration risk if even one or two top-10 customers reduce spend. | Medium | SU003, SU010 |
| CU022 | OpenAI and Google both reduced spend with Scale AI within months of Mercors rapid growth, suggesting platform-switching risk exists at scale. | Medium | SU008, SU009 |
| CU023 | No public churn rate, net revenue retention, or cohort data has been disclosed for Mercors AI-lab customer segment. | Low | SU003, SU012 |
| CU024 | Mercors enterprise product announcement in 2025 suggests the company is attempting to diversify beyond annotation into broader workforce management. | Medium | SU018, SU022 |
| CU025 | The talent portal documentation suggests Mercor uses contractual milestone gates to control project access, a structural retention mechanism for workers. | Medium | SU023, SU024 |
| CU026 | Mercors revenue per worker is not publicly disclosed, making it impossible to assess expansion revenue dynamics from existing accounts. | Low | SU014, SU030 |
| CU027 | Mercor launched Apex, a premium software-engineering evaluation product that benchmarks AI coding models using human expert assessors. | Medium | SU031, SU032 |
| CU028 | The Apex SWE leaderboard publicly ranks AI coding models evaluated on real tasks by Mercor experts, functioning as a customer-facing proof of methodology rigor. | Medium | SU032 |
| CU029 | Mercors Series C raised $350 million in new capital based on TechCrunch reporting of the round and pre- and post-money valuations. | Medium | SU004, SU030 |
| CU030 | Turing AI, a comparable crowdwork and AI annotation platform, was valued at $2.2 billion in March 2025, roughly 20% of Mercors October 2025 valuation, indicating investor premium for Mercors scale and customer quality. | Medium | SU033 |
| CU031 | Mercors company-disclosed blog post describes the revenue trajectory as going from $2M per month in early 2025 to $2M per day later in the year, a primary-source corroboration of the $450M ARR figure. | Medium | SU016 |
| CU032 | Mercors Series C blog post describes the round as driven by customer momentum and demand from AI labs, confirming that customer growth was the primary raise catalyst. | Medium | SU030 |
| CU033 | Forbes profiles of the Mercor founders note direct relationships with AI lab procurement teams, indicating a high-touch enterprise sales motion from inception. | Medium | SU010, SU011 |
| CU034 | The Apex leaderboard evaluation data is produced from actual AI lab customer projects submitted for benchmarking, serving as indirect customer-proof evidence that frontier labs are active platform users. | Medium | SU031, SU032 |
| CU035 | Mercors homepage documents multiple distinct product lines — Annotation, Evaluation, Experts, Apex, and Enterprise — confirming a multi-product customer engagement strategy targeting different buyer segments. | Medium | SU021, SU020 |
| CR001 | The US Department of Labors 2024 independent contractor rule tightens the economic-reality test, increasing reclassification risk for platforms using gig workers. | High | SR001, SR002 |
| CR002 | Californias AB 5 applies the ABC test to worker classification; Mercors annotator workforce likely faces scrutiny under this law if operating in California. | High | SR003, SR004, SR005 |
| CR003 | The California Supreme Courts 2024 clarification of AB 5 scope in a major trucking case signals continued judicial willingness to expand gig-worker protections. | Medium | SR007 |
| CR004 | The EU AI Act (2024) imposes obligations on providers of AI systems used in employment contexts; Mercors AI-assisted matching tools may fall within scope. | Medium | SR010 |
| CR005 | Scale AI filed a trade secrets lawsuit against Mercor and a former employee in September 2025, alleging misappropriation of proprietary customer and pricing data. | High | SR015, SR016, SR017 |
| CR006 | A class-action lawsuit was filed against Mercor in April 2026 alleging negligent data security practices following a confirmed cyberattack that exposed user personal data. | High | SR011, SR012, SR013 |
| CR007 | TechCrunch confirmed in March 2026 that Mercor suffered a cyberattack that exposed personal data of some users; the company disclosed the incident publicly. | High | SR014, SR021 |
| CR008 | Mercor maintains a Trust Center at trust.mercor.com, indicating some level of security-posture documentation and compliance program existence. | Medium | SR026 |
| CR009 | NIST Cybersecurity Framework version 2 (2024) establishes best-practice controls for organizations handling sensitive personal data; Mercor has not disclosed conformance. | Medium | SR008 |
| CR010 | Mercors talent portal contract policy documents indicate workers are engaged as independent contractors under written service agreements. | Medium | SR028, SR029 |
| CR011 | Mercors tax and work-authorization policy requires workers to self-certify eligibility; this shifts classification and tax risk to workers rather than the platform. | Medium | SR027 |
| CR012 | Scale AIs reduction in workforce by 14% following loss of OpenAI and Google contracts illustrates how customer concentration can cause rapid organizational stress. | Medium | SR024, SR018 |
| CR013 | Rest of World documented quality-control challenges among AI annotation workers broadly, suggesting systematic quality risk across the annotation industry. | Medium | SR022, SR023 |
| CR014 | Mercors blog post about handling 10x volume growth in one week reveals operational scaling risks and the absence of pre-built capacity buffers. | Medium | SR031 |
| CR015 | Mercor has not disclosed whether it carries cyber liability insurance, errors-and-omissions coverage, or workers compensation insurance for its contractor base. | Low | SR026, SR030 |
| CR016 | The workers compensation implications of AB 5 are specifically addressed by Californias DIR; Mercors annotators may qualify for coverage under certain interpretations. | Medium | SR006, SR004 |
| CR017 | Time magazine documented wage and working-condition concerns among AI data annotators working for Scale AI in India, raising analogous questions for Mercors global workforce. | Medium | SR032 |
| CR018 | No public SOC 2 report, ISO 27001 certification, or third-party security audit has been published for Mercor; the Trust Center does not disclose certifications. | Low | SR026 |
| CR019 | CNBC reported Scale AIs founder departure in June 2025; this destabilization of the largest competitor creates both opportunity and execution risk for Mercor. | Medium | SR025 |
| CR020 | Mercors Data and AI Usage policy at talent.docs.mercor.com indicates that annotator-produced data is owned by the customer, not the worker — a key IP and liability structure. | Medium | SR030 |
| CR021 | The CourtListener docket for the 2026 class action shows the case was filed in the Northern District of California and remains active as of May 2026. | High | SR012, SR013 |
| CR022 | TechCrunch noted in April 2026 that the data breach and Scale AI litigation arriving in the same month created compounding reputational risk for Mercor. | Medium | SR021 |
| CR023 | The IRS worker-classification guidance requires multi-factor analysis; Mercors reliance on worker self-certification may not insulate it from federal reclassification. | Medium | SR002 |
| CR024 | Mercors legal support documentation at talent.docs.mercor.com provides a dispute resolution pathway for workers, suggesting awareness of contractor-relation legal exposure. | Medium | SR029 |
| CR025 | Worker misclassification penalties under California law can include back wages, benefits, and penalties; against a publicly disclosed roster of more than 30,000 experts, the exposure could still be material. | Medium | SR003, SR004, SR006 |
| CR026 | Reuters reported that OpenAI wound down its Scale AI work in June 2025; Scale AIs subsequent 14% headcount reduction illustrates how a single customer decision can affect a platform at Mercors scale. | High | SR018, SR024 |
| CR027 | Mercors PACER docket for the Scale AI trade-secret case shows ongoing discovery activity as of early 2026, indicating the litigation is not close to resolution. | Medium | SR019, SR020 |
| CR028 | The EU AI Act risk classification for AI-assisted employment matching is likely high-risk, requiring conformity assessment before market deployment in the EU. | Medium | SR010 |
| CR029 | Rest of World and Time reporting on annotation worker conditions suggest Mercor faces reputational risk from association with below-market pay for global contractors. | Medium | SR022, SR032 |
| CR030 | Mercors Trust Center existence indicates basic security governance, but the absence of disclosed certifications leaves material uncertainty about actual security controls. | Medium | SR026, SR008 |
| CR031 | The California AB 5 taxes and work-authorization FAQ from FTB specifically addresses multi-state workers, directly relevant to Mercors cross-state contractor base. | Medium | SR003, SR027 |
| CR032 | Mercors rapid scaling post documents that the platform faced queue failures and worker-matching errors during a 10x volume spike, revealing infrastructure fragility. | Medium | SR031 |
| CR033 | Mercor raised a $350M Series C in October 2025 at a $10B valuation; no burn rate, annual OpEx, or runway figure has been disclosed, creating opacity around financial model risk. | Medium | SR033 |
| CR034 | TechCrunch reported a $450M annualized revenue run rate in September 2025, implying a 22x revenue multiple at the $10B Series C valuation — highly sensitive to any revenue deceleration. | Medium | SR034, SR035 |
| CR035 | Mercors business model depends on sustained enterprise AI training budgets; a slowdown in AI capital expenditure by frontier labs would directly reduce demand for annotation services. | Medium | SR034, SR033 |
| CR036 | A 22x revenue multiple creates significant valuation compression risk; even modest revenue deceleration could reset the valuation anchor and complicate future fundraising. | Medium | SR033, SR034 |
| CR037 | Global contractor payroll at scale for a publicly disclosed roster of more than 30,000 experts creates working-capital demands and cross-border payment risks including FX volatility, sanctions exposure, and payment-rails failure. | Medium | SR027, SR028 |
| CR038 | Legal defense costs for two simultaneous cases (Scale AI trade secrets and Gill class action) consume management bandwidth and cash without disclosed reserve allocation. | Medium | SR005, SR006, SR015 |
| CR039 | A single large-customer revenue departure — analogous to OpenAI leaving Scale AI — could reduce Mercors ARR by an estimated 20-40%, based on industry concentration norms at this stage. | Low | SR018, SR024, SR026 |
| CR040 | Key monitoring indicators for Mercors thesis break include: AB 5 enforcement action opened, second material breach, an adverse court finding or new trade-secret dispute, ARR growth <50% YoY, or customer-concentration ratio >70%. | Medium | SR033, SR035 |
| CV001 | Mercor announced a $30 million Series A at a $250 million valuation in 2024. | Medium | SV001 |
| CV002 | Mercor announced a $100 million Series B at a $2 billion valuation in February 2025. | High | SV002, SV003, SV004, SV005 |
| CV003 | Mercor announced a $350 million Series C at a $10 billion valuation in October 2025. | High | SV006, SV007 |
| CV004 | Mercor's total disclosed primary capital across seed, Series A, Series B, and Series C is about $483.6 million. | Medium | SV001, SV002, SV006 |
| CV005 | TechCrunch reported Mercor had reached a $75 million annual recurring revenue run rate by February 2025. | Medium | SV003 |
| CV006 | TechCrunch reported Mercor was approaching a $450 million annualized revenue run rate in September 2025. | Medium | SV008 |
| CV007 | Mercor's March 2026 engineering post said the company had crossed a $1 billion annualized revenue run rate earlier in 2026. | Medium | SV009 |
| CV008 | TechCrunch reported Mercor's headline revenue includes the full amount customers pay before contractors receive their share. | Medium | SV008 |
| CV009 | Mercor said in October 2025 that it had more than 30,000 contractors and was paying more than $1.5 million per day to them; its 2026 engineering post raised that daily payout figure above $2 million. | High | SV006, SV007, SV009 |
| CV010 | TechCrunch Disrupt 2025 coverage named OpenAI, Anthropic, and Meta as Mercor customers and said the company had increased annualized recurring revenue to roughly $500 million while remaining profitable. | Medium | SV010 |
| CV011 | TechCrunch reported that Mercor was affected by the LiteLLM supply-chain attack and said the company brought in third-party forensics experts. | Medium | SV011 |
| CV012 | TechCrunch reported that Meta paused contracts with Mercor after the breach while other customers reviewed their relationships. | Medium | SV012 |
| CV013 | Claim Depot said the breach litigation alleged exposure of personal data for more than 40,000 people and noted multiple federal class actions tied to the incident. | Medium | SV013 |
| CV014 | Scale AI sued Mercor and former Scale employee Eugene Ling in September 2025 over alleged trade-secret and customer-material misuse. | High | SV014, SV015, SV016 |
| CV015 | PacerMonitor shows the Scale AI lawsuit was voluntarily dismissed with prejudice in January 2026. | Medium | SV017 |
| CV016 | Mercor's research page says the company is used by the top five AI labs and six of the Magnificent Seven. | Medium | SV018 |
| CV017 | Mercor's experts page and contractor docs show a weekly payout system that relies on Stripe or Wise, time tracking, screenshot review, and human judgment over disputed hours. | Medium | SV019, SV023 |
| CV018 | Mercor's supported-countries policy shows that payment coverage depends on Stripe or Wise jurisdiction support and that some countries are unsupported. | Medium | SV024 |
| CV019 | Mercor's assessments page says assessments are now a primary entry point to work on the platform and can qualify talent for multiple roles. | Medium | SV025 |
| CV020 | Mercor's RL Studio documentation describes an internal production system with projects, worlds, task states, reviewer flows, and approval tracking. | Medium | SV026 |
| CV021 | Mercor's research, Enterprise AI, and APEX pages show the company is trying to move from pure expert supply toward benchmark, evaluation, and workflow infrastructure. | Medium | SV018, SV020, SV021, SV022 |
| CV022 | Appen's public product pages show the category already converging around expert RLHF, agent trajectories, regulatory audits, and model-evaluation workflows rather than commodity labeling alone. | Medium | SV028, SV029, SV030 |
| CV023 | Stanford's 2025 AI Index and MarketsandMarkets both point to ongoing AI-investment and data-annotation demand growth, which supports continued category expansion. | Medium | SV031, SV040 |
| CV024 | As of May 2026, Appen's market cap was about $0.23 billion against roughly $0.23 billion of revenue, implying about a 1x revenue multiple. | Medium | SV032, SV033 |
| CV025 | As of May 2026, Upwork's market cap was about $1.08 billion against roughly $0.79 billion of revenue, implying about a 1.4x revenue multiple. | Medium | SV034, SV035 |
| CV026 | As of May 2026, Fiverr's market cap was about $0.39 billion against roughly $0.42 billion of revenue, implying about a 0.9x revenue multiple. | Medium | SV036, SV037 |
| CV027 | As of May 2026, Palantir's market cap was about $328.14 billion against roughly $5.22 billion of revenue, implying roughly a 63x revenue multiple. | Medium | SV038, SV039 |
| CV028 | Public labor-market and data-service comps trading around 1x revenue imply Mercor's $10 billion mark cannot be defended on marketplace economics alone. | Medium | SV032, SV033, SV034, SV035, SV036, SV037 |
| CV029 | Palantir-like software multiples show how much upside exists if Mercor proves durable software-control characteristics, but that outcome requires very different evidence from a labor marketplace. | Medium | SV038, SV039, SV020, SV021, SV022 |
| CV030 | Public evidence indicates Mercor still depends on a small number of frontier AI labs for most of its revenue and does not disclose retention metrics. | Medium | SV008, SV010, SV012 |
| CV031 | Mercor's public materials and media coverage still do not disclose audited net revenue, take rate, gross margin, burn, or cash on hand. | Medium | SV002, SV006, SV008, SV009 |
| CV032 | At $10 billion versus the September 2025 $450 million annualized run-rate figure, Mercor trades at about 22x gross revenue. | Medium | SV006, SV008 |
| CV033 | If Mercor's own 2026 $1 billion annualized revenue claim were verified, the $10 billion mark would imply about a 10x gross revenue multiple, but that figure would still be unaudited and gross of contractor payouts. | Medium | SV008, SV009 |
| CV034 | Breach fallout, customer concentration, and labor or legal exposure make Mercor's downside more asymmetric than pure software comp sets suggest. | Medium | SV011, SV012, SV013, SV014, SV018, SV023, SV024 |
| CV035 | The bull case requires Mercor's benchmark and workflow products to become sticky enough to lift margin, reduce concentration, and support a partial software rerating. | Medium | SV018, SV020, SV021, SV022, SV025, SV026 |
| CV036 | The base case assumes revenue keeps growing but the valuation multiple compresses somewhat because benchmark attach, net revenue quality, and post-breach trust are only partially proven. | Medium | SV008, SV011, SV012, SV020, SV021, SV022 |
| CV037 | The bear case is a reset toward services or labor-platform multiples if a top customer is lost, security issues persist, or contractor and legal costs rise. | Medium | SV011, SV012, SV013, SV014, SV023, SV024, SV032, SV033, SV034, SV035, SV036, SV037 |
| CV038 | Mercor's strongest public upside lever is benchmark and workflow evidence such as APEX, Enterprise AI, RL Studio, and assessments rather than simply adding more contractor volume. | Medium | SV020, SV021, SV022, SV025, SV026 |
| CV039 | Given the current evidence set, the most sensible recommendation is TRACK rather than BUY, with medium confidence and a high risk rating. | Medium | SV008, SV010, SV011, SV012, SV031, SV032, SV033, SV034, SV035, SV036, SV037, SV038, SV039 |
| CV040 | Mercor's valuation stance at the $10 billion mark is stretched until the company discloses cleaner net-revenue, concentration, and trust-remediation evidence. | Medium | SV008, SV011, SV012, SV023, SV032, SV033, SV034, SV035, SV036, SV037 |
| CV041 | A price closer to roughly $6 billion to $7.5 billion, or audited proof of software-like economics at the current mark, would make the setup materially more investable. | Medium | SV008, SV009, SV020, SV021, SV022, SV032, SV033, SV034, SV035, SV036, SV037, SV038, SV039 |
| CV042 | Final diligence should focus on net revenue and take rate, top-10 customer mix, post-breach security controls, and contractor or legal exposure before any buy call. | Medium | SV011, SV012, SV013, SV017, SV023, SV024, SV027 |