Brainforge Knowledge

2026-03-30_weekly-kick-off-update

9 min read

Internal (CSO notes)

Sources used

  • Linear: Team Default; issues and projects pulled via Linear MCP (recent updates through 2026-03-30). Projects referenced: GTM and Revenue Metrics Flow (Laura), Customer Reporting & Enablement (Lauren, Deanna), Customer Product Activity Dashboard (Lev, stream 1), Default Product Analytics Implementation; April-dated attribution streams (LinkedIn, Google/Meta) for forward visibility.
  • Transcripts (last 7 days): knowledge/clients/unassigned/transcripts/2026-03-23_default_-_weekly_kick-off_sync_18d35218.md (internal kick-off: CSO ownership, Q2 plan template, collaboration with Demi, urgency on first draft). No additional Default-dedicated transcripts dated 2026-03-24 through 2026-03-30 in knowledge.
  • Prior client-facing draft (continuity): knowledge/clients/default/meeting-notes/2026-03-23_weekly-kick-off-update.md.
  • Slack (Slack MCP, 2026-03-30):
    • #external-client-default (C08GBBWMMU3): Client-visible thread; includes Greg’s 2026-03-23 weekly update; 2026-03-26 PostHog/Omni alignment doc for Nandika; 2026-03-20 ask from Ryan to meet next week on Salesforce vs Omni number differences; earlier GTM/ARR context and links.
    • #external-client-default-data-team (C09TV7R4G4C): Scheduling and data asks; 2026-03-27 Caitlyn ask for customer list (name, ACV, seat #); 2026-03-26 thread on Thomas export new columns (members/submissions) and whether to backfill pre-December; 2026-03-25 Demi request for brainforge@default.com PostHog admin (Caitlyn confirmed); 2026-03-23 Uttam ask for another data dump from Thomas; 2026-03-30 Caitlyn call timing shifted (Uttam travel); Ryan already has Wednesday booked for the SF/Omni topic; CS availability tomorrow 1:30–3pm CST for a call.
    • #client-default (C0955SNPR2Q) — internal only: Do not paste into client Slack. Use for delivery truth: Mustafa 2026-03-25 EOD on Customer Reporting & Enablement dashboard (many tiles done; users logged in / some PostHog-dependent metrics still open; PostHog sync believed incomplete, investigating with Demi); new ~55GB export and Dec 28, 2025–Mar 20, 2026 product export landing in MotherDuck; Demi 2026-03-27 PR for Laura dashboard metrics / merge path; Hyperline integration ~2 weeks behind per Demi (word carefully for client); Greg Q2 Default Notion draft 2026-03-25; scheduling notes (Ryan out affected ARR review timing). Uttam 2026-03-30 questioned whether a message was meant for full Default team (coordination).
  • Supabase Slack tables: Not queried (MCP not configured here); Slack MCP used instead.

Slack-derived highlights (internal quick scan)

WhenWhereTakeaway
2026-03-26ExternalAlignment doc: PostHog charts ↔ planned dashboards (for sync with Nandika).
2026-03-20ExternalRyan: Salesforce numbers ≠ Omni; wants a meeting next week to reconcile.
2026-03-27Data teamCaitlyn: need customer name, ACV, seat count list.
2026-03-25–26Data team + internalNew/expanded product exports; column/backfill questions for Nandika/Caitlyn; PostHog admin for Brainforge ingestion resolved.
2026-03-30Data teamCaitlyn sync moved**; Ryan Wednesday slot kept; CS window Mar 31 1:30–3pm CST.

Recommendations

  • Client update: Lead with observable client-channel facts (alignment doc, SF/Omni session with Ryan, CS scheduling, ACV/seats deliverable, export progress). Keep Hyperline phrasing soft (“billing connector timeline slipped internally”) unless Caitlyn already knows the name.
  • Do not surface client-default drama (Salesforce “largely wrong” thread, “bigger fish”) in client copy.
  • Tiers: Greg’s 2026-03-23 client post said definitions were provided by Caitlyn; if still not in modeling, align language (“implementing per defs you shared” vs “waiting”).
  • Gantt honesty: Internal thread shows EOW dashboarding pressure and some defs still open on the metrics doc; if we’re not green, say so in the client channel.

Gaps

  • Full thread under Ryan’s Salesforce/Omni message not pulled; confirm Wednesday time with Ryan is the reconciliation session.
  • Omni error / Blobby “main” question from 2026-03-12 external channel: check if resolved before claiming smooth self-serve.
  • DEF-497 subtree still needs client-safe dates once modeling confirms data.

Weekly kick-off update — Default

Date: 2026-03-30

Summary

We are finishing the late-March slice on GTM/revenue, customer reporting, and customer product activity, landing a new product data export into the warehouse, and tightening PostHog so your charts line up with the Omni dashboards in our plan (shared an alignment doc with Nandika ahead of sync). Ryan asked to compare Salesforce to Omni; we are locking time this week (including a Wednesday slot on our side) to walk through differences. We still need live read access to product data for some views; exports remain the bridge. Q2 delivery planning is in draft internally for your template-based review.

Timeline / Milestones

  • GTM and Revenue Metrics Flow (Laura): Dashboarding window Mar 25–27; Laura sign-off target Mar 28 (per plan—confirm against actual reviews).
  • Customer Reporting & Enablement: Dashboarding / ETL slice Mar 25–27; Deanna/Lauren sign-off target Mar 28.
  • Customer Product Activity (Lev, stream 1): Modeling Mar 25–27; metric alignment Mar 28–29; dashboarding target Mar 30.
  • April (upcoming): LinkedIn ads attribution Apr 1–10; Google/Meta/Webflow attribution Apr 11–17; customer qualification model Apr 17–24.

Last week’s achievements

Data platform / GTM / CS reporting

  • Customer Reporting & Enablement in Omni advanced: multiple enablement metrics are built or in QA (workflow adoption, meetings, triggers, renewal timing, new admins, user growth, and related cuts); remaining items are mostly PostHog-dependent or need definition confirmation from your team.
  • New product exports you shared (including a Dec 2025–Mar 2026 window) are on path into the warehouse so dashboards and QA are not stuck on stale extracts.
  • GTM / ARR: Modeling and dashboard work continued toward review and sign-off; Meta spend broken out separately is in flight so blended ad spend is easier to read.
  • Scoped automation-impact reporting (meetings booked via Default, workflow throughput, CRM activity) into concrete build steps.

Product analytics

  • Shared an alignment doc that maps PostHog charts to the Omni / implementation plan so we can decide keep vs tweak efficiently on the next working session with Nandika (alignment doc).
  • PostHog access: brainforge@default.com was granted admin for ingestion support (per your team’s confirmation).
  • Executive product analytics work remained in requirements review.
  • Weekly kick-off style update posted to external-client-default with priorities for the week of Mar 23.

Data quality / trust

  • Positive signal on Revenue accuracy in Omni from your side (2026-03-20 data-team thread); we still owe Ryan a working session to reconcile Salesforce vs Omni where they diverge.

This week’s focus

Salesforce vs Omni (Ryan)

  • Hold a working session with Ryan (and others as needed) to line up Salesforce and Omni on the metrics he flagged; Wednesday is already on the calendar on our side—confirm attendees and prep short reconciliation notes ahead of time.

Executive dashboards (Laura / Ryan / Caitlyn / Deanna)

  • Short sign-off walkthroughs on ARR, financial summary, and customer reporting where calendars allow (with Caitlyn observing where helpful). If Ryan was out for an ARR-specific slot, reschedule rather than force a hollow review.
  • ARR / executive Omni UX: Continue the templated layout pass (sections, how to use, definitions) before broader rollout; baseline remains parity with legacy Equals where that is still the reference.
  • Customer list: Produce (or confirm timing for) customer name, ACV, and seat count per Caitlyn’s ask in the data channel.

Customer reporting & enablement

  • Close out remaining tiles on the Customer Reporting & Enablement dashboard: finish PostHog-backed metrics where the sync is complete; confirm “days in implementation before onboarding” with Ryan against Salesforce milestones; validate admin disconnecting an integration with Nandika when the underlying events support it.
  • Investigate PostHog sync completeness with engineering so “logged in” and activity-change style metrics have a reliable feed.

Modeling / transparency

  • Keep the mart inventory (“everything” sheet) current; code stays in GitHub, models in MotherDuck.
  • Continue Salesforce modeling so GTM self-serve sits on clean grains.

Tiers

  • Implement vanilla Tier 1/2/3 using the definitions you already shared in channel; plan for Phoenix when Sid’s definitions land.

Product analytics (PostHog)

  • Run the PostHog / Omni alignment review with Nandika using the shared doc; treat tables engagement as the template for “is this part of the product getting used.”
  • Instrumentation: More merges to main as coverage expands.

Billing / subscriptions (internal dependency)

  • Hyperline (subscription lifecycle) integration is behind internal target; it is not blocking current dashboard QA, but we will reset expectations if anything you need depends on it.

Next-quarter plan

  • First-pass Q2 roadmap from your template: analytics engineering + product analytics + adoption and trust (walkthroughs, reconciliation, how we explain logic). We will share when the draft is ready for reaction.

How we work together

  • Short “what we’re seeing” segments alongside shipping, not only discrepancy QA.
  • Blobby / Omni AI: Keep weekly usage; explore Slack-connected workflows when tokens and MCP permissions allow.

Blockers

Product data / access

  • Live reads in Omni for some product metrics still wait on read replica / read-only export; until then we rely on refreshed exports (including the new dumps you provided).
  • PostHog → warehouse sync may be incomplete for some metrics; we are debugging with engineering before promising those tiles.

Metric definitions

  • Users logged in and some activity-change signals still need a settled source while tooling changes (PostHog vs legacy).
  • New columns on members/submissions in recent exports: confirming with Nandika/Caitlyn whether to backfill pre-December or treat as forward-only.

Sequencing

  • Expanded GTM outbound metrics vs marketing attribution: keep explicit agreement on order so dates stay credible.

Meetings proposed

  • Ryan (+ Caitlyn / others as needed): Salesforce vs Omni reconciliation (Wednesday slot already in motion—confirm time).
  • Nandika (+ Greg): PostHog chart alignment using the shared doc (plus any separate deep dive already on calendar).
  • CS: 2026-03-31 availability 1:30–3:00pm CST (per data-team scheduling thread); finalize invite.
  • Laura / Deanna: Short dashboard sign-off passes as in prior weeks.
  • Victor / Caitlyn (+ Uttam if useful): Supabase read path when engineering is ready.

Action items

OwnerActionDue
BrainforgeSalesforce vs Omni session with Ryan; prep reconciliation notesThis week (Wed target)
BrainforgeCustomer list: name, ACV, seat #Per Caitlyn ask
BrainforgeLand new product exports in warehouse; sync PostHog where neededIn progress
BrainforgeCustomer Reporting dashboard: close PostHog metrics + open definition checksThis week
BrainforgeQ2 plan first draft for internal review, then client-ready versionThis week
BrainforgeMeta spend column in marketing viewsIn progress
Client (Nandika/Caitlyn)Confirm backfill vs forward-only on new export columns (pre-Dec data)ASAP
Client (Caitlyn)Supabase read path with VictorASAP
Client (Thomas)Additional dumps if we still need coverage beyond latest exportsAs needed

Questions or discussion topics

  • Phoenix tiers later: version dashboards when definitions change, or swap once agreed?
  • Omni / Blobby: If self-serve queries against main are still awkward, should we schedule a short enablement touch?
  • Omni MCP / Slack: What is enabled on your plan, and who can issue tokens for a pilot ask-from-Slack flow?

Next sync

  • Standing weekly review; optional segment on what we are seeing in the data and light Blobby usage as adoption grows.

Graph View