About
In rugby, the flyhalf receives the play, reads the field, and distributes to the scorers. That's the whole product: your systems send events, Flyhalf reads your flows, and the rewards — points, badges, prizes, messages — land where they count.
Why we built it
A points table here, a cron job there, a WhatsApp integration that nobody wants to touch. Loyalty logic ends up scattered across codebases where it can't be tested, audited or changed by the people who run the programme. We built the engine once — properly — so your team designs plays instead of plumbing.
How we build
Append-only ledgers. Idempotent everything. A sandbox that can't touch real customers. Delivery logs you can replay. Built in South Africa with POPIA in the architecture, not the appendix — and priced so a coffee shop and an enterprise both get the full engine.
Principles
Points are never edited in place. Corrections are reversals with references. Your finance team can reconcile every cent.
Test output is unmistakably test output — in the dashboard, the logs and the API. Nobody ships to real customers by accident.
No message leaves without a lawful basis and a working opt-out. Engagement that ignores consent isn't engagement.