Product Admin Dashboard
Executive Summary
Every new product SKU, pricing phase change, and event configuration requires an engineer to manually update Stripe, Salesforce, Sanity, and order-ingestion. Marketing changes things 5 minutes before go-live. A code freeze was attempted a year ago — it lasted 2 weeks.
Without self-service tooling, code freeze is pure policy theater. The Product Admin Dashboard (PAD) is a thin orchestration layer above existing systems — it writes to Salesforce (PricebookEntry), Stripe (Price), Sanity (document), and order-ingestion (config registry). Not a PIM replacement.
Key unlock: BullMQ phase scheduler — marketing schedules price transitions with dates. Scheduler fires at activation time, updates Stripe + Sanity + SF automatically. Zero engineering involvement. PAD “freeze mode” flag transforms policy into a system-enforced guardrail.
What Needs to Happen
3-Phase Build
- Phase 1: Product registry + manual publish (Weeks 1-3) — CRUD UI for products/SKUs with Salesforce + Stripe sync. Retool viable for Phase 1 UI ($50/user/month).
- Phase 2: Pricing phase scheduler via BullMQ (Weeks 4-6) — Marketing sets price change dates, system executes automatically. No more last-minute engineer involvement.
- Phase 3: Order-ingestion config registry (Weeks 7-8) — Product configuration consumed by order pipeline without code deploy.
Why build custom, not buy: Generic PIMs (Akeneo/Pimcore) don’t handle event-date pricing phases, Salesforce PricebookEntry write-back, or Sanity integration.
Claude Code acceleration: Full dashboard app build — CRUD UI, Salesforce/Stripe API integrations, BullMQ scheduler, and config registry. Claude Code can scaffold the entire application. Estimated 8 weeks → 4-5 weeks.
Completion Criteria
- Marketing can create and publish new SKUs without filing an engineering ticket
- Pricing phase transitions execute automatically via BullMQ scheduler
- Salesforce PricebookEntry, Stripe Price, and Sanity document all updated atomically on publish
- Code freeze holds for a full event cycle with PAD freeze mode enabled
- Order-ingestion consumes product configuration from registry (no code deploy for new products)
- 5-10 hours per event cycle of engineering time recovered
- Audit log tracks all product changes with user attribution
Initiative Attributes
Related Risks
| ID | Risk | Severity | Probability | Mitigation |
|---|---|---|---|---|
| RF1 | Nick Jensen disengagement / departure — Nick is owner | CRITICAL | MEDIUM | Lior 1:1 Week 1 post-UPW. Frame S3 + S5 ownership as growth opportunity. Load relief from H4. If Nick leaves, U2, U4, S3, S5 all at risk — he’s bus factor 1 on TonyRobbins.com. |