The concept of a digital twin isn’t new. Manufacturing and engineering have used them for years. A virtual replica of a physical system that updates in real time and lets you monitor, analyze, and simulate against it. What I’ve been noodling on for a couple of years now is what that concept looks like when you apply it to a business. Not a dashboard. Not a data warehouse. A living, continuously updated model of how your organization actually operates.
Where the idea started
The idea started taking shape for me when I was building Iris, a sales operations platform that integrated directly into Slack and wired together Salesforce, Gong, Jira, and Slack into a single conversational interface. The more systems I connected, the more obvious it became that the real value wasn’t in any single integration. It was in the connections between them. A lead doesn’t just appear in a CRM. It originated somewhere, touched specific content, was influenced by specific market conditions, and was handled by a specific seller running a specific process.
That’s the enterprise digital twin. Your CRM, marketing automation, web analytics, ad spend, support systems, sales call transcripts, pricing engines, contract data, all feeding into a unified model where the relationships between them are mapped as they actually exist. You stop asking “how’s the website doing” and start asking how your public brand presence is correlating with pipeline generation in a specific segment this quarter versus last.
An always-on analytical surface
Once the twin has enough signal, it becomes an analytical surface. This is the same idea from the sales call analysis work. Taking data that already exists and interrogating it with real specificity. What does the qualification process actually look like for sellers who close versus sellers who don’t? What content sequences correlate with faster deal cycles? Which pricing structures produce better retention in which segments? These aren’t questions you answer with a single query. They’re questions the twin is always computing against.
Tracking not just what things mean, but when those meanings changed and why.
Consistency matters here too. Human analysis of these patterns is inherently variable. Different managers interpret different signals differently, institutional knowledge lives in people’s heads, judgment shifts with mood and context. The twin doesn’t eliminate subjectivity entirely. The prompts and frameworks still reflect choices. But it applies those choices consistently across every data point, every time.
Ontology with lineage
But the part of this concept I keep coming back to is the ontology layer. And specifically, ontology with lineage.
Everyone talks about ontology as a way to give context to data. And it is. The twin needs a structured representation of what things mean within your organization and how they relate to each other. What counts as an “enterprise deal” in your organization? What’s the boundary between marketing-qualified and sales-qualified? How do your product lines relate to your market segments? These definitions aren’t static. They shift as the business evolves.
But most people stop there. They think of ontology as a flat map of definitions. What makes it powerful is the time dimension. Lineage. Tracking not just what things mean, but when those meanings changed and why.
When your company changes its pricing structure, redefines deal stages, reorganizes territories, or shifts its ICP, those changes are inflection points in your data. Without lineage, a model that compares Q1 to Q3 might be comparing two fundamentally different definitions of success without knowing it. With lineage, those changes become data points themselves. You can see that close rates shifted in Q3, and the twin knows that Q3 is also when the pricing model changed, the sales team was restructured, and the definition of “qualified” was updated. The correlation surface gets dramatically richer.
This is what takes relatively flat data analysis and gives it real depth. Recording mandated changes, strategic pivots, and definitional shifts as first-class data turns organizational history from institutional memory into something queryable. The kind of context that usually lives in someone’s head or gets lost when that person leaves.
Management and accountability
And it applies well beyond sales and marketing. Think about management. Employment records, org changes, who managed what team and when, what turnover looked like during those periods. Historically this stuff gets rolled up to the top based on feels. Based on what managers wanted to share. Based on what employees felt comfortable putting in their company or manager reviews. Now consider all of that as a data layer you can correlate against your larger organization’s data.
Say your support team’s ticket resolution rate starts dropping. You dig in and the decline started shortly after manager X took over that team. Then you start noticing attrition ticking up in the same group while the rest of the org is stable. These are patterns that exist in the data today but nobody is connecting them because the systems don’t talk to each other and there’s no time dimension tying it together.
Consider the level of accountability that provides. Not based on what someone chose to report upward. Based on what actually happened, tracked over time, correlated against everything else the organization knows about itself.
This isn’t something that exists yet. Not the way I’m describing it. But the pieces are all there. The integrations, the analytical capability, the ability to model relationships between systems at scale. The interesting work is in the ontology and lineage layer, because that’s what turns a collection of connected data sources into something that actually understands the business it’s modeling.