Brand Strategy Controller
Build a brand strategy document from Helix's brand and listing data, then pressure-test every differentiation claim against live competitor listings and real customer review sentiment before anything is finalized.
Paste into Claude with your Helix MCP connection active, then swap the [BRACKETED] fields for your own brand.
You want a brand strategy document built from Helix's data, and you want its differentiation claims actually checked against live competitors and real customer reviews, not just restated from the brand's own file.
HELIX BRAND STRATEGY CONTROLLER
OBJECTIVE
Build a brand strategy document using Helix's brand and listing data as the foundation, then pressure-test every differentiation claim against real competitor listings and real customer review data before finalizing anything.
SETUP
Ask me to confirm:
- Brand: [BRAND NAME]
- Primary product / ASIN to use as reference: [PRODUCT]
PHASE 1: DRAFT FROM HELIX DATA
1. Retrieve the brand record: brand story, audience positioning, voice and messaging guidance, proof points, and topics to avoid.
2. Retrieve the latest completed transformation's ListingAnalysis report: ICP and USP mapping, keyword coverage by search volume, brand voice alignment examples, and compliance guidance.
3. Retrieve the ImageAnalysis report: executive summary, what customers want, and the named competitors in its competitive landscape data.
4. The brand record, the ListingAnalysis report, and the ImageAnalysis report each generate their own independent ICP narrative. Do not present all three. Reconcile them into one unified profile.
5. Draft: Brand Overview, Positioning Statement, ICP, USP, What Customers Want, Brand Voice (with before/after copy examples pulled from the report, not invented), Proof Points, Top Keywords by search volume, and Brand Guardrails.
6. Present this draft for review before moving to Phase 2.
PHASE 2: PRESSURE-TEST WITH REAL MARKET EVIDENCE
7. Cross-check every "topics to avoid" item in the brand record against the actual live transformed copy. Flag any contradiction directly, including legal or compliance risk language that's currently in use.
8. Identify named competitors from the ImageAnalysis report, then independently search Amazon's live catalog for each. Do not rely only on the pre-listed names, a live search may surface more relevant or higher-ranked competitors.
9. Pull real customer review sentiment for this product and for at least the top 2 to 3 competitors identified.
10. For every core USP claim, classify it as one of:
- PARITY: competitors make the identical claim, often cheaper
- VULNERABILITY: a competitor makes the same type of claim more confidently or with less risk attached
- TRUE DIFFERENTIATOR: no competitor in the set has anything comparable
11. Rebuild the differentiation section around a Need, Deliver, Differentiate framework. Cite the specific competitor name, price, and category rank behind every verdict.
RULES
- Never assert a differentiation claim without checking it against at least one real, live competitor listing.
- Never treat Helix's internal brand-consistency check as equivalent to competitive market validation. They answer different questions.
- Flag contradictions between brand guardrails and live copy plainly. Do not soften or bury a real compliance risk.
- Cite the specific source, a review quote, a competitor ASIN, a price, a rank, behind every finding. No unsourced claims.