I've got CiviCRM installed for a non-profit client whose membership base is small organizations (theater ensembles) and individuals. I am now considering that I may have fundamentally engineered this wrong and that if I got it right there would be better solutions to problems that arrise.
How should CiviCRM be implemented so that there is the most logical and flexible architecture when both individuals and organizations can hold memberships?
Some details about what I mean about organizations and individuals both holding memberships:
Organizations can hold memberships. Organizations have staff and associates. Organizations often have no email address of their own, only the address of an associate. This maybe be the achilles heel.
Individuals can hold personal memberships. Some of these members are affiliated with member organizations. Some stand alone.
There are also many non-member contacts such as donors, newsletter subscribers, potential members, event participants... you get the idea.
We'd like to keep track of all these folks so that we can (easily) see activity for an individual, an organization, and an aggregate of activity for an organization with its associates.
We'd like members to be able to manage their membership profiles, manage their associates' profiles (if they are organizations), pay for new/renewing membership.
We'd like members to have privileged use of the website based on the type and status of their memberships.
We'd like to send bulk emails based on profile information and past activity. We'd like to send renewal notices and other personalized emails.
We'd like to be able to pose questions like: Which organizations had more than one associate who attend an event last year?
There's so much more of course but it is predicated on getting the architecture right. Any guidance will be most appreciated. Thanks.