Blaine CarterCIOFranklinCovey
IT and business units at a US company of 1,001 to 5,000 employees.
Make success story (vendor case study), published Read the case study (opens Make success story (vendor case study) in a new tab)
Observation
At FranklinCovey, Make replaced aging middleware, and business units now automate their own processes.
- Takeaway
- Make can stand in for aging middleware while the core systems stay as they are. A scenario on tools the company already pays for is worth pricing against a new application.
- What happened
- FranklinCovey connected its systems through a 15-year-old service bus whose original developers had left, so even small changes were slow and costly. Make replaced it as both the integration layer and the automation layer, without changes to the core systems. The company built the functions it needed on tools it already had and chose not to buy a finance application that would have cost about US$60,000 a year. HR, finance, operations, and sales build their own scenarios, and one annual HR process fell from about 30 days to 2 hours.
- Vendor case study
- Savings and process time reported by the customer
- Published by Make
Deployment details
IT and business units at a US company of 1,001 to 5,000 employees.
- Vendor case study
- Savings and process time reported by the customer
- Published by Make
- Team
- FranklinCovey IT under the CIO, with business-unit staff building scenarios
- Duration
- Multiple years of use, per the CIO
- Workload
- System integration in place of a 15-year-old service bus, plus departmental workflows
- Product version
- Make scenarios with automation and agentic features
- Measurement
- One annual HR process cut from about 30 days to 2 hours; about US$60,000 a year in software spend avoided
