Brainforge Knowledge

2026-04-03_end-of-week-update

5 min read

Internal (CSO notes)

Sources used

  • Linear: Team Default; list_issues and list_projects with updatedAt last 7 days (verified 2026-04-03). Done this window includes workflow topic fix and event tracking implementation milestone; active work on CS dashboard implementation, Pylon path investigation, Phoenix PostHog organization issues, ARR definitions, and dictionary updates.
  • Transcripts: knowledge/clients/default/transcripts/2026-03-26_default_sync_06f19a22.md, 2026-03-25_prep_for_default_work_review_c0a598e2.md (last 7 days). 2026-04-02 Deanna CS session: not yet in vault; detail from Slack (#external-client-default) and Linear issue context for implementation punch list.
  • Slack: Slack MCP — #external-client-default (C08GBBWMMU3), read 2026-04-03: Deanna session follow-up (Customer Health dashboard link), LMTD field clarification, customer-list CSV for Caitlyn, PostHog “invitation accepted” thread with Nandika, Greg → Caitlyn on Pylon scope vs timeline. Supabase MCP: not available in this workspace; not queried.
  • Continuity: knowledge/clients/default/meeting-notes/2026-03-30_weekly-kick-off-update.md for links and workstream names.

Recommendations

  • Pylon vs Plain: Client channel already has the tradeoff on the record (Greg to Caitlyn Apr 3). The Slack block should stay factual: you’re waiting on product guidance whether to absorb the extra connector/modeling time now or defer Pylon-dependent fields. Avoid sounding like internal “slipped” unless Caitlyn already agreed to the date move.
  • ARR ACV: External channel flag from a stakeholder; Demi said she’d look — fine to mention “under review” without quoting internal expectations.
  • Do not paste #client-default internals (hours pressure, Hyperline name, etc.) into the client block.

Gaps

  • Confirm whether Deanna walkthrough transcript lands in vault; punch list is tracked for CS dashboard Omni updates.
  • Salesforce vs Omni with Ryan: Monday kick-off listed Wednesday on the calendar; no completion note in #external-client-default in this read—treat as in flight unless you know the session happened.
  • Customer list: Demi shared a refreshed CSV in channel 2026-04-01 per Caitlyn; confirm it fully covers name / ACV / seat cut Caitlyn needs for exec readouts.

End-of-week update — Default

Date: 2026-04-03

Summary

We held the Customer Reporting & Enablement walkthrough with Deanna, shipped a model/topic fix so workflow reporting charts behave again, and advanced PostHog / Phoenix planning into concrete dashboard slices. Pylon access and ticketing surfaced in channel; we’re aligned with you that connecting Pylon (alongside Plain where needed) is the direction, and we need a quick product call on timeline tradeoffs vs deferring Pylon-only fields.

Completed this week

Customer success / reporting

  • Deanna review: Completed the scheduled CS dashboard walkthrough; captured requested layout, labeling, and metrics adjustments for implementation (see shared Omni dashboard and requirements links below). Demilade shared the Customer Health Omni dashboard link in channel after the session for easy reference.
  • Workflow reporting: Fixed missing integration fields in the workflow topic so the “variety of workflow types” style views stop erroring when those fields sit outside the original topic boundary.

Data sources / connectors

  • Pylon: Your team invited our account to Pylon and extended admin access for the Brainforge ingestion user; Demi confirmed sign-in. Channel clarified LMTD ticket sourcing and the plan to keep Plain where it still feeds data while adding Pylon, with care on deduping across both.
  • Product analytics: Closed the event tracking implementation milestone on our side so we can keep pushing PostHog coverage without dragging legacy scope.

Product analytics (PostHog / Phoenix)

  • Backlog structure: Split Phoenix PostHog work into activation, retention, engagement, and product journey dashboard tracks with due dates, owned by Advait, aligned to your dashboard organization doc.

GTM / ops

  • Customer list cut: Demilade posted the updated spreadsheet / CSV Caitlyn asked for in channel (Apr 1) so you can refresh exec-facing cuts.

In progress / carry-over

  • Implement Deanna’s CS dashboard change list in Omni (tiles, customer vs internal splits, definitions).
  • QA pass on the customer success dashboard (chart-by-chart review and issue triage).
  • Pylon → warehouse / Omni path: Scoped investigation on whether ticket data lands in Supabase (or agreed source) for CS tiles; Polytomic connection to Pylon discussed in channel.
  • ARR dashboard: Average ACV for March called out as potentially off (~17.6k expected); Demi is investigating.
  • PostHog: Charting invitation acceptance may need instrumentation or a product-sourced feed; Nandika is looking into what exists today.
  • Customer list (name, ACV, seat count): confirm the Apr 1 CSV/spreadsheet covers the cut Caitlyn needs for Monday readouts (or flag gaps in channel).

Blockers

Decisions

  • Pylon scope vs dates: Connecting Pylon with full modeling was not in the original plan as scoped; doing it now adds a few days to some dashboard tracks vs deferring Pylon-dependent fields. Need your call on which branch we take.

Data / definitions

  • Duplicate tickets risk across Plain and Pylon until dedupe rules are agreed.
  • Some CS metrics still depend on confirming the authoritative path from Pylon into the warehouse.

Next week preview

  • Land Deanna review changes in Omni and re-walk any high-stakes tiles with her.
  • Execute Phoenix PostHog dashboard organization (activation slice first where scheduled).
  • Finish ARR ACV investigation and reply in channel with what changed, if anything.
  • If you choose full Pylon now, sequence Polytomic setup and modeling with the CS reporting workstream.

Graph View