Skip to main content
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.

​
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.
The Landing Page Pillars screen with a uses pillar row and its category chips, opened from the sidebar.

Landing Pages then Landing Page Pillars: open the pillar to reach its prompt.

  1. 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”.
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.

The feature inventory sits in the pillar's Prompt, one entry per feature, each with an id.

​
Fold it into the onboarding document

Paste the list into Pi and have it add the inventory to the onboarding document:
Then get the document out of Pi to review before the call. Press Cmd/Ctrl-K, search for the onboarding document, and open it.
The Pi command palette open, searching for the onboarding document by name.

Cmd/Ctrl-K, then search for the onboarding document.

Copy the content and paste it into Notion, so you can read through and edit it before the onboarding call.
The onboarding document open in Pi's Files panel with a Copy content button at the bottom.

Open the document and use Copy content to move it into Notion.

​
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 ids 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. 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 · 2.3.1 Design a landing-page pillar