Software as a service or SaaS refers to the method of delivering applications over the internet as a service. Instead of installing and maintaining software, you simply access it using the internet, so you don’t have to undertake complex software and hardware management! SaaS is on the rise, and so are the challenges! In this article, we have covered 3 case study examples from 3 of the fastest-growing SaaS companies. Read on!
Table of Contents
Top 3 SaaS Case Study Examples to Check out
Here we have three business case study samples that will tell you what these B2B SaaS companies are doing well, and not so well, so you can improve your own strategies accordingly.
Case Study Sample#1 – GitLab
GitLab is a dev-ops platform that helps development security and operations teams bring down costs and increase time to market. The company’s 738 employees are located in 50 different countries. GitLab ranked 10th on the SaaS Mag’s list of 1000 high-growth companies. Here’s a review of GitLab’s Goldman Sachs case study.
What worked well?
Success in a SaaS case study is measured by statistics, and a business case study sample like this one provides numbers that clearly illustrate the results Goldman Sachs achieved, working with GitLab. We have 1000+ CI feature branch builds a day by some teams, 52K test cases across 11k test classes, and 1500+ adopters in the first two weeks. The case study format flows well. Each section, including customer introduction, solution, challenges, and results, provides clear information that can help the reader visualize how GitLab could help their company too. Using a large block of text on a webpage is going to get you no readers. GitLab avoids this by using subheaders to break up the text so it is easier to scan. These subheaders are descriptive and benefit-driven, another bonus.
The Challenge
Increasing build speed by demolishing toolchain complexity. The company had built its own toolchain and was looking for a way to increase concurrent development. They required a modern toolset for managing code that developers coming into the firm would likely already be familiar with – this led to an evaluation of GitLab and other git-based vendor products.
What could be Improved?
The title of the case study could use some work. Adding GitLab’s company name would boost brand recognition. The title does feature a statistic, however, it would be more powerful and easier to digest if this was a percentage increase, for example, “Goldman Sachs increases build velocity by 2000% using GitLab”. Condensing and tweaking them might make them more impactful. This case study would have a stronger finish if it included a conclusion that addressed how the customer plans on using GitLab moving forward, for example, whether they would add new products to their suite. This case study also requires a call to action which prompts readers to book a call with GitLab or view a product demo online.
Case Study Sample #2 – Sendoso
Sendoso is a sending platform providing businesses with sourcing, inventory tracking, physical warehouse storage, and ROI attribution solutions to enable personalization at scale. The company has 147 employees and is ranked 22nd on the SaaS Mag’s list. Here’s a review of Sendoso’s Pendo case study.
What worked well?
This SaaS case study makes great use of graphics. It’s not just a filler; rather it adds visual interest to the piece, communicating the benefits of Sendoso. This case study also provides a clear summary of the challenges that Pendo faced before working with Sendoso.
The Challenge
Direct mail became a part of Pendo’s sales and customer experience strategy, thanks to a rapidly growing customer base. Sorting and packing direct mail items, writing personal notes, researching email addresses, and dealing with one-off requests were consuming an inordinate amount of time (20 hrs a week) from an already over-extended marketing team. Pendo is data-driven and ran an initial experiment with Sendoso’s basic plan.
Finally, this case study includes a strong CTA at the end which hints at social proof with the phrase “Join the thousands of people using Sendoso”. This CTA highlights a benefit by encouraging readers to personally connect with their customers. Moving the CTA higher up in the case study could make it even stronger so it does not appear to be part of the site’s footer.
What could be Improved?
The case study title appears incomplete – “5X higher close rate. With Sendoso, Pendo reported an approximately 5X higher close rate for prospective deals while saving 20 hours for every direct mail campaign”
This needs to be more than a statistic and must include the customer’s name, company name, and some context like “Pendo closes 5x more sales with Sendoso”. The pull quote is buried in the website footer and appears too long.
Condensing this quote to one sentence and moving it up under the stats section may make it more compelling. This SaaS case study also requires a section that focuses on the solution itself. It must outline which of Sendoso’s products Pendo uses, and how these products addressed each of the challenges customers were facing.
Case Study Sample #3 – Front
Front is an email management software that helps more than 5000 customers improve workflow and collaborate efficiently. The company has 144 employees and is ranked 61st on the SaaS Mag list. Here’s a review of Front’s Boostability case study.
What worked well?
This case study opens with a strong title which includes a statistic and the customer’s name.
Front can improve this by adding its own company name. The boostability case study also features a great pull quote, which is short and sweet with effective messaging. The case study also uses quotes to help tell a human, relatable story :
The executive summary on the side of this case study is eye-catching and provides important information like the tools which integrate with Front (important functionality of Front software).
What could be Improved?
This SaaS case study could be more compelling if it outlined clear statistics near the top in numerical format – for example, “2.5x faster response rate”. The call to action is currently in the executive summary at the top of the case study. This call to action would be better positioned at the bottom of the case study so that when a reader finishes the story and visualizes themselves in the customer’s shoes, they’re prompted to take action. This case study may also use a short boilerplate paragraph on the customer. Case studies have to benefit both parties involved, and including a boilerplate with a link shows your customer your gratitude for their help with the case study.
Conclusion
In conclusion, the 3 case studies above will help you in curating your own case study regarding SaaS. With the world becoming more and more digital, the growth curve of SaaS will only increase.
