# Brandwatch v2 Rebuild Brief
**Synthesized from:** Anton (strategic), Julia (research), Jessica (visual)  
**Date:** 2026-03-07  
**For:** Thibault (build) via Gerri (coordination)  
**Deploy to:** curiousendeavor.com/brandwatch-v2/

---

## VERDICT
The current page is technically competent but strategically weak. CE is positioned as Brandwatch's junior partner, the claims are unsourced, and the page looks like a SaaS template rather than premium CE work. All three reviewers independently flagged the same core issues.

---

## NON-NEGOTIABLE CHANGES (All 3 reviewers agree)

### 1. Kill "Curious Value" Sub-Brand
- **Problem:** Confuses visitor about who they're dealing with. New logo mark ≠ CE brand. Zero search equity.
- **Fix:** "Curious Endeavor × Brandwatch" or "Curious Endeavor — Brandwatch Partner". Use CE wordmark in nav.

### 2. Remove Duplicate Pipeline
- **Problem:** Pipeline explained twice (vertical timeline + horizontal infographic). Adds ~400px of redundant content.
- **Fix:** Keep the vertical timeline (stronger, more detailed). Kill the infographic entirely.

### 3. Add One Real Case Study
- **Problem:** Zero evidence the pipeline has been executed. Portfolio shows brand identity work unrelated to data-driven campaigns.
- **Fix:** Even an anonymized case study: "Enterprise fintech client → Brandwatch data → insight → campaign → 3.2× result" transforms credibility.

### 4. Fix or Remove the 3.2× Stat
- **Problem:** Unsourced, undefined baseline, no methodology. Enterprise analytics leads will scrutinize this.
- **Fix:** Source to specific engagement, or soften to "consistently 2-3× vs non-data-driven campaigns" with methodology note.

### 5. Fix Mobile CTA
- **Problem:** "Get Started" button completely disappears on mobile. No hamburger, no alternative.
- **Fix:** Keep CTA visible on mobile nav. Consider sticky mobile CTA bar.

---

## STRUCTURAL CHANGES

### Page Hierarchy (New Order)
1. **Hero** — CE is the strategic brain. Brandwatch is the data infrastructure.
2. **Problem** — "You've invested in Brandwatch. Are you getting enough value?"
3. **Solution** — AI-native data-to-campaign pipeline (the differentiator)
4. **Proof** — Stats (sourced) + Case study + Client logos (actual SVGs)
5. **Process** — Pipeline (ONE visualization, concise)
6. **Credibility** — Team expertise, Brandwatch depth, regions
7. **FAQ** — Address buyer objections
8. **CTA** — Scheduling link + form (not mailto:)

### Positioning Flip
- **Current:** "Brandwatch gives you X → we do Y with it" (CE is the addon)
- **New:** "You've invested in Brandwatch. We make that investment perform." (CE is the strategic authority)
- Own the "AI-native data-to-campaign" category explicitly — no competitor claims this

### Buyer Language Shift
- **From:** Creative agency language (campaign packages, brand systems, visual direction)
- **To:** Enterprise buyer language (data activation, social ROI, insight velocity, cross-market intelligence)

---

## VISUAL CHANGES

### Typography
- Display headings: 48px → 56-60px (use `clamp(40px, 5vw, 64px)`)
- H2/H3 gap too close (28px/20px) → H2 to 32px
- Body text: unify to 15px (currently 14px/15px inconsistency)
- Partner names: use actual logo SVGs or style as wordmarks (currently plain `<span>`)

### Spacing & Rhythm
- Section padding: 40px → 80px (major) / 60px (minor)
- Heading margin-bottom: 16px → 20-24px
- Card gap vs padding inverted (32px gap, 40px padding) → equalize

### Color & Backgrounds
- Alternate section backgrounds (#fff / #fafafa) — break the "wall of white"
- Remove section border-bottom lines — use whitespace instead (CE standard)
- Reserve red for CTAs and primary labels only — currently everything is red-accented
- Stats section: differentiate with subtle background tint

### Components
- Stats: increase number size to 56px, remove card borders, let numbers breathe
- Work cards: add background-color fallback for missing images
- CTAs: scheduling link (Calendly/Cal.com) + form — replace mailto:
- Ghost button: reduce padding on mobile (full-width looks oversized)

---

## CONTENT TO ADD
1. **Case study section** — anonymized Brandwatch engagement with data flow
2. **FAQ section** — "Do I need Brandwatch already?" / "What markets?" / "How is this different?"
3. **Team/expertise proof** — who runs engagements, Brandwatch depth
4. **Engagement model** — pricing signal, timeline, scope
5. **Brandwatch technical depth** — which modules, dashboards, queries

## SEO FIXES
- Page title: add "Brandwatch" (currently missing)
- H1: include "Brandwatch partner"
- Meta description: target "Brandwatch implementation partner" searches

---

## CE BRAND STANDARDS (Non-Negotiable)
- Fonts: Larken + Inter + JetBrains Mono
- Color: #cc0000 red, white backgrounds
- Quality gate: Read `skills/ce-ui-quality/SKILL.md` before building
- Responsive: Read `skills/responsive-design/SKILL.md` before building
- Frontend: Read `skills/frontend-design/SKILL.md` before building

---

## DONE WHEN
- [ ] "Curious Value" replaced with CE branding
- [ ] Single pipeline visualization (vertical timeline only)
- [ ] Case study section (even placeholder structure)
- [ ] Stats sourced or softened
- [ ] Mobile CTA accessible
- [ ] Section padding 80px+, no border lines
- [ ] Background variation between sections
- [ ] mailto: replaced with scheduling/form CTA
- [ ] SEO: Brandwatch in title, H1, meta
- [ ] Deploy at /brandwatch-v2/ (v1 stays intact)
- [ ] Anton review before showing Assaf

**Autonomy:** 🟡 CHECKPOINT — Deploy draft to /brandwatch-v2/, then pause for review before any further iteration.