Configure Products
CONTENT FOUNDATION
Product configuration creates an approved, structured product vocabulary. The generation engine should not be expected to infer product capabilities or invent supporting claims — it should be given them.
Product configuration. The products listed are examples of a configured workspace, not a fixed or exhaustive product list.
Fields and their effect on generated content
Name
The product name exactly as it should appear in published content. Generation uses it verbatim, so inconsistent naming here becomes inconsistent naming in public.
Summary
A concise, canonical description of the offering.
Summary is the sentence the generator falls back on whenever a draft must introduce the product. A vague summary produces vague posts across every channel at once.
Problems Solved
The customer or operational problems the product addresses.
These supply the opening framing for problem-led drafts and determine which audience pains the generator is allowed to connect the product to.
Key Capabilities
Functions the product is approved to claim.
This is a whitelist. If a capability is not listed, the generator has no basis to describe it, and a reviewer should reject any draft that asserts it.
Proof Points
Evidence that may support marketing statements.
Proof points are what turn a capability into a credible statement. They are used to substantiate claims, not to be quoted verbatim as guarantees.
Active status
Determines whether the product is available for selection and generation. Deactivating a product removes it from new campaigns and stories without deleting the history of content already produced for it.
Field distinctions that matter
- Summary says what the product is. Problems Solved says why anyone would care.
- Key Capabilities bound what may be claimed. Proof Points bound how strongly it may be claimed.
- A capability without a proof point can still be described; it should not be described as a guaranteed outcome.
Do not use Product configuration as a feature backlog. Listing a planned capability as approved allows generated content to promise something the product does not yet do.
Working practice
- Keep one product record per commercially named offering.
- Review capabilities after every release; stale capability lists are the most common source of inaccurate drafts.
- Treat the example products visible in a configured workspace as examples only — each tenant maintains its own list.
Next: Configure Audiences.
Was this helpful?
Last updated 1 month ago