Hiring-signal outbound

A job posting is a company saying in public that it has budget, a gap and a manager who admitted the gap in writing. This skill turns that into a verified contact list in four calls, and releases the calls that find nothing instead of billing them.

Before you start

• Load the core routergrowth skill (https://www.routergrowth.com/SKILL.md) if it is not loaded. Confirm access with the free balance tool or routergrowth balance, without printing credentials.
• Ask for three things if the user did not give them: the role that implies the problem (the title you would search for), the geography, and the buyer persona (the title and seniority that signs).
• Inspect the four capabilities once and show the prices before the first billable run: routergrowth inspect -c company.jobs, then people.search, contact.find, contact.verify. Quote the list as a whole: N accounts, roughly N buyers, roughly N contact lookups. Get a yes on the total.

Steps

1. Accounts from postings

Search postings by title and location, not by company. The account list is the side effect.

routergrowth run -c company.jobs -i '{"query":"lifecycle marketing manager","location":"United States","posted_within":"30d","limit":50}' --max-cost 0.30 --wait 60 -o jobs.json

Keep company, domain, title, location and posted date. Dedupe on domain. Sort by date: newest posting first is the queue.

Optional stacking signals, only when the user wants a tighter list: company.funding (a round inside 90 days is budget that must be spent) and company.technologies (running the tool you replace, or the one you integrate with). Run them on the deduped domains and score: hiring plus funded plus running the tool is not a cold lead.

2. The buyer at each account

The hiring manager is rarely the buyer. Search by seniority and function inside each company:

routergrowth run -c people.search -i '{"companies":["acme.com"],"titles":["VP Marketing","Head of Growth"],"seniority":["vp","head","director"],"limit":2}' --max-cost 0.10 --wait 60

Two people per account at most. Keep first name, last name, title, company domain and the LinkedIn URL when it comes back.

3. Work email

routergrowth run -c contact.find -i '{"first_name":"Alex","last_name":"Rivera","company_domain":"acme.com"}' --max-cost 0.10

Auto routing waterfalls across providers and charges only the one that delivers. A no-match is released, not billed, so a list with a 60% hit rate costs 60% of a list. Over MCP, send all rows in one batch_run with max_cost per item and max_total_cost for the batch. Over the CLI, loop run and collect run IDs.

Before the lookups, run the free dedupe pass: routergrowth history --file people.txt (one email, name or LinkedIn URL per line) says who was already contacted or already enriched, and returns the reusable result so you do not pay twice.

4. Verify before anyone sends

routergrowth run -c contact.verify -i '{"email":"alex.rivera@acme.com"}' --max-cost 0.02

Keep valid. Drop invalid. Hold catch_all and unknown in a separate column and say so: a catch-all domain accepts everything, so the address is unproven, not clean.

Rules

• Inspect once per capability, quote the whole list, then run. Do not re-ask between rows once the user approved the total.
• max_cost on every run. Keep the first company.jobs limit at 50 or below until the user has seen one result.
• Stop and ask before a batch over about $1 unless the user asked for that volume.
• Never present sandbox (rg_test_) output as real data. Every row carries the run ID that produced it.
• Do not email anyone from this skill. Sending is the cold-email-pipeline skill, which starts with its own gate.

Human gate

Before handing off to any outreach: show the account count, the contact count by verification status, the total charged, and five sample rows. Wait.

Output

A CSV with one row per contact: company, domain, posting_title, posted_at, first_name, last_name, title, linkedin_url, email, verify_status, provider, run_id, charge. Plus the totals: accounts found, buyers found, emails found, emails valid, total charged. Misses are listed at the bottom with the reason, so the user can see what was filtered and why.