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

# Pull the feature inventory for client sign-off

> How to pull the feature inventory from a landing-page pillar, fold it into the onboarding document, and get the client to sign it off.

The feature inventory is the list of product features the landing pages draw from, and it lives inside a landing-page pillar's **Prompt**. During onboarding you pull it, get Pi to fold it into the onboarding document, and send it to the client to verify before any pages go live. Run this once the pillar is set up, as part of the [Month-1 onboarding flow](/sops/onboarding-month-1).

## Pull it from the pillar

1. In the sidebar, open **Landing Pages**, then **Landing Page Pillars**.
2. Open the pillar (usually the `/uses` horizontal one) with the edit action.

<Frame caption="Landing Pages then Landing Page Pillars: open the pillar to reach its prompt.">
  <img src="https://mintcdn.com/synscribe/XATz-Y4B2stINVU3/images/sops/landing-page-pillars-list.png?fit=max&auto=format&n=XATz-Y4B2stINVU3&q=85&s=df5f72b40046ef437a16df722fe7395f" alt="The Landing Page Pillars screen with a uses pillar row and its category chips, opened from the sidebar." width="1606" height="1712" data-path="images/sops/landing-page-pillars-list.png" />
</Frame>

3. Scroll the **Prompt** field down to the `## Feature Inventory` heading and copy the whole list. Each entry has an `id`, a "what it is", and a "when to use it".

<Frame caption="The feature inventory sits in the pillar's Prompt, one entry per feature, each with an id.">
  <img src="https://mintcdn.com/synscribe/XATz-Y4B2stINVU3/images/sops/feature-inventory-in-pillar-prompt.png?fit=max&auto=format&n=XATz-Y4B2stINVU3&q=85&s=8225a38ab39ac27911dd6bea0eff7164" alt="The Edit Landing Page Pillar panel with the Prompt field scrolled to a Feature Inventory list showing an id, a what-it-is, and a when-to-use for each feature." width="2183" height="1589" data-path="images/sops/feature-inventory-in-pillar-prompt.png" />
</Frame>

## Fold it into the onboarding document

Paste the list into Pi and have it add the inventory to the onboarding document:

```text theme={null}
we are missing the feature inventory for them to check [paste the copied feature inventory here]
```

Then get the document out of Pi to review before the call. Press Cmd/Ctrl-K, search for the onboarding document, and open it.

<Frame caption="Cmd/Ctrl-K, then search for the onboarding document.">
  <img src="https://mintcdn.com/synscribe/XATz-Y4B2stINVU3/images/sops/pi-cmdk-search-onboarding-doc.png?fit=max&auto=format&n=XATz-Y4B2stINVU3&q=85&s=3e94ee86b66a05afe7e8d6879e71b26c" alt="The Pi command palette open, searching for the onboarding document by name." width="2944" height="1462" data-path="images/sops/pi-cmdk-search-onboarding-doc.png" />
</Frame>

Copy the content and paste it into Notion, so you can read through and edit it before the onboarding call.

<Frame caption="Open the document and use Copy content to move it into Notion.">
  <img src="https://mintcdn.com/synscribe/XATz-Y4B2stINVU3/images/sops/pi-open-onboarding-doc-copy.png?fit=max&auto=format&n=XATz-Y4B2stINVU3&q=85&s=28c891d17b5e846f3f3f859b366e3fe2" alt="The onboarding document open in Pi's Files panel with a Copy content button at the bottom." width="946" height="1712" data-path="images/sops/pi-open-onboarding-doc-copy.png" />
</Frame>

## Get sign-off

* Send the document to the `internal-<client>` Slack channel for Raymond to review, and revise on his feedback.
* After the onboarding call, share the document with the client with full edit access, so they can correct the feature inventory themselves.
* Keep the `id`s intact through the edits. Pages reference features by `id`, so a rename drops that feature from pages already using it.

The inventory is seeded from the [Product Bible](/platform/company-research-product-bible). When a feature is wrong at the source, fix the product bible and have Pi refresh the pillar's feature inventory, rather than patching the prompt by hand.

**Next:** [3.1 Month-1 onboarding](/sops/onboarding-month-1) · [2.3.1 Design a landing-page pillar](/platform/design-landing-page-pillar)