Case study · Failure database
Kenandy
Failure
Finance
Primary gap · Distribution Readiness
Distribution Readiness
Kenandy positioned itself as a cloud-based ERP solution native to Salesforce, targeting manufacturers and complex B2B enterprises. However, the company struggled with a fundamental distribution problem: its tight coupling to the Salesforce ecosystem limited its addressable market to existing Salesforce customers willing to adopt another vendor's solution within that platform. Rather than building independent sales channels or establishing direct relationships with manufacturers, Kenandy relied heavily on Salesforce's ecosystem partnerships, which proved insufficient for enterprise software adoption. The company lacked a clear path to customers outside this narrow channel. Warning signs emerged early: ERP implementations require extensive customization and change management, yet Kenandy's go-to-market approach didn't account for the sales complexity this demanded. The company eventually faced acquisition by Rootstock Software, suggesting its standalone growth strategy had stalled. The core weakness wasn't the product concept but the distribution strategy—betting entirely on Salesforce's platform without developing complementary sales infrastructure or industry-specific channels proved inadequate for penetrating the competitive ERP market.
Source: https://en.wikipedia.org/wiki/Kenandy
Don't repeat the pattern
ReadySetLaunch's Launch Control walks you through thirteen structured questions across the same pillars this case study failed on. You earn your readiness. You don't get told you're ready.
Pressure-test your idea