Buyers talk about the price of experimentation tools in two registers: what the licence costs, and what it costs to run a testing program on it. The first spans a wide range, from enterprise platforms to Shopify testing apps priced at a fraction of them; the second — the people, agencies and developers — can materially add to the first. Below are the seven mechanics buyers describe, and where price-led switches went. The companion read is what experimentation buyers wish they'd known (where the ratings live), and the switching picture is on why teams switch A/B testing tools.
Seven things that set the bill
Across the interviews, the cost of experimentation is set by the tier a team buys into, how the licence meters, what sits on top of it, and the work needed to run tests at all.
The price gap is wide — and it changes with scope
Buyers describe a steep spread in what these tools cost. One who shopped the category found Optimizely and the other enterprise tools “all three times as much as VWO”; another, moving to a Shopify testing app, pays about a tenth of what Optimizely would have cost; a third puts Optimizely at about twice the cost of two rival bids. One buyer's verdict on Optimizely's pricing: “They priced themselves like they were the leader.” But relative price changes with scope: a buyer who wanted VWO's full package found Optimizely cheaper than that. And a higher buyer-described price does not necessarily come with a higher rating — Optimizely and VWO both rate 7.3.
Named in this context: Optimizely · VWO · Intelligems
The free tool left a budget line that did not exist
For some teams that ran Google Optimize, its retirement created a software budget where none had existed. “Before we didn't pay for our A/B testing because of Google Optimize,” one buyer says; another, of the shutdown, “it went away this year and we did not budget for it.” Asked why they had used it, one answers simply: “Frankly, because it was free.” One of these teams moved to Convert, a lower-priced tool.
Named in this context: Google Optimize · Convert
Licences can meter on usage or contracted testing volume
Some buyers describe licences that grow with use rather than a flat fee, in their own terms. One VWO buyer says “they have a consumption-based pricing model, so you pay for how many users.” Another describes a contract sized to a testing volume, which the vendor's own setup consumed faster than planned (see the stories below). The curve matters at the top end: “if you scale it on enterprise, I would say it can become expensive.” This mechanic rests on fewer buyers than the others, and the units differ by vendor and contract.
Named in this context: VWO · Optimizely · AB Tasty
Modules and tiers sit on top of the base
The base licence is not the whole quote. Buyers describe separately priced web, server-side and full-stack modules and premium tiers, with one finding “the cost of the web module is significantly higher than VWO.” Others describe being sold the server-side upgrade, or needing premium licensing for the features they wanted. In the Adobe stack, the analytics that make Target's results usable come as a further product.
Named in this context: Optimizely · VWO · Adobe Target
The team around the tool can materially increase the bill
Software price is not program cost, and several buyers count the program, not just the licence. One buyer, explaining why it left Dynamic Yield, says “if you have to hire three people to run the thing, well it's quite a bit more expensive”; an Adobe Target user without in-house developers says “So we end up relying on external agencies, and that makes everything more costly and slow.” The arithmetic also runs the other way: a VWO user says of its price, “You need a big team to actually justify paying that price.”
Named in this context: Dynamic Yield · Adobe Target · VWO
Adobe bundling can change Target's effective price
Buyers in the Adobe stack describe Target bundled or discounted inside wider Adobe deals. One was told “You want Adobe Target, we're going to throw that in for free” as part of a larger deal; another says “we were getting it at a significant discount at the time because we were looking at taking on Adobe Analytics.” The same bundling cuts the other way over time: “They always weave you into more and more products, and they are not cheap.”
Named in this context: Adobe Target · Adobe Analytics
The price is negotiable, and the incumbent's price sets the anchor
Buyers describe real movement on price. One team leaning toward AB Tasty on cost saw Optimizely respond: “Optimizely kinda came in very aggressively on price,” leaving the two “very comparable.” Another agreed a multi-year plan in which no year costs more than its outgoing contract. A price increase can also end a relationship: one team left its previous testing platform after the vendor's price rise: “They were changing, increasing their prices significantly, and we decided that the price increase wasn't justified.”
Named in this context: Optimizely · AB Tasty · Oracle Maxymiser
Want this read against your own stack?
Get my read →The stories behind the bill
The counter-current: some buyers find the premium worth it
Not every buyer is trading down. A team that left Optimizely for Google's free tool came back: “The cost savings was not worth the usability.” Another says of a premium tool, “They are a more expensive tool, but I think it's worth it with the amount of data that you actually receive,” and one calls Adobe Target “a Cadillac offering. Obviously you pay for that too.” Lower-priced tools have their own limit — one buyer sums up the choice as “Shoplift is too basic. VWO is pretty darn expensive.”
What this means for your testing budget
The interviews describe a wide spread in buyer-described price that changes with scope, licences that can meter on use, modules on top, and people or agency costs that can materially increase the total cost of running the program — with price-led switches moving to lower-cost tools, and a few teams finding the premium worth keeping. Our recommendation, not a practice buyers describe: price the testing program you will actually run — expected usage, required modules, and the people or agency hours — rather than comparing licence quotes alone. If you're replacing an incumbent, use its current cost as the negotiation anchor.
Common questions
How is A/B testing software priced?
In these interviews, often by a base licence that can scale with usage — users, traffic or a contracted testing volume — with modules such as server-side testing or a web module priced on top, and annual or multi-year contracts. Buyers describe a wide price gap: one found the enterprise tools all about three times the price of VWO, and another pays about a tenth of what Optimizely would have cost. The tool is also only part of the bill; several buyers count the people, agencies and developers needed to run tests as a cost that can materially add to the licence.
Why is Optimizely so expensive?
Buyers describe Optimizely as priced like the market leader, with its web module costing significantly more than VWO and one buyer putting it at about twice the cost of two rival bids. Some find the premium worth it for usability and the data they get, and one team that left for a free tool came back. Others moved to lower-cost tools such as VWO, Intelligems, Shoplift or GrowthBook on price. Optimizely also negotiates: one buyer saw it come in aggressively on price against AB Tasty, and another agreed a multi-year plan with no year above its outgoing contract.
Is VWO cheaper than Optimizely?
In most comparisons buyers make here, yes: two companies moved from Optimizely to VWO on price, and one found Optimizely and other enterprise tools about three times the cost of VWO. The exception is scope: one buyer found Optimizely cheaper once it priced the full VWO package it would have wanted. Buyers on volume-based VWO contracts also describe usage that can run out faster than planned.
What do buyers give up when they switch to a cheaper A/B testing tool?
Buyers who switched on price describe meaningful savings, and every price-led switch here moved to a tool they describe as cheaper. What some gave up was capability or usability: one buyer calls a low-cost Shopify testing app too basic, another chose a cheap tool and found it very basic, and a team that dropped Optimizely for a free tool came back because the savings were not worth the usability. Others find the premium worth paying for the data they get. What a cheaper tool costs in practice depends on the testing program a team actually runs.
Is Adobe Target included with other Adobe products?
Buyers describe it being bundled or discounted inside wider Adobe deals rather than bought on its own: one was offered Target free as part of a larger purchase, and another got a significant discount because it was also taking Adobe Analytics. The same buyers note the bundle can widen over time, with more Adobe products added to the contract.
Get this research made for your stack
Trying to get your testing budget under control, or pricing a move off your current tool? Do a 15-minute interview about your traffic, your team and your test cadence and get this personalized — which cost mechanics drive your number, and where peers found the savings.
Get my personalized read — 15-min interviewNo password · your interview is anonymized before it ever informs a page like this one.