[GTM glossary](/glossary.md) Use case GTM Strategy & SaaS Metrics # Use case Also known as: use cases In short A use case is a specific scenario in which a defined type of user applies your product to achieve a particular outcome. It names the who, the problem, and the result, such as "an SDR team building a target account list". In go-to-market, use cases turn a broad product into concrete reasons to buy. They shape messaging, case studies, demos, and which accounts you prioritize. ## What makes a good use case * **Specific user:** A named role or team, not "companies". * **Clear trigger:** The situation that makes the problem urgent, such as a new quota or a market expansion. * **Measurable outcome:** A result the buyer can check, such as more meetings or shorter research time. * **Real product fit:** The product must actually do it today, without custom work. --- ## Use case vs. related terms * **Use case:** A scenario of how the product is applied. * **Persona:** The person who has the problem. One persona can have several use cases. * **Value proposition:** The promise of benefit across the product. A use case is a concrete instance of it. --- ## How GTM teams use them ### Messaging and outreach Lead cold emails and ads with the use case, not the feature list. "Build a list of accounts that match your best customers" lands better than a product description. ### Demos and sales calls Run the demo as the buyer’s scenario from start to finish. Prospects remember workflows, not menus. ### Prioritizing accounts Match accounts to the use case where your product is strongest. Teams with that problem convert faster and stay longer. --- ## How to find and prioritize them Review closed-won deals and ask what job each customer hired the product for. Group the answers, count them, and rank by how often they close, how fast, and how well customers retain. Say five customers use the product for two similar purposes: that cluster is a candidate for a dedicated page and campaign. * **Mistake: too many:** A long list dilutes focus. Lead with two or three. * **Mistake: feature talk:** Describing capabilities without a scenario leaves buyers to do the mapping. * **Mistake: invented scenarios:** Base use cases on real customers, not assumptions. --- ## Use case FAQs **What is a use case in B2B sales and marketing?** A use case is a specific scenario in which a defined type of user applies a product to solve a particular problem and reach a clear outcome. Sales and marketing teams use it to explain value in concrete terms instead of listing features. **What is an example of a use case for a SaaS product?** For a data enrichment tool, a use case could be an SDR team filling in missing contact and company details on a target account list before outreach, so reps can personalize messages and reach the right people faster. **What is the difference between a use case and a buyer persona?** A buyer persona describes who the person is, including role, goals, and concerns. A use case describes what they are trying to do with your product. One persona often has several use cases, and one use case can serve several personas. **How many use cases should a company focus on in its messaging?** Most teams do best leading with two or three use cases that close most often and retain well. Too many dilutes the message and confuses buyers, while a few lets you build focused pages, campaigns, and case studies. Share term --- ## More related phrases * [Business-to-business-to-consumer](/glossary/business-to-business-to-consumer.md) * [Customer acquisition cost](/glossary/customer-acquisition-cost.md) * [Customer lifecycle](/glossary/customer-lifecycle.md) ## Similar phrases * [Buyer persona](/glossary/buyer-persona.md) A buyer persona is a research-based profile of the people who research, influence, and approve a purchase, including their goals, challenges, and objections. * [Persona-based marketing](/glossary/persona-based-marketing.md) Persona-based marketing tailors messages, content, and channels to the roles and needs of different buyers instead of sending one message to everyone. * [Product positioning](/glossary/product-positioning.md) Product positioning describes how a specific product is framed for a target buyer, covering its category, key benefit, and difference from alternatives. * [Positioning](/glossary/positioning.md) Positioning defines the place your company holds in a buyer’s mind: who it is for, what category it competes in, and why it is the better choice. * [Value proposition](/glossary/value-proposition.md) A value proposition is a clear statement of the specific benefit a product delivers to a defined customer and why it is better than the alternatives they have.