HubSpot Ideas

DanAtZ

Contacts at Companies with Multiple Locations

New HS user coming from Salesforce 😲  - was suggested I post this here...

We're in B-to-B sales and we need to identify and work with Contacts at each location under the parent company. HubSpot likes to use one domain name which ushers users into putting all contacts under that domain umbrella.  That won't work for us and I suspect many others. For example, "GiantCompany" (GiantCompany dot com) has 15 locations/business units across North America and even around the world. We need to capture and engage with Contacts at each location under GiantCompany and work with them based on their location (e.g. Giant Company in NY, GiantCompany in Chicago, etc.). Many times locations are separate business units (SBUs) but not necessarily. The key for salespeople is to know/go/meet  Contacts at each location which requires segregating and managing Contacts by location rather than having every Contact under GiantCompany and adding each Contact's address. A key need driver is we need to be able to use mapping software to identify Accounts in an area or starte when we're planning sales trips/meetings and having that Account's Contacts associated with that location is critically important.

In addition to this, an issue we have with HubSpot is the lack of a CLONE button! It's so tedious having to enter the address of each Contact when it's a copy of someone else's address.

We're certainly not the first company dealing with these HS issues. Hoping to get some insight from users who've been there and done that. Thanks in advance!

1 Reply
MYdeAndersen
Member

HubSpot as a system will go from child to adult, if company domain name is reduced in importance for the entire HubSpot and let the "company record ID" be key data field for companies. No serious B-T-B companies can operate seriously with 1 company domain name per unit within a large organisation with e.g. 1 headquarter and 200 outlets. Recommending HubSpots customers to avoid dublets in company domain names is unserious. I understand that it eases the allocation of new contacts using the contact's personal email address as allocation variabel.

You recommend that we only 1 company domain name. As a consequence we then could choose to allocate the company domain name "giantcompany.com" for the headquarter, "giantcompany-1.com" for outlet 1, "giantcompany-2.com" for outlet 2 and so on. This is a poor workaround.

Besides serving fake/non-existing company domain names for the users,  we will not get the web tech stack data from HubSpot knowledgebase (builtwith.com) into the outlets' web tech stach data field - to mention another downside. Another downside is to the timeconsuming tedious task of creating fake company domain names, when importing new outlets/affiliates/children into HubSpot.

Going from company domain name to a new regime with "company record ID" as the "basic company unit," will solve a lot of problems including more logical mechanisms when importing companies. In the same step, HubSpot should also change the "basic contact unit" for contacts from the personal email address to the "contact record ID" as well.

Then HubSpot will get rid of the biggest childhood diseases and create much more value for some of us b-t-b costumers.