Optimizely pricing

About

Optimizely is a digital experience platform (DXP) vendor that sells a composable suite of marketing and web software to mid-market and enterprise teams. The suite spans an agentic CMS built on .NET Core, web and feature experimentation (the original Optimizely A/B-testing product, powered by a proprietary Stats Engine), a Content Marketing Platform, personalization, B2B commerce, a customer data platform, warehouse-native analytics, digital asset management, and a no-code AI Agent Platform branded around its Opal AI. Named customers on its own surfaces include The Wall Street Journal, Zillow, Yamaha’s Watercraft Group, Wonderbly and The Royal Mint.

The company reached its current shape by acquisition and rebrand: Episerver (CMS and commerce) acquired the Optimizely experimentation business in 2020, took the Optimizely name in 2021, and layered in Welcome (content marketing), Zaius (customer data platform) and Netspring (warehouse-native analytics). It is privately held under Insight Partners. Optimizely competes with Adobe Experience Cloud, Sitecore, Contentful, and Acquia on the DXP side and with tools like VWO and AB Tasty on experimentation.

Commercially, Optimizely runs a pure sales-led (and partner-led) motion. There is no published price list, no free tier, and no self-serve signup — the “Plans” page is a lead-capture form that promises an individually packaged plan after a sales conversation. That places it firmly in the quote-only, contract-negotiated cohort of the pricing blueprint rather than the self-serve SaaS cohort.

Pricing summary : why Optimizely’s DXP pricing is quote-only and sales-gated

Optimizely uses a quote-only, contract-negotiated model with no observable public mechanic:

1. Per-product packaging: the DXP is modular (CMS, Experimentation, CMP, Personalization, Commerce, Data Platform, Analytics, Asset Management, Feature Management, Agent Platform), and each customer’s deal is assembled from the modules they select. There are no published module list prices.
2. Custom annual contracts: deals are scoped and quoted by sales (or a channel partner) as annual enterprise subscriptions. Optimizely does not disclose seat counts, traffic/MTU tiers, or overage rates on its site — the /plans page is a lead form, not a price list.

What makes this different: unlike the freemium, self-serve CMS and experimentation vendors it competes with, Optimizely exposes zero prices publicly — the entire funnel is “tell us your needs and we’ll build a plan,” a textbook contract-negotiated DXP posture. See how this compares in the introduction to usage-based pricing and why picking a buying unit at all is hard in the value-metric problem.

Pricing by product

Optimizely does not publish tiers or prices for any product. Every module below is quoted per customer as part of an individually packaged, annual DXP contract. “Custom” means no price is visible on Optimizely’s site — you must submit the /plans lead form to receive a scoped quote.

Experience & content products

Data, commerce & AI products

Sales motions across products: none are self-serve — every module is sales-led (custom quote) or partner-led; there is no public PLG entry point.

No public pricing mechanic

Optimizely exposes no seat prices, no traffic/MTU tiers, no overage rates, and no free tier anywhere on its marketing site. The only “control” a buyer sees is the /plans form field “What products are you interested in?”, which routes the enquiry to sales. Any usage or capacity dimensions (traffic, tracked users, environments, agent runs) are negotiated inside the contract and are not disclosed publicly.

Hidden costs : what a real Optimizely DXP contract actually adds up to

With no public prices, the “hidden cost” of Optimizely is the shape of the deal itself: a base module license plus stacked add-on modules plus mandatory implementation, all rolled into an annual commitment. The line items below are qualitative — every figure is negotiated — but they show where an all-in DXP bill accumulates.

Archetype: a mid-market retailer standing up CMS + Experimentation + Personalization

The lesson: because modules and implementation are priced separately and bundled into a multi-year quote, the true cost of an Optimizely deployment is dominated by which add-ons and integration work a buyer commits to — not by any single headline SKU.

Want to estimate a usage-based software bill? Use the Optimizely pricing calculator to model monthly cost, browse the full calculator hub, and see how to think about usage invoicing and billing cycles for enterprise contracts.

Pricing evolution : from a single A/B tool to a quote-only composable DXP

Optimizely’s public pricing posture has eroded from named tiers to nothing over six years. Archived /plans snapshots trace the arc: a fully tiered, self-serve-friendly page in 2020, a still-public tier comparison in 2021, and a bare lead-capture form by 2026.

Cadence

Tracked range: 2020–2026. Dollar prices were never published on /plans; the cadence tracks the erosion of public tier structure and the packaging/SKU evolution. Quarters not listed were not separately archived (the capture browser truncated the Wayback series after 2021).

Notable changes

• 2020-01 — Standalone Optimizely’s /plans publishes named per-product tiers (Web and Full Stack: Essentials / Business / Enterprise) and a genuinely free Rollouts feature-flag product.
• 2020-10 — Episerver acquires the Optimizely experimentation business; the combined company adopts the Optimizely name in 2021.
• 2021-06 — The rebranded experimentation /plans still shows a public Free Rollouts / Accelerate / Scale tier comparison with a feature matrix, while Episerver’s CMS, Content Hub and Commerce products join the nav.
• 2024 — Netspring’s warehouse-native analytics and the Opal AI assistant are added to the suite.
• 2026-08 — The /plans page is a lead-capture form with no tiers, no free tier, and no dollar prices; the Agent Platform (Opal AI) leads Optimizely’s product marketing.

From published tiers to a lead form, in detail

The most telling shift is not a price hike but the disappearance of the price page itself. In 2020, a developer could land on /plans, read the entitlements of Essentials vs. Business vs. Enterprise, and start free with Rollouts. By 2021 the tier names survived (Free Rollouts / Accelerate / Scale) but paid figures were already gated. By 2026 the entire structure is gone — the page opens with “Every Optimizely plan is individually packaged” above a contact form. The composable-DXP roll-up (CMS, commerce, CDP, analytics, agents) coincided with, and arguably required, this move to fully bespoke quoting.

What’s unique : fully opaque, per-module DXP packaging

1. Zero public pricing across an entire DXP suite. Where most of Optimizely’s CMS and experimentation competitors publish at least a starting price or a free tier, Optimizely shows none — for any of its ~10 products. The /plans page is a lead form whose headline is literally “Every Optimizely plan is individually packaged,” making every buyer conversation start with sales. This is the purest expression of contract-negotiated DXP pricing in the corpus.

2. Modular à-la-carte licensing, not seat tiers. The buying unit is the product module (CMS, Experimentation, CMP, Personalization, Commerce, Data Platform, Analytics, DAM, Feature Management, Agent Platform), assembled per customer, rather than a named plan with a per-seat sticker. That lets Optimizely price-discriminate heavily by which modules and how much traffic a customer commits to — but it makes cross-vendor comparison nearly impossible for buyers.

3. AI packaged as a no-code agent platform, not a per-seat copilot. The Agent Platform (Opal AI) is positioned as an enterprise-grade, governed agent-orchestration layer — 50+ pre-built agents, workflow orchestration, built-in evals and human-in-the-loop review — sitting on top of the existing stack via MCP and pre-built connectors, rather than a metered token add-on. Its commercial terms are, like everything else, quote-only.

Strengths & weaknesses

Billing UX : the lead-form controls that stand in for a price page

Because Optimizely has no self-serve checkout, its “billing UX” is really a lead-qualification UX. The named controls a buyer actually encounters:

• The “Plans” lead-capture form — first/last name, work email, company, job title, phone and country fields with a Submit button; there is no price list behind it, only a promise to “create a plan together.”
• The “What products are you interested in?” field — the single control that scopes the quote, letting the buyer signal which modules (CMS, Experimentation, Agent Platform, etc.) they want priced.
• “Get started” and “Request a demo” CTAs — the site-wide primary buttons, both of which route to the sales/demo funnel rather than a signup or purchase flow.
• Partner channel — a Partners program (referenced across the nav and footer) through which deals can also be sourced and quoted, i.e. partner-led billing.
• Trust Center — where security, data-governance and “your data is never used to train external models” commitments for the Agent Platform are documented, standing in for contract terms during evaluation.

Strategic wins : where the quote-only, modular strategy pays off

1. Consolidating point tools into one composable DXP

By absorbing Episerver, Welcome, Zaius and Netspring under one brand, Optimizely can sell a marketer a single integrated stack instead of five contracts. That land-and-expand surface is exactly what per-module packaging is designed to monetize — each additional module is an upsell inside an existing relationship. See the broader pattern in the introduction to usage-based pricing.

2. Framing AI as a governed platform, not a metered add-on

Positioning Opal as an enterprise Agent Platform (evals, human-in-the-loop, “your data is never used to train external models”) targets the exact objections that stall enterprise AI purchases. It reframes AI from a token line item into a strategic platform commitment — a stickier, higher-value sale than a per-seat copilot. See why agent products are so hard to meter in the AI agentic pricing puzzle and how vendors are shifting toward outcome-based AI pricing.

3. Anchoring the whole suite on the .NET Core CMS and Stats Engine

Owning genuinely differentiated technical assets — an API-first .NET Core CMS and a proprietary Stats Engine for trustworthy experiment results — gives Optimizely a credible reason to command custom, negotiated pricing. Depth in the anchor products makes the surrounding modules easier to attach at premium rates. See how technical moats shape pricing power in the introduction to usage-based pricing.

Areas to improve : closing the transparency and self-qualification gap

1. Publish at least a starting price or “from” band per module

Total opacity forces every curious evaluator into a sales call, which filters out lower-intent buyers and hands self-serve competitors (Contentful, Webflow, VWO) the top of the funnel. Optimizely itself once published named tiers and a free feature-flag product on this very page, so a “starting from” figure or a representative package price per module is well within its comfort zone — and would let buyers self-qualify without eroding enterprise deal leverage.

2. Offer a transparent, self-serve on-ramp for the Agent Platform

Opal’s Agent Platform is the most PLG-friendly asset Optimizely has, yet it is gated behind “Book a demo.” A metered or capped self-serve tier — even a design-partner sandbox — would let teams experience the agents before committing, mirroring how modern AI tools convert usage into contracts. See usage invoicing and billing cycles for how a metered on-ramp can coexist with enterprise contracts.

3. Give buyers a comparison-ready packaging summary

Because modules are quoted à la carte, evaluators cannot tell what a “typical” deployment includes or costs. A published reference architecture — e.g. representative bundles for a mid-market vs. enterprise buyer, with the modules each includes — would reduce evaluation friction and pre-empt the “how do I compare this to Adobe or Contentful?” objection without disclosing exact figures.

Key takeaways

1. Opacity is a deliberate segmentation tool. By publishing no prices at all, Optimizely forces every buyer into a sales-scoped, per-customer quote — maximizing price discrimination but sacrificing top-of-funnel self-qualification.
2. Modules, not seats, are the unit of sale. A composable DXP monetizes through module attach and expansion; the “plan” is whatever bundle of products a customer commits to, which is why no single sticker price exists.
3. Acquisition-built suites need a packaging story. Optimizely stitched five products into one brand; the commercial glue is per-module packaging under a single annual contract, not a unified per-seat plan.
4. AI is being sold as a platform commitment. Framing Opal as a governed Agent Platform (evals, HITL, data-isolation) converts AI from a metered line item into a strategic, higher-value enterprise sale.
5. Transparency is the trade-off. The quote-only model protects enterprise margins but cedes the self-serve funnel to more transparent CMS and experimentation competitors.

UBP implications

1. Contract-negotiated is the anti-UBP end of the spectrum. Optimizely shows that large composable-suite vendors can still thrive with zero observable metering — a reminder that usage-based pricing is a choice, not an inevitability, for enterprise DXP.
2. AI platforms can dodge token metering. By packaging agents as a governed platform rather than a per-token meter, Optimizely sidesteps the consumption-pricing model most AI vendors adopt — trading usage upside for contract predictability and enterprise trust.
3. Opacity has a funnel cost. The absence of any public price or free tier means Optimizely forgoes the self-serve, usage-led acquisition that transparent competitors use — the clearest illustration of the tension between price discrimination and product-led growth. For teams weighing the opposite move, migrating a SaaS product to usage-based pricing shows what a metered on-ramp would require.

Sources

• Optimizely Plans (lead-capture page) (accessed 2026-08-11)
• Optimizely Agent Platform / AI (accessed 2026-08-11)
• Optimizely Get started (accessed 2026-08-11)
• Optimizely product roadmap (accessed 2026-08-11)
• Optimizely insights / blog (accessed 2026-08-11)
• Optimizely /plans, archived 2020-01-04 (named tiers + free Rollouts) (accessed 2026-08-11)
• Optimizely /plans, archived 2021-06-20 (Free Rollouts/Accelerate/Scale comparison) (accessed 2026-08-11)

Bottom line

Optimizely is the corpus’s cleanest example of contract-negotiated DXP pricing: a broad, acquisition-built suite of ~10 products — CMS, experimentation, personalization, commerce, a CDP, warehouse-native analytics and a no-code Opal AI Agent Platform — sold entirely through sales with no public price, no free tier, and no self-serve checkout. The /plans page is a lead form, not a price list, and every deal is individually packaged and quoted.

Want to compare Optimizely against other digital-experience and CMS pricing? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Fully opaque lead form; no-code Agent Platform headlines

Aug 2026

The /plans page is now a bare lead-capture form with no tiers, no feature matrix, no free tier, and no dollar prices — 'every Optimizely plan is individually packaged.' The public tier comparison visible as recently as 2021 is gone. The Agent Platform (Opal AI) headlines with 50+ pre-built marketing agents, no-code orchestration, and built-in governance.

Warehouse-native analytics and Opal AI added

Jan 2024

Optimizely folds Netspring's warehouse-native analytics into the suite and introduces Opal, its AI assistant, laying the groundwork for the later Agent Platform. Pricing remains quote-only.

Post-Episerver rebrand: experimentation /plans still a public tier comparison

Jun 2021

Episerver had acquired Optimizely (Oct 2020) and adopted the Optimizely name; the nav now carried Episerver's DXP products (Digital Experience Platform, Content Hub, Enterprise Commerce). The experimentation /plans page still showed a public tier comparison — Free Rollouts / Accelerate (Contact Sales) / Scale (Contact Sales) with a full feature matrix — so tier names remained public even though paid dollar prices were already gated behind 'Contact Sales.'

Standalone Optimizely published per-product tiers and a free tier

Jan 2020

Before the Episerver acquisition, the /plans page listed named tiers for each product — Optimizely Web and Full Stack each split into Essentials / Business / Enterprise — plus a genuinely free product, Rollouts (free feature flags for developers), with self-serve 'Get Started' and 'Full Comparison' CTAs. No dollar amounts were shown, but the tier structure and entitlements were public.