Expansion Sequencing / Next-Best-Product
Not just what to expand — when and in what order.
Sample output for this workflow will appear here once it is captured.
Run the workflow in Claude, ChatGPT, or Phoenix Playground using the buttons below to see real output.
Overview
`whitespace-cross-sell-map` surfaces *what* to expand into. This workflow answers *when* and *in what order* given the customer's current adoption health and intent posture. Reads adoption stability, sponsor coverage, intent rise on adjacent categories, and budget headroom from spend signals to sequence the next 2-3 expansion plays over the next 6 months — not all at once.
Use cases
Stop the all-products-at-once expansion pitch
Your account team brainstorms 'what else can we sell them' wish-lists with 5 products and no sequence. This workflow picks the 2-3 with the strongest intent + functional readiness + budget headroom, sequences them over 6 months, and names the entry-point function for each. The CSM walks into the QBR with a real plan, not a wishlist.
Health gate keeps expansion honest
If the customer's adoption is declining, the workflow halts and recommends re-engagement — not expansion. You don't pitch the second product to a customer who's mid-churn on the first. The gate is automatic.
View workflow prompt
# Expansion Sequencing / Next-Best-Product
## Parameters
- `{{domain}}` *(required)* — Customer company domain. Example: `acme.com`
- `{{your_product}}` *(required)* — Your current product — anchors the stability check. Example: `HG Insights Core`
- `{{expansion_portfolio}}` *(optional)* — Comma-separated names of your other products the customer doesn't yet use. Example: `HG Intent, HG Spend, HG Operating Signals`
## Purpose
Sequence the next 2-3 expansion plays for {{domain}} over the next 6 months. Anchored on adoption stability of {{your_product}}, intent posture on adjacent categories, functional area readiness, and budget headroom. Pairs with `whitespace-cross-sell-map` (which surfaces *what* to expand) — this workflow answers *when* and *in what order*.
## Process
1. **Stability check** — `company_install_time_series` for {{domain}} filtered to {{your_product}}, `timeRange: last_12_months`. Confirm `intensity_momentum ≥ 0` and `current_intensity ≥ 50`. If unstable, halt and recommend re-engagement instead of expansion.
2. **Adjacent-category intent** — resolve {{expansion_portfolio}} (or your full portfolio if blank) to topic_ids via `list_intent_topics` and category ids via `list_product_categories`. Call `company_intent` for {{domain}} with `limit: 200`; post-fetch filter for adjacent-category topics. Flag any with positive `trend`.
3. **Functional readiness** — `company_fai` against your expansion-portfolio product names. Which functions at {{domain}} are likely consumers of each? Strong functional intensity → ready.
4. **Budget headroom** — `company_spend` for {{domain}}: total IT spend, spend by category. Larger spend in adjacent category → headroom for expansion in that area.
5. **Sequence** — pick top 2-3 products, sequence them by intent rise + functional readiness + budget headroom. Earliest play in the next 30-60 days; later plays in the 90-180-day window. Each play gets a single named entry-point function and a one-sentence "why now".
## Output Format
- `# 🚀 {{domain}} — Expansion Sequence`
- `## Stability gate` — pass / fail + evidence (skip rest if fail)
- `## Recommended sequence` — table: rank | product | timing (30/60/180d) | entry function | why now
- `## Evidence` — 1-2 supporting signals per recommendation, cited
## Quality Checklist
- Halt and re-engage if stability check fails — never recommend expansion into an unhealthy account
- Each recommendation cites at least intent + FAI evidence
- Sequence is over 6 months, not all at once
- No fabricated products — every product in the sequence is from {{expansion_portfolio}} or the user's clearly-stated portfolio
- Cap tool calls at ~12