Pre-Pitch Decisions

DECISION 1 · BRAND GRADIENT

The app ships TWO brand gradients. Document both, or sweep to one?

The docs (DESIGN_STANDARDS.md) declare one official brand gradient: dark midnight purple → black (Variant C). The code ships two: that one (used 45 times) AND a brighter light variant (violet → magenta, used 224 times — including the AppShell wordmark, Explore hero, listing CTAs, FAB). Both look good. The drift is that the standard never blessed the light one.

What dark Variant C looks like (currently in DESIGN_STANDARDS.md)

NABE

Williamsburg · 3:42 PM

Call agent Open to meeting ✨

What the undocumented light variant looks like (currently in 224 places)

NABE

Williamsburg · 3:42 PM

Call agent Open to meeting ✨

Option A · recommended

Document both — light = small surfaces, dark = big frames

Keep both gradients. Update DESIGN_STANDARDS to formally declare: dark Variant C for major frames (drawer heroes, full-bleed banners), light for everything else (wordmarks, CTAs, chips, FABs). What you see in the app today stays as-is.

✅ Matches what's already shipped (224 uses keep working)

✅ Light reads more "modern Nabe", dark reads more "premium drawer"

⚠️ Need 1 hr to write the spec into DESIGN_STANDARDS.md

⚠️ Two gradients to remember when building new things

Option B

Sweep everything to dark Variant C — one gradient, no exceptions

Replace all 224 light-variant uses with the dark Variant C. Visually unifies the app at a much darker tone. Wordmark, FAB, every CTA becomes the midnight-to-black gradient.

✅ True single-source-of-truth design system

✅ Reads as more premium / sophisticated overall

⚠️ 1-3 hr sweep across 224 files

⚠️ App becomes noticeably darker — risk of feeling "heavy"

💡 If you can't decide: Option A. The light variant is already working — formalizing the split is cheaper than a 224-file sweep, and the visual diversity actually serves the app well.

DECISION 2 · COMPASS AGENT NAMES

Are these 3 mock agent names too close to real Compass agents?

The demo ships 3 fictional Compass-branded agents — each appears ~25+ places (profile, properties, conversations, signatures). They're "fictional" but the names are plausibly common. If Reffkin's team pulls the live demo and one of these names happens to match a real Compass agent, that's a credibility moment.

Where these names appear: mockProfile.ts, mockProperties.ts, mockProfessionals.ts, mockConversations.ts, mockProfessionalMessages.ts (with full email signatures + phone numbers), mockRecommendations.ts, mockTransactionHistory.ts, mockVibeQuestions.ts. The names also show up in screenshots in the deck (would need to be re-exported if changed).

EC

Emma Chen

Compass · NYC (Williamsburg / Greenpoint) · Team-1 lead

~80 references across mock data + signature: "Emma Chen | Compass | 917-555-0123"

Keep "Emma Chen"

Lena Park

Mira Donovan

Jenna Russo

Sasha Quinn

MR

Marcus Reyes

Compass · Los Angeles (Eastside / Silver Lake / Echo Park) · Team-5 lead

~25 references · "Reyes-co@nabe.com"

Keep "Marcus Reyes"

Diego Castillo

Tomas Vega

Nico Romero

Ari Soto

SC

Sofía Calderón

Compass · Austin (East Side / Mueller / South Congress) · Team-6 lead

~25 references · "calderon-group@nabe.com"

Keep "Sofía Calderón"

Camila Vargas

Isabela Rios

Lucia Mora

Valentina Cruz

💡 Easiest test: Google "Emma Chen Compass NYC" / "Marcus Reyes Compass LA" / "Sofía Calderón Compass Austin." If any real broker comes up, swap that one. If none → keeping the originals is fine. You must pick a name for all 3 agents (keep or swap) before sending decisions.

DECISION 3 · WC HUB DARK THEME

The World Cup Hub uses a dark "stadium" theme that's not in DESIGN_STANDARDS

The WC Hub V2 destination sheets (hero-city-live, hosted-party, cross-city threads, restaurant specials, etc.) ship in a dark zinc-900 + emerald accent aesthetic — like a sports app. It looks coherent and event-themed, but it bypasses the documented two-layer system (Variant C dark frames + warm pastel content cards). ~45 components are involved.

⚽ LIVE · WBURG VS BUSHWICK

Watching at Devocion

23 neighbors heading to Devocion to watch Argentina vs France. Doors open 12:00, kickoff 12:30. Standing room only after 12:15.

JOIN +1

↑ Current WC Hub V2 style — zinc dark + emerald

⚽ LIVE · WBURG VS BUSHWICK

Watching at Devocion

23 neighbors heading to Devocion to watch Argentina vs France. Doors open 12:00, kickoff 12:30. Standing room only after 12:15.

JOIN +1

↑ What the same surface would look like in Variant C (per DESIGN_STANDARDS)

Option A · recommended

Keep zinc — document as "event surface exemption"

Add a section to DESIGN_STANDARDS: "WC Hub event surfaces use zinc-900 dark frame + emerald accent as a documented exemption — event/stadium context warrants its own visual identity." 30-min fix.

✅ The zinc theme genuinely reads as "live event" — it works

✅ No code touched, no visual regression risk

⚠️ Two design systems in the app (but with a clear "when to use which" rule)

Option B

Sweep zinc → Variant C — one design system everywhere

Replace all ~45 zinc-900 / zinc-800 / emerald uses across wc-hub-v2/*.tsx with Variant C frames + warm content cards. WC Hub loses its event-coded look but matches the rest of the app.

✅ One unified system, no exemptions

⚠️ 2-3 hr sweep across many files

⚠️ Loses the "this is a live event" visual signal

💡 If you can't decide: Option A. The dark stadium look is part of why the WC Hub feels alive in the demo. Document it and move on.

🎯 Pre-Pitch Decisions

The app ships TWO brand gradients. Document both, or sweep to one?

Document both — light = small surfaces, dark = big frames

Sweep everything to dark Variant C — one gradient, no exceptions

Are these 3 mock agent names too close to real Compass agents?

The World Cup Hub uses a dark "stadium" theme that's not in DESIGN_STANDARDS

Keep zinc — document as "event surface exemption"

Sweep zinc → Variant C — one design system everywhere

Your decisions are ready 📋