one table to rule them all

[rivet]

I am starting a new DB and pondering the schema. In a past project I had various company types that required their own section but I had a parent table called company which would hold basically the company name. so:

company: company_name, id 
- agency: [ separate table, agency details ]
- client:  [ separate table, client details ]
- vendor:  [ separate table, vendor details ]

I also did the same for contacts:

profile: first_name, last_name, id
- contact:  [ separate table, contact details ]
- talent:  [ separate table, talent details ]

The new project has similar requirements and  I am wondering if I should normalize it further and merge company into profile. A major benefit is searching a single table and having it return all contact and company but I am wondering if this is straying form best practice or if you can foresee   any downside.