When AI breaks the technical lock on experimentation

{{blue-block-1}}
A/B testing just changed. It's no longer about code. It's about strategy.
At the 1:1 Retail Ecommerce event in Monaco, Kameleoon unveiled a new standard in experimentation. Joined by Louise Elineau, Digital Director of the Yves Rocher Group, CEO Jean-René Boidron showcased a tangible performance leap, revealing how France’s #1 beauty brand reinvented its approach to experimentation and what this shift means for the industry as a whole.
{{cta-block}}
That barrier has not been removed.
With PBX (Prompt-based Experimentation), Kameleoon introduces a breakthrough that goes beyond incremental improvements. We're no longer talking about going slightly faster. We're talking about fundamentally changing the nature of the work: any member of an e-commerce team can now describe in plain language what they want to test and see it generated within minutes.
{{quote}}
From Prototype to Prompt: The End of a Dependency
Until now, launching a test required multiple stages: an idea, a mockup, a developer, a QA pass. Each link added delay. And in experimentation, delays mean missed opportunities.
PBX short-circuits that chain. An urgency sticker on a product page? A two-column versus four-column display toggle on a listing page? A search bar integrated into the mobile menu? These tests — each of which would have required at least a full day of development — can now be built in minutes, directly from a prompt written in plain English. PBX reads the CSS, understands the underlying technology, generates the code, and displays the result. The code remains accessible and editable. The machine does; the human supervises.
At Yves Rocher, the impact was immediate.
{{quote1}}
The Real Bottleneck Moves One Step Up
Solving the development problem doesn't close the topic, it shifts it. When you can launch as many tests as you want, the real question becomes: which ones should you launch?
That's precisely the next frontier. Kameleoon is currently integrating an ideation layer: a prioritization engine powered by a database of over 25,000 experiments, capable of suggesting test ideas using a proven framework developed over more than 10 years by one of Kameleoon's agency partners, Gain.
Teams using it report positive results up to three times more frequently than with their usual tests. The improvement challenges don't disappear: they move upstream, into strategic thinking rather than technical execution.
.png)
Strategic Clarity: The New Luxury for E-Commerce Leadership
Velocity is only useful if it's pointed in the right direction. This may be the most structurally important point of this transformation, and the one Louise Elineau articulates most sharply:
Speed must not become noise. We can't become headless chickens. It's even more important to be clear about what we're looking for, which KPIs we want to move, and which strategic priorities we want to pursue.
When launching a test took ten days, the delay forced prioritization. Now that everything is possible, the risk is reversed: testing in every direction, with no heading. The e-commerce teams that will get the most out of PBX won't be those that launch the most tests, but those that have most clearly defined what they're trying to prove.
Organizations That Need to Reinvent Themselves
The technical acceleration disrupts processes well beyond the CRO team. When any team — retail, CRM, product — can potentially initiate a test, governance must keep pace. Who approves what? Who arbitrates priorities? How do you avoid traffic conflicts between competing experiments?
{{quote3}}
The challenge is no longer technical. It is now a management challenge that calls for concrete answers: clarified roles, streamlined but structured validation processes, and stronger analytics teams. Because if tests launch faster, their interpretation must be more rigorous. Knowing how to read statistical significance, stepping back before drawing conclusions, distinguishing signal from noise : these analytical skills become central.
QA, for its part, remains non-negotiable. Automated code generation doesn't replace human verification. It frees up time to focus on what matters: making sure what goes to production is solid.
The Last Lock: From Winning Test to Deployment
One paradox remains, and Louise Elineau names it plainly: a winning test identified in January may have to wait until April to be hard-coded into production due to insufficiently agile release cycles.
The goal is to make sure that if we speed up the testing, the rollout of the winning test to production is equally fast. Because the objective is to capture value as quickly as possible.
Accelerating experimentation without accelerating deployment means accumulating proven value without capturing it. Yves Rocher is currently working on faster operating models for this final step: pilot teams, short cycles, closer collaboration with technical teams.
This is the next challenge. And it is organizational, not technological.
What Really Changes
PBX is not just another feature. It is a paradigm shift: experimentation moves from long lead times to short ones, from technical dependency to team autonomy, from constrained volume to open volume.
What doesn't change: the need for a clear strategy, solid governance, sharp analytical skills, and an organization capable of turning wins into production.
Technology has unlocked the process. What you do with it is a question of management.
{{cta-block1}}
We wanted to completely rethink the experimentation cycle to allow teams to design their tests not in days, or even hours, but in minutes, from a simple prompt.

We were struggling to move fast. PBX came at the right time. In just a few weeks, we ran more tests than we had managed in the months before.

We can see that other teams are going to want to test. Not just the small CRO team. There are use cases for retail, CRM... So how do we organize that governance?


TL;DR — Yves Rocher x Kameleoon: Next-Generation A/B Testing
The problem: Previously, launching a test took days as it relied on the development cycle (brief → mockup → dev → QA).
The solution: Kameleoon launches PBX (Prompt-based Experimentation), which allows users to describe a test in plain language and see it generated within minutes, no coding required.
The result at Yves Rocher: They completed more tests in a few weeks than they had in several months previously.
What it changes: No more technical bottlenecks. The CRO team can focus on strategy: which tests to run, which KPIs to move, which priorities to set. Testing fast without a clear direction = busywork, not performance.
The new challenges:
- Governance: When every team (CRO, retail, CRM) can run tests, who approves what?
- Analytics: Rigorous analysis of results becomes event more critical.
- Deployment: A winning test identified in January might not reach production until April: the acceleration must extend to go-live as well.
The message: Technology has removed technical blocks. What makes the difference now is management: strategic clarity, organization, and the ability to turn wins into real value.
Want to see PBX in action and revisit the highlights of this keynote with Yves Rocher?
Want to see PBX in action and revisit the highlights of this keynote with Yves Rocher?

Prompt your first test for free!
Experience the power of PBX AI on your site for 30 days. No credit card required.
Prompt your first test for free!
Experience the power of PBX AI on your site for 30 days. No credit card required.



