I'm going to chime in here, because I hate, hate, hate bundles, from a conceptual standpoint. From a functional standpoint, they don't work for our organization.
I think the larger "thing" (aka bundle, in this case) is a completely different entity than the "things" (aka single, individual member, in this case) that make it up. Yet, on WA, both of those things function pretty much the same way - they are both just members.
In my little brain, a parent-child relationship should exist between these entities: employee individual members belong to XX Corporation entity, individual family members belong to The Smith Family entity, individual players belong to a larger Red Sox team entity.
On our site, we have individual members as a level and various corporations as levels, for example, we have a level for ABC Corporation, a level for XYZ Corporation, a level for PDQ Corporation, etc. & all of those are bundle levels. In total, we have 27 bundles! That's insane! We should have 4 at most - unpaid/basic, individual, corporate, event sponsor.
I tried to set up a corporation as a member entity instead of a level entity, but then the corporation takes on all of the properties of the human individual that is the bundle administrator...no elegant solution that I've found.