|
A note on our position Brandmovers operates its own loyalty platforms, BLOYL (B2C loyalty) and BENGAGED (B2B channel incentives). We are a platform provider, not an independent analyst, and we say so plainly. This guide is written to help you run a rigorous, vendor-neutral evaluation, and the scorecard and questions below apply to any provider, including us. Where our platforms would be evaluated on the same criteria as anyone else's, that is the point: a good process should hold every vendor, ourselves included, to the same standard. |
A loyalty platform decision is one of the least reversible technology choices a marketing organization makes. Replatforming is costly and disruptive, and it means migrating a member database, points liabilities, and years of behavioral history, so the organization that selects the wrong platform tends to operate on it for years anyway. That makes the evaluation worth doing rigorously. This guide provides a complete framework: how to prepare before the RFP, a 25-criterion weighted scorecard, demo scenarios that test beyond the rehearsed walkthrough, seven reference-check questions that surface what references will not volunteer, a weighted scoring model, and the five most expensive selection mistakes to avoid.
|
Key Takeaways
|
The most common loyalty RFP failure is issuing a feature checklist before defining a program strategy. When the evaluation is anchored to a feature list rather than a strategic vision, vendors respond by highlighting the features they perform well, and the process drifts toward whoever demos best rather than whoever fits the program you actually intend to run. Before writing a single requirement, define the program you are trying to build: the behaviors you want to drive, the member experience you are aiming for, the economic model, and the two-to-three-year roadmap. The scorecard that follows is far more useful when each criterion is weighted against that strategy, rather than treated as a universal checklist.
The process begins with a longlist assembled from several sources: independent market research such as the Forrester Wave and Gartner Magic Quadrant where applicable, category-specific analyst coverage, peer recommendations, and existing vendor relationships. From the longlist, narrow to a shortlist of three to five vendors that plausibly fit your strategy, scale, and vertical, since a rigorous evaluation of five vendors is more valuable than a shallow one of fifteen. Keep the shortlist small enough that you can run real scenario testing, reference calls, and total-cost modeling on each, which is where the meaningful differences surface.
The scorecard organizes 25 criteria into six categories. Score each criterion from 1 to 5 (1 means does not meet, 3 means meets, 5 means exceeds), then multiply by the criterion weight for a weighted score. The category weights shown are a balanced starting point; adjust them to reflect your own priorities, since a data-heavy enterprise and a fast-launch mid-market program should not weight the categories identically. The weights below sum across six categories: Program Design (20 percent), Data Architecture (20 percent), AI and Personalization (15 percent), Operations (20 percent), Financial (15 percent), and Vendor Viability (10 percent).
|
# |
Criterion |
Category |
Wt |
Evaluation Guidance |
|---|---|---|---|---|
|
1 |
Points, tiers, and program-structure configurability |
Program Design |
5 |
Supports your earn rules, tier thresholds, and structure without custom development? |
|
2 |
Rule-engine flexibility (conditional bonuses, time-limited promos, segment offers) |
Program Design |
5 |
Can marketing configure complex rules (3x in Category A, capped, time-limited) without engineering? |
|
3 |
Reward-catalog depth and redemption types |
Program Design |
4 |
Supports your redemption types (points-to-cash, merchandise, experiences, partner)? |
|
4 |
Coalition / partner earn and redemption support |
Program Design |
3 |
Accommodates partner earn/redemption if planned for years 2 to 3? |
|
5 |
Multi-program and franchise management |
Program Design |
3 |
Runs separate program configs under one instance, with operator-level visibility? |
|
6 |
API-first architecture and integration documentation |
Data Architecture |
6 |
Are all functions (enrollment, posting, tier update, offers) API-accessible and well-documented? |
|
7 |
POS and e-commerce integration (connectors and custom API) |
Data Architecture |
6 |
Which POS systems have pre-built connectors? What requires custom integration? |
|
8 |
CRM, CDP, and ESP integration (data flow and sync) |
Data Architecture |
5 |
Does behavioral data sync to CRM/CDP in real time or in batch? |
|
9 |
Data ownership and export rights |
Data Architecture |
6 |
Who owns member data? Can you export complete profiles and histories at any time? |
|
10 |
Data security (SOC 2 Type II, PCI DSS, GDPR) |
Data Architecture |
5 |
Request the current SOC 2 Type II report; confirm PCI DSS for card data and GDPR support. |
|
11 |
Propensity modeling and churn prediction |
AI & Personalization |
5 |
Built-in churn/purchase propensity or next-best-action, and is it configurable? |
|
12 |
Personalized offer / reward recommendation engine |
AI & Personalization |
4 |
Personalization at the individual-member level from behavioral data? |
|
13 |
Send-time optimization and channel selection |
AI & Personalization |
4 |
Optimizes send time and channel at the individual level? |
|
14 |
Segmentation and audience building (marketer-accessible UI) |
AI & Personalization |
4 |
Can marketing build complex segments without engineering? |
|
15 |
Campaign management (multi-step journeys and automation) |
Operations |
5 |
Can marketing build lifecycle journeys (welcome, nudge, churn prevention) with automation? |
|
16 |
Content and communication templates (email, push, SMS, wallet) |
Operations |
5 |
Template builder for all channels, with personalization? |
|
17 |
A/B testing and experiment management |
Operations |
4 |
Can marketing test offers, messages, and timing in-platform, with significance tracking? |
|
18 |
Reporting (incremental revenue, member behavior, program ROI) |
Operations |
4 |
Does it produce CFO-grade reports (member vs. non-member revenue, program ROI)? |
|
19 |
Fraud detection and account security |
Operations |
4 |
Built-in fraud detection (anomalous redemption, duplicate-account detection)? |
|
20 |
Pricing transparency and total cost of ownership |
Financial |
5 |
Request a 3-year TCO model: implementation, licensing, overages, and services. |
|
21 |
Contract terms (data ownership, termination, migration rights) |
Financial |
5 |
Review export rights at termination, cancellation notice, and migration support. |
|
22 |
Implementation scope, timeline, and accountability |
Financial |
3 |
Guaranteed MVP timeline? What is included versus a change order? |
|
23 |
Client references (industry, scale, recency) |
Vendor Viability |
4 |
Three references in your vertical, at comparable scale, live for 18-plus months? |
|
24 |
Product roadmap (AI, personalization, channels) |
Vendor Viability |
3 |
What ships in 12 and 24 months? How are priorities set? Is the roadmap contractual? |
|
25 |
Vendor financial stability and market position |
Vendor Viability |
3 |
Private, PE-backed, or public? ARR? Profitable? Acquisition risk? |
Vendor demonstrations are rehearsed performances designed to showcase strengths, using pre-configured sample data set up to flatter the product. In our experience, the standard demo reveals only a minority of what you actually need to know. The way to test the rest is to hand the vendor your own scenarios and ask them to configure them live, or to configure them yourself in a sandbox. Four scenarios reliably separate genuine capability from a polished walkthrough.
Scenario 1, conditional promotion configuration. Ask the vendor to configure, live, a promotion where Gold-tier members earn triple points on a specific category, only during a 14-day window, capped at 500 bonus points per account, excluding members who joined in the last 30 days. This reveals whether marketers can build genuinely complex conditional rules without engineering, which is one of the strongest predictors of day-to-day agility.
Scenario 2, member lifecycle journey. Ask them to build a post-enrollment journey: a welcome message on enrollment day, a balance-update notification after the first qualifying purchase, and a tier-progress nudge 30 days later if the member is within a set distance of the next threshold. This tests real automation and journey logic, not just single-send campaigns.
Scenario 3, real-time reporting. During a simulated double-points promotion, ask them to show real-time reporting: incremental transaction volume for members who received the offer versus a control group, and total points liability issued. This exposes whether the platform can measure incrementality and track liability, or only report vanity activity.
Scenario 4, data export. Ask them to walk through exporting the complete member database (identity, enrollment date, tier, lifetime points earned and redeemed, and 24 months of transaction history) in a standard, importable format. This is your insurance against lock-in, and a vendor's willingness and ability to do it cleanly tells you a great deal.
Vendor-selected references are, by definition, happy clients, chosen because they are successful deployments and trusted to speak positively. A call structured to confirm what the vendor already told you produces nothing. A call structured to surface problems produces the most valuable information in the entire evaluation. These seven questions are designed to do that.
1. “Walk me through the implementation, specifically what went wrong and how it was resolved.” Every implementation has problems; a reference that says it was perfect is not engaging honestly. What you learn is how quickly and thoroughly the vendor responds when things go wrong.
2. “What was the most significant gap between what was promised in the sales process and what was delivered?” This surfaces gaps in feature parity, timeline, implementation quality, or commercial support.
3. “What change requests have you submitted that are not yet complete, and how long have they been open?” Change-request velocity is one of the biggest sources of long-term dissatisfaction, and open-ticket age is a hard signal.
4. “What would you have done differently in the selection process?” This consistently surfaces the most useful information of any reference call, often a specific test the reference wishes they had run.
5. “How has the vendor responded when you raised critical bugs or outages that affected member experience?” Incident-response quality cannot be assessed from a demo or an RFP response, only from someone who has lived through it.
6. “If you were starting over today, would you choose this vendor again, and what would make you choose differently?” The ‘starting over today’ framing draws an informed, current verdict rather than a defense of a past decision.
7. “Are there capabilities you are actively waiting for on the roadmap that are critical to your program?” This identifies the gap between current capability and the reference's needs, which is often where your own risks lie.
Once proposals are evaluated and demos completed, compile the scoring. For each of the 25 criteria, assign a score of 1 to 5, multiply by the criterion weight, and sum across all criteria for each vendor's total weighted score. Dividing that total by the maximum possible score gives a normalized percentage that makes vendors comparable at a glance; for example, a vendor averaging 3.8 across all criteria produces about 76 percent of the maximum. Treat the number as a decision aid, not a verdict: a small gap between two finalists is a prompt to look harder at the highest-weighted criteria and the reference calls, not to defer automatically to the higher score. The scorecard's job is to make the trade-offs explicit and defensible, not to remove judgment from the decision.
1. Selecting on headline price without modeling total cost of ownership. Loyalty pricing has many components beyond the license: implementation, configuration change requests, data-storage and API-overage charges, and professional services. In the TCO models we build, implementation often runs roughly two to four times the annual license, so a headline price tells you very little on its own.
2. Not confirming data ownership and export rights up front. If you do not own your member data or cannot export it cleanly, you are locked in, and the cost of that lock-in surfaces exactly when you most want leverage.
3. Evaluating against current requirements rather than two-to-three-year requirements. A platform that perfectly meets launch requirements but cannot support the roadmap forces a replatform just as the program matures.
4. Using a vendor-led demo as the primary evaluation instrument. The demo shows what the vendor wants you to see; scenario testing and hands-on sandbox time show what you actually need to know.
5. Not including IT, finance, and legal from the beginning. Selections made by marketing alone frequently hit late-stage vetoes from IT (integration and security), finance (total cost), or legal (data and contract terms), restarting the process at the worst possible time.
The loyalty platform decision is not reversible on a short timeline, so the discipline you bring to the evaluation pays off for years. Define the strategy before the requirements, weight the scorecard to your priorities, test vendors against your own scenarios rather than their rehearsed demos, structure reference calls to surface the truth, and bring IT, finance, and legal in from the start. A weighted scorecard does not remove judgment from the decision, but it makes the trade-offs explicit and defensible, which is exactly what a multi-year, cross-functional commitment deserves.
|
Evaluating Loyalty Platforms? Full disclosure: Brandmovers is a loyalty platform provider (we operate BLOYL and BENGAGED), and we also help teams structure rigorous, vendor-neutral RFPs and evaluations, including ones we compete in. Get in touch with the Brandmovers team if you'd like help building your scorecard, scenario tests, and TCO model, or a straight answer about where our platforms fit your requirements and where they don't. |