Comenity: 50 Brands For 1 Product
The Situation
Comenity’s business model was built on customization. As a white-label credit card provider serving more than 50 retail brand clients, their value proposition was the ability to tailor the experience to each client’s brand, rewards structure, and customer expectations. That model had worked well enough to grow the business significantly. It had also, over time, produced a platform where no two experiences were quite the same, where sales teams were making promises that operations could not keep, where customer service volumes were climbing, and where compliance risk was accumulating quietly across the portfolio. Each of those problems was being managed as its own issue. Nobody had connected them to a single source.
What Was Actual Broken
Four teams inside the same organization had each developed their own working definition of what Comenity’s product was. Sales had a version that closed deals. Product had a version that was technically buildable. Operations had a version that reflected what actually existed. Clients had a version based on what they thought they had purchased. None of those versions were the same, and none of the teams had been asked to reconcile them. The complexity that was showing up as inconsistent experiences, compliance gaps, and rising service costs was not a technology problem or a design problem. It was what happens when an organization scales without ever aligning on a shared definition of the thing it is selling.
The Turning Point
Before any recommendations were made, time was spent with 40 people across the organization: brand clients, operations teams, customer service representatives, and end users. The goal was not to gather requirements. It was to surface how many different answers existed to the same question: what is this product? Four answers came back. Naming that clearly, putting those four versions of the same product in the same room and asking the organization to choose one, was the moment the work became possible. The question had not been asked before because everyone had assumed everyone else was working from the same definition. They were not. Once that was visible, the path forward was structural rather than symptomatic.
What Changed
A shared product definition replaced four competing ones. That single shift gave sales a clear scope to sell within, gave product a clear boundary to build within, and gave operations a repeatable onboarding process to replace what had been a custom negotiation for every new client. ADA compliance was addressed across the portfolio. Customer service volumes dropped as experiences became consistent. New brand onboarding moved faster. The platform that had been accumulating complexity with every new client started generating efficiency instead. The organization did not need new technology to produce those results. It needed a shared answer to a question it had never formally asked.
Frank’s Take
Complexity at scale almost always traces back to alignment that was assumed rather than established. The teams are usually capable. The work is usually clear within each team’s definition of it. What is missing is the conversation where all of those definitions get put in the same room and reconciled into one. That conversation does not require a consultant to run it. It requires someone with no stake in any of the existing definitions to ask which one is actually true.