Case study · Failure database
Cullinet
Failure
Technology & Software
Primary gap · Demand Signal
Problem Clarity
Cullinet built IDMS, a hierarchical database management system that dominated mainframe environments throughout the 1980s. The core problem they addressed was real: enterprises needed reliable ways to store and retrieve massive volumes of data on expensive mainframe computers, where inefficiency meant substantial operational costs. Large financial institutions and government agencies experienced this acutely—a single poorly optimized database query could consume hours of costly processing time.
The problem was measurably observable through system performance metrics and processing logs. Yet Cullinet missed critical warning signs that relational databases were becoming viable alternatives. While they focused on optimizing their hierarchical model, companies like Oracle and Informix were gaining traction with more flexible relational systems. Cullinet's leadership underestimated how quickly relational technology would mature and how strongly customers would prefer SQL's intuitive query language over IDMS's complex navigation requirements. By the time they recognized the shift, their market position had eroded significantly, making them vulnerable to Computer Associates' 1989 acquisition.
Demand Signal
Cullinet built IDMS into the dominant database system for mainframe environments during the 1970s and 1980s, with behavioral signals showing genuine adoption: enterprises standardized on IDMS across critical operations, customers invested heavily in training staff, and renewal rates remained strong. Early traction manifested through expanding market share in banking and insurance sectors, where mission-critical systems depended on their technology. Revenue growth and customer retention appeared to validate demand beyond stated interest.
However, Cullinet missed a fundamental shift. While they measured success through mainframe penetration and existing customer loyalty, the industry was transitioning toward client-server and distributed computing architectures. Their warning signs went unheeded: declining new customer acquisition, difficulty attracting younger developers, and resistance to modernizing their product stack. By the time Computer Associates acquired them in 1989, Cullinet's core market was already contracting. They had validated demand within a shrinking ecosystem, confusing customer stickiness with market growth. Their error wasn't measuring wrong—it was measuring the wrong market.
Source: https://en.wikipedia.org/wiki/Cullinet
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