ဤအပိုင်းအကြောင်း
Could your enterprise data support a reliable report and still leave an AI agent unsure what the numbers mean?
In this episode of Tech Talks Daily, I speak with Saurabh Gupta, CEO of The Modern Data Company, about the difference between being analytics ready and AI ready.
Saurabh's background includes data strategy and governance work at Thoughtworks, Washington DC government, and international organizations. Our conversation focuses on the information around data that machines need when they begin consuming it directly.
A familiar reporting process can depend on human knowledge that never becomes part of the underlying dataset. Saurabh describes a system-of-record report exported to Excel, adjusted, and then used for compliance reporting. The spreadsheet and the original source now tell different stories. If an AI system encounters multiple copies, it needs a way to understand which version is appropriate and why.
We discuss how context includes quality, lineage, transformations, meaning, usage, and permissions. Those details often live across separate tools and teams. Bringing them together is part of the challenge of making data useful to agents, rather than simply making it available.
The distinction becomes clearer through a furniture company's date fields. Saurabh describes 14 fields that were tagged similarly but carried different business meanings. A warehouse, an ecommerce team, and a delivery team can use a label in different ways. An answer based on the wrong interpretation may look convincing while failing to address the question.
Governance also needs to reach the point of consumption. Saurabh explains why one person may be allowed to see a name, address, and date of birth while another needs the same fields masked. His approach is to connect those permissions with how the data is used, including when a machine becomes the consumer.
We then discuss DataOS, which The Modern Data Company describes as a platform for data products. Saurabh argues for starting with the outcome a user wants, then working backward to the necessary sources and controls. He explains how the company brings data from different locations into that process, while acknowledging that moving or centralizing data can still be appropriate where latency requires it.
The interview also addresses measurement. Saurabh clarifies the company's 90% claim as faster use-case delivery or time saved. It is not a 90% increase in adoption. He describes tracking data interactions to identify stale processing and report schedules that do not reflect actual use. The company also reports potential reductions in data ownership costs, but the interview does not provide enough detail to treat those figures as a universal return.
For CIOs and CDOs, his practical recommendation is to begin with a business problem and implement incrementally. A clearer view of which data people consume can help teams decide what to process, what to retire, and which investments serve a useful outcome.
We also discuss how AI may change the division of work between consumers, analysts, and engineers. Saurabh's forecast is a strong one. The broader issue is how organizations preserve business interpretation and accountability as additional reporting tasks move into automated systems.
The resources supplied after the interview include the company website, the Modern Data 101 practitioner community, and The Modern Data Report 2026. They offer destinations for listeners who want to continue learning about the team's approach.
What would make your data genuinely ready for AI, and where do definitions, permissions, or inconsistent copies still create uncertainty? Please listen and share your thoughts.
