> ## 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 Solutions in Octave?

> Solutions are an offering type for packaged answers to a specific problem — combinations of products, services, and methodology sold as one motion.

## What is a Solution?

A Solution is an [offering](/concepts/offerings) type that represents a packaged answer to a specific business problem — typically a curated bundle of capabilities, services, and methodology sold under a single banner. Solutions sit alongside [Products](/concepts/offerings) and [Services](/concepts/services) as one of the three offering types in the [Octave Library](/concepts/library). Where a Product is what you build and a Service is how you deliver, a Solution is the *answer* you bring to a category of buyer — packaging the right combination for a defined outcome.

Treat a Solution as its own first-class offering in the Library. It plugs into [Motions](/concepts/motions), [personas](/concepts/personas), [use cases](/concepts/use-cases), and qualifying questions exactly like a Product or Service does.

## What a Solution contains

| Field                 | Purpose                                                       |
| --------------------- | ------------------------------------------------------------- |
| Name                  | External-facing solution name                                 |
| Internal name         | Internal alias                                                |
| Description           | What problem the solution solves and for whom                 |
| Primary URL           | Solution page link                                            |
| Summary               | One-paragraph overview                                        |
| Distinct capabilities | What this solution can do that competitors' bundles can't     |
| Key components        | The products, services, and methods that make up the solution |
| Customer benefits     | The outcomes the buyer gets                                   |
| Challenges addressed  | The problems the solution solves                              |
| Status quo            | What the buyer is doing today without the solution            |
| Differentiated value  | Why this packaging wins versus assembling the parts elsewhere |
| Qualifying questions  | Questions to assess solution fit                              |

## How Solutions connect to other entities

Solutions plug into the same Library graph as Products and Services:

* **[Personas](/concepts/personas)** — who the solution is built for
* **[Use Cases](/concepts/use-cases)** — problems the solution addresses
* **[Motions](/concepts/motions)** — GTM strategies built around the solution
* **[References](/concepts/references)** — customer success stories
* **[Competitors](/concepts/competitors)** — competing bundles or platforms
* **[Alternatives](/concepts/alternatives)** — the DIY assembly, status quo, or "do nothing"
* **[Proof Points](/concepts/proof-points)** — outcome metrics
* **[Buying Triggers](/concepts/buying-triggers)** — signals indicating the buyer is ready for a packaged solution

## Managing Solutions via API

* `GET /api/v2/solution/list` — list solutions
* `GET /api/v2/solution/get` — get a solution
* `POST /api/v2/solution/create` — create a solution
* `POST /api/v2/solution/generate` — AI-generate a solution definition
* `POST /api/v2/solution/update` — update a solution
* `DELETE /api/v2/solution/delete` — delete a solution