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.
01 / 06
Why now
The wedge.
See seed for detail.
02 / 06
What this covers
What's in scope.
03 / 06
The problem
What's broken.
01
Fragmented stack: Enable handles reb
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
02
Foreign-shape SaaS: Enable is built
Foreign-shape SaaS: Enable is built for generic B2B distributors, not for OMX's specific customer/supplier rebate complexity
03
Anaplan underused: Paying for an ent
Anaplan underused: Paying for an enterprise platform but only using it for one workflow (demand) — classic "$200k for one feature"
04
Snowflake-native gap: All the input
Snowflake-native gap: All the input data (sales, agreements, contracts, demand history) already lives in Snowflake — but reporting/planning lives in foreign tools
04 / 06
The benefits
The value story.
Lever
Mechanism
Sizing
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
05 / 06
The ask + roadmap
What we need.
Now
Problem vector grid (4)
: Cost / Fragmentation / Lack of fit / Vendor lock-in
P2
Solution mirror grid (4)
: OMX-owned / One platform / Bespoke / Snowflake-native
P3
Cost reclaim table
(new layout — propose): "Today's spend → PPSS = saving" line items