> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octavehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What are Use Cases in Octave?

> Use Cases describe the problems your product solves. Agents match prospects to the right messaging based on their specific scenario.

## What is a Use Case?

A Use Case is a structured description of a customer problem, scenario, or job-to-be-done that your product addresses. Unlike a feature list (which describes what your product does), use cases describe why a customer needs it — the problem they're trying to solve, the outcome they want, and the business drivers behind the purchase. When an agent qualifies a prospect, it identifies which use cases are relevant based on the prospect's industry, role, and signals, then tailors the entire conversation around those specific scenarios rather than leading with generic product capabilities.

## What a Use Case contains

| Field             | Purpose                                  |
| ----------------- | ---------------------------------------- |
| Name              | Short descriptive label                  |
| Description       | Overview of the scenario                 |
| Problem statement | What the customer is struggling with     |
| Solution approach | How your product addresses this          |
| Desired outcomes  | What success looks like for the customer |
| Business drivers  | Why this matters strategically           |

## How Use Cases connect to other entities

Use Cases are referenced by multiple entity types:

* **[Offerings](/concepts/offerings)** — which products or services solve this use case
* **[Motions](/concepts/motions)** — Motion ICPs recommend the use cases most relevant for each persona×segment cell, and Motion Playbooks can override the default selection via anchor overrides
* **[Segments](/concepts/segments)** — which market segments commonly have this use case

When an agent qualifies a prospect, it identifies which use cases are relevant based on the prospect's industry, role, and signals. The matched use cases then inform which [Motion ICP](/concepts/motions#motion-icps) applies and what messaging to generate.

## Managing Use Cases via API

* `GET /api/v2/use-case/list` — list all use cases
* `GET /api/v2/use-case/{id}` — get a specific use case
* `POST /api/v2/use-case/create` — create a new use case
* `POST /api/v2/use-case/generate` — AI-generate use cases from your product and market context
* `PUT /api/v2/use-case/update` — update an existing use case
* `DELETE /api/v2/use-case/delete` — remove a use case