There is a tension at the heart of every loyalty consultancy that has moved its delivery stack onto Salesforce.

The CRM handles programme logic beautifully. Tier management, points accrual, partner programme rules, transactional records, member data - all of it inside the platform your team already knows, integrated natively with the service, marketing, and analytics tools you use for client delivery.

But when a new client mandate arrives, the same gap opens every time. Salesforce does not include a branded customer portal. It does not include reward partner API connections. It does not include the payment flow that converts a points balance into a real-world benefit. It does not include the single sign-on layer that connects a member's identity across channels.

Every new client programme requires this experience layer to be built. And every time it is built from scratch, the clock starts again - time that a competing consultancy might not be spending.

The Problem With Building the Experience Layer From Scratch Each Time

Loyalty consultancies that have made the deliberate decision to exit proprietary technology - choosing Salesforce as their delivery backbone rather than maintaining a bespoke platform - do so for sound commercial reasons. It removes the capital cost and ongoing engineering overhead of owning a platform. It gives clients the confidence of a widely adopted, regularly updated CRM. It makes data integration with clients' existing systems significantly simpler.

What it does not remove is the need for a customer-facing experience layer on top of Salesforce. A loyalty programme without a branded member portal, a reward catalogue, and a working fulfilment flow is a data model - not a programme a member can participate in.

Building this layer bespoke for each new client creates four compounding problems:

• Time to delivery: A custom-built experience layer adds weeks to months onto every new client programme. Enterprise clients increasingly expect programmes to go live in weeks, not quarters. That expectation gap is a competitive risk in every RFP.

• Ongoing maintenance: Each bespoke build becomes a permanent engineering commitment. Reward partner APIs change. Salesforce releases updates. Security patches need applying. A consultancy managing ten client programmes on ten bespoke builds is carrying ten separate maintenance obligations simultaneously.

• Inconsistent quality: When the experience layer is rebuilt for every engagement, quality varies with the team and timeline available. The fifth deployment is not necessarily better than the first - and client programmes that rely on different approaches have different failure modes.

• Limited reusability: Hard-won integration patterns - member identity resolution, voucher issuing, transaction journalling, reward catalogue management - are embedded in bespoke client code rather than shared infrastructure. Every new engagement starts close to zero.

"Enterprise buyers now expect loyalty platforms that go live in weeks, not quarters. The consultancies closing mandates fastest are the ones that do not rebuild their delivery infrastructure for every new client."  - Propello Cloud Loyalty Platform Guide, 2026

What Changes When the Experience Layer Is Already Built

The shift is straightforward in principle: instead of building the experience layer for each new client, a consultancy operates from a shared, multi-tenant experience layer that is configured for each new programme rather than rebuilt from scratch.

Multi-tenancy in a loyalty context means that one installation of the platform serves multiple clients simultaneously, with each client's members, reward catalogue, programme logic, and transaction history completely isolated from every other. A member of Client A's programme has no visibility of Client B's data. The commercial terms, reward mechanics, and branding of each programme are entirely independent. But the underlying infrastructure - the portal framework, the reward partner integrations, the payment flow, the monitoring and alerting - is shared.

For a loyalty consultancy, this changes the economics of every new mandate in three specific ways.

Speed from win to live

When the experience layer infrastructure already exists - portal framework, SSO, reward partner APIs, payment flow, error logging - a new client programme becomes a configuration exercise rather than a build exercise. The branded portal is configured, not constructed. The reward catalogue is populated, not integrated from scratch. The programme goes live faster because the components that take longest to build are already production-ready.

Lower delivery cost per client

The engineering cost of building a loyalty experience layer is substantial. Amortising that cost across multiple client programmes - rather than charging it to each client individually - reduces the cost of delivery for each engagement. That creates margin to invest in the advisory and consultancy work that differentiates a loyalty consultancy from a pure technology vendor, which is where the commercial value actually lies.

Reusable integration patterns

Every integration pattern developed on one client programme - member identity resolution, voucher issuing, transaction journalling, reward fulfilment error handling - is available for the next. The second deployment inherits the quality and reliability of the first. The fifth deployment is meaningfully better than the first because the patterns have been tested and refined across real production environments, not re-engineered each time.

How RewardX Works Alongside Salesforce for Consultancy Delivery

RewardX is VE3's loyalty experience and orchestration platform, built specifically for organisations delivering loyalty programmes on a Salesforce backbone - either for their own customers or on behalf of clients.

The architecture is a clean division of responsibility. Salesforce Loyalty Management handles the master data layer: member records, programme data, tier logic, rewards, vouchers, transactional records, reporting structures, and API governance. RewardX handles the experience and orchestration layer: the branded member portal, single sign-on, reward partner API integrations and margin management, Stripe payment flow with error logging and retry logic, and client-level segregation through programme IDs and client identifiers.

For a loyalty consultancy, the practical implication is this: when a new client mandate is secured, the consultancy is not starting from zero on the experience layer. The portal framework is there. The Stripe payment flow is there. The reward partner integrations are there. The monitoring and alerting infrastructure is there. What changes between clients is the branding, the reward catalogue, the programme rules configured in Salesforce, and the specific integration requirements of each client's environment.

RewardX is already live in production through a full SaaS loyalty deployment. The integration patterns - member lookup, voucher issuing, TransactionJournal, DevOps practices - are proven in a real operating environment, not demonstrated in a demo. That distinction matters when a consultancy is standing behind a client programme that handles real customer transactions at scale.

The Practical Test

The right question for any loyalty consultancy evaluating their delivery architecture is not 'does our current approach work?' It is 'how much faster and at what lower cost could we deliver each new client programme if the experience layer was not rebuilt from scratch every time?'

For consultancies that have already made the decision to build on Salesforce - because the CRM integration advantage, the platform maintenance model, and the client confidence in Salesforce as a known quantity are all genuine benefits worth having - RewardX is designed to close the gap that Salesforce leaves open, without competing with it.

If you would like to see how this architecture works in a live deployment and what it would look like applied to your next client programme, our team is happy to walk through the patterns and the production case study in detail.