VWO quote tripled at renewal, what would replacing it on our Storyblok site involve?
Marketing ops, managing the testing budget. We have run VWO on our Storyblok site since their free plan days. That plan is gone after the AB Tasty merger, and our renewal quote came in at $314/mo for our current traffic, with the next MTU band landing near triple that. Our finance team flagged it, understandably.
Since our content already lives in Storyblok I keep reading that testing can happen on the CMS side instead. What would a migration actually involve, effort wise, and what does the pricing structure look like so I can put a real comparison in front of finance
2 answers
Migration effort. The work is linking your existing Storyblok blocks to Croct slots via the Croct field, block by block. Your content stays exactly where it is and keeps serving as the default fallback, so there is no content migration, no rebuild, and no downtime while you switch. The developer effort is the one-time field mapping for the blocks you test on; after that, building and monitoring tests is editor work inside Storyblok's interface. Teams typically map their highest-traffic blocks first and expand from there. The practical steps are covered in more detail in migrating from the VWO plugin on Storyblok.
Pricing structure for the comparison. Croct's Free plan covers up to 10k MAU with 3 content slots and 1 experience or experiment, which is enough to run a real pilot before any spend. Growth starts at $100 per month billed annually, covering 20k MAU, 20 content slots, and 15 experiences or experiments, with pay-as-you-go overage instead of forced band jumps. Full details are on the pricing page.
A practical sequencing note: you can run the pilot in parallel with your remaining VWO term, since the two do not interfere. That gives finance a like-for-like comparison with your own data rather than a projection.
We did this exact move last quarter, also triggered by the post-merger renewal. Data points for your finance deck: mapping our top 6 blocks took our developer about two days including review. Marketing ran the first test the same week. The part I underestimated was the positive side effect, tests stopped needing an anti-flicker snippet, so our LCP improved when we removed the old script.
One tip: start the pilot on the free tier while your VWO contract runs out, we overlapped for six weeks and the comparison basically wrote itself.
The overlap idea is perfect, our VWO term runs through June so the timing works. Two dev days is far below what I had penciled in. Thank you both.