The Cognitive

Get the reply after “Seen”

The three rules every follow-up has to pass, a Claude skill that writes touches 2, 3 and 4 from your first message, and what to send back for every kind of reply. Built for the candidate who read your message and said nothing.

The three rules

Every follow-up passes all three, or it doesn't go out. “Bump” fails all three.

1

New info

One fact they didn't have yesterday. It goes in the first sentence. If you have nothing new, you have no reason to write.

Test: can you underline the new fact?
Just following up on my last message
2

Shorter

About half the words of the last one, down to a floor of about 15 words. Each touch asks less of their time than the one before.

Test: count the words. Is it about half?
A second full pitch, longer than the first
3

An easy out

End on a question where “no” or “not now” takes one line to say. It lets them answer without feeling cornered.

Test: could they answer in two words?
Let me know if you're interested!

Play the rally

Pick what happened after message one. Step through touches 2, 3 and 4 and watch each one pass the rules, or switch to “bump” follow-ups and watch them fail. People, companies and pay are made up.

What happened after message one

The three rules

new info a fact from the bankeasy out a question that's easy to say no to
100+ recruiters have shared their feedback
“juicebox, metaview, your looks faster and easier to use but with more relevant profiles”
LinkedIn message: compared with Juicebox and Metaview, faster and easier to use with more relevant profiles

Build it

Five steps. The first one happens before you send message one, and it's the one most people skip.

Hold facts back from message one

A follow-up needs new info, so message one can't spend all of it. Before you send, split what you know about the role into two piles: the one fact that earns the first reply goes in message one. Everything else goes into a fact bank for touches 2 to 4. You need at least three facts in the bank. Fewer than three, and the sequence runs dry by touch 3.

FACT BANK · [Role] · [Candidate first name] Message one was built on: "[the line from their profile]" Held back for the follow-ups (strongest first): 1. Pay: [range, plus bonus or equity] 2. What they'd own: [the project, the decision, the system they'd choose] 3. Who they'd work for: [name or title] · [one true thing about that person's work] 4. The team: [size, who's on it, how it's set up] 5. Where and when: [office days, travel, start date] 6. A real date: [interviews start / shortlist closes on ...] 7. What changed since message one: [anything new, or "nothing"] Never use: [anything confidential, anything you can't stand behind]

Good bank facts are specific and checkable. “Great culture” and “fast-growing” are not facts. “The team kept every rep through the reorg” is, if it's true.

Add the follow-up skill to Claude

Save this as SKILL.md in a folder called follow-up-writer, zip the folder, and add it in Claude's settings under Skills. If skills aren't open on your plan, paste the text into a Project's instructions.

--- name: follow-up-writer description: Writes follow-up touches 2, 3 and 4 for a candidate who has not replied to a recruiting message, all at once, from the first message and a bank of held-back facts. Also drafts the answer when they do reply. Use when a candidate has read and ignored a message, never opened it, replied once and gone quiet, or sent an auto-reply. --- # Follow-up writer You write follow-ups to candidates who have not replied. You write touches 2, 3 and 4 together, from message one, so the sequence holds together and never repeats itself. ## What I give you 1. Message one, as sent. 2. The fact bank: facts about the role that were NOT in message one. 3. What happened, one of: SEEN: they read it and did not reply. NOT OPENED: no sign they ever saw it. MAYBE: they replied once, then went quiet. I paste their reply and mine. AUTO-REPLY: an out-of-office. I paste it. 4. The candidate's first name and the profile line message one was built on. If the bank has fewer than 3 facts, stop and ask me for more. Never invent a fact. Never stretch one fact across two touches. ## The three rules. Every touch passes all three. 1. NEW INFO. Each touch carries one fact from the bank (two in touch 2 only if both are short). The fact goes in the first sentence. Quote it from the bank; do not dress it up. 2. SHORTER. Each touch is about half the words of the one before, with a floor of 15 words. Count the words and show the count. 3. EASY OUT. Each touch ends with a question where "no" or "not now" is easy to say. Put the out inside the question: "Worth a call, or not for you?" A question that only allows yes ("Let me know when you're free!") fails. ## Which fact goes where - Touch 2: the fact most likely to turn a no into a yes. Usually pay, if message one left it out. If pay can't be shared, use what they would own. - Touch 3: a person. Who they would work for or with, and one true thing about that person's work. - Touch 4: a real date (interviews start, shortlist closes) and the words "last note". If there is no real date, say "this is my last note" and nothing about time. - If the bank has a "what changed" fact, it beats the order above. Open with "One thing has changed:". ## By what happened - SEEN: write touches 2 to 4 as normal. Never mention that they read it. - NOT OPENED: message one never landed, so touch 2 is a new opener. New first line, new subject line if it's an email, the strongest fact up front, and no reference to message one. Touches 3 and 4 as normal. - MAYBE: their reply is your brief. Touch 2 answers anything they asked that is still open, then offers two times. Touch 3 offers an easier first step (a video call, a shorter call, a written summary). Touch 4 parks it with a time they choose: "If spring suits better, reply 'spring' and I'll write then." - AUTO-REPLY: the clock stops while they are away. Touch 2 goes 2 working days after their return date, opens "Welcome back", and is the short version of message one plus one new fact. A message sent while they were away does not count as a touch. ## Never write - "Just checking in", "bump", "following up", "circling back", "any update?", "did you see my message?", "I know you're busy", "floating this to the top", "hope you're well". - "I can see you read this" or anything else about them opening it. - A deadline that is not real. "Last chance". Guilt. - A fact that contradicts message one. If something changed, say so plainly. - Exclamation marks or emojis. - A fifth touch. After touch 4 the sequence is over. ## Same thread, same voice Touches 2 to 4 go in the same thread as message one, with the same sign-off. First name in touch 2 only. ## Output For each touch: TOUCH [n] · send on: [day] · [word count] words New info: "[the fact, as it appears in the bank]" Easy out: "[the closing question]" [the message] Then: Facts left in the bank: [list, or "none"] Then a check table, one row per touch: touch | new fact? | about half of the last? | easy out? | banned words? Every row must read yes, yes, yes, none. If a row fails, rewrite that touch before you show me anything. ## Days (my defaults; I may change them) Touch 2: 3 working days after message one. Touch 3: 5 working days after touch 2. Touch 4: 7 working days after touch 3. Never on a weekend. ## When they reply Stop the sequence. Do not send any touch that is still waiting. Then: - YES: two times in their time zone, what the call covers, how long it is. - NEEDS INFO: answer the question in the first line with the real fact, then one small ask. Never "happy to discuss on a call". - NOT NOW: ask which month would be worth a note, promise nothing sooner, log the month. - NOT INTERESTED: one line of thanks. No pitch. No reply to their reply. - STOP or REMOVE ME: one line confirming, then add them to my do-not-contact list. Never write to them again, from any inbox. - WRONG FIT: ask what would be worth hearing about. Log the answer. - ANGRY: one line of apology, stop, do-not-contact list. Write each reply in under 40 words.

Run it on one candidate

Paste this into a chat where the skill is on. Fill the brackets. One candidate per run: the sequence depends on what that person did.

Use the follow-up-writer skill. Candidate: [first name] Profile line message one was built on: "[the line]" What happened: [SEEN / NOT OPENED / MAYBE / AUTO-REPLY] [If MAYBE or AUTO-REPLY, paste their message here] Message one, as sent: [paste] Fact bank: [paste the bank from step 1] Write touches 2, 3 and 4 with the check table.

Read the check table first. If touch 3 is longer than touch 2, or touch 4 has no out, send it back with one line: “Touch 3 fails rule 2. Fix it.”

Set the days yourself

The skill suggests days, but you send each touch. These are the skill's defaults. Change them, then keep them the same for every candidate so you can tell what works.

Message oneDay 0
Touch 23 working days later
Touch 35 working days after touch 2
Touch 47 working days after touch 3. Then stop.
  • Never send on a weekend, and send in their morning, not yours.
  • Out of office? The clock stops. Start again 2 working days after they're back.
  • A reply of any kind ends the sequence. Delete the touches still waiting before you do anything else.
  • Write in your calendar or tracker the day each touch is due. Don't count on remembering.

Answer every kind of reply

The sequence exists to get a reply. When one comes, these are the answers. Swap in your own facts; keep the shape.

Yes“Sure, tell me more”

Two times in their time zone, what the call covers, how long. Don't make them propose a time.

Great. Tuesday 10:00 or Wednesday 2:00 your time, for 15 minutes? I'll cover the team, the pay and how they interview. If neither works, send me a time.
Needs info“What's the pay?” “Is it remote?”

The real answer in the first line. Then one small ask. Holding the answer back for a call reads as a dodge.

[$105k to $120k plus a 10% bonus.] [Two days a week in the office.] Does that work for a 15-minute call this week?
Not now“Maybe in a few months”

Ask which month, promise nothing sooner, and write the month down. Then honour it.

Understood. Is there a month when a note would be welcome? I'll write then and not before.
Not interested“Thanks, but no”

One line. No pitch, no “are you sure”. If they write back, answer; if not, the thread is done.

Thanks for telling me, [name]. I won't follow up on this one.
Stop“Remove me” · “Don't contact me”

Confirm in one line, add them to your do-not-contact list, and check that list before every send, from every inbox you use.

Done. You won't hear from me again.
Wrong fit“I don't do that work anymore”

Ask what would fit and log it. This is the reply that turns into your next placement.

Thanks, that helps. What would be worth hearing about? I'll only write if I have it.
Angry“How did you get this?”

Answer the question plainly, apologise once, stop.

From your public profile, because of your work on [X]. Sorry for the intrusion. I won't write again.

Lines that end a rally

Just checking inBumpCircling backAny update?Did you see my message?I know you're busyLast chanceI can see you read thisTouch 5
100+ recruiters have shared their feedback
“pretty good … especially for semiconductor, because it's much harder to find semiconductor talent”
Chat: search quality pretty good, especially for semiconductor talent

The wall

Claude can think, but it can't see people. Plain Claude has no profiles, so the line message one is built on has to come from you, copied by hand from each profile.

It also can't see your inbox. It doesn't know who opened, who replied or who went quiet, it can't send anything, and it can't read 40 replies and sort them. You paste every message in and carry every touch out yourself.

The same rally, two ways

Plain Claude, per candidate

  1. Find the person and copy the line from their profile that message one is built on.
  2. Write message one and a fact bank of three or more facts.
  3. Track who read it, who didn't, who auto-replied, in a sheet.
  4. Paste message one, the bank and what happened into Claude.
  5. Check every touch against the three rules.
  6. Find their email and send each touch from your inbox on the right day.
  7. Read every reply, sort it by hand, and keep a stop list you check before each send.

Same job in The Cognitive

  1. Describe who you want in a sentence or two. People come back ranked, and every card says why they fit, with a quote from their profile: the line message one needs.
  2. Reveal their email, tick the people, press Email and write the message. It goes from your own connected mailbox, personalised per person. Sending costs no credits.
  3. Replies are read for you and sorted: interested, needs information, not interested, opted out. Anyone who says yes is added to the role as a candidate. Anyone who asks to stop is never contacted again.
Keep the skill for touches 2 to 4. You send each one on the day you choose.
100+ recruiters have shared their feedback
“My front runner is … The Cognitive … Yours really beat JuiceBox, PIN, and Metaview”
LinkedIn message: my front runner is The Cognitive.ai; it really beat JuiceBox, PIN, Metaview and Fabric

Send message one from your own inbox

Make a free account, describe who you want in a sentence, and send message one from your own mailbox. Replies come back sorted, so you know who gets touch 2 and who never hears from you again.

7-day free trial, 50 sourcing credits, no card.