Optimizely

Name: Optimizely
Brand: Optimizely

Optimizely is on a mission to make the lives of marketers better with Optimizely One, the world’s first operating system for marketing teams

Est 2010|Valuation $1.2B|Raised $338.6M|89 Ref Customers

LinkedIn 182K|Web traffic 1.0M|FTEs 1,500|HQ New York, New York, US

MarketsConversion Rate Optimization (CRO) & A/B Testing Marketing Automation Platforms A/B Testing & Experimentation

01Competitive Landscape

Narrative competitive analysis

- Optimizely vs VWO (web experimentation/CRO): VWO emphasizes packaged capabilities and public pricing, which can reduce buyer friction. Optimizely is commonly chosen for enterprise governance needs and for organizations evaluating consolidation of content and experimentation tools, but buyers report concerns about price transparency and complexity. - Optimizely vs Statsig (feature flags/product experimentation): Statsig targets engineering-first teams with transparent pricing and data-platform integrations. Optimizely offers a broader DXP suite and a free Rollouts tier for feature flagging, which can be useful for teams evaluating feature management plus content capabilities. - Optimizely vs Adobe Target (enterprise personalization/testing): Adobe Target is often considered by organizations standardized on the Adobe Experience Cloud. Differentiation generally depends on ecosystem fit and specific enterprise requirements rather than purely feature parity.

	Optimizely (Experimentation)	VWO	Statsig
Starting Price	Custom quote for paid plans; free Rollouts exists for feature flags	Public pricing page exists (exact price depends on plan/usage)	Free tier plus a publicly listed paid Pro tier
Best For	Enterprise experimentation programs requiring governance and vendor ecosystem; organizations that may also evaluate CMS/DXP consolidation	Teams seeking a testing suite with more transparent packaging; typically SMB to mid-market (and some enterprise)	Product/engineering-led experimentation and feature flags with a usage-based model
Key Strength	Established web experimentation capabilities and a suite of DXP modules; compliance certifications are publicly stated	Public pricing and packaged offerings reduce buyer friction	Transparent pricing and engineering-centric workflows; integration with modern data stacks
Key Weakness	Price opacity; reported editor and reporting issues; complexity for smaller teams	Depth for high-end enterprise requirements may be less comprehensive; depends on specific needs	Not positioned as an integrated DXP/CMS platform; requires engineering and data maturity

01Competitive Landscape

Narrative competitive analysis

Optimizely vs VWO (web experimentation/CRO): VWO emphasizes packaged capabilities and public pricing, which can reduce buyer friction. Optimizely is commonly chosen for enterprise governance needs and for organizations evaluating consolidation of content and experimentation tools, but buyers report concerns about price transparency and complexity.
Optimizely vs Statsig (feature flags/product experimentation): Statsig targets engineering-first teams with transparent pricing and data-platform integrations. Optimizely offers a broader DXP suite and a free Rollouts tier for feature flagging, which can be useful for teams evaluating feature management plus content capabilities.
Optimizely vs Adobe Target (enterprise personalization/testing): Adobe Target is often considered by organizations standardized on the Adobe Experience Cloud. Differentiation generally depends on ecosystem fit and specific enterprise requirements rather than purely feature parity.

	Optimizely (Experimentation)	VWO	Statsig
Starting Price	Custom quote for paid plans; free Rollouts exists for feature flags	Public pricing page exists (exact price depends on plan/usage)	Free tier plus a publicly listed paid Pro tier
Best For	Enterprise experimentation programs requiring governance and vendor ecosystem; organizations that may also evaluate CMS/DXP consolidation	Teams seeking a testing suite with more transparent packaging; typically SMB to mid-market (and some enterprise)	Product/engineering-led experimentation and feature flags with a usage-based model
Key Strength	Established web experimentation capabilities and a suite of DXP modules; compliance certifications are publicly stated	Public pricing and packaged offerings reduce buyer friction	Transparent pricing and engineering-centric workflows; integration with modern data stacks
Key Weakness	Price opacity; reported editor and reporting issues; complexity for smaller teams	Depth for high-end enterprise requirements may be less comprehensive; depends on specific needs	Not positioned as an integrated DXP/CMS platform; requires engineering and data maturity