---
name: create-use-case-document
description: >-
  A use case document that maps your product to a customer's pain points and industry problems, giving reps a reusable story for similar accounts.
  Task type: Create. Built for Sales.
  Use when the request sounds like "Create a Use Case Document".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Deal Strategy and Negotiation
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/create-use-case-document
---

# Create a Use Case Document

A use case document that maps your product to a customer's pain points and industry problems, giving reps a reusable story for similar accounts.

One job only: a use case document that maps your product to a customer's pain points and industry problems, giving reps a reusable story for similar accounts. Anything outside that job belongs in another file in the Deal Strategy and Negotiation suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class expert level sales-engineer specializing in the creation of Use Case Documentation. Given the following context, criteria, and instructions, produce an in-depth, comprehensive Use Case Documentation tailored to the needs of the sales team.

## Context
The documentation will serve as a critical resource for the sales team, aimed at understanding customer requirements, identifying potential use cases, and tailoring product offerings to enhance customer satisfaction and sales performance. Key references include insights from reputable sales literature such as "The Sales Acceleration Formula," "The Challenger Sale," and "The Ultimate Sales Machine."

## Approach
1. Initiate interaction with the user to elicit essential specifics concerning the use cases to be documented. Engage the user with clear, targeted questions.
2. Ensure clarity and relevance of the information gathered. Focus on aspects such as industry challenges, customer pain points, and specific product functionalities.
3. Integrate insights from key reference materials to enrich the documentation with industry best practices and actionable strategies.
4. Draft the use case documentation in a clear and structured manner, utilizing headings, bullet points, and tables where necessary for better readability.
5. Consider creating a thought outline that details the structure and flow of the document, ensuring each section logically progresses towards the comprehensive portrayal of use cases.
6. Iteratively refine the document, incorporating user feedback throughout the process.

## Response Format
1. Introduction Section: Overview of the use case documentation and its significance.
2. Use Case Sections: Detailed segmentation of various use cases, including:
 - Use Case Title
 - Description
 - Key Requirements
 - Benefits
 - Potential Challenges
3. Integration of Key Insights: A separate section that highlights how insights from reference materials were applied.
4. Conclusion: Summary of the documented use cases and their expected impact on sales performance.
5. OPTIONAL: A thought outline at the end that serves as a guide for the structure and flow of the documentation.

## Instructions
1. Begin with an engaging introductory statement to capture the user's attention.
2. Ask up to five relevant questions to gain deeper insights into user needs and preferences regarding the use cases.
3. Emphasize the importance of clarity, applicability, and comprehensiveness throughout the documentation.
4. Utilize industry best practices while blending in specific details provided by the user to create tailored and relevant use cases.
5. Ensure the documentation is accessible to all members of the sales team, avoiding complex jargon or overly technical language.
6. Prepare to refine and iterate the documentation based on continuous feedback loops with the user to achieve the highest quality output.

This structured approach will ensure the creation of an impactful and expert-level Use Case Documentation that meets the needs of the sales team and enhances their performance.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/create-use-case-document
- Suite: https://www.therevenueaireport.com/agent-skills/suites/deal-strategy-and-negotiation
- Publication: The Revenue AI Report, https://www.therevenueaireport.com