Write InMail Subject Lines Worth Testing
When to use it
Get a batch of subject lines to test against your default, instead of rewriting the same one forever.
The prompt
Write LinkedIn InMail subject lines for outreach to passive candidates about a {{Job Title}} role at {{Company Name}}. WHO THEY ARE: {{current title, company type, seniority}} WHAT'S ACTUALLY TRUE AND INTERESTING: {{the work, the stack, comp, remote policy, the team — only things I can back up in the message body}} MY CURRENT DEFAULT AND ITS OPEN RATE: {{if known}} HOW OFTEN THIS AUDIENCE GETS APPROACHED: {{constantly, rarely}} Give me: 1. Eight lines under 60 characters, each tagged with the angle it tests: curiosity, specificity, company name, compensation, or a direct ask. 2. For each, what the body then has to deliver, so the line doesn't turn out to be bait. 3. Which two to test first against my default, and why those two. 4. How many sends I need before a difference between them means anything. 5. The angles that would be wrong for this audience, and why — I'd rather see them ruled out than not considered. No "Exciting Opportunity", no false urgency, no invented mutual connections.
Tip
Point four is the one people skip. A subject line that wins over thirty sends has told you nothing, and acting on it is how a mediocre line becomes your default for a year.
How to use it
Paste the prompt into ChatGPT, Claude or whichever assistant you use, then replace every {{bracketed}} part with your own detail. The more specific and messier your input, the better the output — a model given raw notes has more to work with than one given a tidy summary you wrote first.
More Sourcing prompts
Open the full tool for all 87 prompts, the glossary, and the JD decoder.