[CONTENT]
$
USD
Total Economic Impact
Cost Savings And Business Benefits Enabled By Hasura
A FORRESTER TOTAL ECONOMIC IMPACT STUDY COMMISSIONED BY Hasura, August 2025
Total Economic Impact
A FORRESTER TOTAL ECONOMIC IMPACT STUDY COMMISSIONED BY Hasura, August 2025
Historical API development techniques supporting data access within modern application development are frequently being replaced by declarative, composable APIs, especially for solutions requiring multiple large, complex data sources. This marks a shift to a more modern approach to building data access APIs.
Hasura provides a platform to rapidly build, deploy, and maintain data access APIs for applications and AI. Hasura’s solution provides a metadata-based approach to API development, an authorization engine for granular access control, and a high-performance distributed API runtime engine.
Hasura commissioned Forrester Consulting to conduct a Total Economic Impact™ (TEI) study and examine the potential return on investment (ROI) enterprises may realize by deploying Hasura.1 The purpose of this study is to provide readers with a framework to evaluate the potential financial impact of Hasura on their organizations.
To better understand the benefits, costs, and risks associated with this investment, Forrester interviewed four decision-makers with experience using Hasura. For the purposes of this study, Forrester aggregated the experiences of the interviewees and combined the results into a single composite organization, which represents an application development team within a large organization that focuses on mission-critical, modern application development.
Interviewees said that prior to using Hasura, their organizations were not meeting data access business requirements. Development of data access APIs would take weeks to months and would frequently have performance issues due to the complexity and size of the data sources accessed. Developers typically manually programmed APIs and had to manually write connections and queries to multiple data platforms, leading to suboptimal queries with aggregation, performance, and concurrency issues.
Hasura provided the interviewees’ organizations with a modern, declarative API integration solution. After a short training period, developers were able to visually explore domain data, configure APIs (vs. manual programming), and apply security controls, all while producing a higher-quality API in a shorter period of time.
Quantified benefits. Three-year, risk-adjusted present value (PV) quantified benefits for the composite organization include:
End-User labor productivity and revenue improvements of $880,000 due to Hasura application. The composite has seen both revenue improvements and labor productivities of solutions’ end users. Breadth of data expansion, scale improvements, response time improvements, and the ability to develop modern solutions over legacy data are primary enablers for these benefits.
API development and change management labor productivity improvement of 50%. The Composite’s API development time per project has been reduced by 40% to 80%. Updates and patches are easily implemented through the continuous integration and continuous delivery/continuous deployment (CI/CD) process.
Licensing cost reduction in existing API integration platform of $571,000. The composite is able to utilize the Hasura APIs and Hasura’s built-in data integration capabilities to replace the existing API integration platform within its organization.
Unquantified benefits. Benefits that provide value for the composite organization but are not quantified for this study include:
Simplified process. With Hasura, developers create and maintain API via metadata configuration rather than coding. Interviewees shared that onboarding developers to build Hasura APIs was easy and took less time than the previous approach. Building and maintaining APIs were also easier, utilizing a more declarative approach to navigate the organization’s data domain.
Security, compliance, and audits improvements. Interviewees shared that Hasura enabled robust data security policies, controlling data access better and integrating with each organization’s identity and access management (IAM) system. This declarative approach to access control improved compliance with internal, contractual, and regulatory requirements.
Enable technology modernization. Interviewees shared that Hasura APIs provided a bridge between legacy data sources and modernized application development. This means that legacy solutions could be transitioned to a modern platform without any disruptions to the business.
Scale and breadth of data sources. Interviewees shared that their organizations were able to develop solutions that drew data from numerous sources while still being able to meet SLAs for both performance and scale. Data sources came from a combination of on-premises and cloud-based databases.
Performance and reliability. Interviewees shared that the performance of the Hasura APIs exceeded previous APIs, sometimes by more than a factor of 10x. All interviewees described the Hasura APIs as reliable, where prior APIs had outages for similar queries with similar loads. Concurrency was tested with hundreds of thousands of users.
Costs. Three-year, risk-adjusted PV costs for the composite organization include:
Licensing, planning, and implementation. Licensing costs for Hasura are based on the number of data models covered by the composite’s solutions. The implementation of Hasura is simple. The composite organization utilizes planning and implementation support to ensure proper placement of Hasura instances on-premises and with appropriate geographical distribution to meet organizational and regulatory requirements, such as GDPR.
Training developers building and using Hasura APIs. Using Hasura was new to the composite organization, so developers are trained to build APIs using Hasura. Building and modifying APIs using Hasura is via configurations, vs. manual programming, so training for development is simpler for the composite than learning to code APIs.
The financial analysis that is based on the interviews found that a composite organization experiences benefits of $1.6 million over three years versus costs of $376,000, adding up to a net present value (NPV) of $1.2 million and an ROI of 328%.
Return on investment (ROI)
Benefits PV
Net present value (NPV)
Payback
| Role | Industry | Region | Primary Use Case |
|---|---|---|---|
| Senior architect | Technology | Global | Sales advisory |
| VP cloud, technology, product | Healthcare solutions | United States | End user, multiple |
| Principal architect | Education solutions | United States | K-12 real-time |
| Head of engineering | Business security | Global | Incident detection and communications |
Interviewees described having two major organizational challenges. More business-driven requirements needed to be satisfied, and the organizations’ existing API solutions had numerous shortcomings that were hindering projects.
Interviewees noted how their organizations struggled with common challenges, including:
Inability to meet current expectations. Interviewees shared numerous drawbacks to their previous API development process and API characteristics. API development required manual coding, taking weeks and hindering agile development. Interviewees described data access issues, including accessing data across multiple data platforms like on-premises legacy sources within a single API without response time issues. Some solutions required access to real-time data and were not able to obtain acceptable response times. Data security was also noted as an issue, with no data access controls available within existing APIs without custom programming.
Shortcomings of previous API integration platforms. Interviewees had existing API integration platforms, and they found that the APIs, both in development and in use, were obstacles toward meeting current business requirements. All of these solutions required programming to build APIs, leading to long development cycles and a greater likelihood of suboptimal queries that would lead to performance issues or outages due to memory leaks. Legacy solutions also struggled to meet performance requirements at scale, especially when API requests involved composing data from multiple sources. Interviewees also noted that internal security requirements were frequently not satisfied because these platforms provided limited data access controls, if any.
The interviewees searched for a solution that:
Utilized composable APIs. Interviewees recognized that single composable APIs were a better choice than a collection of hard-coded representational state transfer (REST) endpoints for their organizations’ requirements because composable APIs are ideal for large, complex, and interrelated data sources.
Supported configuration-based API. Interviewees recognized that programming APIs led to long development cycles and suboptimal results, such as slow-performing queries or programming errors leading to memory leaks and outages. Creating APIs via declarative configuration (e.g., metadata) vs. manual coding was a logical choice, requiring less training while providing a shorter development cycle and a more agile API that was easier to use and maintain.
Provided AI support. Interviewees recognized that data access for AI queries is hard, especially when dealing with the aggregation of large, complex data sources that their solutions frequently required.
Provided data access controls. Interviewees shared that their organizations’ cybersecurity team was not satisfied with the data security that was being provided, so their solution requirements included providing effective data access controls.
After performing proof-of-concept testing with Hasura, interviewees’ organizations chose Hasura and began deployment.
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 organization is a development team within a larger organization that focuses on mission critical, modern application development. The organization utilizes an API integration platform and manual programming techniques to develop APIs for data access. The development team has to work with large data sets that are both on-premises and in cloud data sources. The requirements for the applications include aggregating across these data sources and supporting hundreds to thousands of concurrent users, with real-time interaction, data draws, and user input.
Deployment characteristics. After searching for a means to meet data access needs to build a priority business solution, the composite organization finds Hasura and completes a POC. In Year 1 the organization deploys a first version of that business solution in a six-month period, aggregating data from both on-premises and cloud data sources. Over the next two years the composite organization continues with enhancements to the original solution while working on other projects, adding additional developers and additional data sources.
Organization with large on-premises and cloud data sources
Requirements for agile, modern application development
Two to three end-user solutions, internal and customers/suppliers/partners
| Ref. | Benefit | Year 1 | Year 2 | Year 3 | Total | Present Value |
|---|---|---|---|---|---|---|
| Atr | End-User labor productivity and revenue improvements due to Hasura application | $258,825 | $390,150 | $428,400 | $1,077,375 | $879,597 |
| Btr | API development and change management labor productivity | $23,113 | $57,783 | $115,566 | $196,462 | $155,593 |
| Ctr | Licensing cost reduction in existing API platform | $200,000 | $230,000 | $264,500 | $694,500 | $570,624 |
| Total benefits (risk-adjusted) | $481,938 | $677,933 | $808,466 | $1,968,337 | $1,605,814 |
Evidence and data. All four interviewees shared success stories about the results of the solutions that were enabled by their organizations’ Hasura APIs, both in revenue improvements and in the solution users’ labor productivity. The reasons for the successes varied based upon the use case, but the common theme was that Hasura APIs played a significant role. Solution examples and the Hasura API enablers include:
For the business security organization. The primary Hasura solution collects data from around the world to identify incidents and risks to customers’ employees, efficiently sending mass communications to appropriate people, employees, and customers while collecting responses, collecting updated information about the incidents, and continuing communications. Hasura APIs retrieve data reliably and three times faster than previously, with more data sources and expanded concurrency. These improvements have enabled market expansion, leading to additional revenues.
For the healthcare solutions organization. Hasura helped the organization deliver modernized applications while still upgrading from an infrastructure that is heavily dependent upon legacy on-premises applications. Hasura APIs have provided developers with access to data, independent of its source, with a simple-to-use set of endpoints. The organization’s three use cases are an automated check-in kiosk, customer scheduling via information clerks, and healthcare professionals viewing healthcare information and documents related to specific patients and from numerous sources in a single dashboard. The value of the kiosk solution goes well beyond the labor automation, being a showcase for existing customers of the organization, as well as new prospects, and it has helped improve customer retention, expand existing business, and land new business. The VP of cloud, technology, and product estimated labor productivity from the customer scheduling solution at more than $10 million annually. The patient information portal has improved both the productivity of senior healthcare professionals and employee satisfaction. All three solutions have satisfied a business requirement to not disrupt existing business operations as on-premises solutions are transitioned to modern cloud systems.
For the education solution organization. The first use case was an interactive application for teachers and their students. Hasura’s APIs were an enabler for building real-time applications with responsive UIs. The interviewee also credited Hasura’s “fine-grained access control” as an enabler, as well as its integration with the organization’s IAM. Response times for stress tests of 7,500 concurrent users met expectations, well above current demand estimates. Hasura’s addition has allowed for customer and capability expansion, both leading to additional revenue.
For the technology organization. The primary use case is an overhaul of a sales enablement application that serves the global sales community. The solution has expanded data sources and capabilities while significantly improving user concurrency and response times. Expansion has been enabled by a reduction in API development from more than 80 hours to less than a day. Even with a data source increase, capability expansion, and concurrency increases, the response times have gone from approximately 1 second to an average of 33 milliseconds. The senior architect said, “Our application hit the Hasura APIs 6 billion times with an average of a 33-millisecond response time.” Sales have improved due to the sales enablement application’s insights for salespeople and the time savings it provides salespeople, enabling more time for sales activities.
Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization’s transition from a specific use requiring the use of multiple legacy applications to Hasura-enabled cloud solution with a single front end:
The composite’s use case application is used by 50 employees in Year 1 and 100 employees in subsequent years.
The employees average 8 hours per week for the use case before the Hasura API was used, with a 25% time savings utilizing the Hasura-enabled cloud solution.
Employees capture and use 75% of the time they save for other productive tasks.
Revenue growth due to modernization, concurrency improvements, improved response times, and aggregation of more data sources is $7.5 million in Year 1, $9.0 million in Year 2, and $10.8 million in Year 3.
The percentage of revenue impacted by Hasura’s API capabilities is 25%.
Risks. This benefit may vary across organizations for the following reasons:
Use case complexity and breadth.
End-user count.
End-user compensation.
Revenue opportunities.
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 $880,000.
| Ref. | Metric | Source | Year 1 | Year 2 | Year 3 | |
|---|---|---|---|---|---|---|
| A1 | Employees using Hasura | Composite | 50 | 100 | 100 | |
| A2 | Previous hours per week per employee | Interviews | 8 | 8 | 8 | |
| A3 | Time savings per employee | Interviews | 25% | 25% | 25% | |
| A4 | Fully burdened hourly rate for employees | Composite | $30 | $30 | $30 | |
| A5 | Productivity captured from time saved | TEI methodology | 75% | 75% | 75% | |
| A6 | Revenue growth due to modernization, concurrency improvements, and expanded aggregation | Composite | $7,500,000 | $9,000,000 | $10,800,000 | |
| A7 | Percentage of revenue impacted by Hasura capabilities | Interviews | 25% | 25% | 25% | |
| A8 | Net margin | Research data | 10% | 10% | 10% | |
| At | End-user labor productivity and revenue improvements due to Hasura application | A1*52*A2*A3*A4*A5+A6*A7*A8 | $304,500 | $459,000 | $504,000 | |
| Risk adjustment | ↓15% | |||||
| Atr | End-user labor productivity and revenue improvements due to Hasura application (risk-adjusted) | $258,825 | $390,150 | $428,400 | ||
| Three-year total: $1,077,375 | Three-year present value: $879,597 | |||||
Evidence and data. Interviewees shared that API development time was reduced by 40% to 80%. The VP cloud, technology, product at a healthcare solutions organization said that the process was faster and more cost-effective, sometimes reducing an API’s development cost by more than $50,000. Interviewees also shared that Hasura APIs require minimal maintenance, with low operational costs for maintaining services running on it. They said that updates and patches are easily implemented through the CI/CD process.
Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:
The composite organization creates 10 APIs in Year 1 and expands data sources, use cases, and developers each of the following years, with 25 APIs for Year 2, and 50 APIs for Year 3.
Before Hasura, the average development time was 80 hours per API, which is reduced by 50% when creating Hasura APIs.
Before Hasura, the average API testing time was 4 hours per API, which is reduced by 25% when testing Hasura APIs.
The composite organization requires two API changes due to schema updates in Year 1, five API changes in Year 2, and 10 API changes in Year 3.
Before Hasura, the average time to apply schema changes was 24 hours per API, which is reduced by 90% when changing Hasura APIs.
Developers capture and use 75% of the time they save for other productive tasks (e.g., improving performance or security).
Risks. This benefit may vary across organizations for the following reasons:
Requirement complexity, environmental complexities, and number of APIs.
Testing requirements.
Schema change complexity.
Developer compensation.
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 $156,000.
API development time savings with Hasura
INTERVIEW SPOTLIGHT
Principal architect, education solutions
Head of engineering, business security
Senior architect, technology
| Ref. | Metric | Source | Year 1 | Year 2 | Year 3 | |
|---|---|---|---|---|---|---|
| B1 | Total APIs | Composite | 10 | 25 | 50 | |
| B2 | Previous average development time per API (hours) | Interviews | 80 | 80 | 80 | |
| B3 | Development time savings with Hasura | Interviews | 50% | 50% | 50% | |
| B4 | Previous average testing time per API (hours) | Interviews | 4 | 4 | 4 | |
| B5 | Testing time savings with Hasura | Interviews | 25% | 25% | 25% | |
| B6 | Annual API changes due to schema changes | Interviews | 2 | 5 | 10 | |
| B7 | Previous average time per API change (hours) | Interviews | 24 | 24 | 24 | |
| B8 | API update time savings with Hasura | Interviews | 90% | 90% | 90% | |
| B9 | Fully burdened hourly rate for developers and testers | Composite | $80 | $80 | $80 | |
| B10 | Productivity captured from time saved | TEI methodology | 75% | 75% | 75% | |
| Bt | API development and change management labor productivity | (B1*B2*B3+B1*B4* B5+B6*B7* B8)*B9*B10 | $27,192 | $67,980 | $135,960 | |
| Risk adjustment | ↓15% | |||||
| Btr | API development and change management labor productivity (risk-adjusted) | $23,113 | $57,783 | $115,566 | ||
| Three-year total: $196,462 | Three-year present value: $155,593 | |||||
Evidence and data. Interviewees shared that, depending upon the use case of the solutions utilizing the Hasura APIs, the Hasura licensing cost could sometimes be more than 80% less expensive than using the previous API integration platform.
Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:
The licensing cost reduction for Hasura is $250,000 in Year 1, $287,500 in Year 2, and $330,625 in Year 3.
Risks. This benefit may vary across organizations for the following reasons:
Use case differences.
Results. To account for these risks, Forrester adjusted this benefit downward by 20%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $571,000.
| Ref. | Metric | Source | Year 1 | Year 2 | Year 3 | |
|---|---|---|---|---|---|---|
| C1 | Licensing cost reduction in existing API platform | Interviews | $250,000 | $287,500 | $330,625 | |
| Ct | Licensing cost reduction in existing API platform | C1 | $250,000 | $287,500 | $330,625 | |
| Risk adjustment | ↓20% | |||||
| Ctr | Licensing cost reduction in existing API platform (risk-adjusted) | $200,000 | $230,000 | $264,500 | ||
| Three-year total: $694,500 | Three-year present value: $570,624 | |||||
Interviewees mentioned the following additional benefits that their organizations experienced but were not able to quantify:
Simplified process. Developers configure Hasura APIs rather than write programs to build them. Interviewees shared that onboarding developers to build Hasura APIs was easy and took less time than the previous approach. Building and maintaining APIs was also easier, utilizing a more visual approach to navigate within databases.
Improved security, compliance, and audits. Interviewees shared that Hasura APIs provided security advantages over its predecessor. They said that Hasura enabled robust data security policies, controlling data access better and integrating with their organizations’ IAM systems. This has improved compliance with contractual and regulatory requirements. Hasura supports the GDPR compliance requirement of data processing in geography-specific instances. Client compliance includes the ability to host Hasura on-premises, if required.
Enabled technology modernization. Interviewees shared that Hasura APIs have provided a bridge between legacy data sources and providing modernized solution development. This means that solution development can be done with modern methods on cloud platforms, and the legacy solutions can be transitioned to a modern platform without any disruptions to the business by modifying the Hasura API as needed.
Increased scale and breadth of data sources. Interviewees shared that their organizations were able to develop solutions that drew data from numerous sources while still being able to meet SLAs for both performance and scale. Data sources have come from a combination of on-premises and cloud-based databases. Concurrency has been in the hundreds of thousands of users.
Provided both performance and reliability. Interviewees shared that the performance of Hasura’s APIs exceeds previous APIs, sometimes by more than a factor of 10x. All interviewees consider the Hasura APIs to be reliable, where prior APIs had outages for similar queries.
The value of flexibility is unique to each customer. There are multiple scenarios in which a customer might implement Hasura and later realize additional uses and business opportunities, including:
Quickly optimize APIs via data exploration. Interviewees shared that their teams were able to quickly explore new projects by visually navigating data. This ease of data navigation allows developers to test different data combinations, producing a more versatile API without increasing development time.
Reuse and adapt APIs. API development and maintenance supports the reuse and flexibility that Hasura APIs provide in three significant ways. First, interviewees shared that developers can separate the endpoints from the data sources. Second, the original APIs can be developed to support possible future requirements via the visual data exploration and configuration capabilities. Lastly, developers can more easily adapt to new requirements because Hasura doesn’t require programming, so developers only have to change the API’s configuration.
Flexibility would also be quantified when evaluated as part of a specific project (described in more detail in Total Economic Impact Approach).
| Ref. | Cost | Initial | Year 1 | Year 2 | Year 3 | Total | Present Value |
|---|---|---|---|---|---|---|---|
| Dtr | Licensing, planning, and implementation | $34,500 | $115,000 | $132,250 | $152,087 | $433,837 | $362,609 |
| Etr | Training developers building and using Hasura APIs | $6,912 | $0 | $3,840 | $3,840 | $14,592 | $12,971 |
| Total costs (risk-adjusted) | $41,412 | $115,000 | $136,090 | $155,927 | $448,429 | $375,580 |
Evidence and data. The interviewees shared that licensing costs for Hasura were based on the number of data sources covered by the solution. The implementation of Hasura was simple. Interviewees used Hasura' planning and implementation support to ensure proper placement of Hasura instances on-premises and with appropriate geographical distribution to meet organizational and regulatory requirements, such as GDPR.
Pricing may vary. Contact Hasura for additional details.
Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:
The composite organization’s licensing cost is $100,000 in Year 1, $115,000 in Year 2, and $132,250. The annual increases are due to the addition of new data sources.
The composite organization pays $10,000 to utilize Hasura services for planning and implementation support, while its cost for planning and implementation is $20,000.
Risks. These costs may vary across organizations for the following reasons:
Number of data sources.
Internal security policies and government regulations.
Timing requirements.
Skills for implementation.
Results. To account for these risks, Forrester adjusted this cost upward by 15%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $363,000.
| Ref. | Metric | Source | Initial | Year 1 | Year 2 | Year 3 |
|---|---|---|---|---|---|---|
| D1 | Hasura licensing | Composite | $100,000 | $115,000 | $132,250 | |
| D2 | Hasura planning and implementation support | Interviews | $10,000 | |||
| D3 | Customer planning and implementation costs | Interviews | $20,000 | |||
| Dt | Licensing, planning, and implementation | D1+D2+D3 | $30,000 | $100,000 | $115,000 | $132,250 |
| Risk adjustment | ↑15% | |||||
| Dtr | Licensing, planning, and implementation (risk-adjusted) | $34,500 | $115,000 | $132,250 | $152,087 | |
| Three-year total: $433,837 | Three-year present value: $362,609 | |||||
Evidence and data. Interviewees shared that building Hasura APIs is via configurations rather than historical programming, so training for development is simpler than learning to program APIs. Using Hasura API endpoints was not complex, but interviewees noted that it did require some training because it was new to the developers.
Modeling and assumptions. Based on the interviews, Forrester assumes the following about the composite organization:
Building and using Hasura APIs is new to the interviewees’ organizations, so developers are trained to build Hasura APIs and utilize the Hasura API endpoints.
The composite organization originally trains four developers to build Hasura APIs and trains two additional developers in the two remaining years.
The training to build Hasura APIs averages 16 hours per developer.
The composite organization originally trains two developers to use Hasura APIs and trains two additional developers in the two remaining years.
The training to use Hasura APIs averages 4 hours per developer.
Risks. These costs may vary across organizations for the following reasons:
Developer skill levels.
Complexity of an organization’s environment.
Complexity of requirements.
Developer compensation levels.
Results. To account for these risks, Forrester adjusted this cost upward by 20%, yielding a three-year, risk-adjusted total PV (discounted at 10%) of $13,000.
| Ref. | Metric | Source | Initial | Year 1 | Year 2 | Year 3 |
|---|---|---|---|---|---|---|
| E1 | Developers using Hasura to build APIs | Composite | 4 | 4 | 6 | 8 |
| E2 | Average time for developer to learn to build Hasura APIs (hours) | Interviews | 16 | 16 | 16 | 16 |
| E3 | Developers utilizing Hasura APIs, without training to build them | Composite | 2 | 2 | 4 | 6 |
| E4 | Average time for developers new to Hasura to learn to use Hasura APIs (hours) | Interviews | 4 | 4 | 4 | 4 |
| E5 | Fully burdened hourly rate for developers | Composite | $80 | $80 | $80 | $80 |
| Et | Training developers building and using Hasura APIs | ((E1-E1[-1])*E2+(E3-E3[-1])*E4)*E5 | $5,760 | $0 | $3,200 | $3,200 |
| Risk adjustment | ↑20% | |||||
| Etr | Training developers building and using Hasura APIs (risk-adjusted) | $6,912 | $0 | $3,840 | $3,840 | |
| Three-year total: $14,592 | Three-year present value: $12,971 | |||||
| Initial | Year 1 | Year 2 | Year 3 | Total | Present Value | |
|---|---|---|---|---|---|---|
| Total costs | ($41,412) | ($115,000) | ($136,090) | ($155,927) | ($448,429) | ($375,580) |
| Total benefits | $0 | $481,938 | $677,933 | $808,466 | $1,968,337 | $1,605,814 |
| Net benefits | ($41,412) | $366,938 | $541,843 | $652,539 | $1,519,908 | $1,230,234 |
| ROI | 328% | |||||
| Payback | <6 months |
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 Hasura.
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 Hasura can have on an organization.
Interviewed Hasura stakeholders and Forrester analysts to gather data relative to Hasura.
Interviewed four decision-makers at organizations using Hasura to obtain data about costs, benefits, and risks.
Designed a composite organization based on characteristics of the interviewees’ organizations.
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.
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.
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 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 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 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.”
The present or current value of (discounted) cost and benefit estimates given at an interest rate (the discount rate). The PV of costs and benefits feed into the total NPV of cash flows.
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.
A project’s expected return in percentage terms. ROI is calculated by dividing net benefits (benefits less costs) by costs.
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%.
The breakeven point for an investment. This is the point in time at which net benefits (benefits minus costs) equal initial investment or cost.
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.
1 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.
Readers should be aware of the following:
This study is commissioned by Hasura 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 Hasura. 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 Hasura based on the inputs provided and any assumptions made. Forrester does not endorse Hasura or its offerings. Although great care has been taken to ensure the accuracy and completeness of this model, Hasura 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 Hasura make no warranties of any kind.
Hasura 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.
Hasura provided the customer names for the interviews but did not participate in the interviews.
Eric Hall
August 2025
ABOUT FORRESTER CONSULTING
Forrester provides independent and objective research-based consulting to help leaders deliver key transformation outcomes. Fueled by our customer-obsessed research, Forrester’s seasoned consultants partner with leaders to execute on their priorities using a unique engagement model that tailors to diverse needs and ensures lasting impact. For more information, visit forrester.com/consulting.
© Forrester Research, Inc. All rights reserved. Unauthorized reproduction is strictly prohibited. Information is based on best available resources. Opinions reflect judgment at the time and are subject to change. Forrester®, Technographics®, Forrester Wave, and Total Economic Impact are trademarks of Forrester Research, Inc. All other trademarks are the property of their respective companies.
https://mainstayadvisor.com/go/mainstay/gdpr/policy.html
PDF