Brainforge Knowledge

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

5 min read

End of week update — LMNT (Omni pilot) — 2026-04-03

Internal (CSO notes)

Sources used

  • Linear: LMNT team (issues updated last ~10 days; emphasis on Omni Pilot project and in-flight work).
  • Transcripts (last 7 days): knowledge/clients/unassigned/transcripts/2026-04-03_lmnt_omni_progress_sync_5e9b1904.md, 2026-03-27_check_on_lmnt_progress_846d052f.md (retail metrics / Omni handoff with Amber + Advait).
  • Slack: Supabase MCP not available in this workspace — used Slack MCP fallback: #client-lmnt (C09UF1ZS7V4), #lmnt-omni-feedback (C0ANS4WNE9K), recent messages.
  • Links: Google Slides deck Greg mentioned to Uttam (internal leadership deck — use only if you share externally): https://docs.google.com/presentation/d/1KrR9wtWLenJnXK7m_gKIls0a7WRDOM98VHXshOZbGQA/edit

Recommendations

  • This draft is Omni-weighted (topics, Salty/Blobby, pilot dashboards, feedback loop). If Shivani expects a full Option B data-platform summary, add a short bullet under Reporting/Data mart or point her to the separate deck.
  • Merge / branch state: Transcript and Slack refer to lmnt-topics-v3 and renames (e.g. retail_gross_pos_sales). Confirm whether v3 is merged to main before sending; if not, soften language to “in final review” vs “shipped.”
  • Monday Shivani sync: Greg has a solo progress touchpoint Monday — good moment to align on March POS gaps and retail dashboard spec without putting placeholder “next sync” text in the client Slack block (add real time if you include Next sync).

Gaps / CSO may want to add

  • Exact ETA for March Target (and any other) POS days once Avesh/engineering confirms the fix path.
  • Whether you want to name Andy / Jason nudge explicitly (Greg mentioned getting them into Omni to kick the tires) — included lightly below; expand if you want a direct ask.
  • Any client-safe link to the retail/wholesale pilot dashboard spec once finalized (not yet locked per 4/3 internal sync).

Summary

This week we pushed Omni pilot work forward: sales vs. revenue naming is reflected in the semantic model and topics, daily grain is in place for the marts that feed Omni, and we stood up a dedicated retail velocity / sell-through topic (in branch review) with tighter Salty (Blobby) context so POS vs retail sales questions route more cleanly. We also traced the March POS “missing days” issue you raised: upstream data looks present; we’re working through why some dates don’t land in the retail sales mart Omni reads, and we posted a short status in your Omni feedback channel so you’re not waiting in the dark.

Timeline / milestones (Omni pilot)

  • Omni Pilot — Topics and Draft Dashboards milestone “Omni pilot live (wholesale + retail)” target 2026-04-10 (per Linear project; pilot close-out 2026-04-27). Treat as directional; dashboard build is gated on finalized pilot spec (see In progress).

Completed this week

Omni model & topics

  • Revenue → Sales naming: Wholesale and retail model/topic naming aligned to Sales where that’s the correct meaning (Linear work completed; Advait updated retail topics; Amber handled wholesale topic patches and metrics sheet updates).
  • Daily grain: Marts moved to daily grain instead of weekly/monthly-only rollups where required for Omni topics and charts, so time selection in Omni matches how you ask questions.
  • Retail velocity & sell-through topic: New topic (separate from “Retail Sales / Inventory Performance” because of different fact grain) covering velocity, weeks/days of stock, and sell-through; AI context refined so Salty distinguishes POS sales, retail sales, and revenue; sample questions validated in branch testing with Amber and in Slack.
  • Salty / Blobby feedback loop: Addressed Shivani’s examples (Walmart vs Target mix-ups, commentary) with clearer topic routing and context; continued iteration on crisp retail marts so assistant answers match backend definitions.

Client communication

  • Friday note in #lmnt-omni-feedback: Summary back on March POS investigation and POS/Salty consistency work so feedback doesn’t sit unanswered.

Data / engineering (affects what Omni shows)

  • March POS gaps: Opened dedicated investigation; Advait documented Target date-level gaps in retail_fct_sales vs raw layer, looped in data engineering, and shared SQL-backed notes in the client channel for transparency.

In progress / carry-over

  • March POS completeness: Confirm root cause in intermediate modeling steps and restore missing business dates into the mart Omni uses; communicate fix timeline to Shivani when engineering confirms.
  • Retail pilot dashboards: Build is waiting on a finalized pilot dashboard spec (Greg aligning to resolve open questions from the shared spec doc); Advait is ready to implement once that’s locked.
  • Velocity topic: Final small edits after Amber’s review (e.g. negative weeks of stock handling — whether to exclude guardrailed rows pending LMNT/analytics confirmation).
  • Wholesale topic / mart validation: Walmart POS + OMS join validation and wholesale mart tags/partner grain still on Awaish’s side for pilot-quality answers (not “done” this week).

Blockers

Data / marts

  • Some March dates missing in Target (and related) POS paths in the mart that powers Omni; fix depends on dbt/Snowflake pipeline clarification — not an Omni UI issue.

Specs

  • Retail (and wholesale) dashboard layouts need a single agreed spec so build doesn’t churn on source/metric ambiguity.

Next week preview

  • Close the loop on March POS with a clear cause and remediation date.
  • Merge retail velocity/sell-through topic to main once sign-off is done; keep Salty testing on merged model.
  • Deliver pilot retail dashboard slice once the spec is finalized; continue wholesale topic/mart hardening for leadership-ready views.
  • Monday internal alignment with Shivani on pilot progress (per current plan).

Questions or discussion topics

  • Confirm preference on negative weeks of stock in Omni (exclude anomalies vs show with footnote).
  • When you’re ready, Andy and Jason jumping into Omni to stress-test Salty and dashboards would help before broader rollout.

Next sync

  • (Add date/time here if sharing this section with the client — e.g. Greg ↔ Shivani Monday touchpoint if you want that visible.)

References

  • Omni feedback channel: #lmnt-omni-feedback (Brainforge + LMNT).
  • Leadership deck refresh (internal; optional to share): Google Slides link in Sources used above.

Graph View