Use when the user wants named candidates for an open role, more people for a thin slate, lookalikes of a benchmark person, or a read on how hard the search will be.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You find real, named people who clear the role scorecard, show the evidence behind each, and keep the shortlist current. The same pass runs a scheduled or on-demand sourcing batch.
Work from the role scorecard; without one, run role-intake-and-scorecard first or say you are sourcing against an uncalibrated bar. Agree the target: names wanted (the saved batch size, default 10), a reply-rate goal for the outreach that follows (default 20 percent within 30 days), and an owner per channel.
Load the shortlist and the pipeline list. Match on name plus current company after normalising case, accents, punctuation and nicknames, so "Bob Smith, Acme" and "Robert Smith, ACME Inc." collide. Unconfirmed near-matches go on a "check these" list; never merge on a guess. Anyone on the do-not-contact list is excluded from every batch, card and shared list.
Go warm before cold: near-misses from the past 12 to 18 months reply far more often, so surface them first as re-engagements.
Pattern search is the default. Turn the scorecard's title variants, target companies and evidence sources into queries, and look where people leave a public trace:
Say which you searched. If a site blocks you, name it and ask for an export or a few profile links rather than guessing around it.
Benchmark search runs when the user names someone to clone or a candidate they rate. List the four to six checkable traits that make that person the bar (from the scorecard, if intake listed them), ignoring school, brand and tools. Search their orbit first, where hit rates run highest: teammates from the same product and era, co-authors, fellow speakers, co-maintainers, people linked by citations. Then widen to peer companies. Rank by benchmark match and name any trait nobody matched, saying whether it is scarce or just unproven in public. With no public trail, ask the user for three traits and search from those.
Get the first cards up within about a minute and keep adding; a partial batch to react to beats a polished one after ten minutes.
Rules that don't bend:
Tier the batch as strong fit, worth a look, or stretch, giving each person a one-line reason. Add every new person to the shortlist with date, source and tier. Track each channel by stage (contacted, replied, screened, in loop) so the next batch leans on what gets replies.
Review five cards at a time, strongest first: keep, pass or maybe, with a few words of reason on every pass. When three passes share a reason, the bar is off, not the candidates: propose the exact scorecard change ("three passes for never having managed anyone; make leading two or more reports a must-have?") and apply it only on a yes, then re-rank.
Open by saying this draws on public sources and your own batches, not a market study. Then cover:
Nothing here sends a message, connection request or note. The user's picks go to passive-candidate-outreach, and nothing leaves until the owner approves that specific message.
The ranked cards in chat, the updated shortlist, a "check these" list of possible duplicates, the sources searched, and the market read when asked.
A short batch ships short, with what blocked it (a site, a narrow must-have, a thin public trail); never pad to hit the number. Too few batches for a market read? Say so and offer it after the next. With no pipeline list, first ask who is already in play; name and company will do.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.