In the field of enterprise services, the essence of doing a good job in the product market lies in telling a good story - it may be a beautiful vision that a complete set of product solutions can finally realize, or it may be a specific work scenario for improving the function of a product. Among these stories, customer cases are extremely important evidence. It tells the world how important your product or service is and what a perfect solution it is. By showing how your products and services meet customer needs and help customers achieve their goals, combined with product value point publicity, press releases, etc., the marketing effect is better. Customer cases are very important for self-marketing and self-service for small customers and pitch deck for large customers .
Why Enterprise Services Need phone number list Customer Stories Before you start preparing a customer case, you must first clarify a question: Who is your target customer? Whether it is a vertical enterprise service product or a general-purpose product, the industry, scale, and stage of the customer must be clearly defined. This can answer exactly who your customer case is for. The goal of customer stories is - when your target customers see this content, they will have this feeling: Your product or service is a match for your target audience; You know the pain points of your target users; You know how to fix it. When the target user has read the customer story, they must be able to get this information and find the product useful. Classification, value, purpose, application scenarios, and basic ideas of customer cases.
Customer cases act on the entire life cycle of users, but as you know: users in different life cycles have different needs for content. For example, you can't show pre-sales users to the help center, and they will be confused. The customer case mainly works in three stages: the "Awareness" stage, the "Consideration"/"Selection" stage, and the "Getting started"/"Usage" stage. This customer case can also be divided into three types: 【Cognitive】: Customers may not have a clear understanding of their own problems in the product awareness stage, let alone an in-depth understanding of the product/solution. Therefore, the content requirements at this stage are mainly similar to stories, dry goods, etc. Therefore, the [cognitive] customer case is more likely to be a user story.