Multi-Product Setup
Use this guide if your business sells multiple distinct products or services — for example, multiple ERP lines, service tiers, separate SaaS products, or distinct practice areas. Multi-product mode tells WisePilot to treat each product as its own governed content system, with separate ICPs, tone contexts, operating profiles, and content libraries.
Skip this guide if you run a single-product business or manage single-product clients. Adding product lines to a single-product setup adds complexity without benefit.
What You’ll Need
- ICPs already created for your website
- Brand voice configured (at least a voice and tone description)
- A list of your product lines with names and brief descriptions
Step 1 — Enable Multi-Product Mode
Start here. This is a one-way toggle — once enabled, entity scoping and per-product filtering are active across the platform.
Enable multi-product mode for [website name].
- Entity scoping (content, CTAs, offers, and ads can be tagged to a product line)
- Per-product operating profiles and funnel baselines
- Product-filtered context assembly (content generation pulls only the relevant product’s ICP, tone, and library)
- Product badges in the UI across content and automation views
Enabling multi-product mode on a site with existing content does not automatically tag that content to a product. Run the Content Classification flow after setup to assign existing content to product lines. Step 2 — Create Product Lines
Once multi-product mode is on, create each product line. Give Claude a clear description — this description is used during content classification and context assembly.
Create product lines for [website name]:
1. [Product name] — [What it is, who it's for, key differentiator]
2. [Product name] — [What it is, who it's for, key differentiator]
3. [Product name] — [What it is, who it's for, key differentiator]
create_product_line for each entry. Each product line gets:
| Field | Description |
|---|
name | Display name used across the UI and in content badges |
vendor | Optional — useful for reseller or partner products |
description | Used for classification matching and context assembly |
tone_context | Optional at this stage — set in Step 4 |
Keep product names concise and distinct. They appear as filter labels in the content library and automation views. Avoid names that overlap significantly (e.g., “Enterprise” and “Enterprise Plus”) — these will cause classification ambiguity.
Step 3 — Map Verticals to ICPs
Verticals are sub-markets within a product line. Use them when the same product is sold to meaningfully different buyer types — for example, a compliance platform sold to both Healthcare and Manufacturing buyers.
Add verticals to [product name]: [vertical names]
and map them to the right ICPs.
Add verticals to our Compliance Platform product: Healthcare, Manufacturing, Financial Services.
Map Healthcare to our "Healthcare Compliance Officer" ICP,
Manufacturing to our "Plant Manager" ICP,
and Financial Services to our "CFO / Risk Officer" ICP.
update_product_line to write the verticals configuration (stored as a JSONB field). Each vertical stores a name and one or more targetIcpIds.
When to use verticals vs. separate product lines:
| Scenario | Recommendation |
|---|
| Same product, different buyer language | Verticals |
| Different product features per segment | Separate product lines |
| Same buyer, different tiers | Neither — use offers |
| Completely different go-to-market | Separate product lines |
Verticals are optional. If a product line has a single consistent ICP across all buyers, skip this step and assign the ICP directly at the product line level.
Step 4 — Set Product Tone
Each product line can have its own tone context that blends with (but does not replace) the website’s overall brand voice. Use this when products have noticeably different registers — for example, a technical platform that needs precise language vs. a consumer product that needs warmth.
Set the tone context for [product name] — it should sound [description of desired tone].
For example: more technical and precise than our main brand voice, with a focus on compliance
and risk language rather than growth and opportunity language.
update_product_tone to save the tone context. During content generation, this context is injected alongside the global brand guidelines — it steers emphasis and register without overwriting your core voice rules.
If you’re unsure what tone context to set, skip this step initially and generate a few pieces of content. Review them and note what feels off — that feedback translates directly into tone context language.
What Multi-Product Mode Changes
Once configured, here’s what behaves differently across the platform:
| Feature | Single-product | Multi-product |
|---|
| Content generation | Uses global ICP + voice | Filters to product ICP + blended voice |
| Content library | Single flat list | Filterable by product line |
| Automation inbox | All items in one feed | Items tagged with product badge |
| Operating profiles | One profile per website | One profile per product line + cross-product rollup |
| Funnel baselines | Single set of KPIs | Per-product baselines |
| Classification | Not applicable | Required — see next guide |
Common Edge Cases
Overlapping ICPs across products — It is valid for the same ICP to appear in multiple product lines. WisePilot will use the product line context to determine which ICP attributes to emphasize during generation. You don’t need to create duplicate ICPs.
Migrating from single to multi-product — Enable the toggle, create product lines, then immediately run content classification before generating any new content. New content generated before classification is complete will be unscoped (usable cross-product, but not filtered).
Agencies managing multi-product clients — Multi-product mode is per website. You can have some client websites in single-product mode and others in multi-product mode simultaneously. Agency-level learnings and runner templates work across both modes.