The Cognitive

The first message candidates reply to

"Exciting opportunity" misses before it reaches the rim. A first message that gets a reply has three parts: their work, the reason, one small ask. Below are the rules for each part, a shot clock that grades your draft, twelve openers by role type, and a Claude skill that writes the first line from a profile.

Every first message has three parts

Read these as rules, not tips. A message that breaks one of them rarely gets read to the end.

Their work

One line about something they built or ran.

  • Name the thing, not the skill. "The move of your billing jobs onto Kafka" is their work. "Your Kafka experience" is a keyword.
  • Take it from their profile, in their words where you can. If you can't point to the line, don't write it.
  • Use the current or last role. A line from eight years ago tells them you skimmed to the bottom.
  • No praise words: impressive, amazing, great background, rockstar. The fact does the praising.
  • No numbers they didn't write. If the profile says "40 warehouses", you can say it. If it doesn't, don't guess one.
  • Thin profile with only a title and company? Use the company's work in one plain clause ("you're on the team that runs the checkout at [company]") and keep the whole message shorter.
ClankI came across your profile and was really impressed by your background in data.
SwishYou moved the nightly billing jobs at [company] onto Kafka streams, and you're on call for them.

The reason

Why this role, for them, now.

  • Link their thing to one thing in the role. Pick one: the same problem at a bigger size, the next step up, or something their current seat can't give them (a new build, ownership, a shorter commute, less travel).
  • The "now" must be true and about the role: the team is hiring its first one, the build starts in spring, the seat is new. Never about their life.
  • Never say why you think they'd leave. "Since your manager left" or "after the layoffs" reads as being watched.
  • One sentence. If it needs two, the reason is weak. Find a better one.
  • If you can share the pay range, put it here. It answers the first question they'll have.
ClankMy client is a fast-growing, well-funded leader in their space with a great culture.
SwishA freight company in Chicago starts the same move for its warehouse data in January, and you'd lead it.

One small ask

A yes/no question, not a call.

  • They can answer it in one word from their phone.
  • Never a call, a time slot, "15 minutes", a calendar link or "send me your CV". Those are the second step.
  • Offer the next small thing: the two-line brief, the company name, the pay range.
  • One question mark in the whole message. Two questions get zero answers.
  • For roles where place or shift decides it, ask that: "Is [town] still home?" A "no" saves you both a week.
ClankDo you have 15 minutes for a quick call this week? Here's my calendar.
SwishWorth sending you the two-line brief?

The shot clock

Pick a draft or write your own. The clock counts down from 90 words, the limit for a first message. Shoot it and see what goes in.

Grade a first message · drafts made up

It checks the three parts, the banned openers and the length, and tells you why it scored.

90WORDS LEFT
READY

    A rough check: it reads words, not meaning. It can tell you a part is missing. Claude, with the skill below, does the real read.

    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

    Twelve openers, by role type

    Each one says where to look on the profile for the work line, then gives a three-part message to fill in. Replace every [bracket] with a fact from the profile or the role. If you can't fill a bracket truthfully, pick another line.

    1Software engineerLook for: a named system or feature they built, a migration, what it serves, whether they're on call for it.
    Hi [name], you built [system] at [company], the part that [what it does for its users]. [Hiring company] is rebuilding [the same kind of system] and you'd own it from the first commit. Worth a two-line brief?
    2Data engineerLook for: the pipelines they run (what feeds what), a warehouse move, the volume they wrote down.
    Hi [name], you run the [pipeline] that feeds [team or product] at [company]. [Hiring company] is moving [its data] onto [stack] next quarter and wants someone who has done that move once already. Open to hearing which company?
    3DevOps or site reliabilityLook for: what they keep running, a cloud move, on-call duty, cost or uptime work.
    Hi [name], you took [company]'s [platform] onto [new platform] and you're on call for it. The team I'm hiring for starts that move in [month], and nobody there has done it before. Want the short version?
    4Product managerLook for: what they shipped, for which customers, what changed after. B2B or consumer. Which product area.
    Hi [name], you shipped [feature or product] for [customer type] at [company]. [Hiring company] needs a PM for [area] with the same buyers at an earlier stage, and you'd set the roadmap instead of inheriting one. Worth a look?
    5Product designerLook for: the flow or product they designed, research they ran, design system work, the case studies in their portfolio.
    Hi [name], you redesigned [flow] at [company], and your portfolio walks through [the hard part]. [Hiring company] has the same problem in [their flow] and no designer on it yet, so you'd be the first. Want me to send the brief?
    6Account executiveLook for: segment (small business, mid-market, enterprise), what they sell and to whom, new logos or expansion, any deal size or quota line they chose to write.
    Hi [name], you sell [product type] to [buyer] in [segment] at [company], mostly new logos. [Hiring company] sells to the same buyers, and the [territory] patch has nobody on it today, so you'd start with open ground. Is new business still the work you want?
    7Customer success managerLook for: the book they look after (segment, number of accounts), renewals or onboarding, any retention line.
    Hi [name], you look after [book] at [company] and run their renewals. [Hiring company] is building its first success team for [customer type], and you'd write how it works. Worth a short brief?
    8Marketing managerLook for: the channel or program they own, a launch they ran, budgets or results they wrote down.
    Hi [name], you run [channel or program] at [company], including the [launch] in [year]. [Hiring company] wants one person to own [channel] end to end, with the budget, and you'd report to [title]. Open to a read of the role?
    9Accountant or financeLook for: the close they run, audits, a systems change, number of entities, public or private company.
    Hi [name], you run the month-end close for [entities] at [company] and led the move to [system]. [Hiring company] is getting ready for its first audit and needs that same setup built, [work pattern] in [city]. Would that be worth a look?
    10Recruiter or talent partnerLook for: the roles they hire for, agency or in-house, the markets and levels, any volume they wrote down.
    Hi [name], you hire [role types] for [company], mostly [level] in [market]. [Hiring company] is opening [number] of those seats next year, and you'd run that desk. Is in-house still where you want to be?
    11Manufacturing or plant engineerLook for: the line or process, the product, start-ups they stayed through, cost or yield projects, which site.
    Hi [name], you brought up [line or process] at the [town] plant and stayed through the start-up. [Hiring company] is installing [a similar line] in [nearby town] next year, and you'd own it from install. Is [town] still home?
    12Nurse or clinicalLook for: the unit, the patient type, the shift, charge or preceptor duties, the licences the role requires (not every badge).
    Hi [name], you've worked [unit] at [hospital] and you're charge nurse on [shift]. [Hiring hospital] has a [unit] role on [shift pattern], [distance] from you. Would that schedule work for you?

    The skill that writes the first line

    This gives Claude the three parts as rules, so you paste a profile and a role and get one message back with the line it used and anything risky.

    1. Save the text below as SKILL.md in a folder named first-message.
    2. In the Claude app: zip the folder and upload it under Settings, Capabilities, Skills. In Claude Code: put the folder in ~/.claude/skills/. If skills aren't open on your plan, paste the text into a Project's instructions.
    3. Then say: "First message for this person." Paste the role brief and the profile under it.
    --- name: first-message description: Writes a first message to a candidate from their profile and a role brief, in three parts (their work, the reason, one small ask). Use when I paste a profile and ask for a first message, InMail or opener. --- # First message ## Inputs - PROFILE: the candidate's profile text, pasted. - ROLE: the role brief: the job, the place, pay if I can share it, and the one or two things that make this role different. If either is missing, ask for it. Never write a message from a title alone. ## Step 1. Find the line Read the profile, newest role first. Find the one piece of work this person built, ran, sold, fixed or shipped that is closest to the role. - It must be a line you can quote from the profile. - Prefer the current or last role. Use an older line only if nothing recent fits, and say so under RISK. - Prefer work with a named thing (a system, product, line, account type, unit) over a skill or a software name. - If the profile has no such line (title and company only), write THIN PROFILE under RISK and use what the company does, in one plain clause. Never invent their work. ## Step 2. Write the three parts 1. THEIR WORK: one sentence that starts with "You". Names the thing from Step 1 in plain words. No praise words (impressive, amazing, great, talented, rockstar). No number that is not in the profile. 2. THE REASON: one sentence. Links their work to one thing in the role: the same problem at a bigger size, the next step up, or something their current seat can't give. The reason must be true and about the role. Never mention their manager, their company's troubles, how long they have been in the seat, or anything personal. 3. THE ASK: one yes/no question, under 12 words, that they can answer in one word. Never a call, a meeting, a time, a CV or a link. ## Step 3. Check before you show me - 90 words or fewer. Three to five sentences. No bullet points. No links. - None of these phrases: "exciting opportunity", "came across your profile", "hope this finds you well", "quick call", "15 minutes", "new opportunities", "perfect fit", "great fit", "reach out", "touch base". - The message does not start with "I". - One question mark in the whole message. - Every fact about the person is in the profile. If it isn't, delete it. ## Output SUBJECT: 2 to 6 words, about their work or the role. MESSAGE: Hi [first name], then the three parts, ready to send. LINE USED: the profile line from Step 1, quoted. RISK: anything a reader could catch you on (an old line, a thin profile, a guess about the role). Write "none" if there is none. Write one message. If I ask for options, write two more that each use a different line from the profile, not a reworded version of the first.
    What comes back · person and role made up
    SUBJECT: billing on Kafka → Chicago
    MESSAGE: Hi Tom, you moved the nightly billing jobs at your payments company onto Kafka streams, and you're on call for them. A freight company in Chicago starts the same move for its warehouse data in January, and you'd lead it, at $160k to $185k. Worth sending you the two-line brief?
    LINE USED: "Moved nightly billing batch jobs to Kafka streams; on-call owner."
    RISK: none

    Traps and edge cases

    If this, then that. Keep these next to the skill.

    Same company twiceIf you've written to someone at the same company this month, change the work line and the reason. Colleagues compare messages.
    They replied "not now"Thank them, ask one thing: "Fine to check back in [season]?" Then do it. Don't pitch again in the reply.
    Confidential searchSay what the company does and its size, never "my client is confidential" alone. The reason part still needs a real reason.
    Senior peopleShorter, not longer. Two sentences and the ask. They read for the reason, not the company story.
    Agency recruiterName the industry and the work, not "a leading firm". If the hiring company allows it, name it. Unnamed reads as spam.
    Open to Work banner onStill lead with their work. Their inbox fills with messages that only mention the banner. The work line is how yours stands out.
    Their line is from a side projectFine if it's the closest work to the role. Say "your [project]" so they know you read it, and put the main job in the reason.
    No replyA follow-up adds new information and is shorter than the first message. Never "just bumping this".
    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. The skill only works on what you paste, so every message starts with you finding the person, opening their profile and copying it in, one at a time.

    And the message stays in the chat. You still copy it into your inbox, send it, and keep track of who replied and what they said.

    The same first message, two ways

    Plain Claude, for every person

    1. Search for people somewhere else and open each profile.
    2. Copy the profile and paste it into Claude with the role brief.
    3. Read the draft and check the work line against the profile.
    4. Run the shot clock rules: three parts, banned openers, one question, under 90 words.
    5. Copy the message into your inbox and find their email.
    6. Send it, then note who you sent it to.
    7. Watch for replies and sort them by hand.

    Same job in The Cognitive

    1. Describe who you want in a sentence or two. Every person comes back ranked, with why they fit and a quote from their profile: the line your first message needs.
    2. Tick the people, press Email and write the message. It's personalised per person and goes from your own connected mailbox. Sending costs no credits.
    3. Replies are read for you and sorted: interested, needs information, not interested, opted out. A yes is added to the role as a candidate. Anyone who asks to stop is never contacted again.
    4. Prefer Claude? Add The Cognitive as a connector in Claude: https://app.thecognitive.io/mcp It asks before anything that spends credits or contacts someone.
    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

    Write the first line from a real profile

    Describe who you want in a sentence. Every person comes back with why they fit and a quote from their profile, so the work line is already there. Then send from your own inbox.

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