Lick, an online home decor company, saw a two times increase in sales after migrating to Hygraph. The team managed over 600 product pages and completed their project from idea to launch in just 6 months. The migration enabled more modular content management, improved user experience, and allowed for scalable workflows. (Source)
What specific results did Lick achieve with Hygraph?
After launching their new site with Hygraph, Lick reported a 20% increase in “Add to Bag” conversions, a dramatic drop in bounce rates on product pages, and the ability to quickly build new landing pages using reusable content models. (Source)
Where can I find more Hygraph customer case studies?
You can explore additional Hygraph case studies, including Komax, Stobag, Samsung, Dr. Oetker, and more, on the Hygraph case studies page.
Features & Capabilities
What key features does Hygraph offer for product management and eCommerce?
Hygraph provides fine-grained content modeling, a Management SDK for programmatic schema changes, Reference Fields for building relationships between models, GraphQL Union Types for flexible content modules, a Rich Text Editor, Scheduled Publishing, and native Localization. These features enable modular content management, scalable workflows, and support for global audiences. (Source)
How does Hygraph support modular and reusable content?
Hygraph enables teams to build flexible content models and use Reference Fields and GraphQL Union Types to create reusable components. This allows for quick creation of new landing pages and consistent updates across the site, improving efficiency and scalability. (Source)
Does Hygraph offer localization and scheduled publishing features?
Yes, Hygraph provides native localization features to support wider audiences and scheduled publishing to allow teams to publish or unpublish content at any time, which is essential for eCommerce use cases. (Source)
What are the benefits of Hygraph's Management SDK?
The Management SDK allows teams to programmatically create and ship schema changes, transfer data between environments, and adapt the schema quickly. This enables faster, more flexible workflows compared to manual schema creation. (Source)
Implementation & Onboarding
How long does it take to implement Hygraph?
Implementation timelines vary by project. For example, Lick completed their migration and launched their new site in 6 months. Other customers, like Top Villas, launched within 2 months. Hygraph offers onboarding support and resources to help teams get started efficiently. (Source, Top Villas Case Study)
What onboarding and support resources does Hygraph provide?
Hygraph offers onboarding sessions, extensive documentation, webinars, live streams, how-to videos, and a dedicated Customer Success Manager for enterprise customers. Support is available 24/7 via chat, email, and phone, and users can join the community Slack channel for additional help. (Documentation, Enterprise Support)
Security & Compliance
What security and compliance certifications does Hygraph have?
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and compliance standards for customer data. (Security Features)
How does Hygraph protect customer data?
Hygraph uses granular permissions, SSO integrations, audit logs, encryption at rest and in transit, and regular backups to protect customer data. Enterprise-grade compliance features and transparency in reporting further ensure data safety. (Security Features)
Pain Points & Solutions
What problems did Lick face before using Hygraph?
Lick's previous CMS required heavy developer involvement for content updates, lacked modularity, and slowed down content creation. The workflow was unsustainable, tying development resources to marketing timelines and limiting scalability. (Source)
How does Hygraph solve common pain points for eCommerce and product management?
Hygraph eliminates developer dependency with an intuitive UI, enables modular content modeling, supports reusable components, and provides scheduled publishing and localization. These features streamline workflows, accelerate speed-to-market, and support scalable growth for eCommerce businesses. (Source, Documentation)
Technical Requirements & Performance
How does Hygraph ensure high performance and scalability?
Hygraph offers Smart Edge Cache for faster content delivery, high-performance endpoints, and a GraphQL-native architecture that supports scalable, modular content management. These features are ideal for businesses with high traffic and global audiences. (Performance Blog)
What KPIs and metrics are associated with Hygraph's impact?
Key metrics include time saved on content updates, number of updates made without developer intervention, reduction in operational costs, speed-to-market, system uptime, and user satisfaction scores. For Lick, the impact included a 2x increase in sales and a 20% boost in conversion rates. (CMS KPI Blog, Lick Case Study)
Pricing & Plans
How does Hygraph's pricing work?
Hygraph offers pricing that grows with your project, making it suitable for businesses of all sizes. For specific pricing details, visit the Hygraph pricing page.
Support & Maintenance
What support and maintenance options are available with Hygraph?
Hygraph is a cloud-based platform that handles all deployment, updates, and infrastructure maintenance. Customers have access to 24/7 support, a dedicated Customer Success Manager for enterprise accounts, and extensive documentation and training resources. (Documentation, Enterprise Support)
How Lick increased 2x sales by migrating to Hygraph
2x
Increase
in sales
600+
Product pages
managed
6 Months
Project Timeline from Idea to Launch
Lick is an online home decor company that launched in 2020 with the goal of making it easier for customers to decorate their homes using wall paint or wallpaper.
Being an online business, Lick is reliant on a performant website that delivers a high-quality, intuitive user experience to match their product line of wall paint and wallpapers.
During their initial launch in 2020, the team relied on a site that was built by an external agency using a different headless CMS system. The rapid shift to e-commerce driven consumption propelled Lick’s growth and they quickly outgrew their existing infrastructure, needing more flexibility and scalability. The Lick team chose to reevaluate their approach and develop a new e-commerce site internally with an emphasis on building a modular stack with best-of-breed technologies to ensure scalability and high performance.
Without Hygraph, we would not have been able to achieve the intuitively modeled content pages in the time frame that we did. After the launch of our new site, our “Add to Bag” conversions increased by 20%. It was easier to build the modular site that we imagined to improve user experience without workarounds.
Joel Pierre-PowellPrincipal Software Engineer at Lick
The Process
Having learned a lot about their needs from the initial implementation of the Lick site, the team had a stronger sense of how workflows and systems should work in practice. They hoped to build a stack that could continue to scale with them as they grow and their needs evolve. The most important outcomes had to be scalability, better performance, and more control of the data modeling compared to the previous solution.
The initial stack limited the team’s ability to break down the content modularly and did not allow the team to be as flexible with creating reusable content. The workflow relied too much on developers creating new models for every new landing page. This slowed down content creation and tied the development team to the marketing team's timelines and priorities. It was clear that this workflow was not sustainable. Additionally, the initial stack was built by an external agency. With the switch to a new stack, the team aimed to bring all of the code in-house to better meet their needs.
Hygraph offered fine-grained content modeling, a more scalable approach to workflows, and onboarding sessions that helped the Lick team model content using best practices for their use case. After migrating a small section of the website to the updated stack, it was clear that the new stack would deliver on its promises.
Why Hygraph?
The Lick team chose Hygraph for the following reasons.
Fine-grained Content Modeling Capabilities
Flexibility of content models was a key factor in choosing to work with Hygraph for the Lick team. With Hygraph, the team is able to build models that represent products, product variants, and more while building an intuitive end product.
The ability to build flexible content models with Hygraph was essential for the Lick team when choosing the services that would build their modular content models. With content models that cover products, product variants, and more, the Lick team is able to quickly build new landing pages with existing content models. Hygraph helps ensure that content becomes reusable and that workflows are expedited.
This is done using the Reference Field to build relations between content models that match the intuitive connection between the data. This highly flexible field allows teams to easily model complex data without it becoming convoluted to content editors. Teams are able to create a single model for content that should remain consistent throughout the site, such as paint colors; if changes to that model should occur, the Lick team only has to update it in a single place to be reflected across the site.
Field validations ensure that when content is published that it is not missing any additional content and pages are consistent. Helps ensure that as teams grow that easily and that teams are not relying on internal team knowledge
The fine-grained content modeling and validations help ensure that the data is well organized and easily discoverable in the product. The result of this updated approach to content modeling is a user-centric product experience with better performance. The team has seen a dramatic drop in bounce rates on product pages after the shift to the new stack.
Management SDK
With Hygraph, the Lick team adopted a programmatic approach to building new content pages using a mixture of new and existing content models. The Management SDK enables teams to programmatically create and ship changes to the schema. This workflow is faster and more flexible than a manual approach to schema creation. Developers are able to work programmatically while transferring data between various environments, building new pages, and adapting the schema.
The Development team is able to work entirely with code while delivering the schema to the content team within the Hygraph interface. From there, the content team can make any necessary changes or updates within the content editing UI to be reflected on the final project UI.
GraphQL Union Types
GraphQL Union Types enable a component based approach by creating a more flexible content model. Content editors are able to build new pages using existing content modules and GraphQL union types. Union types allow teams to reorder content fields on content pages, allowing the team to use the single content model more flexibly for various use cases. Implementing this new approach gives the content team greater independence, flexibility, and expedites workflows. By taking a modular content approach, the Lick team is able to create more reusable content and have more control over this content if changes need to occur.
More Efficient Workflows
The component based approach enables the content, UX, and development teams to work together in harmony. Once a new set of components are built by the Development team, the content and UX team can work together to build new pages without the need to involve designers. This new workflow has enabled the team to work quickly and efficiently to meet aggressive timelines to migrate the entire website to the new modular stack.
After moving to the new stack, the content team no longer has to rely on the development team to set new posts live or schedule campaigns. Hygraph makes it easy to publish and unpublish content with a couple of simple clicks. The Scheduled Publishing feature gives the team more flexibility to publish and unpublish content at any time without being at their computer.
The Current Setup
The Lick team chose a stack that would be both flexible and scalable for the future. It was important that the chosen stack matched the competencies and abilities of the team to help keep them engaged and excited about their projects, rather than spending too much time pushing deployments for copy changes. The new stack is built with Next.js, React, Redux, Shopify, a homebrew REST aggregation layer, Typescript, Terraform, and SiteSpect for AB Testing.
This new stack allows the team to build modular content components and reap the benefits of modern frontend framework and tooling. The new stack helps the team meet its goals of providing a high-quality user experience and a high-performing site on a stack that is scalable for the future.
Results and Benefits
Reference Field meant that team could break content modeling down into a bite sized pieces and build circular references
Rich Text Editor makes it easy for content teams to create and add content quickly