🎧 Hyro CS Dashboard v2 — Wireframe Concepts

Three design directions for the rebuild. Static wireframes, click to open full-page.

Audit of the current dashboard
📏 6,046px tall, no nav. Everything is on one infinite scroll. Cohort retention sits below widget intent which sits below open tickets. No way to deep-link or jump.
🎨 Dark teal "ops console" theme. Lots of borders + emojis + ALL CAPS labels. Looks busy, hard to find the one number you care about.
📊 7 top-line metrics, no comparison. "63 needs attention" — vs what? No deltas, no sparklines, no "is this normal?".
📋 3 mixed data tables. Open tickets, theme breakdown, cohort retention all formatted differently. No filtering, no sort, no search.
🤷 No information hierarchy. A 6-minute-old ticket from Veronica@ckwc.com.au sits next to a 45-day-old ticket from Ciarra Cusens. Both equal weight.
📦 Mixed audiences in one view. Today's queue (operational), this week's CSAT (tactical), 17-month cohort retention (strategic). Linear's research: keep these separate.

Four design directions

Concept D matches the Growth Command dashboard style you sent. A, B, C are earlier explorations.

D · Growth-style ⭐
Matches hyro-growth-dashboard.pages.dev
Same design system as Growth Command. Bricolage Grotesque + IBM Plex Mono, near-black, 00/01/02 sections, AU/US/Consolidated toggle.
Audience: Founder + CS team Tone: Hyro Command system Best for: Family with Growth dashboard
Pros: Visually identical to Growth Command. CSAT replaces ROAS as North Star. Triage + escalations are first section. Sales chat widget gets dedicated panel. Cohort + LTV in Section 04.
Cons: Single page (no sidebar nav). May want to split Triage into its own route at build time.
Open full-page →
A · Operator
Linear-style · dense · glanceable
For Lisa + Nicola, every 30 minutes. Built for fast scanning.
Audience: CS team daily Tone: Workspace tool Best for: "What needs action right now?"
Pros: Sticky header always shows queue health. Triage column is the hero. Cohort/strategy moved to a secondary tab.
Cons: Less "wow" for execs glancing in. Needs you to know what columns mean.
Open full-page →
B · Editorial
Stripe/Notion-style · clean · light
For Steve, daily/weekly. Built for understanding, not action.
Audience: Founder + leadership Tone: Executive summary Best for: "How are we doing?"
Pros: Every metric has context (delta + sparkline). Cohort + LTV gets pride of place. Reads like a Stripe Atlas report.
Cons: Less useful for active CS triage. Slower to scan for "what's broken right now".
Open full-page →
C · Mission Control
Datadog/Vercel-style · dark · live
For wall-mount or always-on. Built for ambient awareness.
Audience: Whole team, passive Tone: Live ops Best for: "Glance from across the room"
Pros: Big-number-first. Status indicators (green/amber/red) at a glance. Auto-rotates between panes if needed. Looks great on a TV.
Cons: Less detail-dense. Decorative more than analytical. Cohort/theme tables get squished.
Open full-page →
My recommendation: Concept D — matches the Growth Command system so the whole Hyro Command suite feels cohesive. A/B/C left in for reference. Let me know if D is the right direction and I'll build it for real on hyro-cs-dashboard.pages.dev.

What I'd add to v2 regardless of style: