Brainforge Knowledge

2026-05-04_weekly-kick-off-update

7 min read

Internal (CSO notes)

Sources used

  • Linear: Team Default; snapshots 2026-05-01 and refresh 2026-05-04. Active themes: Client Handoff (trainings, documentation), Customer Reporting & Enablement (post-review iteration; some blocked states), BDR / Biz Dev dashboard feedback, data-modeling handoff with mid-May targets, Omni board organization (internal review). 2026-05-04: large mart-scope batch formalized (unified customer hub, Salesforce core facts/dims, Plain, Gong, product export, Hyperline billing—implementation backlog; client-facing text avoids ticket IDs).
  • Transcripts (last 7 days):
    • knowledge/clients/unassigned/transcripts/2026-05-01_brainforge_x_default_dashboard_sync_b90db462.md (internal Brainforge sync on dashboard flexibility — not client-facing detail).
    • knowledge/clients/unassigned/transcripts/2026-04-30_omni_data_modeling_handoff_sync_e5721b28.md (Default: Nandika, Caitlyn, Greg, Advait — schema clarity, Kimball-style modeling, grain in Omni vs RPT, AI context on topics).
  • Slack (Slack MCP): #external-client-default after 2026-04-24: Greg aligned with Caitlyn on sequencing BDR dashboard fixes vs broader schema granularity work toward May 15; dbt training received positive client feedback; thread for dbt follow-ups; Polytomic / Factors.ai ingestion noted as internal-only activity so far — partner needs to expose more for attribution use cases; Uttam + Greg tag-teaming Omni session.
  • Supabase Slack tables: Not queried here.

Slack-derived highlights (internal)

Takeaway
Client accepted sequencing tradeoff: prioritize coherent schema/modeling path before forcing parallel BDR rework; adjusted near-term BDR completion expectation with rationale in channel.
dbt training landed well; more hands-on practice requested — aligns with operator training track.

Gaps

  • Reconcile monthly reconciliation (April) status with Demi if still open past due date in tracker.
  • Customer Reporting blocked subtree (Deanna-review implementation): confirm whether blocker is data freshness vs Omni wiring before client language claims “blocked only when no forward work.”

Weekly kick-off update — Default

Date: 2026-05-04 (week of)

Summary

We are carrying the data modeling handoff from last week’s Omni session into concrete documentation and modeling work (plain-language schema definitions, fact–dimension structure, and Omni-side grain and AI context) while keeping dashboard delivery honest relative to that foundation. The warehouse mart layer is now broken into explicit build scopes (unified customer logic, core Salesforce facts for GTM/CS, Plain and Gong, product export, Hyperline billing) so implementation can run in parallel without thrashing grains. Operator trainings continue (dbt landed well; Omni workbook and broader training agenda next). Customer reporting and BDR tracks advance where definitions and data allow; we sequenced BDR fixes after schema-oriented work so we do not rebuild charts on shifting grains.

Timeline / milestones

  • Handoff / modeling: Documentation and modeling alignment targeted toward mid-May checkpoints discussed with your team.
  • BDR dashboard: Near-term fix window adjusted in channel so work lines up with schema granularity changes rather than racing in parallel.

Last week’s achievements

Trainings

  • dbt training ran; your team called it out as valuable and asked for more hands-on time — we opened a thread for follow-up questions.

Modeling & trust

  • Omni data modeling handoff session with Nandika and Caitlyn: aligned on clearer schema documentation, Kimball-style facts and dimensions (vs leaning on pre-aggregated reporting tables alone), keeping base tables at the right grain and expressing time windows in Omni measures/topics, and strengthening AI context on critical topics for Blobby.
  • Net new ARR discrepancy on the ARR dashboard was diagnosed and documented with an explanation tile.
  • main schema deprecation and related cleanup completed so Omni exposes fewer confusing paths.

Handoff preparation

  • Handoff roadmap and data architecture diagram deliverables are in done state for the prep track.
  • Omni training agenda draft completed for the training milestone.

Product analytics / Phoenix

  • User Retention PostHog organization work moved to internal review on our side.

Omni hygiene

  • Omni dashboards and folders cleanup remains in internal review before we treat it as client-ready for sign-off.

This week’s focus

Data modeling & documentation

  • Turn the handoff discussion into client-readable schema documentation (what each table is for, how team / customer / account language lines up, what’s in each mart).
  • Execute against the scoped mart backlog (customer hub, CRM core, CS/support surfaces, product export, billing) in step with documentation—not ahead of agreed grains.
  • Align dbt toward consistent fact and dimension patterns and conformed account/customer logic where duplicates confuse NLQ.
  • Fill AI context on priority topics and sanity-check fact–dimension relationships (including manual validation where automation is thin).

Customer Reporting & Enablement

  • Continue remaining dashboard metrics and topic updates where source data and definitions are clear; keep freshness vs wiring split honest in updates when product Postgres timing is the limiter.

BDR / Biz Dev dashboard

  • Finish definition and labeling follow-through (including Salesforce field references on views where missing); respect the sequencing we confirmed in channel so fixes land on stable grains.

Trainings

  • Advance operator trainings (Omni and PostHog alongside dbt): workbook cleanup and hands-on agenda tied to how metrics connect to dashboards.

Omni organization

  • Complete internal review on folder/dashboard organization so naming matches how your teams navigate.

GTM / integrations

  • Factors.ai: connector data is still limited to internal-use signals for attribution asks — we can help draft outreach if you want Factors to expose more.

Blocked

  • Items explicitly waiting on partner or engineering data (e.g., richer Factors payload; some PostHog / Phoenix slices) stay in blocked until the upstream surface area is there — we will say so plainly when it affects a date.

Next week

  • Tighten Customer Reporting punch list against the latest Omni build once modeling/doc tasks move from “structure agreed” to “implemented in layer.”
  • Continue monthly reconciliation rhythm for April if not yet closed on your side.

Slack-formatted block (copy below)

Happy Monday, team!

We're carrying last week's Omni modeling work into documentation and dbt on a mid-May cadence. We also scoped the mart layer into concrete builds this week—unified customer logic, core Salesforce facts for GTM and CS, Plain and Gong, product export, and Hyperline billing—so engineering can execute in parallel without thrashing grains. dbt training landed well; we're layering Omni and PostHog into the operator track next. Dashboard fixes stay sequenced behind stable schema work, matching what we aligned in channel.

*Priorities*

- Ship readable schema documentation and align fact–dimension patterns with how you talk about customers, accounts, and teams.
- Run the scoped mart builds alongside Customer Reporting and BDR follow-through where definitions and data are ready; keep BDR fixes behind the granularity work, not ahead of it.
- Advance operator trainings (Omni workbook and hands-on next to dbt) and finish internal review on Omni folder layout before we call navigation done.

*Wins last week*

- dbt training—your team asked for more hands-on time; we’re here for that.
- Omni modeling handoff with clear direction on grains, measures vs locked-in RPT tables, and AI context on key topics.
- Net new ARR discrepancy diagnosed with documentation on the ARR dashboard; deprecated the confusing `main` schema path in Omni.
- Handoff roadmap and data architecture diagram delivered; Omni training agenda drafted for the training milestone.
- User Retention PostHog work in internal review; Omni board organization moving through internal review.

*In progress*

- Remaining Customer Reporting metrics and topic wiring; BDR definition and view cleanup including Salesforce field references where missing.
- Operator training track (Greg): dbt complete for this slice; Omni training agenda and workbook cleanup next.
- Omni dashboard and folder organization (internal review).

*Blocked*

- Some Phoenix PostHog slices and partner-fed attribution stay blocked until upstream data or partner scope expands—we’ll keep dates honest when that’s the gating factor.

*Next week*

- Close more of the Customer Reporting punch list as modeled fields land.
- Finish April monthly reconciliation if still open.

*References*

- PostHog ↔ Omni alignment doc: https://docs.google.com/document/d/1NQDOKLEkYK3gyLePL3W8GNbdt4DkJfrLrRtnhbwf1d4/edit?usp=sharing
- Customer Reporting & Enablement (Omni): https://default.omniapp.co/dashboards/0b199b8b
- GTM (Omni): https://default.omniapp.co/dashboards/2a84f70d
- Customer Health (Omni): https://default.omniapp.co/dashboards/5c429c97

Graph View