Per-member LTV that updates every month, per location
Every loyalty member has a current LTV — computed from real transactions, segmented by location and behavior, and ready for the CFO, the marketing team, and the LP letter.
The problem
A 200-location operator with half a million loyalty members usually estimates LTV from a CFO spreadsheet — a static range like $1,200 to $1,800 that gets refreshed once a year. The number is plausible enough for board decks. It is useless for decisions: which member is worth winning back at what cost, which segment a referral campaign should target, what the marketing payback period actually is for each location. Loyalty platforms run the points and rewards but do not produce per-member LTV. Customer data platforms can pipe data anywhere but leave the math to you. LTV-analytics tools exist for DTC ecommerce and assume one brand, one location. Enterprise CRMs offer LTV modules but require their own data model and pricing tier. Computing 100M member-month LTV values monthly across 200 locations with the right segmentation and compliance is the gap.
What success looks like
Every loyalty member has a current LTV value, refreshed monthly. The math accounts for purchase frequency, average ticket, margin per service, retention curve, location-specific behavior, and behavior cohort. Identity stitching means a customer who transacted across three locations and two channels has one LTV, not three. State and industry rules govern how regulated data is handled in the calculation. Margin uses real product catalog data, not a flat assumption. The CFO sees real numbers, the marketing team sees which segments to invest in, and your LP letters cite an LTV you can defend.
How most operators solve this today
A handful of tools touch LTV. None of them give you a current per-member LTV across hundreds of locations with the right segmentation:
Loyalty platforms (Square Loyalty, Smile.io, Loopy Loyalty, Zoho Thrive, Stampme, Yotpo Loyalty, LoyaltyLion, Talon.One, Annex Cloud)
$0 to $200,000+/year
They run rewards mechanics. Per-member LTV across locations with margin and behavior segmentation is not what they ship.
CDP and LTV analytics (Segment, mParticle, Tealium AudienceStream, RetentionX, Daasity, LTV.ai, Lifesight)
$500 to $500,000+/year
They pipe data and run general-purpose LTV models — built for DTC, often single-brand. Per-location segmentation and state-by-state rules are not part of the model.
Enterprise CRM with LTV modules (Salesforce Marketing Cloud, HubSpot, Klaviyo CDP, Bloomreach Engagement, Optimove)
$800 to $25,000+/month
LTV is a feature inside a larger CRM. The model is generic and the per-location, per-behavior segmentation is your team to configure.
CFO Excel heuristic
Free, refreshed yearly
A static range that does not change with the business. Plausible for a board deck, not actionable for marketing or retention decisions.
Build it in-house
Senior engineer ($130-220k) + data scientist ($140-250k) + analyst ($80-130k) + six to sixteen weeks
A custom dbt + Snowflake + Python pipeline gets you to v1. Maintaining 100M member-month LTV values monthly across 200 locations is where the cost stays.
What changes when this is an agent skill
LTV is computed per member, per month, against real transactions. The model uses purchase frequency, average ticket, margin per service line, retention curve, behavior cohort, and location-specific patterns. Identity is stitched across channels and locations — a member who transacted in three towns over two channels has one LTV. State-by-state and industry rules govern how regulated fields are handled. Margin comes from your product catalog, not a flat assumption. LTV updates propagate to loyalty, lifecycle marketing, subscription save flows, and reporting so the same number drives every decision. Every LTV value is versioned with the inputs that produced it, so the CFO can drill into any specific member or segment and explain the calculation. The static range gives way to a number you can act on.
Agents that include this skill
Skills live inside agent rentals. To get this skill in production, hire any of the agents below — context-tuning at onboarding is included in the first month.
Loyalty Member Journey Orchestration Agent
Decides when each member gets which offer — tier-transition timing, cross-location earn/redeem, offer dedup.
FAQ
- How is this different from loyalty platforms like Square, Smile.io, or Yotpo Loyalty?
- Loyalty platforms run the points and rewards mechanics. They do not compute per-member LTV across locations with margin and behavior segmentation. We compute the LTV; your loyalty platform remains the system of record for the program.
- How is this different from CDP-based LTV tools (RetentionX, Daasity, LTV.ai, Lifesight)?
- Those tools are built for DTC ecommerce, often single-brand. Per-location segmentation and state-by-state rules are not part of their model. We solve the multi-location case.
- How is this different from enterprise CRM LTV modules (Salesforce, HubSpot, Bloomreach, Optimove)?
- Enterprise CRMs offer LTV as a feature inside a larger platform. The model is generic. We layer on the per-location and per-cohort math and feed results back into your existing CRM through APIs.
- How is identity stitched across locations and channels?
- Email, SMS, in-store visit, call, and loyalty action are reconciled to the same member. A customer who transacted at three locations has one LTV, not three.
- How is margin handled in the calculation?
- Margin uses real product catalog data — cost of goods, service margin, contribution per SKU. Not a flat assumption that overstates LTV on low-margin services.
- How often does LTV refresh?
- Monthly by default, with the option to refresh more frequently for high-velocity segments. New transactions update the inputs continuously; the LTV value reflects the new data at the next refresh cycle.
- How is this work surfaced to the CFO and marketing team?
- LTV values land in your reporting layer alongside per-location metrics. The CFO can drill into any segment. Marketing can target by LTV cohort. The number used in the LP letter and the number used by the campaign team is the same number.
- Does this work for franchise systems with corporate-only loyalty programs?
- Yes. The LTV math runs against the same data regardless of who funds the loyalty program.