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

# Product Intelligence

> Shape one offer or map how your offers work together

Product Intelligence helps you turn what you sell into a clear offer system. Open **Think > Intelligence > Product** to work in an Offer Doc or Product Map.

<Note>
  Offer Docs, Product Maps, field editing, locks, statuses, Offer Score, and
  Agent create (`create_offer_doc` / `create_product_map`) are available. Live
  website-draft smoke remains credit-gated in eval/staging.
</Note>

<CardGroup cols={2}>
  <Card title="Offer Doc" icon="file-lines">
    Build one offer into a working document that covers the offer, buyer, and
    business.
  </Card>

  <Card title="Product Map" icon="diagram-project">
    Arrange your offers by role, from the first purchase through the main and
    follow-on offers.
  </Card>
</CardGroup>

## Build an Offer Doc

Choose **New Offer Doc**, select the offer type, and link an existing Olympus Offer if one already exists. You can also start with an unlinked document.

The document has three sections:

| Section      | What it covers                                                |
| ------------ | ------------------------------------------------------------- |
| The Offer    | Name, one-line description, contents, delivery, and pricing   |
| The Buyer    | Audience, problem, past attempts, desired outcome, and timing |
| The Business | Your approach, proof, results, and advantage                  |

You can edit a field in the document and change the document status from its header. Confirmed facts
and field locks stay with that Offer Doc when you return to it. If two sources disagree, the field
shows the conflict so you can choose the right value.

Offer Docs can be **Draft**, **Active**, **Inactive**, **Seasonal**, or **Deprecated**.

## Check the Offer Score

Offer Score rates six parts of the current document—urgency, transformation, market demand,
uniqueness, monetization, and scalability—out of 10 for a total out of 60. A saved score belongs to
one document version, so editing the Offer Doc makes it ready to score again.

The score uses only the facts in the Offer Doc. It does not verify market size, competitor activity,
or outside demand. Use **Improve** to bring the weakest category into the current chat, or choose
**Open diagnose map** to start a Product Map focused on the gaps.

## Build a Product Map

Choose **New Product Map** and describe the goal in one line. Use cards to map the offer path across front end, order bump, upsell, downsell, backend, and standalone roles. Each card can link to an Offer Doc.

A Product Map can be **Draft**, **Testing**, **Archived**, or **Deprecated** while you work on it. A
locked map is the approved version of the offer system and cannot be edited or moved back to a
working status.

## Work in record threads

Each Offer Doc and Product Map keeps its own threads. Start a new thread when you want a clean line
of discussion, or reopen an earlier one from above the composer. Changing threads reloads the
current record first, so every thread opens beside the latest saved document.

From `/agent`, start an Offer Doc or Product Map when the org has none yet. Each workspace still
keeps its own threads. You can edit Offer Doc fields, lock settled facts, change statuses, score an
offer, and create or open linked documents from the side panel.

## Linked Olympus Offers

An Offer Doc becomes the source of truth after you link it to an Olympus Offer. Confirmed mapped fields sync to the Offer record. Fields that exist only in Product Intelligence remain visible from the Offer page and are edited in the Offer Doc.

Social briefs use the selected Offer Doc when one exists. If an Offer has no document yet, they use the mapped Offer fields and report that no canonical Offer Doc exists. The shared read contract always requires an Offer or Offer Doc selection; Olympus does not choose the first offer in a list.

## Draft from your website

When you create an Offer Doc, you can point Olympus at a website. It reads the site, fills in each of the thirteen fields it can support, and opens the Offer Doc with the conversation ready. While it reads, the workspace shows which site it is reading; fields appear as they are found.

Every field drafted this way is marked as read from the site, with the page it came from and a supporting quote where there is one. A field with a quote shows as **strong inference**; a field without one shows as **hypothesis**. Neither counts as confirmed. The strategist treats them as a starting point, asks you to confirm or correct them, and never presents them back as something you said. Confirm a field in the conversation or edit it directly to settle it.

If the site lists several distinct products, Olympus also drafts a Product Map with one card per product and the stage each plays. A site with one product gets no map.

If the site cannot be read, the workspace says why and the Offer Doc stays usable in the conversation.

## Start a new Offer Doc

Open **Think > Intelligence > Product** and choose **New Offer Doc**. Brainstorm was removed in the Think consolidation; strategy chat lives in the agent.