Five structural divergences from the current loyalty architecture — not as replacements, but as additions and expansions.
Each divergence is framed as: what the current architecture does, and what adding Brian's approach makes possible. These are structural additions, not critiques. The strongest loyalty systems in the world — Xbox Live, Marriott Bonvoy, Starbucks Rewards — got there by layering, not replacing.
The current architecture is built around the high-engagement dining enthusiast. That's the right foundation — but it leaves the majority of guests without an identity to grow into. Brian's model introduces persona tiers (Explorer, Regular, Connector, Tastemaker) that give every guest a meaningful place in the system from day one.
The current model rewards dining frequency. Brian's model also rewards influence — when a guest's recommendation brings someone new to a restaurant, that influence is tracked, attributed, and rewarded. This is the Xbox model: identity investment creates community, community creates advocacy, advocacy creates measurable growth.
The most durable loyalty systems — Xbox Live, Marriott Bonvoy, Starbucks — work because members feel they belong to something. The current Dynery architecture is strong on the transaction layer. Brian's model adds the community layer: events, recognition, social proof, and a sense of membership that makes leaving feel like a loss of identity, not just a loss of points.
Brian's model introduces a distinct economic layer: restaurants fund the community programs that create the word-of-mouth that fills their tables. This is not a new idea — it's how the best local dining ecosystems have always worked. The difference is that Dynery can instrument it, attribute it, and make the ROI legible to operators in a way that has never been possible before.
The current architecture captures what you spend and where. Brian's model captures who you are as a diner — your persona, your influence radius, your community role, your behavioral patterns across occasions. This is the data moat that makes Dynery defensible over time: not transaction volume, but dining identity depth.
Mark's architecture is the transaction and attribution foundation. Brian's architecture is the community and identity layer on top. Neither works as well without the other. The question for this discussion is not which one — it's how we sequence the integration.
Mark's foundation: Precise transaction attribution, restaurant value measurement, access-tag infrastructure, and the discovery layer that makes the whole ecosystem work.
Brian's layer: Persona-based identity, influence attribution, community programming, operator-funded growth mechanics, and the behavioral identity graph that makes the platform defensible over time.
Neither layer needs to wait for the other to be complete. The transaction foundation can launch with the persona system already in place — guests get an identity from day one, and the community layer can activate as restaurant density grows. The goal is parallel development with a clear integration roadmap.