-
Notifications
You must be signed in to change notification settings - Fork 13
2020 September Sprint Notes
Paul Ginsberg edited this page Jun 29, 2021
·
1 revision
We're getting started!
We want to build out a modular solution with a simple, adaptable data model.
- Who is eligible to purchase a membership?
- Who is eligible to receive a discount on the membership?
- More generally, what are the business rules surrounding this membership type?
- Upgrade and downgrade paths?
- Maintenance of membership dates
- How do we allow organizations to control when dates are propagated from the Membership level to the Membership Contact Role level?
- Tracking membership types
- How do we walk the divide between support small orgs that might use a picklist versus big orgs that might use a Product?
- Communities - what is the limitation around Products there? Would a Custom Object be better?
- How do we walk the divide between support small orgs that might use a picklist versus big orgs that might use a Product?
- How do we connect dollars to memberships?
- Acknowledge that memberships and Opportunities are not 1:1 in many situations.
- Forecasting futures.
- What's the broadest, most flexible way to model membership types?
- Automating connections to households/members
- On the Contact and on the Household, we'd want to be able to roll up special types of membership, or criteria about memberships (like that they just expired) from all of the memberships in which they participate.
Note how this pulls in "Who", "Term", and "Benefits"