Implementation volume surged from a dozen simultaneous projects to over 25, with individual project sizes doubling on average. The broader CS team also expanded rapidly. The mandate: scale dramatically while maintaining their hard-won 90+% implementation customer satisfaction rating.
Spreadsheets and disparate documents created information silos that made portfolio-level visibility impossible. "If somebody wanted to see which projects need management attention, they couldn't get a uniform briefing," Glenn explained. "The information was there, but was hard to access and virtually impossible to aggregate."
Beyond visibility, Espresa's implementation process is technically sophisticated with numerous configuration switches, options, and combinations across their Lifestyle Spending Account, Rewards & Recognition, Wellbeing, Challenges, and Communities platform software. Their implementation collateral consisted of lengthy PDF documents that sometimes made it harder for customers to quickly navigate the guidance they needed. Complex tasks involving the inbound programmatic and technical discovery, followed by outbound education, creative design, and configuration instruction created lengthy discussions without predictable endpoints.
Without structured playbooks, new team members required several months of shadowing before running implementations independently. Synthesizing project data for executive briefings consumed significant portions of his week, yet the results were still limited.. "Had we not moved in the direction we did, I think we'd have struggled to keep pace with the company’s growth."