Andrew Luxem

CRM, Lifecycle & Applied AI Strategy

20 years in, I’m still asking: what if we tested this?

At Amazon, that meant helping put early propensity models into marketers’ hands. Today, it means testing what AI-driven marketing actually does against what it claims to do, then looking past the dashboard summary to the customer behavior underneath.

The industries changed. The customers changed. The tools changed many times over. The method did not: follow the behavior, state the hypothesis, run the test, and see whether anything moved.

AMAZONANCESTRYBED BATH & BEYONDSTANLEY BLACK & DECKER

BRAZE FORGE 2025 SPEAKERNORTHWESTERN MEDILL GUEST LECTURERBRAZE MARKETER OF THE MONTH

Andrew Luxem, CRM and lifecycle marketing leader

AI made production cheaper.

It made the fundamentals more valuable.

AI made it cheaper to produce more marketing. It did not make it easier to decide what deserves to exist. When a team can generate more variants than it can responsibly test, production stops being the main constraint. The harder part is judgment: which customer behavior matters, which idea is worth testing, and what result would change the decision.

That puts the value back on the unglamorous work. Read the behavior underneath the dashboard. Design a test that can prove the assumption wrong. Compare the result with a meaningful baseline or holdout. Trust what customers do over what they say they might do. Write something someone is glad to receive, not one more message to ignore.

I learned that early in my career. The model was never the whole answer. The harder part was turning its output into a signal marketers could understand, trust, and use when making decisions. That lesson has stayed with me through every role since.

Across ecommerce, SaaS, global industrial tools, and big-box retail, I’ve seen technology create an advantage when it shortens the distance between a customer signal and a better decision. It creates noise when it increases output without improving judgment or measurement.

The tools and playbooks here are built around that distinction. Run them against your own data and constraints. Keep what changes the result. Revise or discard what does not.

20
years working in-house
72
playbooks across nine modules
126
strategy presets tested
12
open-source repositories

Applied AI

Built for people to understand and agents to execute.

Use AI to shorten analysis, production, and simulation. Keep the customer decision, approval standard, and performance review with a named human owner.

Everything on this site is structured so people can inspect the method and agents can execute it under the same constraints.

01

Machine-readable playbooks

The playbooks use consistent structures that agents can interpret and people can audit. They ship as installable skills. Each includes a SKILL.md, working templates, and a declared operating contract: explicit invocation, no remote calls, and no automatic updates.

02

Reproducible simulation

Deterministic math and seeded runs make the assumptions and results repeatable. The coach interprets the measured output instead of replacing it with an opaque score or treating the dashboard as the answer.

03

Evidence over adjectives

A model must beat a holdout before it ships. Claims published here follow the same standard: show the evidence, state the boundary, and make the test visible. If the result does not support the argument, the argument changes.

Working code on GitHub
Agent skills, design tools, and demonstration pipelines. Every action requires explicit invocation.
customer-journey-lifecycledecision-cardAll repositories

The Strategic Brief

Get the brief in your inbox

CRM strategy, lifecycle systems, experimentation, and applied AI.

Each issue makes one argument, shows the evidence behind it, and gives you something to test in your own work.