Playbook · Signal motion
Hiring spikes: reading the org chart between the lines
5+ open roles in a function in 30 days is the signal; what those roles tell you about the org's actual investment thesis is the play. Reading the role mix (ICs vs. managers, generalists vs. specialists) to predict what tools they'll buy next.
01The signal
Summary
5+ open roles in a function in 30 days is the signal; what those roles tell you about the org's actual investment thesis is the play. Reading the role mix (ICs vs. managers, generalists vs. specialists) to predict what tools they'll buy next.
02Cadence
The step-by-step rhythm we use to run this play. Skipping steps usually loses more than it saves — the asymmetric spacing is part of why it works.
Day 14
email
Anchor on the spike + name the operational reality (onboarding load, tool gaps, cohort-ramp problem)
Day 21
linkedin
Share a relevant artifact (onboarding checklist, ramp framework)
Day 30
email
Offer a specific framework for the post-hire-wave gap
Day 42
email
Break-up
03Expected outcome
Outcome: 12-18% reply rate. Best when the role-mix reading is specific ('your 8 backend reqs + 1 staff hire = you're building infra')
Success metric: Reply with a specific role-related question — opens the conversation.
04Anti-patterns · do not run this when
- Do not pitch recruiting tools — too obvious, low signal
- Do not assume hiring = buying — sometimes it's just hiring
- Do not skip the role-mix reading — generic 'congrats on the hiring' loses
Playbook entry · ships as-of {date('M Y')}. Operator-written, no theory inflation. If you've run this play and the numbers don't match yours — or the rhythm needs a tweak — write to [email protected] and we'll revise.
Signal-anchored outbound, no theater
Run this play on every account in your CRM.
Connect a CRM. Mama detects the trigger, scores the fit, and drafts the first message in the rhythm above. Free up to 100 accounts. No card.