Brainforge Knowledge

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

5 min read

LMNT — Weekly Kick-Off Update

Date: 2026-03-30
Prepared for: LMNT team

Internal (CSO notes)

Sources used

  • Linear: Team LMNT (list_issues by updatedAt, list_projects without milestones; milestone query hit complexity limit).
  • Transcripts (last 7 days): knowledge/clients/unassigned/transcripts/2026-03-23_lmnt_weekly_kick-off_sync_ed415447.md (internal delivery sync; not for client copy).
  • Slack: Slack MCP slack_search_public_and_private — #client-lmnt, #external-polytomic-lmnt (after 2026-03-23). Supabase MCP not available in this environment; no Supabase pull.
  • Links (from prior vault updates / Slack): Data Platform Documentation / changelog; HubSpot deal notifications appeared in search — do not surface contract status or “Phil’s inbox” in client-facing text.

Recommendations

  • Include: Retail vs POS definition clarification (already in channel); Revenue→Sales naming alignment in Omni/dbt; Polytomic Amazon progress and honest backfill status; wholesale partner status metric completion; Omni pilot threads (retail topic in progress, wholesale topic, next validation steps).
  • Consider trimming: If the client prefers shorter updates, collapse Omni bullets into two lines (topics vs. dashboards/Blobby).
  • Optional ask: GitHub access or alternate artifact for Omni context (Advait’s thread to Amber) — frame as unblocking documentation/context, not as blame.

Gaps / CSO to fill

  • Internal sync 2026-03-23: Delivery leadership wants clearer Omni timeline, stakeholder session scheduling, and “what unlocks when” — handle internally; do not paste Uttam/Greg capacity or “at risk” language into Slack.
  • No new LMNT-assigned vault transcripts dated 2026-03-24 through 2026-03-30; narrative leans on Linear + Slack.
  • Milestone-level dates: Omnichannel Revenue Data Mart and related tracks show Phase 2 official kickoff 2026-04-13 in Linear project copy; confirm before treating as client-committed if needed.

Summary

Last week we tightened retail vs. POS definitions in your channel, shipped wholesale partner status metric refinements, and aligned Revenue → Sales naming across wholesale (and retail where it applied) in Omni. Polytomic shared a concrete Amazon sync status. This week we’re pushing the Omni pilot (retail topic, wholesale topic follow-through, validation of the Walmart POS + OMS join for pilot questions) and continuing ingestion and ecommerce modeling work.

Timeline / Milestones

  • Omni pilot — Topics and draft dashboards: Pilot workstream active; GA-style target in Linear remains ~late April (see Omni Pilot project dates in our board).
  • Omnichannel Revenue Data Mart (Phase 2): Linear shows start ~2026-04-13 with a June target for the mart; QA track runs on a parallel timeline into the fall — treat as planning unless you’ve explicitly signed off these dates.

Last week’s achievements

Retail / definitions

  • Clarified “retail sale” (LMNT → retailer, e.g. Target) vs “POS sale” (retailer → end customer) in #client-lmnt so metrics and Omni copy stay consistent.
  • Retail topic: “Create Topic for Retail” is in progress on the Omni pilot project; supporting work includes a Retail Velocity & Sell-through style topic where grain differs from core retail sales facts (per Slack summary from Advait).

Wholesale / Omni / dbt

  • Done: Redefine partner status metric and thresholds (Wholesale Data Mart project).
  • In flight: Align Wholesale and Retail models to use Sales instead of “revenue” where needed; Amber merged a PR for wholesale Omni views; Advait updated impacted retail topic labels in Omni.

Ingestion / connectors

  • Walmart.com 3P (P0): Inventory ingestion work in progress (Ingest and Backfill).
  • Polytomic / Amazon (external channel): Orders table syncing for 2026 with forward updates; Order Items backfill still running (long-running historical sync — they gave explicit timing expectations in #external-polytomic-lmnt).

Ecommerce / supply chain

  • Ware2Go: Ingest/model work in progress toward the Ecommerce Data Mart.
  • Amazon (post-ingestion): Modeling ticket in progress pending data completeness.

Documentation

This week’s focus

Omni BI (pilot)

  • Continue Retail topic build; advance Wholesale topic and Blobby training for retail/wholesale dashboards.
  • Validate Walmart POS + OMS join for pilot business questions (ticket in progress).
  • Progress pilot dashboard design spec (retail + wholesale layouts) and universal Omni rules running list.
  • Finish Sales vs. revenue naming pass in models/Omni where still open (wholesale + retail).

Ingestion / ecommerce

  • Monitor Amazon Order Items backfill with Polytomic; proceed Amazon Seller Central modeling as data supports it.
  • Continue Walmart 3P inventory connector work.
  • Continue Ware2Go path for ecommerce mart (parallel Stord milestone remains on the roadmap).

Governance / documentation

  • Resolve GitHub PR access for Omni context (Advait asked for an alternate if repo access isn’t available — coordinate with Amber).

Meetings Proposed

  • Omni / pilot alignment — Greg, Amber, Advait (+ Shivani as needed): confirm stakeholder demo cadence and what’s unlocked each week for the pilot (if not already scheduled).
  • Polytomic / Amazon — optional async readout if you want LMNT finance or ecommerce leads briefed on backfill timing.

Blockers

Connectors / data

  • Amazon: Historical Order Items sync is slow; Orders for current year are updating. We’re tracking with Polytomic and will keep you posted.

Access

  • GitHub: If LMNT prefers not to expand access, a redacted export or shared spec for the relevant PRs unblocks Omni documentation work.

Action items

OwnerActionDue
BrainforgeContinue Omni pilot execution (retail topic, validation, Blobby, dashboard spec)This week
BrainforgeTrack Polytomic Amazon backfill and Walmart 3P ingestionOngoing
LMNT / BrainforgeUnblock Omni context sharing (GitHub access or alternate artifact)As soon as practical
LMNTConfirm any calendar constraints for April Phase 2 / omnichannel mart kickoff if you want executive visibilityAs able

Questions or discussion topics

  • For the pilot dashboards, do you want the first stakeholder-ready slice to emphasize wholesale, retail, or a split view?
  • Any preference on FAQ-style documentation (separate tab for metric nuances) vs. inline field descriptions in Omni?

Graph View