Question regarding database design
I'd go b.  A person is a person.  Record that then layer over what role they take in your organisation.  

Consider that an employee might also be a customer.  A person might take the role of other participants that you have not yet thought of or chosen to model.  

A customer can also be a business which would have a different shape.  

Lots of potential reasons to keep them separate.