Datacubed Health’s Path to Enterprise: Transforming from Academic Project to Enterprise Solution

The gap between academic innovation and enterprise adoption is where many promising technologies go to die. In a recent Category Visionaries episode, Datacubed Health CEO Brett Kleger revealed how they navigated this treacherous transition, offering a masterclass in transforming academic IP into enterprise-ready solutions.

The Academic Foundation

When Brett joined Datacubed Health in 2020, he inherited a company built on strong academic principles but facing commercial challenges. “They had a product that was getting into market. I would say it was mostly pre revenue. It was mostly pilot testing an incredible product, but they hadn’t really focused as much on the go to market to date,” Brett explains.

Founded by renowned neuroeconomist Dr. Paul Glimcher, the company had spent years developing and testing their solution in academic settings. As Brett notes, “It was more about spending several years to build the product up out to test it on academia, but not necessarily to bring the business case together or the go to market strategies together on how do you make this a much more broad based enterprise solution for the pharmaceutical industry.”

The Pivot Point

The transformation began with a crucial insight about the market. While most clinical trial solutions focused purely on data collection, Datacubed Health had developed something different. “When I first met Paul and first learned about the solution, what really was key to me and different to me is it was entirely focused on the patient,” Brett recalls.

This patient-centric approach became the foundation for their enterprise positioning. However, translating academic innovation into enterprise value required fundamental changes in how the company operated.

Building an Enterprise-Ready Team

The first major shift came in talent strategy. “My focus from a personnel perspective was bringing in the experience or the knowledgeable talent to surround it with an incredible product,” Brett explains. This meant building a team that understood both the technology and the enterprise buying cycle.

The focus shifted from pure innovation to practical implementation: “When I look at the space right now, a lot of companies are good technology companies can build it, but you need to understand the exact vertical that you’re in and that buying customer.”

The Founder Transition

Perhaps the most challenging aspect of the transformation was managing the founder transition. “The founder of the company is a tremendous person, tremendous individual, beloved individual, hyper focused on the users and team members,” Brett acknowledges. However, the needs of an enterprise-focused company required different leadership approaches.

This led to what Brett describes as a pivotal moment: “We looked and said, what happens when new CEO comes in, when the founder may not have the same ideals in terms of going to the market and the product?” The decision to transition leadership marked a crucial step in the company’s evolution from academic project to enterprise solution.

Redefining Success Metrics

The transformation required new ways of measuring success. Instead of focusing solely on technical innovation, the company began evaluating itself through enterprise metrics. Brett implemented a two-tier approach:

1. Immediate ROI through lead management and sales metrics
2. Long-term brand building measured through sales team efficiency

The Enterprise Positioning Strategy

Rather than competing on pure innovation, Datacubed Health positioned itself as the reliable choice in a risk-averse market. “We don’t want to be a sexy tool. We don’t want to be the shiny object that comes and goes very quickly but can’t deliver. We want to be seen as the company that knows the space and can deliver reliably,” Brett emphasizes.

For founders navigating the transition from academic project to enterprise solution, Datacubed Health’s journey offers crucial lessons. Success isn’t just about having superior technology – it’s about building the organizational capabilities, market understanding, and operational discipline required for enterprise adoption.

Most importantly, it demonstrates that academic origins can be a strength rather than a liability when properly positioned. The key is understanding how to translate academic rigor into enterprise value while building the commercial infrastructure needed for scale.