Why Your Software Asset Management Tool Falls Short for Holistic SaaS Management
Table of Contents ToggleWhat Is SaaS Purchasing Hygiene?Clear Governance Is Essential...
Back
Back
Search for Keywords...
Blog
Table of Contents
On-premises software typically goes through a formal IT procurement process, but SaaS is a whole different beast.
One of the many upsides of SaaS is that it’s easy to obtain. So if a business unit (or even an individual employee) recognizes a need for a SaaS solution, they’ll simply purchase it themselves — without the involvement of IT.
So it’s probably not surprising that IT’s share of SaaS spending and management in an organization continues to shrink. Today, IT controls 28% of SaaS spend and 17% of application quantity.
In the meantime, business units’ share of spending continues to grow. Today, line of business (LOB) owners control 69% of SaaS spend.
This shift in spending presents some big challenges for organizations looking to reduce the costs and risk of unmanaged SaaS growth. Improving your SaaS purchasing hygiene has never been more important.
Read on to learn what purchasing hygiene is, what it means for your organization, and what it takes to improve yours.
Of course, personal hygiene practices ensure cleanliness — which helps us prevent avoidable health problems. Similarly, purchasing hygiene is a set of practices that ensure a “clean” method of software intake — which reduces the unnecessary costs and risk associated with uncontrolled SaaS growth.
Purchasing hygiene includes a number of different components, and each is built on a foundation of discovery.
Before organizations can tackle any other purchasing hygiene practices, they must first discover all SaaS applications in use. This includes everything from enterprise software obtained through a formal procurement process to rogue applications purchased via employees’ credit cards. Why is this the first step? Because it’s virtually impossible to manage and “keep clean” what you don’t even know exists.
Once you’ve gained full visibility into all SaaS at your organization, you’re well-positioned to take on other purchasing hygiene best practices, including cutting down on Shadow IT (in other words, any software not purchase through IT), rationalizing your SaaS portfolio, and consistently evaluating what SaaS tools your organization needs — and making those tools available to those who need them.
IT controls a rapidly decreasing amount of SaaS spending and application quantity. However, they still have an important role to play in purchasing hygiene — as well as avoiding unnecessary costs and risk.
IT leaders must be responsible for the overall SaaS governance strategy, which helps protect the organization from unnecessary spend and risk. But business units must be given the flexibility to acquire the SaaS tools they need — within the established governance framework.
IT must collaborate with business units to develop ground rules for acquiring SaaS. This includes a process for bringing new applications into the organization — and ensuring there are systems in place to onboard and manage those apps. Additionally, IT must be in continuous communication with business unit owners to ensure everyone is on the same page — and all teams understand and follow the proper SaaS purchasing processes and procedures.
Evolving Your SaaS Governance Framework for the Digital Workplace
Learn MoreSaaS applications purchased by business units and individual employees typically aren’t vetted for security and compliance. And if something goes wrong, the consequences can be costly. According to IBM, the average total cost of a data breach in the U.S. is $4.45M.
What’s more, when SaaS is purchased throughout the organization, duplicate subscriptions and redundant apps are the norm. On average, 90 SaaS applications are purchased by more than one employee in an organization. And it’s common for there to be multiple applications in use at an organization that fulfill similar functions. For example, there might be a dozen or more training applications used by different teams throughout the organization.
All of those unnecessary costs add up.
And the problem is only getting bigger. Every 30 days, the average organization will see six new SaaS applications enter its environment. That means SaaS portfolios are growing unmanaged — and quickly.
The good news is, good purchasing hygiene can help organizations take control of shadow IT and unmanaged SaaS — and the unnecessary costs and risks associated with these issues.
Discovery and rationalization are essential. You’ve got to understand what SaaS applications you currently have and why you have them. The right governance is also key. IT must define ownership and process for bringing new applications into the organization — and work collaboratively throughout the organization to ensure these processes are understood and widely adopted.
Ready to improve your purchasing hygiene? Learn how here.
Table of Contents ToggleWhat Is SaaS Purchasing Hygiene?Clear Governance Is Essential...
Table of Contents ToggleWhat Is SaaS Purchasing Hygiene?Clear Governance Is Essential...
Table of Contents ToggleWhat Is SaaS Purchasing Hygiene?Clear Governance Is Essential...
Table of Contents ToggleHow to Build a Custom Dashboard from ScratchStep...
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |