The decision
Build vs buy, argued honestly
This is the page to forward to your CTO. No vendor theatre — what building actually includes, what adapting a campaign tool costs you later, and where an engine layer fits. Including when it doesn't.
What "build it ourselves" actually includes
The parts everyone scopes — earn banners, a points widget, a redemption screen — are maybe 20% of the system. The other 80% is invisible until it fails in production. Here it is.
-
An append-only ledger with derived balances
Balances must be computed from immutable history, never stored as editable rows. Get this wrong and your first balance dispute becomes an archaeology project with no artifacts.
-
Idempotency on every value mutation
Mobile retries, duplicate billing file rows, replayed queues — every one of them will hit your credit endpoint twice. Without first-class idempotency keys, you will double-credit, and you will find out from finance.
-
Per-lot FIFO expiry
Points earned in January expire before points earned in June — per lot, exactly, at scale, while members are simultaneously redeeming. This is the feature that quietly breaks most in-house builds.
-
Audit and tamper-evidence
Every value change needs who, what, when, and why — in a form that survives an internal audit or a regulator's question. Bolting this on later means re-architecting the write path.
-
Reconciliation
You need continuous proof that the sum of ledger entries equals every displayed balance — and tooling to investigate drift before it becomes a member dispute or a balance-sheet restatement.
Realistic cost: 12–24 months of senior engineering before the first campaign ships — and that team owns the pager for it forever. If your engineers are excited about building this, ask them who maintains it in year three.
Put a number on it
Drag the sliders to match your build plan. This is the engineering cost alone — before infrastructure, compliance review, and the roadmap your team isn't shipping meanwhile.
Estimate only. Your CFO will have opinions — bring them to the demo.
What adapting a campaign tool costs you later
Plugin-style loyalty tools and promo engines are genuinely good at what they're for — smaller programs, fast campaigns, storefront ecosystems. The problem is what happens when a serious program grows into their ceiling.
-
No real ledger underneath
Most store balances as mutable rows. That works until the first reconciliation request, chargeback dispute, or auditor. Then it doesn't.
-
Per-member pricing shocks
Pricing that looks fine at 100k members becomes a board-level line item at 10M. Check the pricing page math at your five-year member forecast, not your launch forecast.
-
Program logic trapped in someone else's UI
When earn rules live in a vendor's campaign builder instead of behind an API, every integration, migration, and audit runs through their roadmap — not yours.
-
Replatform gravity
Tools designed around a storefront ecosystem pull your program toward that ecosystem. If your members live in your own apps, billing, and CRM, that's a permanent impedance mismatch.
Where LoyaltyGrid sits
We are the engine layer — the 80% that's invisible until it fails. You keep the member experience, your channels, and your data.
-
You own the experience
Your apps, your website, your contact centre. Members never see a LoyaltyGrid screen. We're behind the API, not in front of your brand.
-
We own the correctness
Append-only ledger, idempotent writes, exact integer math, FIFO expiry, audit, reconciliation — the full ledger story — plus multi-tenant isolation and an admin dashboard for your operations team.
-
Weeks, not years
Integration is a REST API and webhooks against your existing systems, with a sandbox tenant before any commitment. First integration typically ships in weeks.
When we're not the answer
An honest page needs this section.
-
You want a member-facing app out of the box
We're headless by design. If you need a ready-made loyalty app and have no channels of your own, a suite-style product will serve you better.
-
Your program is small and simple
A few thousand members, one earn rule, no expiry? A plugin — or honestly a spreadsheet and a promise — will do. Come back when the liability keeps your finance team up at night.
-
You genuinely need to build
If loyalty mechanics are your core product differentiator and you have a platform team to staff it permanently, building can be right. We'll tell you that on the call.
Still weighing it?
Bring your integration map and your member forecast. We'll give you a straight answer — including "build it" if that's the truth.