Phoenix PVP-PQS Framework
Walk a named greenfield target through pain-qualified-segment plus permissionless-value-proposition outbound, end-to-end, in one Phoenix-branded HTML briefing.
€361M capex AI GPU buildout — zero certified HPC-tier storage partner
| Signal | Finding | Gap / Risk |
|---|---|---|
| Storage Stack | OpenStack + OpenIO object storage (proprietary) | No parallel FS for AI workloads |
| Intent Signal | 500 active intent topics · "AI champion" flag | Adoption gap vs. intent level |
| 🎯 Your Account | 44 DCs globally · Italy + US expansion active | Live expansion = open window |
Overview
Marketing Ops and field marketing teams use this workflow to produce a single Phoenix-branded HTML executive briefing that walks an HG Insights customer through pain-qualified-segment plus permissionless-value-proposition outbound, worked end-to-end against a named greenfield target. The briefing ends with a fully drafted PVP email and a four-cell anatomy block where every figure traces to either a Phoenix MCP tool call or a named public source.
Use cases
PVP-PQS briefings your customer's CRO would send unchanged
Marketing Ops and field marketing run the framework against a named greenfield target and get a complete Phoenix-branded HTML briefing: signal board sourced from HG firmographic, technographic, intent, operating signals, and SEC filings; pain-qualified segment named in one specific sentence; six-paragraph PVP email that leads with workload-class observations instead of credentials; four-cell anatomy block where every figure traces to a Phoenix MCP tool call or a named public source.
One reference layout, every greenfield account
The bundled DDN-Nebius worked example demonstrates the structure end-to-end. Run the same framework against a different customer and target pair (Pure Storage and CoreWeave, VAST Data and Lambda Labs, an industrial automation vendor and an EV battery manufacturer), and the output mirrors the same structure with the new customer's vocabulary throughout.
View workflow prompt
# Phoenix PVP-PQS Framework
## Parameters
- `{{customer}}` *(required)* — The HG Insights customer this briefing is for (the audience reading it). Example: `ddn.com`
- `{{customer_category}}` *(required)* — One sentence describing what the customer sells. Example: `Parallel-filesystem storage for AI training and HPC`
- `{{customer_differentiators}}` *(required)* — Two sentences naming what makes the customer defensible. Example: `EXAScaler powers dozens of TOP500 systems including sovereign deployments. Single-vendor accountable hardware boundaries with audit trails.`
- `{{customer_references}}` *(required)* — 3 to 5 named reference customers, comma-separated. Example: `KAUST, Helmholtz Munich, TACC, NHS England`
- `{{customer_competitors}}` *(required)* — 2 to 4 named competitors, comma-separated. Example: `WEKA, VAST Data, Pure Storage`
- `{{target}}` *(optional)* — Named greenfield target for the worked example. Example: `nebius.com`
- `{{sender}}` *(optional)* — Customer-side executive whose name signs the PVP. Example: `Alex Bouchard, President`
- `{{industry_trends}}` *(optional)* — Recent contracts, regulations, or capacity announcements to weave in. Example: `Meta Vera Rubin Q3 2027 start, NVIDIA DGX SuperPod RA update`
## Purpose
Run PVP-PQS for {{customer}} ({{customer_category}}, defensible per {{customer_differentiators}}) against {{target}}. Produce a Phoenix-branded HTML executive briefing ending in a drafted PVP email so specific the target would forward it even if they never buy. Every figure traces to a Phoenix MCP tool call or a named public source. The reference skills carry the canonical procedure and editorial guardrails.
## Process
1. **Context.** Web-search {{customer}}; confirm positioning against {{customer_references}} and {{customer_competitors}}. If {{target}} is empty, pick one by SEC-filer scale + named incumbent in {{customer_competitors}} + verified absence of partnership (two web searches). State the verification.
2. **Signal gather.** Run `company_firmographic`, `company_operating_signals`, `company_technographic` (intensity-sorted, 20 to 30 products), `company_install_time_series` filtered to {{customer_category}}, `company_intent`, `sec_full_text_search`, `sec_filing_section`, and `web_search` on partner/customer pages plus {{industry_trends}}. Build a 9-row signal board with hot badges on the 3 to 4 figures the PVP math depends on.
3. **PQS naming.** Headline "The [specific commitment] with [the missing piece]". Math public commitments times industry attach rate, source named.
4. **PVP composition** (per PVP Composition skill): thesis, three observations (technical / procurement / regulatory), pattern recognition, industry pattern, math for both sides, soft close. Sign with {{sender}} or title. References go *inside* observations.
5. **HTML build** (per Phoenix HTML Briefing Structure skill): mirror `/samples/phoenix-pvp-pqs-ddn-nebius.html`. One gradient-text word, one primary button, no em dashes.
## Output Format
- Section 01: PQS + PVP concept cards + thesis callout
- Section 02: four-card method grid
- Section 03: case header for {{target}}, context, capacity chart, 9-signal board, pain block, PVP card, anatomy grid
- Section 04: five-row playbook table covering {{customer}}'s full ICP
- Footer: working-session CTA
## Quality Checklist
- Every PVP figure traces to a Phoenix tool call OR named public source (anatomy block proves it)
- {{target}} verified greenfield against {{customer}}
- {{customer_references}} appear inside observations, not at the headline
- No em dashes, no rule-of-three lists, no rhetorical questions, no AI vocabulary