About
The number 10 doesn't score. It makes the score happen.
In rugby, the flyhalf receives the ball, reads the field, and puts it where the points are. That's the product: your systems pass Flyhalf what customers do, Flyhalf reads the pattern — who is building a habit and who is drifting — and the right challenge, badge or reward lands while it can still change the outcome.
Why we built it
Loyalty was stuck counting transactions.
A ledger records what has already happened. The sign that a customer is leaving — thinner visits, a broken routine — sits between the transactions, where no points table looks. Teams that wanted to act on it ended up with a cron job here and a WhatsApp integration nobody wants to touch. We built that behavioural layer once, properly, so your team designs plays instead of plumbing.
How we build
Boring guarantees, visible workings.
Append-only ledgers. Idempotent everything. A sandbox that can't touch real customers. Delivery logs you can replay. Built in South Africa with consent and data protection in the architecture, not the appendix — and priced so a coffee shop and an enterprise both get the full engine.
Principles
Three things we won't trade.
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.