This article will go into detail on what you need to automate in order for your SaaS company to have a functional subscription billing solution.
One of the problems SaaS companies face when selling subscriptions is connecting their application to a billing process.
Some of the things that are need to be considered are:
The challenge in managing these billing processes is handling these events, such as restricting access to an application when a trial expires or if there no longer has a valid funding source attached to an account.
The process a customer goes through when doing business with a SaaS company can be broken down into the five events above. Managing these events is the key to integrating a billing system with a SaaS.
This is the first stage in the journey a user takes with a subscription. In this step, the customer has just signed up for a subscription which needs to trigger an automated process.
The process generally looks something like this:
From a DevOps perspective, these are considered “Day 1” operations. These are the steps that a service goes through after being requested in order to be considered “provisioned,” such as installation and configurations of software.
In the trialing stage, a customer has subscribed to a service, but is not paying until their trial expires.
Approximately 75% of SaaS companies offer free trials. Although free trials are almost guaranteed to bring you more paying customers, one of the trickier things about offering them is deciding what happens when a trial expires without a customer adding a funding source.
At this stage of the service lifecycle, a company will need to build logic around trials which will, upon expiration, restrict access to an application and alert the customer that they need to pay.
Many SaaS businesses support multiple tiers of service. If a customer pays a premium, they have access to additional features. This is considered a “Day 2” operation, actions which can be taken after a service has been provisioned which affect the end user.
Generally, it follows the pattern below:
While this usually takes the form of strict pricing tiers, sometimes customers pay “per user per month” or have “thresholds” which if passed will trigger higher rates.
Inevitably, there will be cancellations of subscriptions, also called churning. The steps which occur in order to fulfill a cancellation go as follows:
Reaching out to your former customers after they have cancelled will also require some sort of process. It’s recommended that cancellation triggers a process which sends an automated email to the former customer, perhaps with an attempt to recover the customer or a feedback survey to see what reasons they may have had for canceling.
When a former customer decides to return after canceling, a company can’t just go through the original process to subscribe them as a new customer — they need to reactivate the previously terminated access so that they retain all their former data. This process can be described in three steps:
Some complex scenarios might include limited time discount codes for resubscribers, a free trial, or part of another service as part of a combo deal.
The key to selling software-as-a-service is connecting software to a billing system that can support the lifecycle I just described. Being able to automate this process is a boon to businesses, since manual processes are one of the biggest barriers to scaling.
Trying to manage the challenges of SaaS billing? Let’s Talk.
We solve challenges SaaS companies face when billing customers by providing easy to integrate hooks which can trigger automated processes.