Search update template
Show pipeline progress, market feedback, blockers, and the decisions the search needs.
A good search update does one job: show pipeline progress, what you are learning, and where the search needs a decision. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn pipeline data, candidate notes, outreach results, market feedback, blockers, and next steps into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the search update
- Search goal, role, and reporting period.
- Pipeline numbers by stage.
- Strong candidates, risks, and next actions.
- Market feedback, compensation signals, and blockers.
- Decisions needed and plan for the next period.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/search-update" skill.
How to create it with Send
Give Claude pipeline data, candidate notes, outreach results, market feedback, blockers, and next steps, plus any constraints, examples, or audience notes that matter. Ask it to create the search update with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether clients and hiring managers open it, come back to it, or share it internally. You can update the same link when details change.
Search update structure
Status
Role, period, pipeline, and topline progress.
Candidates
Notable candidates, stage, strengths, and concerns.
Market feedback
Outreach response, compensation signals, objections, and blockers.
Next steps
Decisions, owners, and plan for the next update.
Why send a search update as a page
Search updates are easier to trust when the pipeline, feedback, and decisions are in one place. Send gives clients and hiring managers a current link instead of a buried weekly email.