Hiring signal board for your customers and open pipeline

I want an app my account managers open every morning to see which of our existing customers and open-pipeline accounts are hiring right now. Hiring is the cheapest early signal that budget is moving, since a company staffing up a team is usually well ahead of the purchase decision that follows. Be explicit about the direction: this app starts from accounts we already own in HubSpot and is aimed at expansion and renewal timing. It is not net-new prospecting, and it must never create new company records.

The main surface is a board of accounts. Load it from HubSpot with Search Companies, pulling companies that are current customers or have an open deal, and read each company's name, website domain, owner and lifecycle stage. Match and deduplicate companies by domain: normalize by lowercasing, stripping the protocol, any www prefix and any trailing path, then treat two HubSpot records sharing a normalized domain as one row, keeping a reference to every underlying record ID so later writes land on the right one. Records with no usable domain cannot be matched against posting data, so skip them but show a clear count of how many were skipped.

Each row shows the account name, the open-role count over the last 30 days, the departments those roles sit in, the seniority mix, and a technology-stack column. Source the role data from JobsPipe Search Job Postings, filtered by the account's domain and a posted-after date 30 days back, and source the technology column from JobsPipe Scan Domain Technology Stack on the same domain. Use the live JobsPipe search and never the sandbox routes, which return canned sample data rather than real results. JobsPipe postings already arrive deduplicated across more than 30 ATS and job-board sources, so do not build a second deduplication pass over the postings themselves.

Derive the department breakdown by grouping returned postings by occupation or job function into plain buckets such as Engineering, Data, Sales, Marketing, Finance, Operations and Support, showing the top few with counts. For the seniority mix, ask JobsPipe to include postings with no stated level, because roughly 55 percent of the corpus carries no labelled seniority and filtering on seniority silently drops them. Show unlabelled roles as their own 'Not stated' slice rather than hiding them, so the mix stays honest.

Scans must run on demand rather than on every page load, because each JobsPipe request costs one credit including requests that return zero results. On first load, show the accounts from HubSpot immediately with the hiring columns empty, a Scan button per row, and a 'Scan selected' action for a ticked batch. Store every scan result with the timestamp it was fetched, show that timestamp on the row so people can judge freshness, and reuse the stored result instead of rescanning unless the user explicitly refreshes. JobsPipe caches stack-scan results for about 14 days, so treat a stack column older than that as stale and worth refreshing. Before any scan action runs, tell the user how many scans, and therefore how many credits, it will spend.

I want to filter the board to accounts whose hiring lands in the departments my product serves, with that department set configurable in the app rather than hard-coded. I want to sort by signal strength, computed from the volume of open roles, how well the departments match my configured set, and how senior the roles are, and I want that score shown as a simple explainable number rather than a black box. Critically, keep zero-signal accounts visible with an explicit zero instead of filtering them out, so I can see that coverage is real rather than cherry-picked. A toggle to hide them is fine, but showing them is the default.

Every row needs a 'Build the expansion case' button that kicks off a background agent for that one account. The agent pulls that company's recent postings with JobsPipe Search Job Postings, scans their stack with JobsPipe Scan Domain Technology Stack, then writes a short brief covering what the company appears to be building, which teams are growing, what the stack suggests about how they work, and why that matters to us specifically, closing with two or three concrete talking points the account owner can use. It then files the brief onto the company record as a HubSpot note with Create Note, opens a follow-up for the account owner with Create Task using a due date a few days out and the account owner as assignee, and stamps a hiring-signal property on the company with Update Company carrying the open-role count, the top hiring department and the date of the scan.

Show the agent's progress on the row while it runs, and when it finishes show the brief inside the app alongside links to the created note and task, so nobody has to switch to HubSpot to confirm it worked. Keep a per-account history of briefs with who ran them and when, so two account managers do not commission the same research twice. If the agent fails partway, report which of the three writes succeeded rather than a generic error, since a filed note with no task is a very different situation from nothing happening at all.

The users are account managers, AEs and CS leads, so the board should be readable at a glance and default to the accounts owned by the signed-in user, with a toggle for all accounts. Keep each user's department configuration and their show-zero-signal preference sticky between visits.