Build Mom Wholesale OS in Claude Code

Codified from Gmail draft 19dc11055985f097 · Apr 24 2026

Status update - 2026-05-07

This HOW_TO is superseded for execution.

Use it for historical intent only: it explains the original desire for a Mom wholesale OS. Do not follow the "create a new repo" path unless Sam explicitly reopens that strategy.

Current execution path:

1. Iterate CM_Invoice_System.
2. Use active Sheet CM Invoice System_v2: 1nMTEl_eYpAsQ774Qe0MNEcbib8Qgj2X6_9PfeZk32iI.
3. Use bound Apps Script 106wdSg6lMTsqBaGBtH93j_D0AbSrjUtKuRM2WzdjKE7tq5Vqbe1ZQPAp.
4. Deploy/push the local wide Invoice_Record patch, run setup on v2, then finish the validation plan.
5. Only after the wide invoice save/edit/view/PDF flow works, add dashboard/tasks/Hebrew/new features.

Why this changed: docs/MOM_INVOICE_BUILD_SPEC.md confirmed that CM is Mom's real tool, and the standalone clone was retired to archive/graveyard/2026-04-28_mom-clone-redundant/.

Honest answer first

You have a spec (docs/MOM_WHOLESALE_OS_CONTEXT.md).
The work is 3–4 Claude Code sessions of ~90 min each, spread over 2–3 weeks.
Do NOT try to build it in one session. You will burn out and ship slop.
Final session is in-person with Mom — not at the keyboard.

Pre-session prep (15 min, do once)

1. Open docs/MOM_WHOLESALE_OS_CONTEXT.md — confirm spec is current
2. Identify the 3 core entities (likely products / suppliers / customers)
3. Decide repo location:
   - New repo: gh repo create zee78900/mom-wholesale-os --private
   - Or sub-folder of existing workspace
4. Decide the platform: Google Sheets + Apps Script (you know this stack) OR Notion (Mom may prefer)
5. Write down Mom's actual workflow in 5 bullet points BEFORE designing the system

Session 1 — Scaffold (90 min)

Open Claude Code in working dir. Prompt:

Initialize Mom Wholesale OS per attached spec (MOM_WHOLESALE_OS_CONTEXT.md).
Create repo structure: README.md, CONTEXT.md, SKILL.md, /sheets, /scripts.
Build the base Google Sheet with 3 tabs: Products, Suppliers, Customers.
Each tab gets headers, validation rules, and one example row.
Create the Apps Script connection. Commit and push.

Verify before ending session:
- Repo exists, pushed
- Sheet opens, 3 tabs visible
- Apps Script editor connects to sheet
- One example row in each tab

Session 2 — Core flows (90 min)

Prompt:

Build the order intake form (Google Form → Sheet).
Build inventory tracking — when an order comes in, deduct from product quantity.
Build supplier reorder trigger — when product qty drops below threshold, flag and email me.
Test with 3 sample orders end-to-end.

Done when: Mom can submit a form, you see the order, inventory drops, reorder fires.

Session 3 — Reporting (60 min)

Prompt:

Build weekly summary email automation. Saturday night, send to Mom + Sam:
- Orders this week (count + $ total)
- Products low/out of stock
- Top 5 customers by spend
- Margin by product

Build aging receivables view. Build monthly P&L view.

Session 4 — In-person with Mom (90 min, NOT at keyboard)

1. Walk her through the system
2. Watch her use it (don't help — see what she clicks)
3. Note every friction point
4. Don't fix in real-time — write them down
5. Fix in Session 5 alone

Session 5 — Polish (60 min)

Apply the friction fixes from Session 4. Often: rename buttons, simplify forms, add confirmation messages.

Done state

Mom takes orders without your involvement. You get a Saturday night summary email. Inventory + reorders run themselves. You touch it once a month for review.

Time + cost

• ~6 hours active across 3–4 weeks
• $0 incremental (Google Sheets + Apps Script free; existing Anthropic API)