CASE-03 · RECSYSE-commerce · Recommender Systems

One owned recommender, replacing a five-vendor stack.

A global retailer ran personalization across five vendors with diverging cohorts and runaway cost. We consolidated into one owned, edge-deployed system — and moved AOV by 38%.

Engagement signals
Live
+38%
Average order value
+19%
Conversion rate
<50ms
Edge inference p95
1.4B
Daily inferences
The brief

Problem, strategy, implementation.

Problem

Five overlapping personalization vendors produced inconsistent shopper experiences, diverging A/B winners, and unit economics that broke at scale. Engineering owned none of the models, so iteration cycles were quarterly — not daily.

Strategy

Replace the vendor stack with a single owned two-tower retrieval + ranker, deployed at the edge for sub-50ms latency. Unify the feature store across web, app and email. Make the team self-sufficient on model evaluation and rollout.

Implementation

Five Ptimz engineers across modeling, platform and infra. Edge-deployed inference across 14 regions, with warm fallbacks for cold geographies. Full ownership transfer with documented eval, monitoring and rollout protocols.

Engagement timeline

Kickoff to compounding outcomes.

W01-02

Discovery

Vendor decomposition, traffic shape, feature inventory, eval baseline.

W03-06

Modeling

Two-tower retrieval, ranker, calibration; offline + online eval harness.

W07-10

Platform

Feature store, model serving, observability, A/B framework.

W11-14

Edge rollout

14-region deployment, vendor cutover, A/B graduation.

W15-16

Handover

Team enablement, on-call rotation, retrain pipeline ownership.

Verified results

Outcomes signed off by the client's CFO.

+38%
AOV lift on personalized cohorts
+19%
Conversion improvement
1.4B
Daily inferences across 14 regions
Client voice
"We replaced a five-vendor stack with one Ptimz system. Order value is up double digits, engineering owns the model, and our infra bill went the right direction for the first time in years."
CTO · Global Retailer
Engineering stack

What we actually built with.

PythonPyTorchTritonRayFeastKafkaSnowflakedbtRedisKubernetesNVIDIA T4Cloudflare WorkersDatadog
More work

Related case studies.

Engagement

What could we ship for you?

A 30-minute session with the engineers who would lead your deployment. No slides, no sales — a working conversation.