Corporate Membership Setup
Teri Rosenbaum
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.)
Yayem
Teri Rosenbaum
Since this touches billing rules, account permissions, cancellation behavior, and eventual dashboards, the most important step is defining the real-world scenarios you want supported.
This doesn’t need to be technical — just a clear description of how you expect these relationships to function.
To help guide the outline, here are the critical ownership questions:
- Who is responsible for managing seats?
Will corporate admins (“Parent accounts”) manage their own Child accounts, or will Limestone admins manage this manually? This determines the entire workflow and whether a management UI is needed.
- Who owns the payment method and billing relationship?
If the corporation is paying, does the corporate admin control the card on file and seat count, or should those stay locked and only editable by Limestone?
- How much control should corporate parents have?
Should a Parent be able to:
• add/remove employees
• assign seats
• pause or activate access
• view usage
Or should they only see a list of employees while Limestone handles any changes?
- What is the lifecycle of Child accounts?
If an employee leaves, who removes them?
Does the seat free up immediately?
Should changes be reviewed by Limestone before taking effect, or self-managed by the corporation?
Until these ownership decisions are clarified, we can’t map out the technical model — each option leads to a very different system.
Once Limestone provides this outline (even in bullet-point form), we can review it, validate feasibility, and determine cost.
For context, this would be a single custom build delivered in full prior to release, not a phased rollout.
Teri Rosenbaum
Yayem Very helpful - understood that all these need to be answered before you can scope. Will follow up with the team and revert