Clover, a cloud-based Android point-of-sale platform, has shipped over one million devices worldwide, allowing its customers to easily manage their businesses and run more profitably thanks to web apps and third-party app integration. Clover chose Contentful as a headless CMS to empower its content and marketing team to create and control content without relying on the engineering team. The company's first project with Contentful was the homepage, which resulted in 24 section types that could be used on three different page types for a total of 48 different content models. However, this led to content model overload, as it was overwhelming for people not used to working in this kind of system. To address this issue, Clover's Senior Software Engineer, Rachel Church, recommended fixing the content model overload by avoiding creating new content models for variations of the same thing, requiring hint text and validation for every field, and always reviewing content models with stakeholders. Clover expanded into new markets, outgrew its help site running on WordPress, and required more flexibility and localization capacity, leading to a total of 16 content models that were tweaked during the development cycle. Through practice and iteration, Clover learned to build content models that are both reusable and intuitive, and the company's experience serves as a valuable lesson for others looking to implement Contentful in their own projects.