# Deck 02 · PPSS — Seed brief

**Status:** Draft (not yet built)
**Saved:** 2026-06-28 by Jeff (verbal)
**Owner:** Plex / OMX Strategy

---

## One-line thesis

**PPSS** — the OMX-owned Promotion Planning, Sales Activity, and Customer/Supplier Rebate Management platform.
**Replaces ~$350k/yr of SaaS** (Enable + Anaplan-demand-only) with Snowflake-native tooling.

## Cost reclaim (the headline)

| Today | Cost / yr | Status |
|---|---|---|
| **Enable** — B2B rebate management SaaS | **$120k** | Replace fully |
| **Anaplan** — used only for demand planning, plus storage | **$200k + $30k storage** = **$230k** | Replace with Snowflake-native |
| **Total annual reclaim** | **~$350k** | |

## Why now

- New Snowflake tooling makes the "build" much cheaper than 12 months ago
- We're already paying for Snowflake — incremental storage + compute is marginal
- OMX has the data (sales, customer agreements, supplier contracts) in Snowflake already
- Enable is an industry SaaS — fine for a generic SMB, expensive for our specific shape

## What PPSS covers

1. **Promotion Planning** — automated lift forecasting, calendar, ROI
2. **Sales Activity automation** — rep workflows, target setting, pipeline mechanics
3. **Customer rebate management** — contract terms, accruals, payouts (replaces Enable customer-side)
4. **Supplier rebate management** — claim management, reconciliation (replaces Enable supplier-side)
5. **Demand planning** — what Anaplan does today (replaces Anaplan demand-only use case)

## Reference (competitor we're replacing)

- Enable — https://www.enable.com/rebate-management/
- B2B rebate management software · ~$120k/yr OMX spend

## Data + info to work through tomorrow

### Problem framing (what's broken)

- **Fragmented stack:** Enable handles rebates; Anaplan handles demand; Sales activity is in SF/Excel; Promo planning is its own spreadsheet world — no closed loop between them
- **Foreign-shape SaaS:** Enable is built for generic B2B distributors, not for OMX's specific customer/supplier rebate complexity
- **Anaplan underused:** Paying for an enterprise platform but only using it for one workflow (demand) — classic "$200k for one feature"
- **Snowflake-native gap:** All the input data (sales, agreements, contracts, demand history) already lives in Snowflake — but reporting/planning lives in foreign tools

### Benefits (the value story)

| Lever | Rough $ value | Note |
|---|---|---|
| **SaaS reclaim** | ~$350k/yr | Enable $120k + Anaplan $200k + storage $30k |
| **Demand-plan accuracy lift** | ? | If Snowflake-native + AI uplift adds 1-2% accuracy → big inventory $ unlock; quantify with finance |
| **Promo lift discipline** | ? | Linked promo planning + actual demand history reduces over/under-spend; reference Promo Analyst agent |
| **Rebate accrual accuracy** | ? | Less missed customer/supplier rebates; reference Enable claim that 3-5% rebate leakage is industry norm |
| **Internal capability uplift** | Strategic | Snowflake-native = OMX team can extend; SaaS = vendor roadmap dependency |

### Open questions to resolve tomorrow

---

## Research deepening (background-agent, 2026-06-28)

### Enable.com — at the $120k/yr tier
- Standard B2B rebate workflows (claim automation, accrual calculation, payout reconciliation)
- Customer pain pattern: **"generic platform forced into non-generic shape"** — OMX's customer/supplier rebate complexity exceeds Enable's SCD2 hierarchy model
- Industry tells: high configuration burden; vendor lock-in on roadmap

### Anaplan demand-planning replacement playbook
- **IBP Program** at `D:\20-PROJECTS\officemax\ibp-program\IBP-PROGRAM.md` formalises this — PPSS is **Workstream 1** (Portfolio & Pricing, research phase); Demand Planning is **Workstream 2** (foundational; statistical forecast partial; promotional forecast not started)
- No published market "Anaplan replacement playbook" — market assumes Anaplan + dbt/Snowflake are complements
- OMX differentiation: custom Snowflake-native build using existing dbt models
- Alternatives (SaaS): **RELEX**, **Kinaxis** — specialised, not full replacement

### OMX Snowflake data sources already feeding PPSS
Located in `lens/Current/libraries/dbt/models/presented/`:
- `F_AGG_SALES_PERFORMANCE_ACCOUNT` — daily sales + targets by account/rep (SALES_AMOUNT, TRUE_GP_AMOUNT, SALES_MARGIN)
- `F_AGG_SALES_PERFORMANCE_ROLE` — sales by rep role
- `F_CUST_TARGET_ACCOUNT_DLY` — daily customer targets
- `F_CUST_TARGET_BY_REP_DLY` — by sales rep
- `D_CALENDAR`, `D_CALENDAR_MTH` — 445 fiscal (daily, MTD, QTD, YTD)
- **Grain:** D_CALENDAR_KEY + ACCOUNTCODE + REP_CODE
- **Status:** dbt models v4 verified against Snowflake CSV exports — ready for promo/rebate logic layer

### Competitor pricing stack (Plex-CI)
- **NXP** (won ACC $3.2M contract) · 11,823 SKUs · Next.js + Contentful · B2B focus
- **Discount Office** · 34,880 SKUs · Shopify · tiered B2B pricing
- **McGreals** · 911 SKUs · Shopify · Afterpay/Zip
- **Hurdleys** · 42 SKUs · Shopify · quote builder
- **Observation:** none publish custom promo/demand planning. All standard Shopify/Contentful. **PPSS is a genuine competitive differentiator.**

### Open questions — resolved
- **Promo/Demand stream in flight?** YES — IBP WS1 (PPSS, research) supersedes manual spreadsheets + Enable. WS2 (demand, foundational) builds on existing dbt models.
- **Other Anaplan use cases beyond demand?** NO — seed assumption confirmed. Demand-planning only.
- **Audience?** DUAL — **CFO** (cost-reclaim $350k/yr) + **Commercial Director** (capability + competitive positioning). IBP MBR governance shows the right cross-functional room.


- Which deck arc fits best? Likely:
  - Cover → Problem (cost overspend + tool fragmentation) → Solution (one OMX-owned platform) → Market/Scope (5 capabilities) → Product → Architecture (Snowflake-native) → Roadmap → Cost reclaim ($350k/yr)
- Is there a Promo/Demand stream-of-work already in flight that PPSS would supersede?
- Are there other Anaplan use cases beyond demand we'd need to handle?
- Who's the audience? ExCo? CFO? Both?

## Layout candidates from the gold standard

- **Problem vector grid (4)**: Cost / Fragmentation / Lack of fit / Vendor lock-in
- **Solution mirror grid (4)**: OMX-owned / One platform / Bespoke / Snowflake-native
- **Cost reclaim table** (new layout — propose): "Today's spend → PPSS = saving" line items
- **Architecture pipeline**: Promo + Sales + Rebate + Demand → PPSS Core → Snowflake
- **Roadmap**: stages from POC to full replacement of both SaaS contracts
- **The ask**: budget to build, payback period from SaaS reclaim