playbook-hiring-surge

Generates a cold-email clause about department-level role starts using Clay headcount counts.

Updated May 28, 2025
One-click install
npx skills add https://github.com/meloShaya/insteltech --skill playbook-hiring-surge-meloshaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-hiring-surge
Source: https://github.com/meloShaya/insteltech/tree/main/crm/library/skills/playbooks/playbook-hiring-surge
Command: npx skills add https://github.com/meloShaya/insteltech --skill playbook-hiring-surge-meloshaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cold email campaigns need a specific, verifiable personalization angle, and "your company is growing" is too vague to convert. This Skill produces a copy-ready clause stating how many people on one specific department started new roles in the last six months, backed by measured department-level headcount counts. ## Core Features & Use Cases - Department-level surge detection: Runs Clay's free Find Employee Headcount by Criteria action twice per department (total and last-6-months) to compute role-start counts for sales and marketing teams. - Validated gating logic: Applies a ratio check plus absolute floors (role_starts >= 2 && dept_total >= 4), benched at 17/20 versus 10/20 without, cutting the qualifying segment from 14.6% to 5.2%. - Locked copy prompt: A 502-token prompt that outputs hiring_surge_line, a lowercase second-person clause that slots into "Noticed <line>.", with a hard rule against claiming anyone was hired (28.3% of role starts are internal moves). - Use Case: A demand-gen agency building a 5,000-lead campaign sources roughly 96,000 rows, runs the free headcount columns, and pushes only gated rows with a personalized surge line into their sequencer. ## Quick Start Build the Clay table from clay-table.md and ask the assistant to generate hiring surge lines for a list of company domains.

Frequently Asked Questions about playbook-hiring-surge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I personalize cold emails based on hiring growth?

Count how many people on a target department started their current role in the last six months using Clay's free Find Employee Headcount by Criteria action, then phrase it as a second-person clause like "your sales team has 8 people who started new roles in the last six months".

How do I count department headcount changes in Clay for free?

Use the Find Employee Headcount by Criteria table action, which is free on every Clay plan. Run it once per department for the total, and again with current_role_max_months_since_start_date set to 6 for the recent count.

Can I say a company hired people based on LinkedIn role start dates?

No. Measured data shows 28.3% of recent role starts are internal promotions or moves, not external hires. Copy must say people "started new roles", never "hired" or "added", or recipients can disprove the claim instantly.

Why does Find Employee Headcount by Criteria return zero for a department?

A wrong job_functions enum value silently returns zero instead of erroring. Only "Sales" and "Marketing and Public Relations" are confirmed values; test any new value on 10 known-good companies or use free-text job_title_keywords.

What are the limitations of company-level headcount growth as a signal?

Company-level growth is too vague for copy because the reader cannot tell what it means for them. A measured pre-filter on headcount_growth >= 50 gives only a 1.28x lift while discarding 76% of TAM, so department-level counts are the usable signal.