Topic starter
09/07/2026 1:41 pm
TL;DR: AI is changing how customers optimise rewards and point pooling, while loyalty teams still face 12-month deployment backlogs that slow monetisation and margin protection, according to Comarch and Loyalty360. The governance challenge is no longer campaign creativity but whether loyalty platforms can adapt fast enough to support revenue, incrementality, and customer behaviour shifts.
Editorial analysis by NHI Mgmt Group, based on content published by Comarch: “AI-Native Loyalty: How to Bypass the 12-Month IT Queue”.
Key questions
A: Treat loyalty release latency as a governance problem, not just a technology one.
Q: Why do long IT backlogs reduce the value of loyalty programmes?
A: Because loyalty value depends on timely changes to incentives and policy.
Practitioner guidance
- Shorten loyalty policy release cycles Map the current approval chain for reward changes, pooling rules, and discount logic, then remove bottlenecks that force those changes into annual release trains.
- Measure incrementality before scaling incentives Separate habitual buyers from incremental responders so the programme stops rewarding behaviour that would have happened anyway.
- Define a hybrid change model for legacy stacks Identify which loyalty functions must remain in the core platform and which can be delivered through adjacent AI-native services without a full rip-and-replace programme.
Bottom line: Loyalty programmes now compete against customer behaviour that is increasingly shaped by AI-assisted optimisation.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 1:46 pm
Legacy loyalty backlogs are now a governance constraint, not a delivery inconvenience. When customer optimisation is accelerating through AI, a 12-month deployment cycle turns loyalty from an adaptive control surface into a frozen policy layer. The programme can no longer respond at the speed of the behaviour it is trying to shape, which makes delay itself a strategic risk. Practitioners should treat release latency as part of loyalty governance, not a separate IT metric.
A question worth separating out:
Q: When should organisations choose incremental changes over a full loyalty platform replacement?
A: Choose incremental change when the business needs faster value delivery than a rip-and-replace programme can support. A layered approach can add AI-native capabilities to an existing stack while preserving core systems, but only if governance for data, rules, and change control is explicit and tightly owned.
👉 Read our full editorial: AI-driven loyalty growth is outpacing legacy IT deployment cycles