Brainforge Knowledge

2026-04-02_cs_dashboard_439daa8e

3 min read

CS Dashboard

Date: April 2, 2026 Source: Granola Meeting ID: 439daa8e-17ea-4453-8165-c1ff1c657f0b URL: https://notes.granola.ai/t/439daa8e-17ea-4453-8165-c1ff1c657f0b

Participants:

Dashboard Status & Data Blockers

  • Dashboard built in Omni; currently on static exports — not live data
    • Blocked on Supabase production DB access (Victor hasn’t prioritized)
    • Once connected, data would refresh every 12–24 hours
  • Deanna had been prepped on an older version of the dashboard — newer version shown on the call
  • Pylon (tickets data) may not flow through Supabase — needs engineering clarification on pipeline

Feedback & Scope Decisions

  • Dashboard split into two: customer-facing (top half) and internal (bottom half)
    • Customer-facing: meetings booked, users added, meeting duration over time, integrations, workflows
    • Internal only: CSM-level views, days to renewal, month-over-month growth by team (Lara’s charts)
  • “Users” labeling needs clarification throughout — distinguish customers vs. CSMs
  • Add “meetings booked per user” metric — customers frequently request this; tells the adoption/expansion story
  • Add new users (non-admin) — Deanna flagged distinction between admins and regular sales reps matters for expansion tracking
  • Workflow data should show active workflows only, not total created
  • Accounts without assigned CSMs = community customers (intentional) — expected to receive automated monthly reports
    • Suggest filtering by “CSM is blank” to identify community accounts
  • Customer-facing dashboard goal: shareable or clip-able for decks; auto-send on the 1st of each month with prior month’s data
  • Add user breakdown per account at the end of customer-facing view: users in account, pending invites, meetings booked, power users
  • Value story today = meetings booked (no CRM integration yet to tie to revenue)
    • Future state: connect to CRM opportunity/closed data to show ACV generated via Default

Next Steps

  • Deanna Garcia

    • Push Victor to grant Supabase production DB access (tied to her end-of-month project sprint)
    • Sync with Nandika on internal items discussed
    • Explore the current dashboard and share any additional feedback with Greg or the team
    • Check with engineering on whether Pylon ticket data flows into Supabase

  • Greg / Brainforge team

    • Clarify “users” labeling in all charts (customers vs. CSMs)
    • Document metric definitions (what each metric measures) to be included at top of dashboard
    • Archive the old/duplicate dashboard
    • Confirm whether active workflow filter exists in the data and apply it
    • Send Deanna the updated dashboard link
    • Investigate Pylon → Supabase pipeline with engineering
    • Align with Lara on CSM activity / ARR reporting work already in progress

Verbatim transcript

(Full verbatim transcript: use Granola URL above or Granola MCP get_meeting_transcript for meeting 439daa8e-17ea-4453-8165-c1ff1c657f0b — omitted here for file size.)

Tickets Created

Generated by post-call-to-tickets on 2026-04-02

  • DEF-518 — Implement CS Reporting Omni dashboard updates from Deanna review (2026-04-02) — Owner: Demilade Agboola — ToDo in Cycle (current)
  • DEF-519 — Investigate whether Pylon ticket data lands in Supabase for CS dashboard — Owner: Demilade Agboola — ToDo in Cycle (current)

Parent / epic: DEF-253 — Dashboarding: Customer Reporting and Enablement

Updated with comments: DEF-514 (walkthrough complete note)

Not ticketed (client-owned): Deanna to push Victor on Supabase production access; Deanna/Nandika sync on internal items; Deanna to confirm Pylon pipeline with Default engineering (parallel to DEF-519).

Graph View