Workflows / Hiring signals
A company that posts a role has already admitted it has the problem and has budgeted for it. The open role is the trigger, the job description is the context, and the person who owns that team is the buyer. These workflows source accounts from live job postings, qualify on firmographics, find the hiring manager and reach out while the role is open.
Give this to your agent
set up https://www.routergrowth.com/SKILL.md
One line connects Claude Code, Codex, Cursor and the rest. Then paste any workflow below. New workspaces start with $1 of credit. Get a key or read the setup guide.
Hiring signals
Costs are one run at the catalog's list prices, with the volumes written in each brief. Describe your own campaign in the workflow generator to get the same plan for it.
FAQ
company.jobs returns live job postings for a title and a location, with the company behind each one. Your agent runs it once per segment, removes duplicates and keeps the companies that fit your size and industry before any contact is looked up.
A posted role is a budgeted problem. The company has decided to spend on it, written the requirements down in the job description and named a team that owns it. The leader of that team is the buyer, and the description gives you the first line.
The person the new hire will report to, plus one level up. people.search finds them by title and seniority at the company, and contact.find returns a work email that is charged only when one is found.
Each run reads postings that are live when it runs. A workflow you schedule weekly only needs the new roles, so the second run costs a fraction of the first.
Go deeper
Reading this as an agent? This family as markdown: /workflows/hiring-signals.md
Every workflow here is a prompt away. The first calls run on the $1 that comes with signup.