playbook-hiring-surge

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

678|243|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/growthenginenowoslawski/coldoutboundskills --skill playbook-hiring-surge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-hiring-surge
Source: https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/playbooks/playbook-hiring-surge
Command: npx skills add https://github.com/growthenginenowoslawski/coldoutboundskills --skill playbook-hiring-surge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a credible "your team is growing" cold email requires department-level hiring evidence that is accurate, cheap to source, and phrased so prospects cannot disprove it. This playbook produces a copy-ready clause about people who started new roles in one department in the last six months, plus the headcount counts behind it, without paying for enrichment credits.

Core Features & Use Cases

  • Free department headcount counting: Uses Clay's free Find Employee Headcount by Criteria table action twice per department (total and last-6-months role starts) for sales and marketing.
  • Validated segment gate: Applies a growth-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 deterministic model prompt that outputs hiring_surge_line, a lowercase second-person clause completing "Noticed <line>.", and is forbidden from claiming anyone was hired because 28.3% of role starts are internal moves.
  • Use Case: A cold email agency wants to target companies scaling their sales team. It runs the Clay table build over 96,000 source rows, gates to roughly 5,000 qualified leads, and pushes each lead to a sequencer with a personalized hiring_surge_line variable.

Quick Start

Ask Claude to run the hiring surge playbook on your lead list to find companies whose sales or marketing teams had multiple people start new roles in the last six months and write the personalization line for each.

Frequently Asked Questions about playbook-hiring-surge

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

FAQPage Schema
How do I find companies that are hiring for cold email outreach?

Use Clay's free Find Employee Headcount by Criteria action twice per department: once for the department total and once with a six-month role-start recency filter. The ratio of recent starts to the pre-existing team, gated by absolute floors, identifies a genuine hiring surge.

How do I write a cold email first line about a company growing its team?

Write a lowercase second-person clause like "your sales team has 8 people who started new roles in the last six months" that completes "Noticed <line>." Never say the company hired anyone, because measured data shows 28.3% of role starts are internal promotions or moves.

Does the Clay headcount action cost credits?

Find Employee Headcount by Criteria is free on every Clay plan and is the engine of this playbook. Do not confuse it with similarly named third-party employee-count actions that charge around 5 credits per row even when they return nothing.

Why does the hiring surge gate return so few qualifying companies?

The floors (at least 2 role starts and a department of 4 or more) cut the qualifying segment from 14.6% to 5.2% by design. They were benched at 17/20 accuracy versus 10/20 without them, so plan roughly 96,000 source rows per 5,000-lead campaign.

What are the limitations of LinkedIn role-start data for hiring signals?

Role-start counts include promotions, re-titles, and lateral moves, so they are an upper bound on actual hires. The data also cannot date starts to a specific month, and bare-domain company matching can collide with same-named companies, requiring a headcount sanity guard.