NatterValley is a wine tasting community platform that helps users receive a personalised selection of wines suited to their palate. I redeveloped the existing WordPress site in Webflow, building a dynamic taste quiz that returns a scored result, then triggers a personalised email recommendation based on the answers.
The Webflow build includes a wine glossary powered by the Webflow CMS, giving NatterValley a structured way to add and manage wine education content over time. Each entry in the glossary has its own templated detail page, with category routing built in so users can browse by varietal, region, or tasting note.
The site supports the broader NatterValley community with editorial content, member resources, and a clear path into the personalised wine experience, all manageable directly by the team through the Webflow Editor.
Project scope
- Apps
- Websites
- Website development
- AI automation and connected systems
NatterValley had a WordPress site that worked fine as a basic brochure, but it could not deliver the personalised wine experience that was central to their value proposition. The concept is clever: a taste quiz that learns your preferences and recommends wines you will actually enjoy.
But on WordPress, the quiz was clunky and the recommendation engine was disconnected from the rest of the site. The experience fell flat at exactly the moment it needed to be most engaging.
The wine education content was also hard to manage on the old platform. NatterValley wanted to build out a structured wine glossary that users could browse by varietal, region, or tasting note, but WordPress did not offer the content modelling flexibility to make that work without significant custom development. For a community platform built around discovery and personalisation, the digital experience was ironically generic.
There was a larger strategic issue too. NatterValley was trying to build a community, not just a shop. That requires editorial content, member resources, and a sense of ongoing life on the site. The old WordPress setup made every content update feel like a chore, which meant the site felt static at a time when the business needed it to feel alive.
