Skip to main content

Quick Tips: Do you own more or less of SaaS Application you pay for?

Have you ever realized, how much do you really pay for a SaaS Application? The general answer would be to look into your invoice and find the number. But, have you realized that the quantity of Technical Services you own or paying for may not be optimally utilized in your organization. There are SaaS where your invoice is specifically calculated based on your usage, but not all SaaS is based on that pricing model. I would even say that only selected few calculate invoice at granular level of details. e.g. AWS. I have got bills ranging from low as $0.57 cents to $50+ based on usage. But, most of the B2B SaaS applications are contractually bound for few number of years with a bucketed types of services. Generally, in many situation, no one goes back and checks whether those services are being utilized or not. Also, it will rarely happen that you own less and your usage is more.

If you see the contractual document, you might find following, but not limited to, criteria based on which you get your invoice.
  1. Amount of storage
  2. Number of requests/response
  3. Number of API called
  4. Number of current user or number of user account
  5. Number of other types of Technical Service provided
  6. Timeline or duration of the current service
  7. ingress/egress
  8. Compute Resources used


All of the above characteristics also falls under the domain of non-functional requirement. It is always good idea to keep track above characteristics for all production environment. Traditionally many of these are tracked through monitoring services, but only for fallout scenarios. In other words, monitoring services never trigger any alarm or sends out a usage pattern.

You could save little more money on doing proper analysis of your Cloud environment. It would not be as easy compared to On-Premise Software, but nothing like, you can't do that. The above criteria can provide a starting point to collect the data and re-negotiate the deal. This also gives an opportunity to study your Application Portfolio.

In general for On-Premise Software license is based on number of users (limited or unlimited). Counting the usage pattern is difficult but not as difficult in SaaS Application, where number of users is just one factor of licensing.

Of course there are other types of complex licensing especially in Mainframe or other complex technology area, which is beyond scope of this discussion.

Comments

Popular posts from this blog

Product Evaluation - MuleSoft Anypoint Platform one day workshop

People, Business Executives, Enterprise Architects, Solution/System/Application Architects, Tech Leads, Developers,  who are looking for and want to know more about MuleSoft Integration offering which is compared to other key providers like Software AG WebMethods, Oracle SOA Suite, WSO2, Informatica, etc. Recently I attended a one day Workshop on MuleSoft Anypoint platform . The overall goal of this workshop was to evaluate MuleSoft integration technology offering for a mid-size integration environment which is currently supported through Software AG WebMethods and Oracle SOA Suite. So, if you are in process of evaluating MuleSoft Anypoint Platform for your integration needs, this write up will give you a good high level executive summary overview. MuleSoft Product Offering falls under following category of market offering: iPaaS (Integration Platform as a Service) Hybrid Integration On-Premise Integration Platform Internet of Things (#IOT) Integration ...

Salesforce - Scheduling a Schedule Job

Following are the different ways to schedule a Schedule Job through a script. Run the given code in Execute Anonymous window and then you could see in Setting -> 'Scheduled Job' that your Job is waiting to be executed. Run a Schedule Job NOW Method - 1 ScheduleSalesTargets c = new ScheduleSalesTargets(); c.execute(null); Method - 2  (This one I prefer, whenever I need to run a job) Check the current Time. If it is, let's say 10:39 AM, in your clock, then set the minute to 41. This will schedule the job for 10:41 AM just two minutes from now. But, if you set minute value to 38, then it will schedule to next hour 11:38 AM ScheduleSales c = new ScheduleSales(); String sch = '0 0 * * * ?'; System.schedule('Sales Job Name - 1',  '0 41 * * * ?', c); You could repeat following, so that job keeps running every 5 minutes while you debug and change the Apex code behind the scene. ScheduleSales c = new ScheduleSales(); String sch = ...

Salesforce Code and Configuration Deployment

Following are a varied list of ways through which Code or Configuration could be deployed in Salesforce Server. It is assumed that deployment focus would be on Production instance, but it is true with Developer Edition and Sandbox instances as well. Technical Prerequisites for a Salesforce Deployment There are some tools and software that must be installed and properly configured on the Release Manager’s machine in order to enable the Deployment Process described in this guide. Some other tools are not required but we recommend using them. Here is a quick description of these tools. Tool Required / Optional Purpose Comment Eclipse Optional Eclipse is a developer tool that supports several languages. The currently recommended version of Eclipse to download is Eclipse Kepler 4.3 (the “Eclipse for Java developers” version is recommended) and can be downloaded from http://www.eclipse.org/downloads/pac...