Decisions · Strategy and governance
Should you benchmark against competitor programmes
Benchmark competitor programmes, but only for visible member expectations: how many points a typical transaction earns, how fast rewards arrive, what redemption looks like. Do not benchmark hidden economics such as breakage, expiry accounting or partner margin splits; derive those from your own profit and loss. The condition is that every copied number must pass the test: would a member notice if this changed before their next transaction?
The decision
The decision is not whether to look at competitor programmes; it is whether those programmes become your design source or your design context. Benchmarking feels neutral because the numbers are public, but every visible loyalty mechanic encodes an invisible choice about margin, liability and member segmentation. A competitor may offer one point per dollar because it has a 30 per cent gross margin or because its points are funded by a third party. When you adopt the one point per dollar without that structure, you adopt the output and ignore the engine. The mechanism underneath is anchoring: the first number you see becomes the number you defend, and design stops being a decision and becomes a copy.
What it costs you
The real cost of benchmarking competitor programmes is not the time spent looking; it is the cost of carrying their hidden assumptions into your economics. Every competitor reward rate you copy becomes a liability on your books. An illustrative calculation: a competitor gives one point per dollar spent and lets members redeem at one cent per point. That creates one cent of deferred loyalty liability for each dollar of tracked revenue. If your tracked revenue is 50 million dollars a year, copying that rate adds 500,000 dollars of points liability before breakage. If your own margin model supports only 0.4 cents per dollar, the same revenue base should carry 200,000 dollars. Benchmarking tells you that one cent is normal in your market; it cannot tell you whether your margin can absorb the extra 300,000 dollars. The recommended path costs you the discipline to keep those two numbers separate, and the engineering time to record, compare and discard what does not fit.
How to decide
Apply one test to each competitor number before you let it into your design: is this something a member would notice before their next transaction? Earn rate, reward visibility, redemption speed and status thresholds are visible expectations. If your competitor changes them, your members will ask why you have not. Benchmark those. Point expiry rules, breakage assumptions, liability accounting, partner margin splits and internal service levels are invisible economics. Members do not see them until something breaks, and by then you have already committed to the wrong cost base. For your own programme, write down the benchmark value and then ask: if a competitor doubled it tomorrow, would my members change their behaviour before their next purchase? If yes, treat it as a market norm and design against it. If no, leave it out of the benchmark entirely.
What would change our mind
We would reverse this recommendation and say do not benchmark at all if your team cannot document a competitor metric without copying it into the next draft. The entire value of benchmarking depends on a clean separation between observation and adoption. When that separation fails, every hour spent studying a competitor becomes a liability decision you did not intend to make. In that state, the next visible earn rate or redemption value will anchor your design and the hidden economics behind it will follow. Cutting off the input is cheaper than cleaning up the output. A programme that cannot look at a competitor without imitating it is better off looking at its own margin and member data until the discipline exists.