Problem

C12 had recently endured a failed software system rollout; it was a customizable ERP that had to be completely scrapped at the 11th hour. This was not the first time either. C12 had tried a few different technology approaches to improve the functionality of their business, but hadn’t landed on a sustainable long-term solution. As a result of their past experience, C12’s leadership came to RoleModel very wary of custom software. The RoleModel team needed to not only prove they could deliver working software, but also that they could understand C12’s business to ensure that the customized system delivered would be what C12 actually needed.

Since permissions vary for different groups of C12 users, they couldn’t all have access to the same data. This problem was presently addressed by having a separate system for the different groups of users. Standard members had their own system, Chairs and staff had their own system, and additional third-party applications were being leveraged as well. In many cases, when one group would need to access data from another group’s system, inconsistency, different logins, and no single sign-on greatly impeded this process. 

Not only that, but because of C12’s spliced-together system, the data was very untrustworthy. Data wouldn’t save historically and without a reliable way to know that there was a problem, errors were easy to miss. There were concerns about data being compromised in a hack, or low-level users getting access to high-level information that they weren’t supposed to. Support requests from members at all levels were numerous and staff were constantly needing to access and manually change data that was breaking.