Total Economic Impact

The Total Economic Impact™ Of Observe By Snowflake

Cost Savings And Business Benefits Enabled By Observe

A FORRESTER TOTAL ECONOMIC IMPACT STUDY COMMISSIONED BY Snowflake, november 2026

[CONTENT]
 

Total Economic Impact

The Total Economic Impact™ Of Observe By Snowflake

Cost Savings And Business Benefits Enabled By Observe

A FORRESTER TOTAL ECONOMIC IMPACT STUDY COMMISSIONED BY Snowflake, november 2026

Forrester Print Hero Background
T
B
M
K
[CONTENT]
[CONTENT]

Executive Summary

Forrester research indicates that fragmented data, inconsistent context, and limited governance undermine operational outcomes, while modern observability capabilities can play a key role in enabling proactive issue detection, smarter operations, and stronger business continuity.1 Organizations must modernize their observability capabilities to move beyond reactive firefighting and manage increasingly complex cloud, AI, and agentic environments with greater resilience and accountability.2

Observe by Snowflake is a cloud-native observability solution built on the Snowflake data platform to collect, correlate, and analyze logs, metrics, traces, and events across applications, infrastructure, and business systems. Snowflake’s separation of cloud object storage and compute can enable cost-efficient telemetry retention and flexible compute for analysis as data volumes grow, while bringing telemetry into the broader enterprise data estate. This foundation helps engineering, operations, and site reliability engineering (SRE) teams investigate issues, understand dependencies, and connect system performance with business context.

Snowflake commissioned Forrester Consulting to conduct a Total Economic Impact™ (TEI) study and examine the potential return on investment (ROI) enterprises may realize by deploying Observe.3 The purpose of this study is to provide readers with a framework to evaluate the potential financial impact of Observe on their organizations.

Key Statistics

190%

Return on investment (ROI) 

$34.2M

Benefits PV 

$22.4M

Net present value (NPV) 

To better understand the benefits, costs, and risks associated with this investment, Forrester interviewed four decision-makers with experience using Observe. For the purposes of this study, Forrester aggregated the experiences of the interviewees and combined the results into a single composite organization, which is a global enterprise that employs a team of 25 SREs and 1,000 other technical and engineering staff in multiple geographic locations.

Before adopting Observe, interviewees relied on a mix of observability and monitoring tools and internally developed platforms, which were managed by centralized operations, SRE, platform engineering, and observability teams. As telemetry volumes and system complexity grew, these multitool environments made it difficult to correlate data across systems, increasing operational overhead and limiting the scalability of observability practices across the enterprise.

After the investment in Observe, the interviewees’ organizations benefited from a unified observability platform that improved visibility across applications and infrastructure, accelerated troubleshooting and root cause analysis, and delivered lower observability costs at scale. It also improved operational efficiency, reliability, and engineering productivity compared with their previous observability environments. Finally, Observe enabled teams to scale observability practices to more users and use cases without proportional increases in effort.

Key Findings

Quantified benefits. Quantified benefits for the composite organization include:

  • Avoiding spending to scale observability delivers $15.9 million to the bottom line. The composite organization selects Observe to address a growing challenge: rapidly expanding telemetry volumes that outpace the scalability, economics, and operational feasibility of traditional observability platforms. Observe enables the composite to support enterprise-scale growth, including hundreds of terabytes of telemetry per day and future petabyte-scale workloads, while maintaining lower unit costs, longer data retention, and more predictable spending than its legacy solutions.

  • Improving technical and engineering productivity saves $15.0 million in human resources. Observe improves SRE and platform engineer productivity at the composite by consolidating fragmented observability tools into a single platform, reducing administrative overhead, accelerating investigations, and simplifying onboarding. It also improves application engineer and other technical personnel productivity by democratizing access to observability data, enabling developers and operational teams to troubleshoot independently without relying on SRE specialists. By replacing fragmented tools and complex query languages with a more accessible, unified platform, Observe accelerates onboarding, simplifies root cause analysis, and gives technical employees greater visibility into dependencies, helping teams resolve issues faster and work more efficiently.

  • Enhancing system reliability provides $3.3 million in unplanned downtime cost savings. Observe improves system reliability for the composite organization by unifying telemetry data, accelerating root cause analysis, and providing greater visibility into application and service dependencies. The composite experiences faster resolution of incidents, broader adoption of modern observability practices, reduced reliance on specialized experts, and a stronger ability to proactively identify and mitigate operational risks across complex environments.

Unquantified benefits. Benefits that provide value for the composite organization but are not quantified for this study include:

  • Reduced operational risk through better governance and security practices. Observe strengthens the composite’s operational governance by centralizing observability data, reducing reliance on direct system access, and supporting more secure troubleshooting and monitoring practices.

  • Increased observability maturity through a unified full-stack platform. Observe helps the composite organization advance its observability maturity by bringing logs, traces, metrics, and other operational data together in a common platform, creating a more comprehensive view of system health and behavior.

  • Greater organizational flexibility through open architectures and reduced vendor lock-in. Observe provides the composite organization with strategic flexibility by supporting open standards (e.g., OpenTelemetry, Apache Iceberg) and data portability, helping it avoid vendor lock-in and adapt more easily to future technology changes.

Quantified costs. Quantified costs for the composite organization include:

  • Fees paid to Snowflake to access Observe functionality total $10.8 million. The composite leverages Observe to scale its telemetry collection and extend data retention. The predictable ingest-based pricing model helps it avoid cost escalations often associated with traditional observability platforms.

  • Internal time spent on preparation and implementation costs $1.0 million. To deploy Observe, the composite focuses primarily on observability strategy, vendor evaluation, telemetry onboarding, OpenTelemetry instrumentation, and user adoption rather than large-scale infrastructure changes.

The financial analysis that is based on the interviews found that a composite organization experiences benefits of $34.2 million over three years versus costs of $11.8 million, adding up to a net present value (NPV) of $22.4 million and an ROI of 190%.

“The difference with Observe is that it’s much easier to keep all the data, and to use that data to see what’s going on, avoid problems, and resolve incidents.”

Head of SRE, educational technology

Benefits (Three-Year)

[CHART DIV CONTAINER]
Avoided spending to scale observability Improved technical and engineering productivity Enhanced system reliability

The Observe Customer Journey

Drivers leading to the investment in Observe by Snowflake

Interviews

Role Industry Region Users Telemetry Volume
SRE leader Financial services APAC 5,100 200 TB per day (logs only)
Distinguished engineer, enterprise observability Financial services Global ~1,000 400 TB per day
Head of SRE Educational technology Global ~900 ~30 TB per day
Head of platform for observability Financial services Global >6,500 Not available

Key Challenges

Before adopting Observe by Snowflake, interviewees described fragmented and immature observability environments spread across multiple commercially available tools and internally built solutions. Observability was generally managed by centralized operations, SRE, platform engineering, or observability teams that collected and analyzed logs, metrics, traces, and infrastructure data on behalf of application and infrastructure teams. Engineers used these tools to monitor application health, investigate incidents, troubleshoot performance issues, and support operational reliability across increasingly complex cloud and hybrid environments.

Despite significant investments in monitoring and logging tools, teams struggled to gain a complete operational picture of increasingly complex, distributed environments. These challenges created operational inefficiencies, slowed incident response, and limited organizations’ ability to mature their observability practices. Specific challenges included:

  • Fragmented observability stacks created data silos. Interviewees’ organizations relied on multiple monitoring, logging, and application performance management tools, each containing only a portion of the information required to understand system behavior. Teams often used combinations of multiple specialized observability tools, forcing engineers to switch between them and manually correlate information during troubleshooting and analysis. The distinguished engineer in enterprise reliability at a financial services firm recalled: “Before Observe, we had multiple tools for traditional observability. We had one for application performance monitoring (APM) infrastructure, another for cloud infrastructure, and another for logs. There were probably five to seven variations of open-source commercial products. This made it difficult or impossible to correlate our traces, our APM data, and our infrastructure to our application logs.” Similarly, the SRE leader at another financial services firm described an environment consisting of five well-known commercial products and several niche tools: “There was a lot of complexity there. It was not a great engineering experience.”

  • Limited visibility across application and infrastructure dependencies. Interviewees consistently described difficulty understanding how systems interacted across organizational boundaries. The head of platform for observability at a financial services firm noted that their SRE teams often had visibility only into data they personally owned, which made it challenging to understand upstream and downstream dependencies or diagnose issues that spanned multiple domains. The distinguished engineer in enterprise observability at another financial services firm described similar challenges correlating infrastructure telemetry, applications, and logs that prevented teams from understanding end-to-end service relationships. Both agreed that a silo-driven lack of access to correlated cross-system data stopped their teams from developing a complete understanding of application dependencies and operational health.

  • Limited telemetry correlation that constrained observability maturity. Many interviewees’ organizations had strong logging capabilities but lacked effective ways to correlate logs, metrics, traces, and operational events. This limited their ability to understand system behavior holistically and prevented more advanced observability practices from emerging. The distinguished engineer in enterprise observability at a financial services firm reported that their teams struggled to build comprehensive visibility when telemetry was separated across multiple systems. Interviewees consistently characterized this as a barrier to achieving mature, full-stack observability.

  • Manual, time-consuming, and resource-intensive incident investigations. When incidents occurred, interviewees’ organizations frequently assembled large groups of stakeholders to determine ownership and root cause. Because data was fragmented across teams and systems, investigations required extensive manual coordination, with large numbers of people comparing evidence from different systems during incidents. The head of platform for observability at a financial services firm with more than 6,500 users explained: “In order to understand the root cause analysis, we’d have to get several hundred people on a call. And then one by one, they would come with the data that they produced and say, ‘Yes, it was me’ or ‘No, it wasn’t me.’ Everyone had to prove their guilt or innocence.” The head of SRE at an educational technology company similarly noted that incident investigations often depended on finding the individual who knew a particular system well enough to interpret telemetry, creating delays during critical events.

  • Challenges scaling existing platforms with telemetry growth. As interviewees’ organizations modernized applications and adopted cloud-native architectures, telemetry growth exposed limitations in existing observability platforms. The distinguished engineer in enterprise observability at a financial services firm described concerns about continuing to scale legacy platforms, and said, “We knew our observability platform wasn’t going to scale if we brought in all the other telemetry data from [our APM platform] into it.” He also noted that, even if it were possible, scaling their existing platform to support consolidated observability would have required substantial additional infrastructure, licensing, and support resources. The SRE leader at another financial services firm recalled that teams were using logging platforms to perform broader observability functions, which he described as “a very cost ineffective way to do things.”

  • Low adoption and usability of legacy tools. Several interviewees noted that existing observability tools were difficult to learn, cumbersome to use, or poorly aligned with modern engineering workflows. As a result, observability capabilities were often concentrated among specialists rather than broadly adopted across engineering organizations, which reduced the value derived from these observability investments. The SRE leader at one financial services firm stated that one of their tools “wasn’t that intuitive to use to get maximum value out of it,” and another said that “it wasn’t easy to learn the query language or the interface.” The head of SRE at an educational technology company similarly reported that engineers found their legacy observability platform difficult to use and that obtaining useful information often required mastering a specialized query language. The distinguished engineer in enterprise observability at a financial services firm also described a steep learning curve as teams became accustomed to operating within isolated tools designed for specific telemetry types.

“Everybody was kind of throwing their data in the pot and then trying to put Humpty Dumpty together on the fly in the middle of an incident.”

Head of platform for observability, financial services

Composite Organization

Based on the interviews, Forrester constructed a TEI framework, a composite company, and an ROI analysis that illustrates the areas financially affected. The composite organization is representative of the interviewees’ organizations, and it is used to present the aggregate financial analysis in the next section. The composite organization has the following characteristics:

  • Description of composite. The composite is a global enterprise that has infrastructure in multiple geographies to meet local data processing and storage regulations. It ingests approximately 20 terabytes of logs and 7.5 terabytes of traces daily and retains that data for six months. It also ingests 1 million data points per minute (DPM) in metrics, which it retains for 13 months.4 The organization employs 25 SRE team members to monitor and maintain its systems with this data, as well as 500 application engineers and 500 other technical personnel who also use the data to a varied extent to accomplish their jobs.

  • Deployment characteristics. The composite organization begins using Observe by Snowflake in Year 1 and realizes initial value within a few weeks. A broader rollout across geographies and channels, including legacy observability solution migration, team enablement, and use case expansion takes approximately four months. Adoption continues to deepen as engineering teams become more proficient with the platform’s self-service capabilities, extend its use across more applications, and develop more advanced observability practices.

 KEY ASSUMPTIONS

  • Global enterprise

  • 25 SREs

  • 500 application engineers

  • 500 other technical personnel, including other engineers using observability data

  • 20 TB per day of logs

  • 7.5 TB per day of traces

  • 1 million DPM of metrics

Analysis Of Benefits

Quantified benefit data as applied to the composite

Total Benefits

Ref. Benefit Year 1 Year 2 Year 3 Total Present Value
Atr Avoided spending to scale observability $6,375,000 $6,375,000 $6,375,000 $19,125,000 $15,853,681
Btr Improved technical and engineering productivity $4,709,790 $6,369,035 $7,310,655 $18,389,480 $15,037,896
Ctr Enhanced system reliability $722,500 $1,275,000 $2,125,000 $4,122,500 $3,307,081
  Total benefits (risk-adjusted) $11,807,290 $14,019,035 $15,810,655 $41,636,980 $34,198,658

Avoided Spending To Scale Observability

Evidence and data. A consistent theme across the interviews was that organizations were experiencing rapid growth in telemetry volumes while simultaneously facing pressure to control observability costs. Interviewees reported that many incumbent platforms were prohibitively expensive at enterprise scale, unable to support required retention periods and data volumes, or required complex architectures that increased infrastructure and operational overhead. They selected Observe because it combined scalability, lower unit costs, and an architecture capable of supporting future telemetry growth.

  • Interviewees described telemetry growth as a structural challenge driven by cloud adoption, modernization, microservices architectures, and increasing observability maturity. The SRE leader at one financial services firm reported processing just more than 200 terabytes of logs a day, with telemetry growth continuing as applications modernize. He explained, “As the business grows, and as it’s modernized, like going from monolithic-type applications to microservices, we see a massive increase in the amount of logging and tracing.” The distinguished engineer in enterprise observability at a financial services firm said they were already ingesting approximately 400 terabytes of data daily into Observe and had validated a future scale target approaching 1 petabyte per day. These organizations were not merely looking for a less expensive tool; they needed a platform capable of supporting orders-of-magnitude telemetry growth while remaining operationally feasible.

  • Interviewees repeatedly described how scaling traditional observability platforms to meet future needs would have required substantial ongoing investments in licensing, infrastructure, and staffing. According to the SRE leader at an APAC-based financial services firm, their organization’s objective was not necessarily to reduce observability spending but to avoid unsustainable cost growth while telemetry volumes expanded. They said, “Our whole business case around Observe is more trying to keep costs flat or minimize the uplift rather than cost savings.” The distinguished engineer in enterprise observability at a large financial services firm said the cost implications of scaling their legacy observability platform were even more pronounced. Although their organization considered consolidating telemetry into its logging platform, the economics were unworkable. This interviewee explained: “The cost and feasibility and the scaling just did not add up. We were looking at spending from $20 million to $60 million, easy. Most likely it would have been an $80 million investment year after year.”

  • More importantly, interviewees explained that they had evaluated the capabilities of their existing solutions, as well as others available to them, and had concluded that it was impossible to scale those platforms to fit their telemetry data needs. Several interviewees described conducting extensive evaluations of competing observability platforms before selecting Observe. The distinguished engineer in enterprise observability at a financial services firm said their evaluation of existing strategic vendors yielded disappointing conclusions, “When we approached them and asked, ‘Can you handle the volume that we have in application logs and [our observability platform]?’ they said no.”

  • A key advantage cited by interviewees was Observe’s lower cost structure relative to prior solutions. The head of SRE at an educational technology company reported spending only 9% more than they did for their previous logging environment while storing more than three times as much data. The company also reported lower spending on metrics relative to its legacy platform while continuing its migration effort. The head of platform for observability at a large financial services firm related that Observe offered lower costs and improved retention: “From a price-point perspective, Observe was slightly less expensive than our existing solution, and their cost model is ingest-based. So the default storage is much higher than a lot of other observability tools will give you.”

Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:

  • It was spending, or would have had to spend, $7.5 million annually on legacy observability tools to meet its telemetry ingestion and storage requirements.

  • It no longer needs to spend the money on these tools as it replaces them with Observe by Snowflake.

Risks. The scale of this benefit may vary by organization based on:

  • The amount of telemetry data an organization ingests and saves for analysis.

  • The licensing and other fees associated with the tool(s) it uses for its observability program before switching to Observe.

Results. To account for these risks, Forrester adjusted this benefit downward by 15%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $15.9 million.

“We were running a hundred terabytes a day of ingest, and while a lot of products might be options if you look at the cost on paper, in reality they just don’t scale. They just fall over and break. Observe’s scale, usability, and costs ticked all those boxes for us.”

SRE leader, financial services

“Observe was basically agnostic to data, and its Snowflake approach was very scalable from compute to storage. We were able to converge all our telemetry data and much more.”

Distinguished engineer, enterprise observability, financial services

“We’ve tripled the amount of telemetry we’re collecting at about the same investment, so that’s one-third the unit cost we were paying our legacy observability vendor.”

SRE leader, financial services

Avoided Spending To Scale Observability

Ref. Metric Source Year 1 Year 2 Year 3
A1 Projected cost of legacy observability solutions to meet telemetry needs Interviews $7,500,000 $7,500,000 $7,500,000
At Avoided spending to scale observability A1 $7,500,000 $7,500,000 $7,500,000
  Risk adjustment ↓15%      
Atr Avoided spending to scale observability (risk-adjusted)   $6,375,000 $6,375,000 $6,375,000
Three-year total: $19,125,000 Three-year present value: $15,853,681

Improved Technical And Engineering Productivity

Evidence and data. Interviewees’ organizations reported that Observe improved productivity across SRE, platform engineering, application engineering, development, observability, and operational support teams by consolidating fragmented observability environments, making telemetry easier to access and analyze, accelerating investigation workflows, and reducing reliance on specialized expertise. Before Observe, technical teams frequently moved between disconnected tools; manually correlated logs, metrics, traces, and infrastructure data; learned specialized query languages; and relied on SRE or observability specialists to investigate problems. Observe brought these activities into a common platform and data model, enabling a broader population of technical users to independently investigate issues while allowing SRE and platform teams to spend less time administering observability tools and supporting other engineering teams.
Interviewees agreed that Observe by Snowflake:

  • Reduced the operational burden of fragmented observability tooling. SRE and platform teams previously maintained and supported numerous overlapping monitoring and logging systems, which each introduced additional administration, integration, governance, and operational complexity. By consolidating telemetry into a common environment, Observe reduced the effort associated with managing disconnected observability systems and enabled these teams to focus more of their time on reliability engineering and other higher-value activities.

  • Accelerated troubleshooting and incident investigation. Technical teams previously spent substantial time locating and manually correlating information from logs, traces, infrastructure monitoring, and APM platforms before effective troubleshooting could begin. Observe brought telemetry into a single environment where relationships between data sources could be analyzed together, reducing the time engineers spent gathering evidence and coordinating across organizational boundaries and allowing them to focus more quickly on diagnosis and remediation.

  • Enabled application engineers, developers, and other technical personnel to troubleshoot more independently. Legacy observability platforms often required specialized knowledge or query language expertise, limiting the ability of application teams to investigate issues themselves. Observe made telemetry accessible to a broader technical audience, allowing engineers to answer operational questions and understand relationships among applications, infrastructure, and dependent services without relying as heavily on SREs, observability specialists, or other teams to retrieve and correlate data for them.

  • Improved visibility into application and service dependencies. As organizations adopted increasingly complex microservices architectures, their engineers struggled to understand upstream and downstream dependencies and determine how failures or application changes could affect other systems. Observe’s unified data model, through its Context Graph, improved SRE productivity by automatically establishing relationships among logs, metrics, traces, infrastructure, applications, code changes, and business entities. This reduced the manual effort SREs spent locating and correlating telemetry, reconstructing service dependencies, and coordinating with other teams during investigations. The Context Graph also provided AI SRE with the contextual information needed to reason across the environment, further accelerating troubleshooting and allowing SREs to redirect time toward higher-value reliability engineering activities.

  • Reduced the learning curve for observability. Interviewees highlighted Observe’s ease of use as an important productivity advantage. Compared with legacy tools that could require substantial onboarding, training, or specialized expertise, Observe enabled new SREs and application engineers to become productive faster, expanded observability use beyond small groups of power users, and reduced the time experienced engineers spent providing support and training.

  • Used AI to further streamline investigations. Observe’s AI SRE enabled users to ask questions in natural language and automatically investigated telemetry to help identify the causes of operational problems. Rather than simply searching raw logs, AI SRE reasoned over Observe’s Observability Context Graph, which connects logs, metrics, traces, infrastructure, applications, code changes, and business entities, further reducing the manual effort required to investigate complex issues.

  • Enabled technical teams to support growth without proportional increases in effort. Interviewees reported that Observe allowed SRE and observability teams to support expanding observability programs and substantially higher telemetry volumes without corresponding increases in operational administration, infrastructure management, or engineering effort. This allowed teams to redirect effort from tool management and manual investigations toward activities such as improving observability maturity, expanding tracing and telemetry coverage, and advancing reliability and AI-driven use cases.

Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:

  • It employs a 25-member SRE team, and the fully burdened hourly rate for these employees is $114.5

  • Before deploying Observe by Snowflake, each team member spends approximately 30% of their time monitoring and preventing incidents, and another 20% investigating and remediating incidents that do occur.

  • After deployment, that time investment decreases by 30% in Year 1, 50% in Year 2, and 60% in Year 3.

  • The composite employs 500 technical personnel to build and develop internal and market-facing applications.

  • Before Observe, these 500 people spend approximately 20% of their time testing for, identifying, and addressing UX and performance issues.

  • Once Observe is fully deployed by Year 3, these application engineers save 55% of that time, or 229 hours per engineer.

  • The organization employs another 500 technical users in roles such as operational support staff and database administrators, who are more moderate users of observability data.

  • These technical users spend approximately 15% of their time using telemetry data to perform their functions.

  • Once fully deployed by Year 3, Observe saves these technical users 50% of the time they previously spent gathering and analyzing telemetry data.

  • The average fully burdened hourly rate across all these other technical users is $91.6

  • The organization redeploys 50% of the total time saved as productive labor.

  • The impact of Observe ramps up over time as it is deployed across the organization and adopted by various technical personnel.

Risks. The scale of this benefit may vary by organization based on:

  • The size of the SRE, application engineering, and other technical teams and their rate of pay.

  • The mix of time devoted to tasks affected by Observe before deployment.

  • The rate at which an organization is able to recoup productive labor value from the time saved.

Results. To account for these risks, Forrester adjusted this benefit downward by 10%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $15.0 million.

60%

SRE time saved preventing, investigating, and remediating incidents

“Our enterprise systems are vast and complex and span across many different organizations. One of our largest frustrations before establishing a modern observability practice was the lack of transparency into data that the investigating teams themselves didn’t own.”

Head of platform for observability, financial services

“The amount of times I can onboard an engineer and have them doing useful work in less than half an hour is phenomenal.”

SRE leader, financial services

Improved Technical And Engineering Productivity

Ref. Metric Source Year 1 Year 2 Year 3
B1 SREs employed Composite 25 25 25
B2 SRE time spent investigating and remediating incidents before Observe (hours) Interviews 416 416 416
B3 SRE time spent after Observe (hours) Interviews 291 208 166
B4 SRE time spent monitoring/preventing incidents before Observe (hours) Interviews 624 624 624
B5 SRE time spent monitoring/preventing incidents after Observe (hours) Interviews 437 312 250
B6 Total SRE time saved with Observe (hours) (B2-B3)+(B4-B5)*B1 4,800 8,008 9,600
B7 Fully burdened hourly rate for an SRE Research data $114 $114 $114
B8 Application engineers employed Composite 500 500 500
B9 Application engineer time spent monitoring and fixing UX/performance before Observe (hours) Interviews 416 416 416
B10 Application engineer time spent monitoring and fixing UX/performance after Observe (hours) Interviews 250 208 187
B11 Total application engineer time saved with Observe (hours) (B9-B10)*B8 83,000 104,000 114,500
B12 Other technical users of observability data Composite 500 500 500
B13 Average time spent by other technical users on observability tasks before Observe (hours) Interviews 208 208 208
B14 Average time spent by other technical users on observability tasks with Observe (hours) Interviews 156 125 104
B15 Total time saved by other technical users with Observe (hours) (B13-B14)*B12 26,000 41,500 52,000
B16 Fully burdened hourly rate for other technical users of observability data Research data $91 $91 $91
B17 Productivity recapture TEI methodology 50% 50% 50%
Bt Improved technical and engineering productivity (B6*B7+B11*B16+B15*B16)*B17 $5,233,100 $7,076,706 $8,122,950
  Risk adjustment ↓10%      
Btr Improved technical and engineering productivity (risk-adjusted)   $4,709,790 $6,369,035 $7,310,655
Three-year total: $18,389,480 Three-year present value: $15,037,896

175,000+ hours

Technical time saved per year after full adoption

Enhanced System Reliability

Evidence and data. Interviewees’ organizations consistently described the reliability improvement as one of the most important outcomes of their Observe deployments. Before Observe, fragmented telemetry, limited visibility into system dependencies, and manual investigation processes made it difficult to quickly identify the causes of incidents and understand the impact of failures across increasingly complex technology environments. Observe enhanced reliability by providing unified visibility across telemetry sources, enabling faster diagnosis of system issues, improving understanding of service dependencies, and helping organizations proactively identify and address operational risks. As organizations expanded telemetry collection and improved data accessibility, they gained greater ability to identify patterns, dependencies, and operational anomalies that could affect reliability.

  • A recurring theme across interviews was that reliability suffered when logs, traces, infrastructure data, and application telemetry were distributed across multiple systems. Without a common view of telemetry, engineering teams often lacked the context required to quickly determine the source of service disruptions. Observe’s ability to bring these telemetry sources together enabled teams to understand system behavior more completely and identify issues before they became larger operational problems.

  • As organizations migrated toward cloud-native and microservices architectures, understanding service relationships became increasingly important for maintaining reliability. Before Observe, teams often struggled to identify which systems were affected by a particular dependency failure, resulting in longer investigations and uncertainty during incidents. Observe enabled engineers to visualize and analyze relationships between applications, infrastructure, and services in a unified environment. The head of platform for observability at a large financial services firm noted that at enterprises such as theirs, “the systems are vast and complex and span across many different organizations.” Observe helped expose these relationships, making it easier to understand the operational impact of failures and reducing the likelihood that hidden dependencies would compromise service reliability.

  • Observe accelerated root cause investigation during critical incidents, whereas interviewees described pre-Observe incident investigations as highly manual processes that often required contributions from many different teams. The head of platform for observability at a large financial services firm recalled that incident investigations routinely required pulling together people from across the organization on a call. Such investigations consumed significant operational resources and increased the duration and impact of service disruptions. Observe’s ability to correlate telemetry automatically reduced reliance on manual information gathering and enabled teams to focus on remediation rather than data collection.

  • Observe expanded the use of tracing and modern observability practices, and several interviewees linked improvements in reliability to broader adoption of distributed tracing and full-stack observability. The SRE leader at a financial services firm described their organization’s observability maturity journey: “Logging for us was level one. That’s what people did 10 years ago. Having metrics now is going to level two, and level three is going to be tracing.” He explained that Observe enabled their organization to collect and analyze significantly more telemetry than before, expanding visibility into the behavior of distributed applications. As tracing adoption increased, engineers gained greater insight into transaction flows, service interactions, and points of failure that previously would have been difficult to identify.

  • Several interviewees indicated that reliability improvements stemmed not only from technology capabilities but also from broader organizational access to operational knowledge, rather than their former reliance on individual experts. The head of platform for observability at one financial services firm and the SRE leader at another described environments where observability expertise was concentrated among a relatively small number of specialists. Observe made telemetry easier to access and understand, enabling more engineers to participate directly in operational troubleshooting and reducing key-person dependencies during incidents. This broader operational participation helped organizations respond more consistently and effectively to reliability events.

  • Finally, interviewees described Observe as providing a stronger foundation for identifying issues before they developed into larger business-impacting events. The head of platform for observability at one financial services firm emphasized the value of having access to data beyond what individual teams owned, allowing their organization to better understand systemwide behavior and emerging issues. The distinguished engineer in enterprise observability at another financial institution described Observe’s consolidated data environment as creating a foundation for advanced operational analytics and future AI-driven use cases, both of which depend on reliable telemetry and system visibility.

Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:

  • It experiences 10 hours of unplanned downtime annually before deploying Observe by Snowflake.

  • The total cost of that downtime for the organization averages $500,000 per hour. This includes internal (e.g., time to identify and remediate errors) and external (e.g., lost revenue, unproductive employees) costs.

  • After fully deploying Observe across the organization by Year 3, it reduces its unplanned downtime by 50% to 5 hours.

  • That improvement increases over time, beginning with a 35% reduction in Year 1 and a 40% reduction in Year 2.

Risks. The scale of this benefit may vary by organization based on:

  • The amount of unplanned downtime an organization experiences before using Observe by Snowflake in its observability program.

  • The specific costs to an organization for downtime incidences.

Results. To account for these risks, Forrester adjusted this benefit downward by 15%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $3.3 million.

50%

Reduction in unplanned downtime

“In order to do the root cause analysis, we would have to get several hundred people on a call. Everyone had to come and prove their guilt or innocence.”

Head of platform for observability, financial services

Enhanced System Reliability

Ref. Metric Source Year 1 Year 2 Year 3
C1 Average downtime before Observe (hours) Interviews 10.0 10.0 10.0
C2 Average downtime with Observe (hours) Interviews 8.3 7.0 5.0
C3 Average downtime cost per hour Composite $500,000 $500,000 $500,000
Ct Enhanced system reliability (C1-C2)*C3 $850,000 $1,500,000 $2,500,000
  Risk adjustment ↓15%      
Ctr Enhanced system reliability (risk-adjusted)   $722,500 $1,275,000 $2,125,000
Three-year total: $4,122,500 Three-year present value: $3,307,081

Unquantified Benefits

Benefits that provide value for the composite organization but are not quantified for this study include:

  • Increased observability maturity through a unified full-stack platform. Across their organizations, interviewees described Observe as a catalyst for advancing observability maturity by consolidating logs, metrics, traces, and infrastructure telemetry into a single platform and making that data more accessible across the enterprise. Rather than maintaining separate monitoring and observability tools for different use cases, teams were able to unify telemetry, standardize practices, and expand observability adoption to a broader set of users. The SRE leader at a financial services firm characterized this shift as “a massive step up in maturity for observability in the firm.” The head of platform for observability at another financial services firm explained that broader access to observability data increased organizational engagement and accelerated adoption of modern observability practices. Interviewees consistently indicated that Observe’s unified full-stack platform helped their organizations move beyond fragmented monitoring approaches toward a more mature observability model, enabling richer telemetry correlation, wider user adoption, and a common operational view across applications, infrastructure, and services.

  • Reduced operational risk through better governance and security practices. Interviewees described how Observe reduced operational risk by giving their organizations broader, more controlled access to observability data while improving governance, data management, and platform standardization. Interviewees explained that their organizations could safely retain more telemetry data, apply consistent observability practices across teams, reduce reliance on fragmented tools, and enable wider self-service access without requiring users to directly manage underlying data sources. These capabilities improved auditability, reduced the risk of missed operational issues, and helped them scale observability in a more secure and governed manner across the enterprise.

“We’ve attracted [internal] customers that were sitting on the sidelines. Now that they’ve played around in Observe and they understand what they can do with it, they’re like, ‘When can we get on?’”

Head of platform for observability, financial services

Flexibility

The value of flexibility is unique to each customer. There are multiple scenarios in which a customer might implement Observe and later realize additional uses and business opportunities, including:

  • Greater organizational flexibility through open data standards and reduced vendor lock-in. Interviewees collectively expressed concerns about vendor-specific technologies and proprietary formats that limited portability and future strategic options. They sought to reduce dependency on proprietary agents, data models, and architectures that limited flexibility and increased long-term platform risk. The distinguished engineer in enterprise observability at a financial services firm discussed these concerns with their legacy platforms, “The cost, feasibility and scaling just did not add up — and the technology was also proprietary with both of those tools, which limited our options.”
    Interviewees said that Observe provided greater organizational flexibility by enabling them to consolidate telemetry from diverse sources into a single platform without being constrained by the proprietary architectures, storage models, or data limitations of traditional observability tools. Observe’s embrace of open standards, like OpenTelemetry and Apache Iceberg, allowed their organizations to evolve observability strategies without having to redesign their tooling around vendor-specific requirements.

Flexibility would also be quantified when evaluated as part of a specific project (described in more detail in Total Economic Impact Approach).

“We really wanted to have something that was OpenTelemetry-native to give us that flexibility and ease if we wanted to move away from the product in the future.”

SRE leader, financial services

Analysis Of Costs

Quantified cost data as applied to the composite

Total Costs

Ref. Cost Initial Year 1 Year 2 Year 3 Total Present Value
Dtr Fees for Observe platform $0 $4,320,750 $4,320,750 $4,320,750 $12,962,250 $10,745,066
Etr Upfront planning and implementation $432,630 $358,358 $201,401 $141,341 $1,133,730 $1,031,049
  Total costs (risk-adjusted) $432,630 $4,679,108 $4,522,151 $4,462,091 $14,095,980 $11,776,115

Fees For Observe Platform

Evidence and data. Interviewees consistently described Observe’s pricing approach as materially different from traditional observability platforms, which often based price on indexed data, retained data, or multiple telemetry products. Instead, interviewees highlighted Observe’s predictable ingest-based pricing model, which allowed them to increase telemetry collection and retention without experiencing the same degree of cost escalation associated with incumbent solutions.

Note: Pricing varies depending on the type and amount of data collected and the required storage period. Contact Snowflake for additional details.

Modeling and assumptions. Based on the interviews, Forrester assumes that the composite organization pays Snowflake annual fees for the Observe platform of $4.1 million based on its unique telemetry data volume and storage requirements.

Risks. The impact of this cost may vary by organization depending on the following:

  • The size of an organization.

  • The amount of log, metric, and tracing data ingested.

  • The length of time an organization wants to store and use the data.

Results. To account for these risks, Forrester adjusted this cost upward by 5%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $10.7 million.

Fees For Observe Platform

Ref. Metric Source Initial Year 1 Year 2 Year 3
D1 Fees paid to Observe Observe 0 $4,115,000  $4,115,000 $4,115,000
Dt Fees for Observe platform D1 $0 $4,115,000 $4,115,000 $4,115,000
  Risk adjustment ↑5%        
Dtr Fees for Observe platform (risk-adjusted)   $0 $4,320,750 $4,320,750 $4,320,750
Three-year total: $12,962,250 Three-year present value: $10,745,066

Upfront Planning And Implementation

Evidence and data. Interviewees’ organizations generally described Observe deployments as requiring modest implementation effort relative to the scale of their observability environments. Most deployment activities focused on onboarding telemetry sources, configuring OpenTelemetry instrumentation, establishing data pipelines, and training engineering teams rather than performing large-scale infrastructure implementations. Because Observe is a SaaS offering and supports open standards, interviewees reported that much of the effort involved integrating existing telemetry sources into the platform rather than replacing or rebuilding application monitoring architectures. Their organizations spent the majority of upfront effort evaluating observability architectures, assessing scalability requirements, and determining telemetry onboarding approaches.

  • The SRE leader at one financial services firm indicated that platform selection involved extensive evaluation of alternative observability vendors, scalability testing, pricing analysis, and architectural review due to its large telemetry footprint, which exceeded 200 terabytes of logs per day. The primary planning effort centered on evaluating whether prospective solutions could support enterprise-scale telemetry growth while maintaining acceptable economics.

  • The distinguished engineer in enterprise observability at another financial firm described a similar extensive vendor evaluation process that examined whether competing solutions could handle their organization’s telemetry volumes and long-term scalability requirements before they selected Observe.

  • Rather than requiring major infrastructure deployments, implementations generally centered on onboarding logs, traces, metrics, and application telemetry into Observe. The SRE leader at a financial services firm described their deployment activities: “We went to all our different logging sources and got them reconfigured to point to the telemetry pipeline we created. For a number of weeks, we basically forked the data. We sent a copy of it to [our legacy platform] and a copy to Observe. That provided enough time for teams to go and get used to the data, build queries, build dashboards, and do training.”

  • Several interviewees emphasized that successful deployment required enabling engineers to use the platform effectively. However, participants generally reported that Observe’s usability reduced training requirements compared with prior observability platforms. This suggests that onboarding and adoption costs were relatively low because engineers could become productive quickly without extensive formal training.

  • Across interviews, the primary internal resources devoted to implementation were:

    • Platform engineering and observability teams responsible for architecture, telemetry onboarding, and governance.
    • SRE teams responsible for instrumentation, reliability workflows, and operational integration.
    • Application engineering teams responsible for tracing adoption and telemetry generation.
    • Security and infrastructure stakeholders involved in data access, governance, and platform integration.

Interviewees did not generally describe large dedicated deployment teams or extensive consulting engagements. Instead, deployment appeared to be executed primarily by existing engineering and observability personnel as part of broader modernization and observability initiatives.

Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:

  • In the pipeline creation and implementation phase of deployment, the 25 SRE team members, along with an additional 15 engineers from other teams, each spend about half of their time working on the project over a one-month period.

  • During implementation, the 25 SRE team members receive 10 hours of formal training on Observe.

  • In Years 1 to 3, each of the 1,000 non-SRE users receive 2 hours of formal training, but 100 of those each year (primarily application engineers) go on to receive an additional 8 hours of training as they ramp up their own use of Observe.

  • The equivalent of one SRE spends the first year facilitating rollout, migrating additional tools, and administering and maintaining the Observe platform.

  • That commitment falls to 15% of an FTE on an ongoing basis.

  • The average fully burdened hourly rate for an SRE is $114 and is $91 for other participating users.7

Risks. The impact of this cost may vary by organization depending on the following:

  • The size of an organization.

  • The amount and complexity of pipeline and migration work that needs to be completed up front.

  • The speed at which an organization wants to drive migration and adoption of the solution.

  • The extent to which non-SRE employees are engaged in using Observe, and how quickly that interest ramps up.

  • The skill levels of employees, especially non-SRE employees, which may vary by role and affect adoption speed.

Results. To account for these risks, Forrester adjusted this cost upward by 10%, yielding a three-year, risk-adjusted total PV of $1.0 million.

“Observe was super responsive. Once we signed, they stood up an instance for us within days. In approximately three weeks, we did a proof of concept for all our different must-have requirements.”

SRE leader, financial services

Upfront Planning And Implementation

Ref. Metric Source Initial Year 1 Year 2 Year 3
E1 Pipeline creation and implementation (hours) Interviews 3,200      
E2 User training (hours) Interviews 250 1,500 1,700 1,100
E3 Ongoing platform administration (hours) Interviews   2,080 312 312
E4 Fully burdened hourly rate for a relevant employee Research data $114 $91 $91 $91
Et Upfront planning and implementation (E1+E2+E3)*E4 $393,300 $325,780 $183,092 $128,492
  Risk adjustment ↑10%        
Etr Upfront planning and implementation (risk-adjusted)   $432,630 $358,358 $201,401 $141,341
Three-year total: $1,133,730 Three-year present value: $1,031,049

Financial Summary

Consolidated Three-Year, Risk-Adjusted Metrics

Cash Flow Chart (Risk-Adjusted)

[CHART DIV CONTAINER]
Total costs Total benefits Cumulative net benefits Initial Year 1 Year 2 Year 3

Cash Flow Analysis (Risk-Adjusted)

  Initial Year 1 Year 2 Year 3 Total Present Value
Total costs ($432,630) ($4,679,108) ($4,522,151) ($4,462,091) ($14,095,980) ($11,776,115)
Total benefits $0 $11,807,290 $14,019,035 $15,810,655 $41,636,980 $34,198,658
Net benefits ($432,630) $7,128,182 $9,496,884 $11,348,564 $27,541,000 $22,422,543
ROI           190%
Payback           <6 months

 Please Note

The financial results calculated in the Benefits and Costs sections can be used to determine the ROI, NPV, and payback period for the composite organization’s investment. Forrester assumes a yearly discount rate of 10% for this analysis.

These risk-adjusted ROI, NPV, and payback period values are determined by applying risk-adjustment factors to the unadjusted results in each Benefit and Cost section.

The initial investment column contains costs incurred at “time 0” or at the beginning of Year 1 that are not discounted. All other cash flows are discounted using the discount rate at the end of the year. PV calculations are calculated for each total cost and benefit estimate. NPV calculations in the summary tables are the sum of the initial investment and the discounted cash flows in each year. Sums and present value calculations of the Total Benefits, Total Costs, and Cash Flow tables may not exactly add up, as some rounding may occur.

From the information provided in the interviews, Forrester constructed a Total Economic Impact™ framework for those organizations considering an investment in Observe.

The objective of the framework is to identify the cost, benefit, flexibility, and risk factors that affect the investment decision. Forrester took a multistep approach to evaluate the impact that Observe can have on an organization.

Due Diligence

Interviewed Snowflake stakeholders and Forrester analysts to gather data relative to Observe.

Interviews

Interviewed four decision-makers at organizations using Observe to obtain data about costs, benefits, and risks.

Composite Organization

Designed a composite organization based on characteristics of the interviewees’ organizations.

Financial Model Framework

Constructed a financial model representative of the interviews using the TEI methodology and risk-adjusted the financial model based on issues and concerns of the interviewees.

Case Study

Employed four fundamental elements of TEI in modeling the investment impact: benefits, costs, flexibility, and risks. Given the increasing sophistication of ROI analyses related to IT investments, Forrester’s TEI methodology provides a complete picture of the total economic impact of purchase decisions. Please see Appendix A for additional information on the TEI methodology.

Total Economic Impact Approach

Benefits

Benefits represent the value the solution delivers to the business. The TEI methodology places equal weight on the measure of benefits and costs, allowing for a full examination of the solution’s effect on the entire organization.

Costs

Costs comprise all expenses necessary to deliver the proposed value, or benefits, of the solution. The methodology captures implementation and ongoing costs associated with the solution.

Flexibility

Flexibility represents the strategic value that can be obtained for some future additional investment building on top of the initial investment already made. The ability to capture that benefit has a PV that can be estimated.

Risks

Risks measure the uncertainty of benefit and cost estimates given: 1) the likelihood that estimates will meet original projections and 2) the likelihood that estimates will be tracked over time. TEI risk factors are based on “triangular distribution.”

Financial Terminology

Present value (PV)

The present or current value of (discounted) cost and benefit estimates given at an interest rate (the discount rate). The PVs of costs and benefits feed into the total NPV of cash flows.

Net present value (NPV)

The present or current value of (discounted) future net cash flows given an interest rate (the discount rate). A positive project NPV normally indicates that the investment should be made unless other projects have higher NPVs.

Return on investment (ROI)

A project’s expected return in percentage terms. ROI is calculated by dividing net benefits (benefits less costs) by costs.

Discount rate

The interest rate used in cash flow analysis to take into account the time value of money. Organizations typically use discount rates between 8% and 16%.

Payback

The breakeven point for an investment. This is the point in time at which net benefits (benefits minus costs) equal initial investment or cost.

Appendix A

Total Economic Impact

Total Economic Impact is a methodology developed by Forrester Research that enhances a company’s technology decision-making processes and assists solution providers in communicating their value proposition to clients. The TEI methodology helps companies demonstrate, justify, and realize the tangible value of business and technology initiatives to both senior management and other key stakeholders.

Appendix b

Endnotes

1 Source: The Strategic Role Of Observability At The Edge, Forrester Research, Inc., December 1, 2025; Embed Data Observability Principles Throughout Your Data Ecosystems, Forrester Research, October 1, 2026.

2 Source: Harness Contextual Observability To Drive Scalable Innovation And System Resilience, Forrester Research, Inc., October 31, 2025.

3 Total Economic Impact is a methodology developed by Forrester Research that enhances a company’s technology decision-making processes and assists solution providers in communicating their value proposition to clients. The TEI methodology helps companies demonstrate, justify, and realize the tangible value of business and technology initiatives to both senior management and other key stakeholders.

4 DPM is a measure of metric ingest volume. It means “data points received per minute” and is averaged over time. For example, 10,000 time series reporting every 10 seconds produce about 60,000 DPM: Each reports six times per minute.

5 Source: US Bureau of Labor Statistics.

6 Source: Ibid.

7 Source: Ibid.

Disclosures

Readers should be aware of the following:

This study is commissioned by Snowflake and delivered by Forrester Consulting. It is not meant to be used as a competitive analysis.

Forrester makes no assumptions as to the potential ROI that other organizations will receive. Forrester strongly advises that readers use their own estimates within the framework provided in the study to determine the appropriateness of an investment in Observe. For any interactive functionality, the intent is for the questions to solicit inputs specific to a prospect’s business. Forrester believes that this analysis is representative of what companies may achieve with Observe based on the inputs provided and any assumptions made. Forrester does not endorse Snowflake or its offerings. Although great care has been taken to ensure the accuracy and completeness of this model, Snowflake and Forrester Research are unable to accept any legal responsibility for any actions taken on the basis of the information contained herein. The interactive tool is provided ‘AS IS,’ and Forrester and Snowflake make no warranties of any kind.

Snowflake reviewed and provided feedback to Forrester, but Forrester maintains editorial control over the study and its findings and does not accept changes to the study that contradict Forrester’s findings or obscure the meaning of the study.

Snowflake provided the customer names for the interviews but did not participate in the interviews.

Consulting Team:

Kim Finnerty

Published

November 2026

The Total Economic Impact™ Of Observe By Snowflake