What you decide is "needed by individuals and small teams" is not always what an individual or small team actually needs. This makes the open core model extremely difficult to get right (I am not sure I know any examples of anyone who has continued to do it right for very long).
For example, I would love SSO for my homeserver, so that I can share secrets with my family. I would guess that my family is a "small team", but many open core products don't open source SSO features. Many small actual businesses would prefer SSO too, as juggling multiple logins is as much a pain for a small team member as it is for a member of a big team.
I appreciate any open source contribution even if it is missing features. I understand it can be difficult to sell a product that is 100% open source.
Even when I am implementing something for a larger organization, I always prefer to specify open source over open core.
I end up very rarely adopting any open core product due to missing features- and when I do, I am often spending money re-implementing the closed source features, and thus the money isn't there to pay the company for support. I don't know how common this approach is, I just know a lot of open core products get skipped by me because of limitations.