But rarely do I see a case study that is so good it sets the bar for the industry. It involves Spotify switching from its own data centers to Google to host its streaming music service. Published in the form of a blog post from Spotify, it goes far beyond the usual “apple pie and motherhood” generalities to describe specifically why Spotify chose Google over other cloud providers.
Maybe this level of detail results from what sort of a discount Spotify got. More likely it has to do with an engineering-centric culture at Spotify that led them to share the technical details behind their infrastructure growth in gleeful detail.
But instead of wondering how this case study came about, let’s talk about what makes it so good and how you can try for the same level of detail with your customers.
Why They Choose Google – Specifically
In its blog post announcing the shift, Spotify said:
What really tipped the scales towards Google for us…has been our experience with Google’s data platform and tools. Good infrastructure isn’t just about keeping things up and running, it’s about making all of our teams more efficient and more effective, and Google’s data stack does that for us in spades… (f)rom traditional batch processing with Dataproc, to rock-solid event delivery with Pub/Sub to the nearly magical abilities of BigQuery, building on Google’s data infrastructure provides us with a significant advantage where it matters the most.
Note that Spotify went beyond euphemisms such as “enhancing efficiency” or “end to end solution” to talk specifically about how Google helps them cut costs and improve the streaming experience for their users. It also mentioned specific Google tools. While the post could have been more specific about how those tools helped, it’s already head and shoulders above most case studies.
Questions to ask your customers to get similar results include:
- What specific products or services from other vendors did you consider besides ours?
- For each of our offerings you chose , describe the specific benefits (such as lower cost, higher performance, greater ease of use) that drove your choice, with at least one example of how we were better in each area.
- What strategic aims or needs (such as optimizing use of your infrastructure or assuring a great customer experience) drove your purchase decision? Please provide an example of how each of our products or services helps you reach these high-level objectives.
Honesty – Painful Honesty
In its more detailed “deep dive” technical blog post, the Spotify team also discussed frankly what they don’t like among Google’s tools and services. It found, for example, that the Google Cloud Deployment Manager was too difficult to use, leading it to build its own Spotify Pool Manager to more easily spin up new servers as needed.
Admitting your own products aren’t the absolute ideal fix for every customer, regardless of their needs, takes courage. Standing by graciously while one of your customers does so ain’t easy either. But the smart, and ethical, product managers I talk all the time are the first to know, and admit, when one of their solutions isn’t a good fit for a specific customer. Just imagine the credibility you get by being as honest, and as technical, as Spotify is when talking about Google.
Sweat the Details
The common theme here is the importance of details in making a case study come alive. Push your customers to explain what they mean by jargon such as “transformation” or generalities such as “agility.” Digging into specifics helps tell your story, and may even give you added insight into your client’s needs for follow-on sales.
Filed under: Content Marketing For IT Vendors
Like this post? Subscribe to my RSS feed and get loads more!