What is zero-based budgeting?
Zero-based budgeting is an accounting technique that requires all expenses to be justified and approved for each financial period, starting from zero rather than a pre-existing spend. This enables organizations to monitor and assess the necessity of each cost on a more granular level, lowering expenses and promoting fiscal responsibility.
Originally conceived in the 1970s, zero-based budgeting isn’t a new idea — but in the current economic climate, accounting for every dollar is helping businesses to regain control over their outgoings. The technique can be applied to a wide range of costs, from research and development to asset management.
Related Definitions
Spot Instances
What are spot instances?
As with any cloud service provider, AWS will have spare capacity available to support surges in customer demand. To offset the loss, AWS offers this excess EC2 capacity – in other words, spot instances – at a heavily discounted rate.
To benefit from these spot instances, users must bid on this unused EC2 capacity in their desired region. The capacity is then allocated to the highest bidder. While it can be a great way to reduce costs by as much as 90%, it is only suitable for workloads that can tolerate interruptions and don’t require continuous availability. This is because AWS will terminate the instance after a two-minute notification in the event that it needs to reclaim the resources, or because the spot price exceeds the bid price. In other words, when other customers are willing to pay more.
Auto-Renewal
What is an auto-renewal clause?
Auto-renewal is a term often used in SaaS agreements referring to the automatic renewal of a user’s subscription plan at the end of their contract term. These auto-renewal clauses will automatically extend the user’s subscription for another period, typically the same duration as the initial term, unless the customer explicitly cancels or modifies their subscription by a specified date. This is often referred to as a termination window and is typically either 30, 60 or 90 days prior to the renewal date.
SaaS Management
What is SaaS management?
SaaS management is the process of identifying, managing, and governing the software applications that exist within an organization’s technology portfolio.
When software goes unmanaged, it not only puts the business at risk of data breaches and security issues, but it can also lead to a substantial amount of wasted spend as a result of redundant and duplicate SaaS apps, not to mention unused licenses.
Cloud Instances
What is an instance in the context of cloud computing?
In cloud computing, an instance refers to a virtual server provided by a third-party cloud service, for example AWS, Azure or Google Cloud. These instances ultimately enable companies to deploy and run their applications or services in the cloud, in a scalable and flexible manner. This is because instances are on-demand and can be adjusted based on your workload requirements.
Master Service Agreement (MSA)
What is a Master Service Agreement?
A Master Service Agreement (MSA) is a contract between two parties, in this case the software provider and the buyer, outlining the terms and conditions of the agreement. It will typically cover pricing, payment terms, service levels, intellectual property rights, confidentiality, liability, termination, and dispute resolution.
Unlike a service level agreement (SLA) which outlines the specific performance metrics and criteria for the delivery of a particular service, for example uptime guarantees and support response times, an MSA covers the broader terms of the business relationship.
Maverick Buying
What is maverick buying?
Maverick spending, also known as rogue spending, can be defined as any purchasing that takes place within an organization, outside of an established procurement process.
In the context of SaaS, maverick spending refers to the acquisition of cloud-based software solutions that are purchased unbeknownst to the finance, IT or procurement teams, and in a way that does not comply with the organization’s formal IT procurement process — and so may not be approved, vetted, or appropriately documented.