The problem this solves
Hiring is the most readable growth signal a company emits, and it lives outside the CRM. A rep working a segment has no idea which accounts posted five roles this month and which posted none, so every account gets the same energy. The segment that could be sorted by momentum is sorted alphabetically.
Appending hiring data to a CRM segment turns it into a prioritized queue. The count of open roles says how fast the company is growing; the departments say where the budget is; the latest posting title gives the rep an opener. Written back as properties, the fields become filters and views inside HubSpot rather than a one-off sheet, and the export to Sheets gives the team a ranked list for this week.
How the mission runs
- Read the segment. The Enrichment Agent loads the companies in HubSpot segment <name> with their domains, resolving any that lack one.
- Pull hiring data per company. For each company, hiring data returns the current open roles. The agent counts them, groups them by department, and captures the most recent posting's title and date.
- Write the properties back. Open-role count, departments hiring and the latest posting title and date are written to company properties in HubSpot, created if they do not exist, as a batch you review first.
- Export the ranked segment to Sheets. The segment is exported to Google Sheets sorted by open roles descending, with the department breakdown and the latest posting on each row so the week's priorities are visible at the top.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
HubSpot companies in segment <name> carrying four new properties - open-role count, departments hiring, latest posting title, latest posting date - and a Google Sheet of the segment sorted by open roles with the same fields. The report gives the distribution of open roles across the segment so you can see how many accounts are actively growing.
Make it yours
- Filter the postings to a function relevant to your product - only sales roles, only engineering roles - and count those.
- Add a change column on the next run so accelerating and decelerating accounts stand out.
- Create HubSpot tasks for the account owner at every company above a threshold of open roles.
- Chart the distribution of open roles across the segment and post it to #sales with the sheet.
Frequently asked questions
How current is the open-role count?
It reflects postings live at run time. Schedule the mission weekly and the properties stay current and the sheet re-sorts.
Can I see the postings themselves?
Yes. Ask for a postings tab and the sheet lists every open role per company with its title, department and date.
Will the properties be overwritten on the next run?
Yes, by design, since they describe the present; the previous values are kept in the change log.
Which sources are covered?
Hiring data aggregates postings from company career pages and major job boards, deduplicated so a role listed in several places counts once; the source is stored per posting.
Can I count only senior roles?
Yes. Ask for director-level and above and the counts and the latest posting reflect senior roles only, which is a stronger signal of budget than volume hiring.
Can the properties drive a HubSpot workflow?
Yes. Once the properties exist, a workflow can trigger on a threshold - say five open roles - to assign a task or change a lifecycle stage.
Does it work with a Pipedrive filter instead?
Yes. Name the Pipedrive filter and the same fields are written to the organizations it contains, with the export sorted the same way.