Feature Sheets
Feature Sheets are the definitive reference documents for every capability in ES Loyalty. They translate complex product functionality into structured, accessible information while bridging the gap between what the platform does and why it matters to your business.
The problem they solve
ES Loyalty is a deep, configurable platform. Without a consistent reference point, understanding what a feature does, let alone how to communicate its value, means hunting through scattered engineering documents that weren't written with business audiences in mind. This could have key stakeholders facing issues such as the following:
Feature Sheets solve these problems by giving every stakeholder a consistent, plain-language view of what ES Loyalty can do and what value it delivers.
What's inside
Every Feature Sheet follows the same structure, making it easy to find what you need regardless of which feature you're reading about.
Business definition
What the feature does, in plain language, no technical background required.
Business requirements
The functional expectations and rules that define how the feature behaves.
Availability status
Whether the feature is available, in development, or planned, so nothing gets miscommunicated.
Configuration details
Guidance on how the feature is set up and what options are available to program operators.
Key use cases
Feature Sheets serve a range of practical purposes across the product lifecycle, from initial scoping to ongoing program management.
Client discovery and scoping
Quickly communicate what ES Loyalty supports without pulling engineering teams into early discovery conversations.
Release communication
Provide product, marketing, and support teams with accurate, consistent information ahead of a release.
Product gap analysis
Use Feature Sheets as a baseline for identifying where capabilities are missing or need improvement.
Cross-team alignment
Ensure product, delivery, and client success teams are working from the same understanding of a feature.
Program planning
Identify features that unlock new engagement tactics, targeting capabilities, or reporting improvements.
Supporting documentation
Serve as the source of truth that feeds user guides, help content, and release notes.
Who should read them
Feature Sheets are written for business audiences first. You do not need a technical background to get value from them.
Product managers
Track what is built, what is in flight, and how features connect to program outcomes.
Client success and delivery
Confidently communicate feature scope and limitations without needing engineering support.
Loyalty program owners
Understand what tools are available to design and evolve a member experience.
Marketing and strategy
Identify features that unlock new engagement tactics, targeting, or reporting capabilities.