LMNT Renewal: Week-by-Week Inputs/Outputs Table — Plan of Attack
Date: 2026-03-10
Context: Shivani/Phil ask (vs Gantt + memos): at ~$90k/month, a simple week-by-week table showing what we ingest, model, dashboard — i.e. inputs and outputs — so Phil can “clearly see progress being made weekly worth the price point.”
Owner: Uttam (spreadsheet deliverable)
1. What Phil Actually Wants
| He said | Meaning |
|---|---|
| ”One level deeper than the Gantt” | Not high-level phases; concrete weekly progress. |
| ”Inputs and outputs” | Inputs: what we ingest, what we model, what we use as source. Outputs: dashboards (can be vague, e.g. “one dashboard for retail VP”), data marts, business outcomes/unlocks. |
| ”Worth the price point” | Each week should show tangible in/out so it’s obvious value is being delivered. |
| Shivani: “Output = Amazon and Shopify sales data aligned and finance ready” | Frame outputs as business outcomes, not just “dbt model X." |
| "Gantt high level, memos verbose” | This artifact = middle ground: scannable, specific, weekly. |
Deliverable: A spreadsheet (or table) with weeks as rows and columns for inputs and outputs, plus optional: work stream, owner/person (which new hire affects what).
2. Table Structure (Recommended)
Keep it to one sheet; Phil can scan top-to-bottom.
| Column | Purpose | Example |
|---|---|---|
| Week (start date) | Week of | 2026-03-10 |
| Work stream | Data Foundation / Commercial Performance / Supply Chain / BI & Self-Service | Commercial Performance |
| Inputs | What we ingest, connect, or model this week | Shopify orders incremental sync; Amazon settlements table modeled |
| Outputs | What becomes available or ships this week — marts, dashboards, unlocks | Amazon + Shopify sales aligned in unified orders mart; finance-ready export for month-end |
| Business outcome (unlock) | One line in plain English | ”E‑commerce sales (DTC + Amazon) reconciled and ready for close” |
| Primary person (optional) | Which role drives this (maps to “new folks”) | AE / Analyst / DE |
Optional second sheet or appendix: Same table with a “Person” column that maps to actual names (or “New AE”, “New Analyst”) so Phil sees who affects what type of work.
3. Outputs = Business Outcomes (How to Word Them)
Phil and Shivani want outcomes, not jargon. Use these as templates; fill in channel/domain.
- Data / marts: “Amazon and Shopify sales data aligned and finance ready”
- Marketing: “Marketing efficiency for e‑commerce only (MER, CAC by channel)”
- Channel: “Customer/order marts for [channel] — wholesale 360”
- Dashboards: “One dashboard for retail VP” / “Wholesale partner performance dashboard”
- Visibility: “Cross-channel revenue trend (weekly + monthly)”
- Governance: “Revenue reconciliation report (LMNT vs Shopify vs finance)”
- BI: “Omni pilot live for wholesale + retail exploration”
Pull phrasing from:
- Strategic Planning Framework — “What our output will be” and “What we want to accomplish” columns.
- Data Sources CSV — Connector status (Shivani already showed this to Phil; reference it).
- Omnichannel Revenue Plan — Deliverables 7–9 (unified transactions, Wholesale 360, NetSuite readiness).
- Ramp-up memo — Omni pilot scope and “Dashboard live” style milestones.
4. Inputs (What to Put in the “Input” Column)
Be specific enough to show progress, not a full technical spec.
- Ingest: “Shopify orders (initial backfill)” / “Emerson POS daily sync” / “Polytomic connector for Amazon settlements”
- Model: “Staging for Shopify refunds” / “Unified order date logic (order/ship/rev-rec)” / “Wholesale account canon model”
- Dependencies: “Definitions Council sign-off on net revenue” / “Jason: Snowflake role for Omni”
Data sources to drive inputs:
- Data Sources CSV — Which sources are Active, Integration Access (Granted/Waiting), Priority.
- Instagantt / Gantt — Explore → Define → Ingest → Deliver value; translate phases into weekly chunks.
- Renewal transcript — Feb–July sequencing (retail clean tables, BI, then supply); use to order weeks.
5. Assumptions to Call Out (So Phil Knows It’s Not Random)
Add a short Assumptions section (above or beside the table, or on a second tab). Suggested bullets:
- Dashboard scope: Exact dashboard specs (e.g. “retail VP”) will be refined with stakeholders; we’re planning for one dashboard per major persona/use case (e.g. retail VP, wholesale, finance) based on our experience with similar engagements.
- Definitions and access: Weekly progress assumes Definitions Council sign-off and timely access (credentials, API, Polytomic/LMNT approvals); delays will shift later weeks.
- Shopify/Amazon alignment: “Finance ready” assumes we align to LMNT’s chosen order-date taxonomy and refund logic; any change to definitions may add 1–2 weeks.
- Marketing/MER: Marketing efficiency (e.g. MER, CAC) depends on marketing cost ingestion (Meta, Google, etc.) and channel mapping; we’re sequencing that after core sales data is stable.
- Supply chain: Supply chain visibility work is scoped to start after commercial performance milestones (or in parallel if they choose a higher-touch option).
These match what you said: “Will list out assumptions that are based on our experience.”
6. Mapping “Which Person Affects What”
You said you’d make clear which new person affects what type of work. Options:
Option A — Column on main table:
Add Primary role (e.g. DE / AE / Analyst). Then a one-time key: “New AE = [name when known]; New Analyst = [name when known].”
Option B — Separate small table:
| Role | Type of work they unblock |
|---|---|
| DE | New connectors, new staging/models, backfills |
| AE | Marts, metrics, reconciliation logic, dbt releases |
| Analyst | Dashboards, reports, QA, stakeholder-facing outputs |
Then in the week-by-week table, you can tag rows with DE/AE/Analyst so Phil sees “this week is analyst-heavy” or “this week we need the new AE.”
Use the renewal transcript staffing (half DE, 1 AE, 2 analysts, plus strategists) and Option 2/3 pacing (extra analyst → faster; extra AE → even faster + supply in parallel) to decide which weeks get which role.
7. Where to Pull Data From (Repo / Vault)
| Need | Source |
|---|---|
| Data sources + connector status | knowledge/clients/lmnt/resources/data_platform_documentation/Brainforge x LMNT - Data Platform Documentation - Data Sources.csv |
| Work streams, outcomes, outputs | knowledge/clients/teamlmnt/resources/LMNT_Strategic_Planning_Framework.md (Commercial, Data Trust, BI, Strategic Analysis tables) |
| High-level sequencing (Feb–July) | knowledge/clients/unassigned/transcripts/2026-02-23_lmnt_renewal_documentation_b8e3e6ef.md (option 1 = 3 work streams to July; option 2 = + supply in July; option 3 = compress to May) |
| Channel-by-channel deliverables | knowledge/clients/lmnt/resources/Brainforge LMNT Omnichannel Revenue Plan.md |
| Omni / BI milestones | knowledge/clients/lmnt/resources/lmnt-omni-accelerator-ramp-up-memo.md |
| Instagantt / Gantt detail | Referenced in Omnichannel Plan; if you have a spreadsheet or export, use it to break phases into weeks. |
8. Suggested Build Order
- Define time window — e.g. next 12–16 weeks (align to renewal term and Feb–July from renewal doc).
- List major milestones from Gantt/Instagantt + renewal (retail clean tables, BI pilot, wholesale 360, etc.).
- Assign weeks to each milestone (roughly); then break each milestone into 1–3 weeks of inputs/outputs.
- Fill Inputs from Data Sources + ingestion roadmap (what’s connected, what’s modeled when).
- Fill Outputs using outcome-style phrasing (finance ready, dashboard for X, MER for e‑commerce).
- Add Business outcome column with one line per week (or per multi-week block).
- Add Primary role (and optionally Person) so “which new person affects what” is clear.
- Draft Assumptions (section or tab) from §5 above; tighten to 4–6 bullets.
- Share with Shivani for a quick pass (she can plug in Phil’s wording for “retail VP” etc.).
9. Price Point Note
Slack said “~20K/40K per month, keep the table scope-based (what gets done each week) and let pricing live in the SOW/options doc; the table just shows “what you get when.”
10. One-Liner for Shivani/Phil
“We’re adding a week-by-week table: each row is a week, with columns for what we’re ingesting/modeling (inputs) and what’s shipping—dashboards, marts, and business unlocks (outputs). So you can see progress every week. We’ll call out assumptions and which role drives which type of work. Dashboards will be described at a level like ‘one dashboard for retail VP’ until we lock specifics with you.”
You can paste that into Slack or the doc as the short description of the deliverable.