Build vs Buy: Loyalty Program Software for Multi Channel Retail Groups
Buy while your programme is one channel with a simple earn rule and points outstanding your finance team never argues about. Build once balances differ by channel, or once the breakage assumption behind your deferred revenue has become an audit conversation.
On this page
Buy while your programme is one channel with a simple earn rule and points outstanding your finance team never argues about. Build once balances differ by channel, or once the breakage assumption behind your deferred revenue has become an audit conversation. The deciding factor is accounting exposure rather than member count, because points issued with a sale are a liability you have to defend.
The programmes that should buy, and buy quickly
Some of this decision is easy. Buy if all of the following describe you:
- One channel, or several channels that already share a single customer record.
- An earn rule that is essentially a percentage of spend.
- Points outstanding small enough that nobody in finance has raised them.
- No partner earn, no coalition, no transferable balances between members.
- A point of sale (POS) estate on one software version that is reliably online.
Antavo handles tier and reward modelling well for a programme of that shape and will have you live in a fraction of the time and cost of a build. Punchh suits restaurant and convenience operators who want its member experience out of the box. Salesforce Loyalty Management is a natural fit for a group already committed to that platform, provided you price the transaction volume once every till in the estate is calling it. Talon.One is a genuinely strong rules engine and worth pairing with whatever else you run rather than treating it as a competitor to a build.
Building a points ledger to operate a stamp card is a waste of capital, and we would say so on the first call. The reason to be blunt about it is that loyalty builds fail more often from ambition than from engineering: a group decides to replace everything, discovers that the reward catalogue and the campaign tooling are commodity, and spends its budget rebuilding what it could have rented.
What actually pushes a retail group into building
The trigger is usually a customer standing at a till. She checks the app and sees one balance, the terminal shows another because it holds a cached figure that syncs overnight, and the service desk shows a third. She was promised a reward at four thousand points and she is being told she has not reached it. The associate overrides, which creates a manual adjustment nobody reconciles, and your outstanding balance drifts a little further from anything finance can defend.
That is not a reporting problem. It is architecture. Most stacks store a balance and update it, and a stored balance cannot be audited, cannot be replayed, cannot survive a duplicate message and cannot explain itself to a member on the phone.
The accounting is the second driver and the more serious one. Under IFRS 15 and ASC 606, points issued in a sale are a separate performance obligation, so part of that revenue is deferred until the points are redeemed or expire. Your outstanding balance is a liability, valued on a breakage assumption your auditors will question, and many programmes carry a rate set years ago that has never been re derived from actual behaviour.
The third is cadence. Grocery and fuel operators change earn rules weekly, and a vendor configuration cycle cannot keep up. The fourth is partner earn or a coalition, where every partner is a settlement relationship as well as an integration.
Digital Heroes builds in this category, starting with a written product requirements document covering the ledger, idempotency and the liability report before any code exists, because here the specification is a finance document as much as a product one. Because there is an India LLP, a US LLC and a UK LTD in the group, a retailer signs where it already trades and the member ledger transfers under that same law. Past 2,000 projects delivered, a team over 50, and 2.5 million subscribers on our YouTube channel.
The numbers on each route
The licensed route usually prices on active members or on transaction volume, plus implementation. Read the metering definition carefully, because a promotion that triples earn events triples the bill in the month you least want a surprise, and active member definitions vary enough between vendors that quotes are hard to compare without normalising them.
Commissioning a platform costs $120,000 to $250,000 for a first release shipping in 14 to 22 weeks, on Digital Heroes delivery numbers: a single append only ledger with idempotent earn and burn, tier evaluation, point of sale integration inside the till's latency budget, and offline earn with reconciliation. A full platform adding partner earn, offer and coupon interaction rules, breakage cohort modelling with auditable liability reporting, transfer and fraud controls, member self service and migration from your existing programme runs $320,000 to $800,000 across 9 to 18 months.
What drives the number is the point of sale estate first, because integrating one till software version is a project and three is three projects. Then migration. Then partner earn. Then multi country operation, since points carrying monetary value attract different tax and consumer protection treatment by market and you need local advice rather than a template.
Design decisions that turn into costs later
The first is a duplicate message. Tills retry, networks stutter, and the same transaction arrives twice. Without an idempotency key derived from the source transaction, the member is awarded twice, nobody notices, and your liability inflates silently in a direction no report will surface. This is the most common preventable defect in loyalty systems and the cheapest to design in at the start.
The second is the refund path. When a purchase is returned, the points must be reversed against the original earn event rather than deducted from the current balance. Deducting from the current balance is how members end up negative, how buy and return cycles keep the points, and how a fraud pattern hides in plain sight.
The third is your offline policy, which is a finance decision rather than a technical one. Allowing redemption while a store is disconnected creates real exposure; refusing it creates a customer service moment at the till. Somebody has to choose, and that conversation should happen calmly in a design session rather than during an incident at four on a Saturday.
The fourth is migration. Importing balances is straightforward. Importing the history that justifies them is not, and members notice immediately when their statement starts empty or their tier progress resets. Plan to import transaction history far enough back to cover your tier qualification period, run both systems in parallel for a full cycle, and reconcile daily during that window.
The fifth is finance sign off, which is a genuine workstream with genuine meetings rather than a review at the end.
A test your finance and retail teams can run together
Pick one member with activity across at least two channels in the last month. Ask for their balance from the app, from a store terminal and from the service desk at the same moment. If the three figures differ, you have your answer and no amount of interface work will change it.
Then ask how the current breakage rate was derived and when. If the answer is a number inherited from a previous system or a previous person, that is the assumption underpinning deferred revenue in your accounts, and it deserves a cohort based method behind it.
Third, ask the point of sale team what happens to earn and redemption when a store loses its connection, and whether that behaviour was agreed with finance or discovered during an outage.
Finally, take one week of manual adjustments and check whether each one names a person and a reason. Adjustments that cannot be attributed are the difference between a liability report an auditor accepts and one they test line by line.
Consistent balances, a derived breakage rate and an agreed offline policy mean your programme is well run and a build would be an expensive tidy up. Three different balances plus an inherited breakage number is the combination that justifies commissioning something.
Questions to ask before you commit
Ask the vendors to demonstrate against your awkward cases rather than a clean journey: a member earning online and redeeming in store within the same hour, a refund of a promotional purchase, a transfer between two member accounts, and a coupon stacked on top of a points redemption. Watch what happens to the balance in each case.
If you are interviewing developers, open with a single question: what happens when the same point of sale message arrives twice. If idempotency keys do not appear in the first half minute of the answer, expect double awarding. Then ask how the till behaves when the loyalty service is unreachable, and require a specific answer covering earn queuing, redemption decline and reconciliation on recovery. Then ask how they would produce the liability report and what an auditor would ask for. A team that has done this talks about cohorts, redemption curves and adjustment attribution. A team that describes a dashboard has built a marketing tool.
Settle ownership before kickoff. You hold the repository, the cloud accounts and the member ledger, because that ledger is the record of a promise made to millions of customers and it carries a balance sheet liability, so it has to be portable by design. Check the D-U-N-S record matches the signing company, read the public Clutch and Trustpilot listings for reviews that describe a delivered system, and establish which legal entity contracts with you and can assign intellectual property in your jurisdiction.
If you want a second opinion before signing anything, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
How much does custom loyalty program software cost for a retail group?
A first release with a single append only ledger, idempotent earn and burn, tier evaluation, point of sale integration and offline earn runs $120,000 to $250,000 over 14 to 22 weeks in Digital Heroes delivery experience. A full platform adding partner earn, breakage modelling, auditable liability reporting, fraud controls and member self service reaches $320,000 to $800,000 across 9 to 18 months. Till software versions drive cost most.
How long does it take, and what usually delays the schedule?
Fourteen to twenty two weeks to a first release. Delays come from two places rather than engineering. The first is the point of sale estate, where each till software version behaves differently under timeout and retry conditions. The second is finance sign off on breakage method, offline redemption policy and adjustment authority, which needs real meetings with people whose diaries are already full.
How hard is migrating members from an existing loyalty programme?
Importing balances is simple. Importing the history that justifies them is the hard part, and members notice at once when a statement starts empty or tier progress resets. Import transaction history at least far enough back to cover your tier qualification period, run both systems in parallel for a full cycle, and reconcile balances daily during that window before switching any customer facing surface.
What does a loyalty platform need to integrate with?
Point of sale first, inside the till's latency budget, then ecommerce, your customer data platform or warehouse, the mobile app, and your finance system for the deferred revenue entries. Partner earn adds a settlement relationship per partner rather than just a technical connection. Ask any developer to name the till software versions they have integrated with in production, since that is where the effort concentrates.
How is points liability calculated and why do auditors question it?
Points issued with a sale are a separate performance obligation under IFRS 15 and ASC 606, so part of that revenue is deferred until redemption or expiry. The outstanding balance sits on the balance sheet, valued using a breakage assumption about points that will never be used. Auditors test the assumption, so derive it from your own cohort redemption curves by tier and channel rather than carrying an inherited rate.
Who actually builds loyalty platforms for large retailers?
Digital Heroes builds them, though only where the points ledger has become an accounting asset rather than a marketing feature. Retailers choose us for jurisdiction and process: we contract through an India LLP, a US LLC or a UK LTD so IP assignment sits under your own law, and we write a product requirements document covering the ledger, idempotency and the liability report before any code exists. Past 2,000 projects delivered.
How is Digital Heroes different from a general development agency?
We reverse points on refund by linking the reversal to the original earn event rather than subtracting from the current balance, and we key every earn message from the source transaction so a retried till call cannot award twice. Both sound like details and both decide whether your liability figure is defensible, because double awards and negative balances are invisible in every dashboard a general team builds.
How do we verify a development partner before signing anything?
Check the D-U-N-S record against the company that will sign your agreement. Read Clutch and Trustpilot for reviews describing real engagements rather than adjectives. Confirm which legal entity invoices you and whether it can assign intellectual property in your jurisdiction. Then require the repository, the cloud accounts and the member ledger in your own name, and run a full export during the build to prove portability.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
What does it cost to maintain a custom CRM after launch?
Budget 15 to 20 percent of the build cost per year, so roughly $6,000 to $10,000 annually on a $40,000 system, covering hosting, security patches, dependency updates, and a pool of small improvements. Hosting itself is the minor part, typically $50 to $300 a month for companies under 100 users. For comparison, a 20-user team on Salesforce Enterprise pays about $9,900 in licenses every quarter at list price, close to a full year of that maintenance budget.
We're outgrowing HubSpot's free CRM. Should we upgrade to a paid plan or build our own?
Upgrade inside HubSpot if your problem is limits on contacts, seats, or automation; Sales Hub Professional lists at $90 to $100 per seat per month and solves volume problems well. Build custom when the data model is the problem, for example deals that involve multi-site installations, equipment rentals, or recurring service visits that HubSpot's contact-company-deal structure cannot represent without workarounds. Roughly a third of the CRM projects Digital Heroes takes on replace a HubSpot account the team had bent past its limits.
How do I vet a CRM development agency before signing a contract?
Ask to see two live CRMs they built for businesses your size and talk to those clients about what happened after launch, not during the sales process. Then pin down three specifics: who owns the code (you should, fully, on final payment), what a change request costs after go-live, and how they plan data migration. An agency that cannot walk you through a migration plan on the first call will improvise yours.
Can a custom CRM integrate with QuickBooks, Gmail, and our phone system?
Yes, and integrations are usually the main reason to go custom: QuickBooks, Gmail and Outlook, Stripe, Mailchimp, WhatsApp, and VoIP platforms like Twilio all have stable APIs we wire into CRMs routinely at Digital Heroes. Each standard integration adds roughly $2,000 to $6,000 and one to two weeks to the schedule. The expensive ones are legacy systems with no API, which need file-based syncs or database-level connections, so flag those in the first conversation.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other CRM software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
