The Storyblok Difference
Chaos to Control
A Q&A on Storyblok + Adobe Commerce with Alycia Delhaye and Brandon Fieger
When Primo Water needed a new digital experience, they faced a tricky puzzle: they already had a license for Adobe Commerce but needed a CMS that would empower marketers and streamline content updates. That’s where our team stepped in.
In this candid conversation, Creative Director, Alycia Delhaye and Customer Experience Practice, Lead Brandon Fieger walk us through the journey.
Brandon Fieger
Customer Experience Practice Lead
Alycia Delhaye
Creative Director
When “Water” first came to us, what was your gut reaction to their digital setup?
Honestly, it felt like they were juggling so many different sites, each doing their own thing — mismatched branding and outdated workflows.
The design didn’t match the modern feel of the Primo brand, and the scattered content made it harder for customers to get a clear picture. It was obvious the site needed to do a better job at educating customers while enabling the marketing team.
From your CX perspective, how did those CMS headaches actually show up in the customer experience?
Slowdowns created frustration and missed opportunities. What should have been a quick content update turned into a week-long process. By the time something went live, the moment for impact had passed. Their old CMS just wasn’t built for speed — every change required multiple manual steps and the “right” person with the “right” access.
If you had to sum up their day-to-day challenges in three words, what would they be?
Limiting. Disconnected. Frustrating.
Can you give an example of a “this should be simple, but it’s not” moment you noticed?
Out of all the CMS options, what was the differentiator for Storyblok?
Storyblok gave them the freedom and control they were missing, without adding more complexity… even non-technical users could jump in and update pages quickly. Storyblok also gave us the foundation to create a site that can grow and adapt with their needs, without starting from scratch every time.
How did you approach blending Storyblok with Adobe Commerce, since Primo already had that license?
What’s the single most important thing we did during implementation to futureproof their site?
The scalable block library. The Primo team can mix and match blocks to build new pages or update existing ones — quickly, consistently, and without needing us every time.
Why was that block library such a game-changer?
How did you approach training so that their team actually felt confident?
We didn’t just do a one-off training. We ran “learn by doing” workshops, so by launch day, their team had already built real pages and handled updates with our support.
Do you remember a lightbulb moment when they realized how much easier this would be?
How did we strike the balance between support and dependency?
We set them up to handle day-to-day confidently, but we’re still available for big-picture needs.
Which result makes you proudest — the 35% faster updates, the autonomy boost, or governance improvements?
Faster updates, hands down. But honestly, seeing their team own the process is just as rewarding.
What’s one unexpected way their team has improved since launch?
Collaboration. With fewer bottlenecks, marketing and IT work together instead of tripping over each other.
If you had to describe the “before and after” in one sentence, what would it be?
Before, it was a jumble of disconnected sites; now it’s one platform that’s on-brand and built around the customer journey.
What advice would you give to a brand still stuck with a rigid, outdated CMS?
Don’t accept frustration as normal. The right tools make your team faster, more creative, and more effective.
What’s the one thing about this project you’ll still be talking about a year from now?
How design and technology together unlocked so much efficiency.
What would you say is the biggest reason this implementation worked so well?
Partnership. We didn’t just deliver tech — we built a system that let their team thrive.