# Brandwatch V2 Landing Page — CE Review **Page:** https://curiousendeavor.com/brandwatch-v2/ **Source:** `/root/.openclaw/workspace/public/brandwatch-v2/index.html` **Reviewed:** 2026-03-09 **Reviewers:** Jessica (Art Direction), Ogilvy (Copy), Anton (Quality Critic) --- ## 1. Overall Grade: **B-** The page is technically competent and mostly CE-compliant, but suffers from a structural flow problem that undermines conversion. An enterprise VP of Marketing lands on this page and has to scroll past operator bios and a callout quote before they even understand what CE does or why they should care. The red section is overused. The AI team reveal is a conversion risk for enterprise buyers. Good bones, wrong skeleton. --- ## 2. Top 5 Priority Fixes (Ranked by Impact) ### 1. **Restructure the page flow — move Problem before Operators** **Impact:** HIGH — this is the #1 conversion killer **Current order:** Hero → Operators → Callout → Problem → Solution → Deliverables → Team → Expertise → FAQ → Work → CTA **Correct order:** Hero → Problem → Solution → Deliverables → Work/Proof → Operators → Expertise → Team → FAQ → CTA **Why:** Enterprise buyers need to see themselves in the problem before they care about who you are. The current flow front-loads credibility before establishing relevance. Every landing page framework says: Problem → Solution → Proof → CTA. The Operators section (line ~548) should come AFTER the solution and deliverables, not as the second thing on the page. ### 2. **Shrink or eliminate the red-section background on Solution** **Impact:** HIGH — visual dominance and brand compliance **Lines:** 117-152 (CSS for `.red-section`), line ~588 (`section.solution.red-section`) **Problem:** The Solution section is the largest section on the page and it's entirely on a red background. This violates CE's "red used sparingly and intentionally" principle. It makes the page feel like it has a giant red billboard in the middle. Red backgrounds should be reserved for a single high-impact moment (like the final CTA or a short callout), not a full process infographic section. **Fix:** Make Solution/Process a white section. Use red only for the step numbers, icons, and accent lines. Save red-section treatment for the callout quote only (if even that). ### 3. **Reframe or remove the AI team section for enterprise audience** **Impact:** HIGH — enterprise credibility risk **Lines:** ~648-710 (Team section in HTML) **Problem:** Showing 8 AI agent avatars with names like "Kitt," "Ogilvy," "Tatiana" to an enterprise Brandwatch buyer is a significant risk. A VP of Marketing paying $50-150K wants to know they're working with senior humans, not a chatbot roster. The avatars look AI-generated (they are), which doubles the uncanny-valley problem. **Fix:** Either (a) reframe as "Our AI-powered workflow" without anthropomorphized names/avatars — show it as technology, not fake team members, or (b) replace entirely with a "How We Work" section showing the human+AI methodology without the character cards, or (c) move to a secondary page and link to it. The Operators section (Assaf + Lukas) provides the human credibility — the AI team section undermines it. ### 4. **Add real social proof — logos, testimonials, or case study results** **Impact:** HIGH — trust gap **Problem:** Zero client logos. Zero testimonials. Zero case study results with numbers. The Figma embed (line ~730) shows portfolio work but it's not the same as "Company X saw 3x engagement increase." An enterprise buyer at this price point needs third-party validation. **Fix:** Add a logo strip after the hero (even 4-5 logos). Add 1-2 short testimonial quotes in the proof section. If no Brandwatch-specific case studies exist yet, use adjacent enterprise work with permission. ### 5. **Fix non-compliant CSS: border widths, transitions, font sizes** **Impact:** MEDIUM — brand compliance and quality perception **Issues:** - Line 338: `border-top: 2px solid var(--red)` on `.feature` — CE spec is 1px only - Line 434: `border: 2px solid var(--border)` on `.infographic-icon` — should be 1px - Line 505: `border-top: 2px solid var(--red)` on `.expertise-card` — should be 1px - Line 383: `transition: transform 0.4s ease` — CE max is 200ms - Line 400: `transition: opacity 0.3s ease` — CE max is 200ms - Line 440: `transition: border-color 0.3s ease, background 0.3s ease` — CE max is 200ms - Line 216: `font-size: 24px` on `.bio h3` — not in the 7-size scale (should be 28px/`--size-h1` or 20px/`--size-h2`) - Line 229: `font-size: 15px` on `.bio p` — not in scale (should be 14px/`--size-body`) - Line 243: `font-size: 11px` on `.embed-label` — not in scale (should be 10px/`--size-label` or 12px/`--size-small`) - Line 269: `font-size: clamp(28px, 4vw, 42px)` on `.callout-text` — 42px max is fine but 28px min doesn't match scale - Line 340: `font-size: 32px` on `.feature-icon` — not in scale **Fix:** Align all values to CE design system tokens. --- ## 3. Jessica's Visual Notes ### Typography Hierarchy - **Generally clean.** Larken for headings, Inter for body — correct. - **Line 216:** `.bio h3` uses 24px — not in the 7-size scale. Should be `var(--size-h1)` (28px) or `var(--size-h2)` (20px). Currently falls between sizes, which breaks the system. - **Line 229:** `.bio p` uses 15px — should be `var(--size-body)` (14px). One pixel off but it breaks the discipline. - **Line 340:** `.feature-icon` at 32px — what is this? If it's an icon container for SVGs, don't set font-size. If it's for emoji icons, emojis are banned per CE rules. - **Line 269:** `.callout-text` clamp range (28-42px) works visually but doesn't snap to scale. Consider `clamp(var(--size-h1), 4vw, var(--size-display))`. - **Inline style on line ~556:** `font-size: 17px` on the operators intro paragraph — not in scale. Should be 14px body or use a class. ### Spacing & Rhythm - **Sections breathe well** at `padding: 100px 0` (line 111). Good. - **The Operators section** feels visually heavy — two large bios with 120px photos take up a lot of vertical space before the visitor understands the offering. - **Deliverables section** spacing is excellent — the table-like grid with numbered rows is clean editorial design. Best section visually. - **Team grid** (8 cards × 4 cols) creates a wall of content that doesn't breathe. Consider 2 rows of 4 with more gap, or reduce to key 4-5 agents. ### Color Usage - **Red background overuse:** The Solution section (`.red-section`) spans the full width with 100px padding top/bottom plus a 5-step infographic. This is approximately 600-700px of solid red. CE uses red as an accent, not a wall. This should be white. - **Callout section** (line ~572) uses inline `color: #cc0000` instead of `var(--red)` — works but breaks variable discipline (line ~574-575). - **The red is otherwise well-controlled** — section labels, stat numbers, step numbers, CTAs. Good restraint outside the red-section. ### Border Violations - **Line 338:** `.feature` has `border-top: 2px` — CE is 1px only, no exceptions. - **Line 434:** `.infographic-icon` has `border: 2px solid` — should be 1px. - **Line 505:** `.expertise-card` has `border-top: 2px` — should be 1px. - All three create a heavier visual weight than CE's hairline aesthetic. ### Transition Violations - **Line 383:** `.work-item img` hover at 0.4s — too slow. Change to `0.2s ease`. - **Line 400:** `.work-caption` opacity at 0.3s — change to `0.2s`. - **Line 440:** `.infographic-icon` at 0.3s — change to `0.2s`. - Line 106 `.btn` transition at 0.2s — ✅ correct. ### Mobile Responsiveness - **Line 464-489:** Responsive rules look reasonable. Grid collapses to 1-col, infographic goes vertical. - **Concern:** The Figma embed iframe (line ~733) at `height: 700px` desktop / `450px` mobile could be problematic. Figma embeds are notoriously slow on mobile and may not render well. No fallback if embed fails. - **Mobile CTA** (fixed bottom bar, line 69-80) — good pattern, but it shows on scroll based on JS (line ~752). Could flash or be delayed. - **Team grid** goes to 2-col on tablet, 1-col on small mobile — this means 8 cards stacked vertically. Very long scroll. ### CE Quality Gate Checklist - [x] Background is white (`#fff`) — except red-section (intentional but overused) - [x] Only Larken / Inter / JetBrains Mono fonts used - [x] Typekit `ffj8sbd` loaded - [x] Google Fonts loaded for Inter + JetBrains Mono - [x] Only CE colors used (no blues, purples, greens) - [x] Red accent is `#cc0000` - [x] Section labels styled correctly - [ ] **FAIL:** Font-weight above 500 not found (✅) but border widths exceed 1px - [ ] **FAIL:** 5 font sizes outside the 7-size scale (24px, 15px, 17px, 11px, 32px) - [ ] **FAIL:** 3 borders at 2px instead of 1px - [ ] **FAIL:** 3 transitions exceed 200ms - [x] No gradients - [x] No box-shadows - [x] Container max-width 1100px ✅ - [x] No emojis as icons ✅ - [ ] **WARN:** 6 inline styles — should use classes --- ## 4. Ogilvy's Copy Notes ### Hero (Lines ~536-546) - **Headline:** "You've invested in Brandwatch. We make that investment *perform*." — **Strong.** Speaks directly to the sunk-cost psychology of a Brandwatch buyer. The italicized "perform" adds weight. Keep this. - **Subheadline:** "Brandwatch gives you the data. Curious Endeavor is the strategic brain..." — Good framing. "Strategic brain" is vivid. One concern: "multi-market execution in days, not months" is a big claim. Can we back it up? If yes, keep. If not, soften to "weeks, not quarters." - **CTA:** "Book Strategy Call →" — Clear, specific, good. ✅ ### Operators Section (Lines ~548-570) - **"Market veterans building the future"** — Generic. Every consultancy says this. Replace with something specific to the Brandwatch angle: "Brandwatch insider + brand strategist" or "One built campaigns. One sold Brandwatch." - **Assaf's bio:** "I've spent my career in rooms where the budget was big and the stakes were real" — Strong opening. But "brand isn't decoration" feels like it's setting up a brand strategy pitch, not a Brandwatch activation pitch. The bio should connect more directly to *why this matters for Brandwatch buyers*. - **Lukas's bio:** "I sold Brandwatch to enterprise clients across DACH and beyond" — This is the money line. Should be more prominent. Currently buried in the second bio of a section that appears too early. ### Callout (Line ~574) - **"Not a demo. Not a prototype. A production system that ships real work."** — Punchy and good. But it appears before the problem section, so the reader has no context for what "real work" means yet. This should come AFTER the solution/deliverables to land with impact. ### Problem Section (Lines ~578-585) - **"Are you getting enough value from your Brandwatch investment?"** — Good question headline. Directly challenges the reader. - **"expensive reporting"** — Strong phrase. Hits the pain point. - **"campaigns that move the needle"** — Cliché. Replace with something specific: "campaigns that win in their actual markets" or "creative that reflects what your audience actually cares about." ### Solution Section (Lines ~588-640) - **"From social intelligence to finished campaigns"** — Clear value prop. Good. - **"While agencies take your brief and apply templates, we start from what your audience is actually saying"** — Excellent differentiator line. This is the core positioning and it works. - **Infographic labels are clear** but "Data Extraction" (Step 1) sounds technical/internal. Reframe for the buyer: "Audience Intelligence" or "Insight Capture." - **"Multi-Region Scaling"** (Step 5) — sounds like infrastructure. Try "Market Expansion" or "Global Deployment." ### Deliverables Section (Lines ~642-680) - **"Concrete deliverables, not decks full of recommendations"** — Excellent headline. Best on the page. Directly addresses enterprise buyer frustration. - **"Not concepts. Not strategy decks that need another agency to execute."** — This is killer copy. Keep. - **The 5 deliverables are clear and well-described.** No jargon. Each one answers "what do I get?" - **Minor:** "Deployable assets, not mockups" (Deliverable 03) echoes the section headline. Slight redundancy but acceptable for emphasis. ### Team Section (Lines ~648-710) - **"Eight specialists. One coordinated system."** — Clean headline. - **Problem:** The descriptions are cute but not credible for enterprise. "Words that sell without feeling like selling" (Ogilvy) and "Ships what others say can't be built" (Thibault) read as marketing fluff for AI personas. An enterprise buyer will see through this. - **"They work in parallel, with human oversight at every decision point"** — This is the key trust line but it's buried in the section description. If we keep this section, this sentence needs to be a standalone callout. ### Expertise Section (Lines ~714-730) - **"We Know the Brandwatch Buyer"** — Strongest credibility section. Should be higher on the page. - **Bullet points are excellent.** "What makes Brandwatch clients renew — and what makes them churn" — this is insider knowledge that builds trust. - **"The questions CMOs ask that dashboards can't answer"** — Great line. Enterprise buyers will nod at this. ### FAQ (Lines ~532-578... actually ~735-775) - **Pricing answer:** "$50-150K" with "50% upfront, 50% on delivery" — Very specific. This can work as a qualifier (scares off tire-kickers) but could also anchor enterprise buyers low. Consider whether this belongs on the page or in a conversation. - **"What if the campaigns don't perform?"** — The answer is honest but reads as a disclaimer. "We optimize for strategic soundness and production quality, not performance guarantees" could sound defensive. Reframe: lead with what you DO guarantee (methodology, speed, quality) before the caveat. ### Final CTA (Lines ~740-750) - **"Ready to make Brandwatch *actually deliver?*"** — Strong. Implied criticism of the tool on its own, which is exactly the positioning. - **"Tell us your markets and your current Brandwatch setup"** — Good specificity. Tells the buyer what to prepare. ### Redundancy Check - **Solution section** and **Deliverables section** overlap. Solution describes the process; Deliverables describes the output. They could be combined into one section with the infographic showing the process and the deliverable list showing what comes out of each step. - **Operators** and **Expertise** sections both establish credibility but from different angles. Consider merging: Operators bios → with the expertise bullets underneath each person. --- ## 5. Anton's Strategic Critique ### What's the single biggest weakness? **The page structure puts the team before the problem.** An enterprise buyer lands here from a Brandwatch referral or cold outreach. They see the hero (good), then immediately get two bio paragraphs about people they don't know yet, then a callout quote they have no context for, then FINALLY the problem statement. By then, many have bounced. The page fails the "5-second test" — if I scroll past the fold, can I tell what problem you solve? Not until section 4. ### What would make an enterprise buyer close the tab? 1. **The AI team section.** An enterprise VP paying $100K+ sees 8 cartoon avatars with names and thinks "this is a guy with ChatGPT." Even if the methodology is genuinely powerful, the presentation screams "small operation pretending to be a team." The Operators section (real humans) builds trust — the AI team section tears it down. 2. **No proof.** No logos, no testimonials, no case study with numbers. The Figma embed is portfolio work but there's no "we did X for company Y and they saw Z result." At this price point, that's a hard pass. 3. **The massive red section.** Visually screams "agency trying too hard." Premium looks quiet. The red wall contradicts CE's editorial, white-first aesthetic. ### What's missing that competitors would have? - **Client logos** — even "trusted by teams at..." with 4-5 logos - **A concrete case study** — "Brandwatch data → insight → campaign → result" with real numbers - **ROI framing** — "Brandwatch costs you $X/year. We turn that into $Y of campaign value." - **Integration details** — How does CE actually connect to Brandwatch? API? Manual export? Direct collaboration with their CS team? - **Timeline specificity** — "days, not months" is vague. "First campaign delivered in 2 weeks" is concrete. ### Grade Justification: B- - **Copy quality:** B+ (hero is strong, deliverables section is excellent, some redundancy) - **Visual execution:** B (mostly CE-compliant, several spec violations, red section overuse) - **Page structure:** C+ (fundamentally wrong section ordering) - **Conversion optimization:** C (no social proof, no case studies, AI team reveal is risky) - **Brand compliance:** B- (multiple spec violations: borders, transitions, font sizes, inline styles) ### Top 3 Changes with Most Impact 1. **Reorder sections:** Hero → Problem → Solution + Deliverables (merged) → Work/Proof → Operators + Expertise (merged) → FAQ → CTA. Remove or radically rethink the AI team section. 2. **Add social proof:** Logo strip after hero. One testimonial quote in the proof area. Even aspirational ("Working with enterprise teams in fintech, SaaS, and consumer brands"). 3. **Kill the red-section background.** Make Solution white. Use red only for accents. The page should feel editorial and premium, not like a trade show booth. --- ## 6. Quick Wins (Under 30 Minutes Each) ### CSS Fixes (15 min) - **Line 338:** Change `border-top: 2px` → `border-top: 1px` on `.feature` - **Line 434:** Change `border: 2px` → `border: 1px` on `.infographic-icon` - **Line 505:** Change `border-top: 2px` → `border-top: 1px` on `.expertise-card` - **Line 383:** Change `0.4s` → `0.2s` on `.work-item img` transition - **Line 400:** Change `0.3s` → `0.2s` on `.work-caption` transition - **Line 440:** Change `0.3s` → `0.2s` on `.infographic-icon` transition ### Font Size Alignment (10 min) - **Line 216:** `.bio h3` 24px → `var(--size-h1)` (28px) or `var(--size-h2)` (20px) - **Line 229:** `.bio p` 15px → `var(--size-body)` (14px) - **Line 243:** `.embed-label` 11px → `var(--size-label)` (10px) - **Line 340:** `.feature-icon` 32px → remove or use SVG sizing only - **Inline on ~556:** `font-size: 17px` → `var(--size-body)` or `var(--size-small)` ### Inline Style Cleanup (10 min) - **Line ~556:** `style="font-size: 17px; color: var(--grey)..."` — create `.intro-text` class - **Line ~574-575:** `style="color: #cc0000;"` → use `` with `.callout-text em { color: var(--red); }` - **Line ~583:** `style="text-align: center; margin-left: auto..."` — add to `.problem .section-desc` in CSS - **Line ~728:** Inline styles on the Work section h2 and p — use classes - Replace all `#cc0000` inline references with `var(--red)` ### Copy Quick Fix (5 min) - **Line ~551:** Change "Market veterans building the future" → "Brandwatch insider meets brand strategist" - **Line ~583:** Change "campaigns that move the needle" → "campaigns built from what your audience actually says" ### Remove Red Section (10 min) - **Line ~588:** Remove `red-section` class from the Solution section - The infographic and content will automatically render correctly on white background since base styles exist --- --- ## 7. 🚨 CRITICAL: Audience Framing Audit — WRONG AUDIENCE THROUGHOUT **The page is currently written for Brandwatch's end-users (brands/VPs of Marketing). The actual audience is BRANDWATCH LEADERSHIP — this is a partnership pitch TO Brandwatch.** Every section audited below for: **Is this talking to Brandwatch leadership about what CE can do for their platform and clients? Or is it talking to a brand about using Brandwatch?** --- ### Hero — ❌ WRONG AUDIENCE **Current (line ~668-674):** ``` You've invested in Brandwatch. We make that investment perform. ``` > "Brandwatch gives you the data. Curious Endeavor is the strategic brain that turns it into finished campaigns — strategy, creative, and multi-market execution in days, not months." **Problem:** "You've invested in Brandwatch" is talking to a brand that bought Brandwatch. Brandwatch leadership didn't "invest in Brandwatch" — they ARE Brandwatch. The subheadline talks about "your Brandwatch data" — again, end-user framing. **Corrected:** ``` Your clients have the data. We turn it into the campaigns they can't build alone. ``` > "Curious Endeavor is an activation layer for Brandwatch — we take your clients' social intelligence and deliver finished campaigns: strategy, creative, and multi-market execution in days, not months. Higher ARPU. Stickier platform. Clients who renew." **Badge text:** Change "Brandwatch Partner" → "Brandwatch Activation Partner" or "Partnership Proposal" **CTAs:** "Book Strategy Call" → "Explore the Partnership" / "Book a Partnership Call" --- ### Operators — ⚠️ PARTIALLY WRONG **Current Assaf bio (line ~681-684):** > "I've spent my career in rooms where the budget was big and the stakes were real — presidential campaigns, Fortune 500 repositions..." **Problem:** This bio is written to impress a brand buyer. Brandwatch leadership cares about: Can this person actually deliver for our clients? Does he understand our business model? **Corrected Assaf bio:** > "15 years building campaigns for enterprise brands — presidential campaigns, Fortune 500 repositions, fintech scale-ups. I know what Brandwatch clients need because I've been the strategist they hire after they buy the platform." **Current Lukas bio (line ~689-692):** > "I sold Brandwatch to enterprise clients across DACH and beyond. I know how buyers evaluate social intelligence, what drives renewals, and where the gap between data and action costs them." **Problem:** Mostly correct — speaks to Brandwatch's business. But "the gap between data and action costs them" frames it as the end-user's problem. Reframe for Brandwatch: the gap costs YOU (Brandwatch) renewals. **Corrected Lukas bio:** > "I sold Brandwatch to enterprise clients across DACH and beyond. I know what drives renewals, where clients get stuck after onboarding, and why the gap between data and action is Brandwatch's biggest churn risk. Now I'm building the activation layer that closes that gap." **Section headline:** "Market veterans building the future" → "We know your clients — and your churn problem" --- ### Callout — ⚠️ NEUTRAL (needs reframing) **Current (line ~699):** > "Not a demo. Not a prototype. A production system that ships real work." **Problem:** Ambiguous — who is this talking to? It works generically but doesn't address Brandwatch leadership specifically. **Corrected:** > "Not a consulting deck. Not a pilot program. A production system your clients can use tomorrow." or: > "Your clients don't need another dashboard. They need someone who turns the data into finished campaigns." --- ### Problem Section — ❌ COMPLETELY WRONG AUDIENCE **Current (line ~703-709):** ``` Are you getting enough value from your Brandwatch investment? ``` > "You're paying for enterprise social intelligence. But social data without strategic action is just expensive reporting. Most teams struggle to turn audience insights into campaigns that move the needle." **Problem:** This is 100% talking to a brand that bought Brandwatch. "You're paying for..." / "Your Brandwatch investment" — Brandwatch leadership isn't paying for Brandwatch. They're selling it. This section needs to describe their clients' problem as a BUSINESS problem for Brandwatch (churn, underutilization → lower renewals, ARPU ceiling). **Corrected headline:** ``` Your clients' biggest gap is your biggest growth opportunity ``` **Corrected body:** > "Most Brandwatch clients underutilize the platform. They pull reports, track mentions, run sentiment — but they can't turn that intelligence into campaigns. That gap is why accounts plateau, why renewals stall, and why ARPU stays flat. We close it." or even sharper: > "Brandwatch gives your clients world-class social intelligence. But intelligence without activation is just expensive monitoring. When clients can't turn data into campaigns, they question the investment — and that's a renewal conversation you don't want to have." --- ### Solution Section — ❌ WRONG AUDIENCE **Current (line ~713-718):** ``` From social intelligence to finished campaigns ``` > "We turn your Brandwatch data into ready-to-deploy campaigns. While agencies take your brief and apply templates, we start from what your audience is actually saying..." **Problem:** "Your Brandwatch data" / "your audience" — talking to the end-user. Should be: "your clients' data" / "their audience." **Corrected headline:** ``` The activation layer your platform is missing ``` **Corrected body:** > "We turn your clients' Brandwatch data into ready-to-deploy campaigns. While agencies take a brief and apply templates, we start from what the audience is actually saying inside your platform — and build strategy, creative, and execution playbooks directly from that intelligence. Your clients get more value. You get stickier accounts." **Infographic step labels — mostly fine** but Step 01 "Pull structured audience intelligence from Brandwatch" should be "Pull structured intelligence from the client's Brandwatch instance" or simply "Connect to client's Brandwatch data." --- ### Deliverables Section — ❌ WRONG AUDIENCE **Current headline (line ~736):** ``` Concrete deliverables, not decks full of recommendations ``` **Problem:** This is selling to a brand buyer who's tired of consultants. Brandwatch leadership doesn't care about deliverable format — they care about what CE produces for THEIR clients and how it affects retention/ARPU. **Corrected headline:** ``` What your clients get — through you ``` **Corrected intro:** > "Every engagement produces finished work your clients can deploy immediately. Not concepts. Not strategy decks that need another agency. Production-ready campaigns built from their own Brandwatch data — delivered as a premium service layer on your platform." **Individual deliverables — reframe each:** 1. **Strategy Brief** → same content but add: "Positions Brandwatch as the strategic foundation, not just the data source." 2. **Campaign Brief** → add: "Branded as a Brandwatch-powered deliverable." 3. **Production-Ready Assets** → add: "Your clients see these as Brandwatch ecosystem value." 4. **Multi-Market Localization** → add: "Unlocks expansion conversations — and upsell opportunities for regional licenses." 5. **Execution Playbook** → add: "Creates ongoing dependency on Brandwatch data, reinforcing renewal." --- ### Team Section — ⚠️ NEEDS REFRAMING **Current (line ~762):** > "Eight specialists. One coordinated system." > "Strategy, research, creative direction, copywriting, design, and quality control — each handled by a dedicated AI agent. They work in parallel, with human oversight at every decision point." **Problem:** For end-users, AI team is a credibility risk. For Brandwatch leadership, AI team is a SCALABILITY story — this is actually a strength when framed correctly. Brandwatch wants to know: can you serve 50 clients? 200? The AI team IS the answer. **Corrected headline:** ``` Built to scale with your client base ``` **Corrected intro:** > "Our AI-powered production system handles strategy, research, creative, copy, and quality control in parallel. Human oversight at every decision point. This isn't a boutique — it's infrastructure that scales with your enterprise client roster without adding headcount." **Keep the team cards** but reframe the section description to emphasize: this is why we can serve your entire enterprise book, not just one client at a time. --- ### Expertise Section — ⚠️ PARTIALLY WRONG **Current "We Know the Brandwatch Buyer" card (line ~785-795):** > "We've been on the other side of the table — selling Brandwatch, onboarding enterprise teams, watching what happens after the deal closes." **Problem:** "the other side of the table" implies CE is now on the buyer's side. For a Brandwatch pitch, we're on the SAME side. Reframe. **Corrected:** > "We've been on your side of the table — selling Brandwatch, onboarding enterprise teams, watching what happens after the deal closes. We know where clients get stuck, what makes them renew, and what makes them churn. We built CE to solve the problem we saw over and over: great data, no activation." **Bullet points — reframe for Brandwatch's interests:** - "How enterprise teams evaluate and buy social intelligence" → ✅ keep (relevant to their sales cycle) - "Where the gap between data and action shows up" → ✅ keep - "What makes Brandwatch clients renew — and what makes them churn" → ✅ keep (this is THE line for Brandwatch leadership) - "The questions CMOs ask that dashboards can't answer" → ✅ keep - "How to turn platform investment into visible ROI" → Change to: "How to turn platform investment into visible ROI — making Brandwatch indispensable, not optional" **"Global Campaign Experience" card** — mostly fine but add a closing line: "This experience is now available as a service layer for your enterprise clients." --- ### FAQ Section — ❌ MOSTLY WRONG AUDIENCE **Every FAQ is written for end-user buyers. Brandwatch leadership has different questions.** **Replace entirely with partnership-relevant FAQs:** 1. **"How does the commercial model work?"** > "We operate as a referred services partner. Brandwatch refers clients who need activation support, we deliver, and we can structure revenue share, referral fees, or white-label arrangements depending on your preference." 2. **"Can you scale across our enterprise client base?"** > "Yes. Our AI-powered production system is built for parallel execution. We can run 10+ client engagements simultaneously without quality degradation. Each engagement is human-overseen but AI-accelerated." 3. **"Do you need access to our clients' Brandwatch instances?"** > "Yes — read access to their Brandwatch data is how we extract the intelligence that drives strategy. We work within your existing client permissions framework." 4. **"What markets can you cover?"** > "Any market where Brandwatch collects data. We've delivered campaigns across 50+ countries with particular strength in North America, Europe, APAC, and LATAM. Our system produces native-quality content in any market language." 5. **"How does this affect client retention?"** > "Directly. Clients who see finished campaigns built from their Brandwatch data view the platform as indispensable, not optional. We've seen this pattern repeatedly — when data drives visible output, renewal conversations become formalities." 6. **"What's the typical engagement size?"** > "Project-based, typically $50-150K per client depending on market scope. This represents incremental revenue for Brandwatch — either as a referred service or as a revenue-share partner offering." --- ### Work/Portfolio Section — ⚠️ NEEDS REFRAMING **Current (line ~820):** > "This is what it could look like" > "Real campaigns. Real markets. From strategy through production-ready assets." **Problem:** "What it could look like" is selling to an end-user prospect. For Brandwatch: show them what their clients would receive. **Corrected:** > "This is what your clients receive" > "Real campaigns built from real Brandwatch data. Strategy through production-ready assets — delivered in days." --- ### Final CTA — ❌ WRONG AUDIENCE **Current (line ~836-840):** ``` Ready to make Brandwatch actually deliver? ``` > "Tell us your markets and your current Brandwatch setup." **Problem:** "Make Brandwatch actually deliver" is a dig at Brandwatch — you're saying their product doesn't deliver. That's exactly the wrong message when pitching TO Brandwatch leadership. "Your current Brandwatch setup" — they don't have a setup, they ARE the setup. **Corrected:** ``` Ready to turn data into revenue — for you and your clients? ``` > "Let's explore how CE becomes the activation layer for your enterprise accounts. We'll show you the model, the economics, and a sample campaign built from live Brandwatch data." **CTAs:** - "Book Partnership Call →" (not "Strategy Call") - "Email Directly" → ✅ fine --- ### Nav + Footer — Minor fixes **Nav CTA:** "Book a Call" → "Explore Partnership" **Mobile CTA:** "Book a Strategy Call" → "Book a Partnership Call" **Footer:** "Curious Endeavor — Brandwatch Partner" → ✅ fine **Meta description (line 5):** "Brandwatch implementation partner. Curious Endeavor turns social intelligence into finished campaigns..." → Change to: "Brandwatch activation partner. Curious Endeavor turns your clients' social intelligence into finished campaigns — increasing platform stickiness, ARPU, and retention." --- ### Section-by-Section Verdict | Section | Current Audience | Correct? | Severity | |---------|-----------------|----------|----------| | Hero | End-user (brand buyer) | ❌ | CRITICAL | | Operators | Mixed — mostly end-user | ⚠️ | HIGH | | Callout | Ambiguous | ⚠️ | MEDIUM | | Problem | End-user (brand buyer) | ❌ | CRITICAL | | Solution | End-user (brand buyer) | ❌ | CRITICAL | | Deliverables | End-user (brand buyer) | ❌ | HIGH | | Team | End-user (credibility play) | ⚠️ | MEDIUM | | Expertise | Mixed — partially correct | ⚠️ | MEDIUM | | FAQ | End-user (brand buyer) | ❌ | CRITICAL | | Work/Portfolio | End-user (prospect) | ⚠️ | MEDIUM | | Final CTA | End-user + insults Brandwatch | ❌ | CRITICAL | | Nav/Footer | Mostly fine | ✅ | LOW | **5 sections are CRITICALLY wrong-audience. This is not a polish issue — it's a rewrite.** --- ### Updated Overall Grade: **C+** Previous grade (B-) assumed correct audience targeting. With the framing correction, the page is fundamentally addressing the wrong reader. The copy quality is decent but aimed at the wrong person. A Brandwatch VP reading this would think: "This is a pitch to steal our clients, not a partnership proposal." ### Revised Top 3 Priority Changes 1. **Rewrite all copy for Brandwatch leadership audience** — every section flagged above. The value prop shifts from "we activate your Brandwatch data" to "we activate your clients' Brandwatch data, making your platform stickier and more valuable." 2. **Reframe the Problem section** from "are you getting value?" to "your clients' activation gap is your growth opportunity." 3. **Replace the entire FAQ** with partnership-relevant questions about commercial model, scale, client retention impact, and integration. --- *Review complete. The page has strong copy foundations (especially hero and deliverables) but needs structural surgery, social proof, and — most critically — a complete audience reframe from end-user to Brandwatch leadership.*