Feature Requests

Increase error messages during the applicant sign up process, as well as hardening any edge cases observed in the last 6 weeks.

Provide both a list and calendar view on the web app for non-members and mobile app for members.

Internal tags that allow operators to group and segment members into custom cohorts for filtering, organization, and analysis.

This feature will launch as a beta release, surfacing key engagement, behavioral, and revenue-driven signals at the member level. These insights are designed to help operators identify trends, understand retention risk, and make more informed decisions around member engagement and lifecycle management.

Track lifetime value (LTV) and average transaction value at the member level by aggregating completed payments over time. This data will be used to understand member value, purchasing behavior, and revenue contribution, and to support segmentation, reporting, and operational decision-making.

We will track a view each time a member opens an event’s detail page. This data will be used to measure engagement, analyze conversion from views to RSVPs, and identify drop-off points across the event funnel.

The first steps to managing multiple secret keys per community. This includes Stripe, Brevo, Revinate, etc.

Create a place where members can clearly refer to their included benefits for their given subscription tier (for example, 10% off F&B at property) or any other local benefits (15% of local pilates studio as an Aethos member).

Implement professional digital membership identification system similar to Soho House for member verification.

We're engaging with Limestone & tax advisors to make sure we get the Stripe setup right by location - no expectation for Yayeym to play a role in this piece. Our primary ask is related to how we can operationalise this on the Yayem front & back end. This will need further fleshing out but in essence we need to enable a parent-child user type for corp clients, eg: A Parent account that pays for X # of accounts and is mapped to Child accounts that sit underneath the Parent account. They do not pay anything and their subscriptions are only cancelled if the Parent account stops paying (There would eventually be a need for a UI for Parent accounts to see & manage their subscriptions, but this would be phase 2.)