Overview
In this episode of The Dashboard Effect, Brick Thompson and Caleb Oaks make a distinction that is easy to overlook in the middle of a software implementation: deploying a platform and getting business results from it are not the same thing. The conversation covers why the default reporting built into CRMs and ERPs consistently falls short of what organizations actually need to measure performance, and what it takes to build the analytics layer that turns software investment into measurable business outcomes.
The gap between software deployment and business results is almost always a data architecture problem. See how Blue Margin’s Managed Data Platform helps organizations build the consolidated data foundation that turns their existing software investments into the cross-system insights their business actually needs.
What This Episode Covers
The Limitation of Canned Reporting (1:24 – 1:59, 4:00 – 4:21)
The reporting built into most CRMs and ERPs provides snapshots of current data but does not track trends over time in the ways that business decision-making requires. Even with customization, these systems remain siloed: they can report on what is happening within their own data but cannot relate that data to information living in other platforms. The result is that each system tells part of the story, and nobody has a complete picture.
The Role of a Data Lakehouse (4:36 – 6:13)
Moving data into a consolidated data lakehouse addresses the silo problem directly. A central data environment provides the flexibility to store long-term historical data, enables an analytics team to work across multiple source systems simultaneously, and removes the dependency on individual vendors for reporting that those vendors were not designed to provide. The lakehouse is not a replacement for the operational systems. It is the layer that makes their data collectively useful.
The Power of Cross-System Insights (6:14 – 7:06)
The most significant business impacts from data consolidation come from the connections that only become visible when data from different systems is brought together. The hosts use field services as a concrete example: combining fleet management data with timekeeping records and work order values produces a true measure of technician utilization and first-time fix rates that no individual system could generate on its own. That kind of cross-system insight is where the real return on data investment lives.
Preparing for the Future of AI (8:16 – 9:09)
As AI and machine learning capabilities become embedded in enterprise software, those capabilities will likely remain siloed within their respective platforms unless organizations have built a central data environment to feed them consolidated data. Predictive analytics like customer churn forecasting require a complete view of the customer across systems, not just the slice visible from within a single platform. A central data layer is not just valuable for current analytics. It is the infrastructure that makes enterprise AI meaningful rather than limited.
Business Results as the Measure of Success (9:33 – 10:47)
The hosts close with a framing that should sit at the center of every software and data investment conversation: the goal is not process improvement. It is business results. Organizations that cannot quantify the impact of their investments on the metrics that matter to the business have not finished the job, regardless of how well the software is configured or how clean the data is. Taking control of the data is what makes it possible to close that loop and demonstrate that the investment was worth making.
Who It’s For
This episode is worth your time if you are a business or technology leader who has invested in modern CRM or ERP platforms and is still unable to answer the cross-system questions that those investments were supposed to make easier, a data or analytics team trying to make the case internally for a consolidated data environment beyond what individual platform vendors provide, a CFO or operations leader evaluating whether current software investments are producing the business results they were purchased to deliver, or any organization that has strong operational systems and weak cross-system visibility and wants to understand what closing that gap requires.
Why It’s Worth a Listen
The software implementation versus business results distinction is one that many organizations discover too late, after a significant investment has been made and the expected outcomes have not materialized. This episode names that gap clearly and connects it to the specific architectural decision, consolidating data into a lakehouse rather than relying on platform-native reporting, that closes it.
The cross-system insights example is the most concrete illustration of where value lives in a consolidated data environment. The individual data points for technician utilization exist in multiple systems already. The insight that drives operational improvement only exists when those points are connected, and that connection requires infrastructure that no individual vendor will build for you. Understanding that dynamic changes how organizations think about what a data investment is actually purchasing.
And the AI readiness point is increasingly relevant for organizations evaluating enterprise software with embedded AI features. Those features are only as useful as the data they can access, and a siloed platform can only access siloed data. The organizations that will get the most from enterprise AI are the ones that have already built the consolidated data environment that makes AI insights comprehensive rather than partial.
