From open role to a shortlist worth defending
“I have an open role and thirty InMail credits this month.” Four steps, run in order, with the credit budget treated as a first-class constraint rather than something you discover in week three.
Each step's output is the next step's input
Read the In and Out lines down the page. Where they do not line up, the workflow has a gap — that is the test, and it is why these are written this way rather than as a diagram.
Decide where to look20 min, once per role
- In
- The job description and the geography
- Out
- Source archetypes, the titles the role is called at each, and a pool verdict
Build the searches5 min each
- In
- One archetype at a time
- Out
- A tight and a broad Boolean string per archetype
Shortlist with evidence10 min per batch
- In
- The job description and 20–40 pasted profiles
- Out
- A ranked shortlist with evidence per requirement and a screening question each
Reach out3 min each
- In
- One shortlisted candidate
- Out
- Subject line, message, and the reply for "not looking"
What you end up holding
Each step leaves something behind. These are the things worth keeping between runs.
Source archetypes, the titles the role is called at each, and a pool verdict
A tight and a broad Boolean string per archetype
A ranked shortlist with evidence per requirement and a screening question each
Subject line, message, and the reply for "not looking"
The reference behind this workflow
The two numbers this whole workflow is sized against.
Run it with the context already loaded
Every step goes faster inside a Project that already knows your ICP, your product and the platform limits. That is what the packs are.