Statsig

1.1 Corporate Identity and Product Model

Statsig was established in 2021 in the Seattle metropolitan area to build a modern, unified product development platform combining enterprise feature flagging, statistical A/B testing, and integrated product analytics. Rather than forcing software engineering and product data organizations to stitch together disparate point solutions for release gating and analytics, Statsig introduced a single integrated architecture that supports both multitenant cloud software-as-a-service and warehouse-native deployments directly on Snowflake, BigQuery, and Databricks. At enterprise scale, the platform operates with high-throughput infrastructure, processing over one trillion events per day and evaluating approximately 2.5 billion unique monthly experiment subjects across more than 300 paying commercial accounts. Industry estimates indicated the business scaled to an annual recurring revenue run-rate of approximately $40 million by May 2025 before its acquisition, underpinned by an event-metered consumption model that expands alongside customer product rollout volumes.[CO001, CO009, CO010]

1.2 Founding Leadership and Governance Split

Statsig was founded by veteran technology executive Vijaye Raji, who previously accumulated almost a decade of software engineering leadership at Microsoft and later served as Vice President of Entertainment and Head of Facebook Seattle. Raji guided Statsig's rapid product iteration and culture of developer responsiveness, serving as founder, chief executive, and lead frontend developer. Following OpenAI's acquisition of Statsig in September 2025, Raji assumed the role of Chief Technology Officer of Applications at OpenAI. In May 2026, OpenAI executed a novel structural carve-out that transferred Statsig's commercial brand, customer relationships, and operational platform code to analytics provider Amplitude, while Raji and the original Statsig core engineering team remained at OpenAI. To steward platform continuity, Amplitude assigned Vice President of Product Management Chris Yu to lead a dedicated organization of approximately 50 personnel. However, this bifurcated arrangement has drawn criticism from industry observers and competitors, who argue that separating the operational software codebase from its original founding talent creates substantial key-person dependencies and technical support risks for customers.[CO002, CO005, CO006, CO011, CO012]

1.3 Capitalization History and Ownership Structure

Across its independent venture lifecycle, Statsig raised approximately $153.4 million in equity capital across three institutional funding rounds. The company completed a $10.4 million Series A round in August 2021 and a $43 million Series B round in April 2022, both led by Sequoia Capital with recurring participation from regional venture firm Madrona Venture Group. In May 2025, Statsig completed a $100 million Series C financing led by ICONIQ Growth at a post-money valuation of $1.1 billion, consisting of $80 million in primary corporate growth capital and $20 million in secondary liquidity for employee shareholders. Just four months later, in September 2025, OpenAI announced an agreement to acquire Statsig in an all-stock transaction valued at $1.1 billion, representing one of the largest corporate acquisitions in OpenAI's history. The ownership structure transitioned again in May 2026 when Amplitude entered into a definitive strategic partnership to take custody of the customer base, platform software, and operating revenue stream.[CO003, CO004, CO007, CO008]

1.4 Corporate Milestones and Integration Outlook

Statsig's evolution from an early-stage experimentation startup into a core infrastructure asset spans three distinct operating eras: independent venture expansion, incorporation into OpenAI's application development stack, and subsequent commercial absorption by Amplitude. While initial integration under OpenAI focused on utilizing Statsig's runtime evaluation tools for internal AI applications, the May 2026 transaction tasked Amplitude with operating the enterprise SaaS platform externally. In June 2026, Amplitude outlined its Phase 1 technical priorities, which focus on enterprise control and governance tooling, native Model Context Protocol integrations, and connecting Statsig's statistical engine with Amplitude's behavioral analytics pipeline. Critical diligence gaps remain, however, regarding post-deal gross margins, net revenue retention rates, and the contractual pricing terms that enterprise customers will face during their upcoming renewal cycles under Amplitude's consolidated governance.[CO003, CO004, CO005, CO013, CO014]

1.5 Exhibits

2.1 Market Boundary, Taxonomy, and Product Scope

Statsig operates across three converging categories in modern software delivery: feature management and progressive rollouts, statistical A/B experimentation, and integrated product analytics. Historically, software organizations procured discrete point solutions for each workflow: LaunchDarkly or Split for feature gating, Optimizely or VWO for experimentation, and Amplitude, Mixpanel, or Heap for user behavioral tracking. This fragmentation created substantial friction, including duplicated SDK network overhead, inconsistent user exposure logging, and time-consuming data pipeline synchronization between telemetry systems and experimentation engines. Statsig's core architectural thesis consolidates these layers into a single workflow where every feature flag rollout automatically acts as an instrumented experiment backed by built-in statistical evaluation. Additionally, Statsig pioneered Warehouse Native deployment, allowing enterprise data teams to compute experimental metrics directly inside cloud data warehouses like Snowflake, BigQuery, and Databricks without external ETL data egress. This boundary definition encompasses core developer-first experimentation and feature flags while explicitly excluding legacy visual web page builders, static configuration management, and general-purpose enterprise business intelligence suites.[CM001, CM008, CM009, CM010, CM011]

2.2 TAM, SAM, and Sizing Lenses Across Operating Models

Quantifying Statsig's addressable opportunity requires segmenting the broader software telemetry and experimentation landscape across multiple operational lenses. Traditional industry estimates often view A/B testing through a narrow web-optimization lens. According to Convert Experiences' 2026 market analysis, the standalone web-only experimentation total addressable market sits at approximately $1.0 billion with annual expansion slowing to roughly 10%, indicating maturation and saturation among traditional front-end marketing buyers. However, Statsig addresses a substantially larger technical market by serving engineering-led product development and integrating into modern data warehouse infrastructure. Sacra estimates that the broader cloud data warehouse analytics ecosystem exceeds $10 billion in annual enterprise spend. Within this intersection, the serviceable addressable market (SAM) for developer-first feature management and statistical experimentation is estimated between $350 million and $500 million, expanding at 15% to 20% annually. Constrained by customer maturity and high-velocity engineering requirements, Statsig's serviceable obtainable market (SOM) is estimated at $50 million to $75 million, anchored by its reported $40 million ARR base across over 300 enterprise accounts prior to acquisition.[CM004, CM005, CM011, CM012]

2.3 Enterprise Buyer Personas, Budget Ownership, and Procurement Patterns

Adoption of Statsig is characterized by distinct buyer and user personas across startup, scale-up, and enterprise tiers. At early-stage startups and growth teams, adoption is typically bottom-up and developer-led, initiated by engineering leads seeking to deprecate fragile internal config databases. Statsig's Free Developer tier, offering up to 1 million monthly tracked users (MTUs) and unlimited seats, acts as an effective low-friction adoption funnel. In mid-market and enterprise organizations, budget ownership shifts toward the VP of Product and Head of Data, who evaluate platforms based on statistical rigor (such as CUPED variance reduction) and the total cost of ownership across combined tooling. According to Vendr procurement transaction benchmarks, Statsig's commercial packaging scales primarily on unique MTUs exposed to flags or tests, combined with seat tiers. Mid-market teams on Pro contracts starting at $150/month commonly negotiate 15% to 25% annual contract discounts, while enterprise deployments exceeding 10M MTUs achieve 20% to 35% discounts against initial quotes. For regulated financial services and healthcare enterprises, the Chief Technology Officer and Chief Data Officer serve as critical gatekeepers, demanding warehouse-native architecture to satisfy stringent data residency, SOC 2, and GDPR governance constraints.[CM002, CM003, CM010, CM013]

2.4 Market Consolidation, Growth Drivers, and Post-M&A Diligence Gaps

The experimentation category has entered an era of rapid structural consolidation driven by macroeconomic budget rationalization and the rise of AI-assisted software generation. As generative AI dramatically cheapens code generation, the software engineering bottleneck has shifted from shipping features to verifying what works in production. Standalone point solutions unable to scale beyond simple front-end web tests have been absorbed by broader platforms: Datadog acquired Eppo for $220 million in May 2025, Harness acquired Split, and Everstone merged VWO with AB Tasty to create a private-equity rollup. Statsig followed an unprecedented dual-exit path: in September 2025, OpenAI acquired Statsig for $1.1 billion in stock to absorb its runtime control plane and talent, appointing founder Vijaye Raji as CTO of Applications. Subsequently, on May 5, 2026, Amplitude announced a strategic partnership assuming Statsig's brand, operational continuity, and customer relationships. While this handover ensures ongoing SaaS support, it introduces commercial friction and diligence uncertainty. Key operational metrics—including net revenue retention, contract renewal terms under Amplitude, and the long-term convergence of warehouse-native processing with Amplitude's event stream infrastructure—remain undisclosed to private market diligence.[CM006, CM007, CM008, CM014]

2.5 Exhibits

3.1 Competitive Landscape & Categorization

The competitive landscape surrounding Statsig divides into three primary architectures: dedicated enterprise feature management vendors, warehouse-native experimentation platforms, and all-in-one product analytics suites. Dedicated enterprise feature management incumbents like LaunchDarkly focus heavily on DevOps release workflows, fine-grained access governance, and extensive multi-language SDK ecosystems, but historically treat deep causal experimentation and post-release product analytics as secondary modules or add-on packages. In contrast, warehouse-native alternatives such as GrowthBook and Eppo operate directly against enterprise data warehouses—including Snowflake, BigQuery, and Databricks—avoiding redundant event pipelines while keeping data strictly within customer-controlled infrastructure. Specialized marketing tools like PulseCRO target non-technical growth teams with visual no-code page editors, contrasting with Statsig's developer-centric SDK architecture.[CP001, CP004, CP005, CP008, CP014]

3.2 Feature Capabilities & Statistical Architecture

Statsig differentiates its core offering by tightly unifying in-application feature flagging, product analytics, and an enterprise-grade statistical engine into a cohesive developer workflow. The platform provides automated sample-ratio mismatch diagnostics alongside advanced statistical methodologies, specifically CUPED variance reduction and sequential testing with always-valid p-values. These statistical treatments accelerate experiment velocity by reducing required sample sizes and experiment durations by 30% to 50% without inflating false-positive rates. Traditional enterprise suites like Adobe Analytics treat experimentation as an afterthought, relying on separate add-on tools such as Adobe Target with basic frequentist statistical frameworks. While open-source alternative GrowthBook also supports CUPED and local in-process SDK evaluation, Statsig's turnkey statistical automation provides immediate statistical rigor for engineering teams without requiring bespoke SQL pipeline development.[CP002, CP003, CP004, CP011, CP015]

3.3 Pricing Structures & Total Cost of Ownership

Total cost of ownership varies substantially based on the metric unit governing commercial billing. Statsig anchors its entry-level adoption on an unusually generous free tier granting 2 million events monthly across unlimited seats, followed by usage-based pricing scaling at approximately $400 per million events on self-service tiers. However, this event-based pricing structure can penalize teams utilizing the platform purely for operational feature flags rather than event-heavy behavioral analytics. Specialized challengers like Rollgate capitalize on this friction by pricing on flat SDK requests rather than analytics events, while providing default European Union data hosting across standard tiers. By contrast, Statsig restricts dedicated European Union data residency to custom enterprise agreements, forcing European teams on standard Pro tiers to address international data transfer compliance through standard contractual clauses.[CP006, CP007, CP011, CP012]

3.4 Switching Costs & Strategic M&A Risks

Switching barriers for Statsig customers center around deep code instrumentation, custom metric configurations, and historical experiment archives. Replacing Statsig requires engineering teams to rip and replace SDK calls embedded across production codebases, re-establish metric definitions in alternative BI or warehouse tools, and export experiment results before platform migrations. These technical switching barriers are compounded by acute roadmap uncertainty stemming from corporate ownership shifts. Following OpenAI's acquisition of Statsig in September 2025 to bolster AI-native evaluations, Amplitude acquired the Statsig brand and customer base in May 2026 while the core engineering team remained at OpenAI. This dual transfer creates long-term integration and support ambiguity as Amplitude executes a phased convergence into its own analytics product without the platform's original builders.[CP009, CP010, CP012, CP013]

3.5 Exhibits

4.1 Revenue Streams, Event Metering, and Pricing Mechanics

The retained evidence supports an event-linked software model, but not a complete current price book. TechCrunch reported that Statsig expanded its free feature-management allowance from 5 million to 500 million monthly events in February 2023 while keeping advanced analytics paid. A July 2025 company comparison described pricing as usage-based, without seat or monthly-active-user charges, but supplied no numeric rate card. Current technical documentation presents both Statsig-hosted and warehouse-native delivery. Sacra describes metering across feature-flag exposures, experiment participants, and analytics events; that is an analyst characterization rather than a disclosed contract schedule. Statsig's own educational material distinguishes ARR from total revenue, so the May 2025 $40 million ARR figure cannot be treated as accounting revenue.[CI001, CI003, CI004, CI006, CI009, CI016]

4.2 GTM Motion, Sales Efficiency, and Delivery Cost Structure

The 2023 free-tier expansion documents a product-led acquisition mechanism, not its conversion efficiency. Statsig's chief executive told TechCrunch that feature management was relatively inexpensive to operate, that large-customer analytics workloads carried significant costs, and that conversion by only a few free users could cover the free plan; no conversion cohort or contribution-margin schedule was supplied. Sacra says warehouse-native deployment can lower Statsig's infrastructure cost because analysis occurs inside a customer's data environment, but public evidence does not quantify the saving or prove a high-margin outcome. The assigned sources disclose no sales cycle, customer-acquisition cost, CAC payback, gross margin, or net retention. Those omissions prevent a reliable judgment on whether usage expansion produces attractive incremental economics.[CI001, CI002, CI005, CI008]

4.3 Public Traction, Capital Adequacy, and Corporate Transition

GeekWire reported Statsig's company-disclosed $40 million ARR in May 2025, and Sacra separately estimated $40 million ARR for that month and reported more than 300 paying customers. The agreement between those two sources does not replace an audited ARR bridge, and GeekWire said Statsig declined further financial detail or a profitability disclosure. Sacra reported that the $100 million Series C comprised $80 million of primary capital and $20 million of employee secondary sales, while GeekWire and Sacra put cumulative funding above $153 million. Funding raised is not cash available: none of the assigned sources provides current cash, burn, debt, runway, or post-close capital obligations. Convert, a competitor in experimentation software, later reported that Amplitude would take on the Statsig brand and customers in May 2026; its account makes renewal pricing and contract continuity diligence priorities, but is not an independent benchmark.[CI007, CI008, CI010, CI011, CI012, CI013, CI014, CI015, CI016]

4.4 Exhibits

5.1 Product Definition and Core Module Portfolio

Statsig defines its core product offering as a modern, unified product development platform that integrates five principal capabilities within a single console and software development kit. Rather than forcing engineering and growth teams to stitch together disparate point tools, Statsig consolidates feature management, A/B testing experimentation, product analytics, session replay, and warehouse-native analytics. This unified model is engineered to remove context switching between deployment and evaluation, allowing teams to wrap new capabilities in feature gates and observe downstream metric impacts immediately. Advanced capabilities such as CUPED variance reduction, sequential testing, dynamic configurations, autotune, and holdouts are natively embedded into the experimentation workflow. Founder Vijaye Raji framed this architectural approach around building a one-stop product-building platform that unifies conceiving, releasing, and observing software behaviors as rapid artificial intelligence adoption accelerates release velocity and behavioral complexity.[CE001, CE002, CE006, CE014]

5.2 Technology Architecture and Ingestion Operating Model

The underlying technical architecture of Statsig is structured around decoupled edge evaluation, high-throughput streaming ingestion, and flexible storage execution. Client and server SDKs download targeting payloads upon startup to execute feature gate checks and dynamic configuration evaluations locally, achieving sub-millisecond evaluation latency without network overhead. Telemetry from exposure checks and downstream user interactions streams through ingestion pipelines capable of processing over one trillion events daily at 99.99% system availability. Strategic partnerships with infrastructure providers like Databricks historically enabled Statsig to process tens of billions of daily data events through scalable lakehouse streaming pipelines without manual cluster intervention. For organizations with rigorous data sovereignty requirements, Statsig's Warehouse Native option evaluates experiment data directly within customer-hosted Snowflake, BigQuery, or Databricks instances, preventing sensitive raw event extraction while maintaining statistical rigor. APIs act as the essential connective tissue linking these modular microservices into a cohesive deployment model.[CE003, CE004, CE005, CE007]

5.3 Deployment Workflows and Developer Integration

Developer workflows center on minimal implementation friction and rapid iteration across multi-language codebases. Statsig provides over thirty open-source SDKs spanning major client, server, and content delivery network edge environments, supported by developer tooling including a Chrome debugger and automated migration assistants. Product and data teams leverage this developer surface to replace complex custom instrumentation with standardized event capture and automated experiment calculations. Enterprise case studies demonstrate tangible operational benefits: financial platform Brex reported a 50% time efficiency reduction for data scientists and a 20% analytics tooling cost reduction after consolidating onto Statsig's unified platform. In parallel, ecommerce operator Secret Sales demonstrated that deploying Statsig Warehouse Native reduced event underreporting from 10% to 1-2% by resolving client-side browser tracking limitations and running calculations directly on verified warehouse data.[CE006, CE008, CE009]

5.4 Technical Differentiation, Governance, and Platform Risks

Statsig differentiates technically through deep statistical sophistication and flexible data deployment, yet the platform faces operational critiques and substantial ownership governance risks. Competitors highlight that Statsig's metered event-volume pricing can penalize experimentation scale and that its proprietary statistics calculations lack the full query transparency of open-source SQL alternatives. More critically, corporate transitions have introduced significant technical uncertainty: following OpenAI's acquisition of Statsig in September 2025, the Statsig brand and customer base were transferred to Amplitude in May 2026 under a perpetual non-exclusive license, while the founding engineering team remained at OpenAI. Competitors like GrowthBook and Conductrics emphasize that this split creates acute roadmap, support, and maintenance risks as platform stewardship transitions to a new engineering organization. From a compliance perspective, Statsig supports SOC 2 Type II controls and GDPR requirements, leveraging customer warehouse boundaries to satisfy strict data governance standards.[CE010, CE011, CE012, CE013]

5.5 Exhibits

6.1 Customer Base Segmentation and Buyer Persona

Statsig's commercial penetration is concentrated within engineering-driven, product-led technology organizations where rapid experimentation directly impacts top-line business metrics. Third-party firmographic analysis of job listings and LinkedIn telemetry reveals that purchasing decisions are predominantly driven by Senior Product Managers (accounting for 18% of mentions) and Directors of Data Analytics (8%), with operational usage distributed across Senior Data Scientists (15%), Senior Product Analysts (12%), and Growth Engineers (10%). The customer roster exhibits a heavy structural skew toward mature venture-backed and public enterprises: companies utilizing Statsig are 1,216 times more likely to be at Series F and 768 times more likely to be at Series D or E funding than the baseline software population. By industry vertical, software development represents 36% of active accounts, followed by technology platforms at 12% and financial services at 12%, with mid-market firms (51 to 200 employees, 24%) and large enterprises (1,001 to 5,000 employees, 21%) forming the backbone of the deployed base.[CU001, CU002, CU003]

6.2 Adoption Trajectory, Enterprise Scale, and Usage Growth

Operational adoption has scaled from early developer-led feature flagging into high-throughput enterprise infrastructure. Independent research estimates that Statsig surpassed 300 paying customers and reached an estimated $40 million in ARR prior to its announced acquisition, supported by carrier-grade platform reliability. Production telemetry reflects immense daily workload throughput: Statsig's distributed services ingest and evaluate over 1 trillion events per day and touch 2.5 billion unique monthly experiment subjects across web, server, and mobile client endpoints. Technical adoption demonstrates high stickiness within complex multi-product environments, where organizations deploy Statsig alongside developer experience tools like DX and enterprise search platforms like Glean. Enterprise expansion is particularly pronounced among organizations adopting Statsig's Warehouse-Native architecture, which executes SQL-based statistical calculations directly inside customer Snowflake, BigQuery, and Databricks clusters without requiring third-party data extraction pipelines.[CU002, CU005, CU006, CU008, CU013]

6.3 Customer Durability, M&A Transition Friction, and Retention Scrutiny

While verified production case studies at Brex, Notion, Bluesky, and Secret Sales prove substantial operational benefits—including Brex's reported 50% data scientist time reduction and 20% analytics tooling cost savings—customer durability faces unprecedented structural friction. The May 2026 transaction structure fundamentally bifurcated Statsig's organization: Amplitude assumed commercial ownership of the Statsig brand, platform maintenance, and customer relationships, whereas OpenAI retained the founding engineering team, technical leadership, and statistical researchers. This split has sparked acute concern among enterprise buyers who chose Statsig specifically for its blistering engineering pace and developer intimacy. Competitors like Optimizely have publicly targeted this operational vulnerability, terming the orphaned platform a 'race car without a driver' and predicting support degradation and eventual product consolidation. Third-party telemetry indicates that 38 companies have already churned and 48 enterprise contracts face upcoming renewal within 90 days, creating an immediate test of customer retention.[CU007, CU009, CU010, CU011, CU012, CU014, CU015]

6.4 Exhibits

7.1 Ranked residual-risk view

The evidence supports a high-priority diligence focus on assurance visibility and configuration governance, not a claim that a breach or outage has occurred. Statsig says customer data can be sensitive, describes itself as SOC 2 Type II audited, and publishes risk-management and incident-response controls. RiscLens nevertheless reports that it could not confirm a public SOC 2 report and says its profile is based only on publicly observable, automated discovery. That conflict is best treated as an evidence-access gap: request the current report, scope, exceptions, bridge letter, and post-acquisition control ownership rather than interpreting public non-discovery as failed certification. The second risk tier covers live configuration, analytical validity, and availability. Statsig's own scale and uptime figures are unaudited company claims, while independent implementation guidance warns that a successful flag rollout alone does not prove that experiment analysis is correct. The heatmap is therefore qualitative and ranks diligence urgency, not observed incident frequency.[CR001, CR002, CR003, CR004, CR012, CR014, CR016]

7.2 Operational, security, and dependency exposure

Statsig describes layered mitigations: need-based production-data access, logged employee access, risk assessments, an incident-response plan, backups, multi-cloud infrastructure, and granular permissions. Recent company-issued release notes syndicated by Releasebot also describe narrower edit/delete permissions, project- and role-level MCP scopes, and a safer single-user override deletion path. These are meaningful controls, but they also identify the failure modes management is trying to contain: over-permissioned users or agents, concurrent configuration mutation, delayed detection, and recovery failure. Deployment choices shift rather than eliminate dependency. Hosted use depends on Statsig and cloud providers; the warehouse-native option depends on the customer's warehouse availability, permissions, query governance, and compute budget. Statsig further says it may use subprocessors and Amplitude affiliates. Public materials in the assigned pool do not quantify provider concentration, recovery objectives, subprocessor exposure, or the customer impact of an incident, so those fields remain diligence items rather than estimated facts.[CR004, CR005, CR006, CR007, CR008, CR009, CR010, CR011, CR015]

7.3 Mitigations, monitoring indicators, and thesis-break triggers

The investment case should be conditioned on evidence that controls operate, not merely that control descriptions exist. Before commitment, obtain current independent assurance, penetration-test and disaster-recovery summaries, the incident and material-outage history, recovery-time and recovery-point objectives, and a deployment-specific data-flow map. For live product risk, require approval workflows for high-impact gates, least-privilege MCP and console roles, reconciled assignment and exposure logs, sample-ratio-mismatch monitoring, pre-agreed stopping rules, and a tested rollback path. For warehouse-native economics, monitor query spend by experiment and reload because the 2026 release notes explicitly added cost-attribution tags to expose that spend. Thesis-break triggers should include an unremediated material assurance exception, failure to provide an incident record, repeated control bypass, unreconciled experiment data that changes decisions, missed contractual recovery objectives, or deployment costs that erase consolidation savings. Revenue burn, customer concentration, and contractual liability cannot be quantified from this chapter's pool and should remain open rather than receiving invented thresholds.[CR003, CR004, CR009, CR010, CR011, CR012, CR013, CR016]

7.4 Exhibits

8.1 Investment Thesis, Anti-Thesis, and Financing Context

Statsig presents a high-conviction product thesis centered on developer velocity, pairing feature management, A/B testing, and analytics into a single platform that delivers demonstrated operational efficiency gains for engineering organizations. The company's architectural innovation—specifically its warehouse-native deployment model—shields core margins by offloading analytical compute to customer-managed data warehouses. However, the investment anti-thesis is driven by extreme valuation pricing and competitive absorption. Statsig raised $153 million in cumulative venture capital across three financing rounds, including a $43 million Series B at a $420 million valuation in 2022 and a $100 million Series C in May 2025 led by Iconiq Growth alongside Sequoia Capital and Madrona Venture Group. The Series C set a $1.1 billion post-money valuation against $40 million in ARR, representing an expensive 27.5x multiple. Coupled with emerging competitive pressure from point-solution consolidation and open-source tooling, new standalone capital faces an unfavorable risk-reward profile, justifying an avoid stance with high conviction.[CV001, CV002, CV003, CV005, CV006, CV010, CV012, CV014]

8.2 Valuation Multiples, M&A Precedents, and Scenario Underwriting

Evaluating Statsig's $1.1 billion valuation against software industry benchmarks highlights significant valuation stretch. At $40 million in ARR, Statsig's 27.5x revenue multiple sits at more than double the prevailing median for high-growth private enterprise software vendors. M&A dynamics illustrate accelerating market consolidation: Statsig reportedly rejected an acquisition takeover bid from Datadog, after which Datadog acquired experimentation competitor Eppo for roughly $220 million to embed testing into its observability stack. Subsequently, OpenAI announced an agreement to acquire Statsig for $1.1 billion in stock, fundamentally altering the liquidity landscape. Under scenario underwriting, our base case yields a $700 million fair value at a normalized 10x ARR multiple assuming revenue expands to $70 million, indicating a 36% valuation haircut from Series C pricing. The bear case models contraction to $225 million if platform absorption accelerates, while the bull case requires expansion to $120 million ARR at an 18x multiple to achieve a $2.16 billion outcome.[CV002, CV003, CV004, CV007, CV008, CV009, CV011, CV013]

8.3 Exit Readiness, Diligence Priorities, and Thesis-Break Triggers

Statsig's exit trajectory has shifted permanently from an independent initial public offering to strategic absorption following OpenAI's announced $1.1 billion acquisition agreement. For prospective investors evaluating secondary transactions or synthetic exposure, critical diligence blind spots remain unresolved in public filings. Crucially, Statsig has not publicly disclosed gross margin profiles, net revenue retention (NRR) rates, customer acquisition cost (CAC) payback periods, or top-customer revenue concentration. These omissions prevent precise underwriting of cash flow durability. The underwriting thesis would break favorably if Statsig demonstrates verified NRR exceeding 130% alongside sustained revenue growth above 80% year-over-year while operating under independent commercial governance. Conversely, negative triggers include accelerating enterprise churn toward bundled observability features or severe renewal attrition following corporate ownership transitions.[CV003, CV004, CV009, CV010, CV011]

8.4 Exhibits