HubSpot Territory and Owner Assignment by Firmographics
Apply your territory rules to firmographic data filled by MoltSets, and automatically set the right owner on HubSpot deals and companies.
example prompts
-
Assign owners to these HubSpot companies based on employee count and region -
Run territory assignment on companies that just got firmographics filled
about this skill
What this skill does
Puts firmographic data to work once it is on the record. It reads your territory rules (employee range, industry, region, or a combination), applies them to HubSpot companies and their open deals, and sets the correct owner. Built to run right after firmographic fill, so companies that just had industry, size, and region completed get routed immediately rather than sitting unassigned or with the wrong rep.
Chain
HubSpot companies (recently firmographic-filled, or unassigned / misassigned)
to hubspot/search-crm-objects (companies missing an owner, or owner mismatch vs rules)
to MoltSets:
search_companies (domain -> employee_range, revenue_range, industry, if not already on record)
to apply territory rules (employee range + industry + region -> owner or team)
to hubspot/update-object (set company owner)
to hubspot/list-associations (open deals on the company)
to hubspot/update-object (set deal owner to match, where deal owner is unset or stale)
Inputs
- Territory rules - the mapping from employee range, industry, and/or region to owner or team
- Scope - unassigned companies only, or also companies with an owner that no longer matches current rules
- Deal cascade - whether to also update the owner on associated open deals, or company only
- Fallback owner - who or which queue gets a company that matches no rule
How it works
- Pulls companies missing an owner, or flagged as a rule mismatch under the current territory logic
- Runs
search_companiesfor any company still missing the firmographic fields the rules depend on - Applies the territory rules in order (most specific rule first, for example named account lists before general industry rules) to determine the correct owner or team
- Writes the owner to the company record
- Lists open deals associated with the company and, where the deal owner is unset or does not match, updates the deal owner to align
- Routes anything matching no rule to the fallback owner or queue rather than leaving it unassigned
Output
| Company | Domain | Employees | Industry | Region | Rule Matched | Assigned Owner | Deals Updated |
|---|
Companies reviewed: X
Owner assigned: X
Rule mismatches corrected: X
Fallback owner used: X
Deal owners updated: X
MoltSets tokens used: X
Search filters
search_companies filters on query (company name only), domain, industry, linkedin_industry, naics_code, employee_range, revenue_range, country, and state.
domainbeats free text every time - exact match, and full URLs are normalised automatically, sohttps://www.acme.com/aboutneeds no cleanup first.- Filters are free precision - a filters-only search runs ~40x cheaper than one carrying free text, and most firmographic work needs no
queryat all. - Three industry vocabularies -
industryis 22 broad buckets ("Information Technology", not"Computer Software"); niches like software or insurance live inlinkedin_industry("Software Development") ornaics_code. A thin result is often a neighbouring-label problem rather than a coverage one. - Company location is derived from where the team is based, and large multinationals resolve to a single one of their offices - pair location with another filter on enterprise or international targeting.
- Range values are exact and skewed -
"1-10"dominates employee counts,"$500k - $1M"dominates revenue.
Tips
- Requires the HubSpot remote MCP (mcp.hubspot.com) and the MoltSets MCP connected in the same client
- Run this right after the firmographic fill skill so newly completed data gets routed the same day rather than sitting stale
- Order your territory rules from most specific to most general (named accounts, then industry plus size, then a catch-all) so the first match wins predictably
- Reassigning an owner on a deal already being worked is disruptive, so consider excluding deals with recent activity from the cascade
- Custom objects are not reachable through HubSpot's remote MCP, so write to standard company and deal owner properties