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

> Offerings represent what you sell — Products, Services, and Solutions. Every persona, use case, and motion connects back to one.

## What is an Offering?

An Offering is a top-level entity in the [Octave Library](/concepts/library) representing something your company sells. Offerings are the anchor for the rest of your GTM knowledge. [Personas](/concepts/personas) buy them, [use cases](/concepts/use-cases) describe the problems they solve, [Motions](/concepts/motions) orchestrate how to sell them, and [competitors](/concepts/competitors) are evaluated against them. Every other entity in the Library ultimately connects back to an Offering, making it the foundation that agents use to understand what you sell and why it matters. Most companies have between one and a handful of Offerings — each carrying its own features, deliverables, differentiators, qualifying questions, and pricing — giving agents the specificity they need to position the right offering for the right prospect, rather than pitching your entire portfolio in every conversation.

## The three offering types

Octave models three kinds of offerings, each with its own data shape:

| Type         | What it represents                                                                                           | Read more                        |
| ------------ | ------------------------------------------------------------------------------------------------------------ | -------------------------------- |
| **Product**  | Software, hardware, or anything you ship as a built capability                                               | This page                        |
| **Service**  | Consulting, implementation, advisory, managed, or professional services                                      | [Services](/concepts/services)   |
| **Solution** | A packaged answer to a specific business problem — typically a bundle of products, services, and methodology | [Solutions](/concepts/solutions) |

All three offering types plug into [Motions](/concepts/motions), [Personas](/concepts/personas), [Use Cases](/concepts/use-cases), [Competitors](/concepts/competitors), and the rest of the Library in the same way. Choose the type that best matches what you sell — a workspace can mix all three.

## What a Product offering contains

| Field                   | Purpose                                 |
| ----------------------- | --------------------------------------- |
| Name                    | Product name                            |
| Description             | What the offering does and who it's for |
| Features & capabilities | What it can do                          |
| Differentiators         | What makes it unique vs alternatives    |
| Pricing information     | Tier structure and pricing model        |
| Primary URL             | Product page link                       |
| Qualifying questions    | Questions to assess prospect fit        |

For Services and Solutions, see [Services](/concepts/services) and [Solutions](/concepts/solutions) for their full field sets.

## How Offerings connect to other entities

Offerings sit at the top of the entity hierarchy. Everything flows from them:

* **[Personas](/concepts/personas)** — which buyer and user personas care about this offering
* **[Use Cases](/concepts/use-cases)** — which problems this offering addresses
* **[Motions](/concepts/motions)** — GTM strategies built around this offering
* **[References](/concepts/references)** — customer success stories for this offering
* **[Competitors](/concepts/competitors)** — vendors competing with this offering
* **[Alternatives](/concepts/alternatives)** — non-product substitutes prospects use instead
* **[Proof Points](/concepts/proof-points)** — stats and validations supporting this offering
* **[Buying Triggers](/concepts/buying-triggers)** — signals indicating a prospect is ready to buy
* **[Objections](/concepts/objections)** — recurring pushback against this offering

## Managing Products via API

Product offerings use the `/api/v2/product/*` endpoints:

* `GET /api/v2/product/list` — list all products
* `GET /api/v2/product/get` — get a specific product
* `POST /api/v2/product/create` — create a new product
* `POST /api/v2/product/generate` — AI-generate a product definition from your website or description
* `POST /api/v2/product/update` — update an existing product
* `DELETE /api/v2/product/delete` — remove a product

[Services](/concepts/services) and [Solutions](/concepts/solutions) have their own parallel `/api/v2/service/*` and `/api/v2/solution/*` endpoints.