We’ve seen an uptick in companies using Kloudless in the employee success space and want to make sure that your company can reap the same benefits that other applications have. One such company, O.C. Tanner, chose Kloudless for its specific calendaring needs. To give you more context into their specific case, let’s delve a bit more into the company itself. BackgroundO.C. Tanner helps companies make their workers feel appreciated and well cared for. They do this mainly through employee experience apps, referred to as the Culture Cloud, which reinforce employees’ sense of purpose, accomplishment and connection to one another. A benefit that motivated and energized their employees performance in their duties.The Culture Cloud manifests worker appreciation by acknowledging anniversaries, work achievements and other indicators of their employee’s hard work. For example, their app might acknowledge an employee for repeatedly engaging in behaviors that improve well-being -such as exercise or meditation- or celebrate their achievements in their work by broadcasting that accomplishment across the company. This functionality required reliable integration with cloud calendar services such as Outlook, Google Calendar and more. The ChallengeTo start, the company built an integration with Microsoft Outlook from scratch themselves. This build-out required a full-time engineer and took six months to deploy, effectively delaying O.C. Tanner’s overall product roadmap.Building out integrations like this, one at a time, could have worked on a small scale, however, O.C. Tanner boasts 12 million+ users across more than 150+ countries. So not only did O.C. Tanner need reliable integrations, but it also required integrations at scale, with a variety of calendar services and feature options for its diverse enduser base. Simply put, building the integrations out one at a time presented a tall task with diminishing returns. The more time and energy put into this feature, the less there would be to spend on more pressing issues and features.Since O.C. Tanner is in the employee success business and not the integrations business, it did not hire a calendar integrations specialist to build out and maintain integrations to calendars beyond Outlook. Doing so would require at least two more full-time engineers’ salaries and another roadmap delay. They were facing an inevitable sunk cost fallacy, as they had already invested so much time and money into the initial implementation of Outlook.SpecificationsSo, in recognition of the growing importance to its business of integrations at scale, O.C.Tanner sought a tool to save them the time and resources they would lose in continuing a one-off-build strategy. Since O.C. Tanner is all about personal empowerment, their product leaders desired a solution from a company with similar values.At a basic level, O.C. Tanner needed a core set of calendaring features that worked out of the box with users’ native calendaring software. These services include Outlook Calendar, Exchange Online, Google Calendar, and Exchange Server. The use case mentioned further above demonstrates this need:If an app is to celebrate a worker for engaging in several consecutive weeks of exercise and meditation, it needs to identify when that exercise occurred in the past, when it will occur in the future, and how frequently it can be expected to occur.The O.C. Tanner engineering team required a solution that would handle the various edge cases and inconsistencies that arise between different users’ calendar accounts while maintaining a highly responsive, low latency API layer to access and sync calendar data.Serving end-users from enterprise companies all over the world, including European countries, necessitated enhanced data privacy and security measures. And last but not least, since the company was growing so quickly, they needed a flexible pricing model that could adjust with the company as it grew.