One Merger, Three BI Environments: How Franklin Templeton Built an AI-Ready Analytics Foundation
Quick Answer
Franklin Templeton unified three separate BI environments by standardizing identity and access, centralizing governed business logic, and consolidating its deployments on Strategy.
The move reduced infrastructure and security-management overhead while creating a consistent analytics foundation for enterprise AI.
Every acquisition creates a moment of reckoning for enterprise technology. Two companies, multiple tech stacks, one big decision: how to consolidate without losing business logic, weakening security, or delaying strategic initiatives?
For Franklin Templeton, a $1.6 trillion global asset manager, that moment arrived in 2024 with its acquisition of Putnam Investments, and it landed squarely on the BI team's desk. But the inherited environments introduced a significant integration challenge: a fragmented analytics foundation spread across multiple deployments.
As Sulochana Modur, Director of Enterprise Business Intelligence, highlighted:
"We had to go back to evaluating, because Franklin Templeton had a few other tools."
Three BI environments created one integration problem
Most merger playbooks push teams to consolidate data onto whatever's already standard. Franklin Templeton paused first, testing the new ecosystem before making a decision.
The team found three independent environments, each with its own contract, semantic layer, and authentication model. These differences created a complex integration challenge:
On-Premises (Standard): Data stored on physical, company-owned servers inside their own building, secured by basic, traditional corporate login methods.
On-Premises (Custom): Also stored on physical office servers, but locked behind a highly specific, home-grown security system built by engineers before the acquisition.
Cloud-Native: Another modern data setup inherited from Putnam that lived entirely on the internet (AWS) and used a modern, centralized login tool (Okta Single Sign-On).
Ultimately, this meant the organization now had three separate, locked data silos that couldn't talk to each other, preventing employees from getting a single, unified view of their business data.
Reconciling three sets of business logic is difficult enough on its own. Doing it alongside three separate security architectures, under a regulated financial services compliance regime, was even more complex.
What are the risks of having multiple versions of business logic?
Multiple versions of business logic create conflicting definitions, calculation paths, and governance rules. When different departments calculate core metrics (like revenue, risk, or growth) using different rules (such as definitions, structures, and security protocols), it leads to inaccurate reporting. This prevents the organization from achieving a single source of truth and introduces severe compliance risks in highly regulated industries.
Unifying business logic, identity, and governed access
Franklin Templeton's first step was to perform a comprehensive security review, helping the team identify potential vulnerabilities and control gaps across the fragmented environments.
Sulochana Modur explained why Strategy was Franklin Templeton's preferred partner for this evaluation:
"Our push was to consolidate existing platforms but having worked with Strategy for a long time at Putnam Investments, we decided to take a first look at what capabilities the tool brings us."
Its engineering and security teams worked alongside Strategy to evaluate the path toward Strategy's native cloud environment, harden firewalls, validate the architecture against Franklin Templeton's data-protection, security, and regulatory requirements.
Once the foundation was secure, Franklin Templeton standardized identity and access for all three instances through Okta single sign-on, with governed access to Snowflake. This delivered three core benefits:
Seamless Access: User credentials passed straight through to Snowflake's multi-cloud architecture without delays or operational friction.
Strict Data Governance: Existing entitlements were applied so users could access only the data authorized for their roles, minimizing the risk of leaks and compliance issues.
Zero Logic Duplication: The organization could manage reusable business logic through one semantic foundation rather than maintaining separate versions.
As a result, Franklin Templeton retired its legacy on-prem servers and consolidated three separate contracts and data environments into one AI-ready platform, with monthly security patching handled by Strategy instead of an internal team's already-stretched bandwidth.
Building a governed foundation for AI analytics
The unified semantic and security foundation gave Franklin Templeton a governed base for moving selected AI analytics use cases into production.
Users gained access to Strategy's out-of-the-box AI tools, including Auto Answers, Auto Dashboards, and Auto Narratives. Because the team had already unified the metadata within the semantic layer, the underlying business logic remained consistent, allowing AI outputs to follow the same approved definitions and calculation rules.
The value of this shared foundation is perfectly exemplified with the "organic growth rate" metric. Originally, calculating this required a complex, multi-pass process: analysts had to manually pull sales for a specific period, extract assets for the same timeframe, and then carefully derive the final rate from both data sets.
With the latest iteration of Strategy's AI agents, Franklin Templeton's team can now embed custom instructions directly at both the attribute and agent level. The AI agent can execute the defined mathematical sequence and return an answer based on the same governed logic.
Franklin Templeton's next focus is on leveraging Strategy's HyperIntelligence. The organization is exploring how HyperIntelligence can surface real-time, "zero-click" insights from these AI agents inside web browsers, emails, and other tools employees already use.
The result: stronger governance with less infrastructure overhead
As Khalil Parran, Senior Vice President of Enterprise Data & Analytics, put it:
"Implementing Strategy One has opened up opportunities to provide data insights efficiently while reducing risk and ultimately enabling better data-driven decisions."
The proof is in the results. By consolidating three separate environments and establishing a single, unified source of business logic, Franklin Templeton now possesses a data infrastructure that's ready for AI-driven analytics.
This unified data foundation has delivered three major strategic advantages:
Comprehensive Market Benchmarking: The enterprise dashboard suite combines Franklin Templeton's own investment performance data with competitor metrics from Morningstar and Lipper.
Flawless Data Oversight: Teams possess unprecedented access controls through Strategy's enterprise-grade governance framework.
Reduced IT Maintenance: The organization has reduced the internal overhead associated with platform upgrades, security patching, and infrastructure management.
What financial services leaders can learn from Franklin Templeton
For any organization navigating a complex merger, or simply carrying the accumulated weight of multiple fragmented BI tools, Franklin Templeton's path offers a clear lesson.
True data consolidation doesn't start by adding more tools. It starts by understanding how your organization collects, combines, and controls its data sources. A successful integration requires building a governed source of business logic that BI and AI applications can rely on.


.png&w=750&q=75)




