Recently, we got a few customers. When we first met them, their initial question was whether our data was accurate. When we tried to understand the context behind the question, we found they were already using an SMP.
Since the data was not accurate in their existing SMP, they faced many issues, like a lost opportunity for cost optimization and security challenges due to shadow IT. After the POC, they happily moved ahead with us.
After that discussion, we continuously explored this angle for a few months. In this blog post, we will explain why Zluri is the most accurate SMP.
Nowadays, most decisions are taken based on data, so it's imperative to have a reliable data source. Otherwise, you won’t be able to make precise decisions.
Before we discuss why Zluri is the most accurate SMP, let's see what key data-related challenges are faced by customers of most of the SMPs available in the market.
Zluri is the most accurate SaaS management platform. Let's see how.
Any SMP is as good as its discovery engine. This is because only depending on the discovery of the SaaS in an organization will the SMP be able to manage, optimize and secure the applications.
Zluri has a robust discovery engine that is capable of discovering any problem and providing solutions. With over 225,000 apps, it has the largest app library in the world. This, combined with various discovery methods, helps Zluri to provide 100% SaaS discoverability.
Zluri uses five powerful discovery methods to trace the SaaS apps present in an organization's SaaS landscape. It offers a granular view, and IT admins can stay up to date on apps that are being used or left idle to take relevant actions.
It uses its multiple discovery methods to uncover all the apps used in your organization: SSO or IDP, finance systems, direct integrations, browser extensions, and desktop agents.
You can read about the working of Zluri's discovery engine in this article. Here we have given a summary of all the discovery methods.
1.1 SSO and IDP: Zluri connects with single sign-on and identity provider systems such as Okta and Google Workspace and collects different types of data.
From the SSOs, Zluri also collects lists of authorized apps and login events like sign-in attempts, the number of times the user has accessed the app, and if it was a successful or failed attempt.
This discovery method also provides data shared with third-party apps. Example name, email, and other details.
1.2 Finance and expense management systems: We connect with your expense and finance management systems, such as Xero and Netsuite, to collect the following data:
1.3 API integration & SaaS library
We connect directly with 750+SaaS apps. This is our primary differentiation from SSOs and other SMPs.
1.4 Desktop Agents: (optional): Using desktop agents, you can track the basic insights of device information, apps installed, and time spent on each app. You can analyze if an employee purchased any app or installed any app without the knowledge of the IT department.
Zluri collects only non-sensitive information from the system through desktop agents. This data includes apps installed on a device, apps running in the background, and app sign-in and sign-out details.
SaaS operations manager (or IT or software asset manager, whoever is in charge of managing the business applications) can see how many employees have installed it directly from the Zluri dashboard.
The desktop agent is available for macOS, Windows, and Linux operating systems.
1.5 Browser extension: Data about websites users visit in a browser. You can find the extensions for Chrome, Firefox & Microsoft Edge. We collect data on the websites visited by users: the URL, title, and timestamp of opening/closing the tab.
Note: Browser Extensions are optional too. Kindly note that we do not read the cookies saved in the browser, browser history, or any content from the websites visited.
Further, you can check how many users have installed it.
One of the reasons why many SaaS management platforms struggle with data accuracy is because of not updating their data frequently. Zluri, on the other hand, updates the data most frequently.
Most SMPs take several days to sync data, while Zluri updates information like license usage, number of applications, and all other critical data in real time. This helps you to make more informed and precise decisions.
The reason why our customers trust the data in Zluri is that all the data can be traced back to the original source of truth. Because of this transparency, you can always verify any data.
Be it discovery or SaaS usage data; you get to know where the data is coming from.
SaaS Discovery - Source Data
Zluri has the largest direct integration number, over 750 applications, and keeps growing every month. Since we are directly connected to the source of truth, our SaaS usage data is accurate, updated, and covers all the commonly used apps.
With direct integration, you get more granular-level insights. Further, we provide custom integrations options if the app that you want is not present in the integrations library.
This is not limited to just SaaS data. All the data points can be traced.
Source - Users' Data
Further, Zluri gives your flexibility to choose the primary data source. For example, in the setting options, you can select the primary source for users' data.
Another example is for finding hidden charges.
In the cost column, the amount is sourced from the contract, while the actual amount you paid is in the spending column (sourced from financial management systems). The bigger the difference is, the higher you are charged than what is mentioned in the contract.
Zluri is the highest-rated SaaS management platform on G2. It has also been recognized as the best tool in SaaS operations management, and SaaS spend management categories.
Due to the high data accuracy, our customers love us and have rated us the highest SaaS management platform on reviews sites like G2 and Capterra.
Furthermore, we have received many awards for our good performance.
In the context of SaaS management, with accurate data, you will be able to reduce your SaaS wastage, eliminate shadow IT, and control SaaS Sprawl.
An SMP is supposed to be a system of record for your SaaS governance efforts. When the SMP is itself not correct, then you will face the following issues:
SaaS spend management is the core use case of an SMP. When SaaS spending is not managed properly, it leads to the wastage of a lot of IT budget.
If an SMP doesn't provide accurate information about an organization's SaaS applications, it gives rise to unnecessary SaaS spending.
Let’s see this with three examples:
2.1 This can create shadow IT in your organization: If you don’t have an accurate and updated inventory of all the SaaS apps being used in your organization, then it can pose a lot of security issues.
You can read about the risks of shadow IT here.
This problem is present mainly due to employees purchasing apps.
Since the IT team does not vet these SaaS apps for data security, these apps make your organization vulnerable to hackers. Even a single vulnerability in any of these apps provides these hackers an entry point to your entire organizational data.
2.2. Ex-employees may access data: If the de-provisioning is not done properly, then the ex-employees may access the apps even after they leave the company. This can be a serious security risk for the organization as ex-employee may misuse the data.
Suppose one employee was using 50 apps in your organization. But, you have discovered 40 apps and revoked the access. Failing to detect and revoke the remaining ten apps will create a risk of a data breach in the organization by which the employee or hacker can damage your system.
Imagine one of your employees joining competitors, and they can access your customer relationship management tool.
Read why Zluri is the best solution for deprovisioning in the market.
When license management is not done properly, it leads to SaaS waste either unused licenses or unsuitable license tiers.
Licenses remain unoptimized mainly due to two reasons: all licenses being not used or unsuitable license tiers. Let's see them one by one.
Sometimes, though the tiers were suitable for immediate needs, you realize you don’t need most of the features with time. So, you can degrade the license, and if you need more features, you can upgrade your license.
If you don’t have accurate data on your application usage, then you might fail to negotiate a better agreement during renewals.
Suppose you bought 500 licenses of Grammarly, but only 350 are currently being used. Ideally, you should renew only 350 licenses, but in the absence of usage data, you would most probably renew the entire 500. In the worst case, you may buy additional licenses for new employees without knowing the existing ones are not being used properly.
Though SaaS vendors have this data, they don't share it with costumes. Hence, the negotiation is always in favor of vendors. An SMP with accurate data balance this information asymmetry and makes it fair play for both parties.
Tackle all the problems caused by decentralized, ad hoc SaaS adoption and usage on just one platform.