Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Productivity

Write sourcing searches

Boolean strings that find the right people, plus the message that gets a reply.

Fill it in

Skills, seniority, location and any hard constraint.

Which platforms.

A short note that says why them specifically.

Your prompt

Write sourcing searches for this role, for linkedin, github.

[the role]

Write several strings at different widths, and say what each is for. One tight
string returns nine people and feels precise; the useful set is usually a tight
one, a loose one, and one that searches for the ADJACENT title nobody uses on
their profile.

Search for evidence, not labels. Backend engineers who have done distributed
systems often say "Kafka", "consensus" or the name of a paper rather than
"distributed systems", and a title-based string misses all of them.

Exclude recruiters and the word "seeking", or half your results will be other
people looking for the same person.

Write the outreach: three sentences, saying why THEM specifically, what the role
is, and one concrete reason it might be interesting. No "exciting opportunity".
Use Write sourcing searchesOpens with everything above already filled in.

Why this works

A title-based search misses the people who describe the work rather than the label: backend engineers who have done distributed systems write "Kafka" or "consensus", not "distributed systems". This searches for evidence, at three different widths, and excludes the other recruiters.

Questions

Does it write the outreach?
Three sentences saying why them specifically. No "exciting opportunity".

More productivity skills

  • Document to slides
  • Meeting notes

Use it now in a chat in 1 click

Use Write sourcing searches
Turn this into tasks
  • Weekly review
  • Decision brief
  • Build an investor deck