How Chiefs Of Staff Use AI Browsers for Candidate Sourcing

This guide is for chiefs of staff who run candidate sourcing. It explains how an AI browser like Strawberry runs the workflow given the tools a chief of staff actually uses every day, what the output should look like, and where the workflow fits in the chief of staff's week.

Why this matters for chiefs of staff

A chief of staff spends time on this: shadow the CEO across every meeting, surface what is being lost in the noise, and turn decisions into shipped work. The pain that makes candidate sourcing feel slow is real: context lives in every channel at once; the chief of staff is the only one with cross-functional visibility but no time. The reason an AI browser helps is that chiefs of staff already use multiple surfaces (Notion, Gmail, Slack, Google Workspace, the company CRM and analytics tools) to do this work, and the browser is the only tool that can read across all of them and produce a finished output.

What success looks like

The goal of candidate sourcing is to build a shortlist of 10-30 candidates who match the role and have at least one signal of openness. For a chief of staff, success metric is concrete: 30% reply rate to first outreach, 5+ first-call conversions per 30 sourced. A finished candidate sourcing run should look like this: an exec brief, a meeting recap with owners, or a synthesised view of cross-functional state.

Signals candidate sourcing needs

The workflow needs these signals: current role and tenure; recent role changes (often visible on LinkedIn); GitHub or content output for technical roles; company stage match (someone leaving a Series B is more likely to talk to a seed-stage co). For a chief of staff the practical question is which signals come from the tools already in the stack (Notion, Gmail, Slack, Google Workspace, the company CRM and analytics tools) versus what the browser has to fetch. Strawberry reads the in-stack tools through native integrations and uses the browser for the rest (LinkedIn, news, company websites, search). The chief of staff stays in one surface.

Paste-ready Strawberry prompt

I'm a chief of staff. Run candidate sourcing for me using Notion, Gmail, Slack and the browser, then save the draft.

What a finished candidate sourcing output looks like

Concrete example, not a placeholder:

Role: Founding Engineer (Stockholm or remote EU)
Candidate: Marek Novak - Senior Engineer @ Klarna, 4 years
Fit: 5/5 (worked on payment systems, contributed to Rust open source, recent talk on type-safe APIs)
Opening line: noticed his RustConf talk on type-safe API contracts and our backend lead's tweet about Marek's library
Contact: LinkedIn DM + GitHub email

When this works, and when it does not

This workflow is right for chiefs of staff when the work is repeatable and crosses multiple tools. It is wrong when anything that requires the CoS to become the bottleneck on a function that should own itself. In that case, the chief of staff should keep doing the work manually until the pattern is clear enough to automate.

Three mistakes to avoid

Spray-and-pray DMs that mention nothing specific
Missing the obvious signals (someone just posted 'thinking about a change')
No quality bar - putting 200 names on the list to look productive

Caveats

Strawberry holds back on sending email, updating CRM records, or changing shared systems until a human approves the action. Treat the agent as a fast first-draft author, not an autopilot.

How chiefs of staff run candidate sourcing with Strawberry

1 Inputs

Tools

Chiefs Of Staff typical stack: Notion, Gmail, Slack.

2 Augment

Browser

Public web, LinkedIn, news, search fill the gaps the stack does not store.

3 Draft

Compose

Synthesise into the candidate sourcing shape that a chief of staff can ship.

4 Review

Human

Approve before any external action; save to system of record.

FAQ

Is this useful for a chief of staff who already has a workflow?

Yes - the question is which part of the workflow is the bottleneck. If it is research, data transfer, or writing the first draft, that is where Strawberry helps. The chief of staff keeps the judgement calls and final approvals.

What tools does the chief of staff need to connect?

The most common stack for chiefs of staff: Notion, Gmail, Slack, Google Workspace, the company CRM and analytics tools. The browser handles everything else (LinkedIn, news, search) without extra setup.

What is the biggest mistake to avoid?

Spray-and-pray DMs that mention nothing specific.

Run candidate sourcing in 10 minutes with Strawberry for chiefs of staff

Pull live context

Open Strawberry and let it read what is already on the screen plus the Notion, Gmail, Slack tabs you usually work from. A chief of staff should not have to re-type the company name, role, or stage - the browser sees it.
Name the candidate sourcing target

Tell Strawberry the specific subject of this run: the prospect, account, candidate, or partner you want to source candidates. One sentence is enough; the agent asks back if the scope is unclear.
Let the agent gather signals

Strawberry walks the public web (LinkedIn, company site, news, job boards) and pulls the signals this workflow needs: current role and tenure; recent role changes (often visible on LinkedIn); GitHub or content output for technical roles. It keeps source links so the chief of staff can verify.
Review the draft

Strawberry returns the output in the exact shape a chief of staff can ship: A shortlist with one row per candidate: name, current role, target role fit (1-5), one personalised opening line, contact link. No padding, no buried "I could not find" sections - missing signals get flagged explicitly.
Approve and log

Nothing external goes out until the chief of staff approves it. Send the email, update the CRM, post the message - whatever the next step is - then Strawberry logs the run so the next candidate sourcing on a similar subject reuses the context.

Paste-ready prompt for candidate sourcing with Strawberry as a chief of staff

You are helping a chief of staff source candidates.

Subject: [name of the company, person, account, or partner]
Goal: build a shortlist of 10-30 candidates who match the role and have at least one signal of openness
Definition of done: a A shortlist with one row per candidate: name, current role, target role fit (1-5), one personalised opening line, contact link.

Inputs you can use:
- Notion
- Gmail
- Slack
- Google Workspace
- public web (LinkedIn, company site, news, job boards, podcasts)

Signals I care about:
- current role and tenure
- recent role changes (often visible on LinkedIn)
- GitHub or content output for technical roles
- company stage match (someone leaving a Series B is more likely to talk to a seed-stage co)
- geo match for hybrid roles

Output format (mirror this shape):
- Role: Founding Engineer (Stockholm or remote EU)
- Candidate: Marek Novak - Senior Engineer @ Klarna, 4 years
- Fit: 5/5 (worked on payment systems, contributed to Rust open source, recent talk on type-safe APIs)
- source links for every claim
- flag anything you could not verify - do not guess

Constraints:
- do not send email, update CRM, or post anything until I approve
- use the live tabs I already have open as primary context
- if the subject is ambiguous, ask me one question instead of assuming

Copy into a fresh Strawberry chat. Replace the bracketed bits with your real subject.

When this is NOT a fit for chiefs of staff

This workflow earns its keep when chiefs of staff run candidate sourcing more than once a week and the stack is mostly online. Skip it when the run depends on hand-held domain context Strawberry cannot see - private investor calls, off-the-record conversations, paywalled databases the chief of staff has special access to. Run it manually those times and capture the playbook for the next iteration.

The other anti-pattern: using candidate sourcing to flatter a senior buyer with surface-level facts they already know. chiefs of staff that scale this workflow always pair Strawberry with a sharp opinion or hypothesis the chief of staff brings. The agent is great at gathering. It is not great at picking a fight.

3 mistakes that kill the run

spray-and-pray DMs that mention nothing specific
missing the obvious signals (someone just posted 'thinking about a change')
no quality bar - putting 200 names on the list to look productive

Honest tradeoff

Strawberry will not invent missing signals. If a partner does not have a public hiring page, the agent says so - it does not pad the brief with guesses. That is the right behaviour, but it means a chief of staff sometimes sees a shorter output than expected. The fix is upstream: feed it better sources, or accept that this subject is information-sparse and move on. Pretending the signal exists is what gets chiefs of staff into trouble; an empty section is a feature, not a bug.

What a finished output looks like

A chief of staff should be able to send the result to the buyer (recruiter, founder hiring, hiring manager) without a major rewrite. If the draft needs more than ten minutes of editing, that means the input scope was too broad or the wrong signals were prioritised. Re-run with a tighter subject. Concretely, a strong candidate sourcing brief includes:

Role: Founding Engineer (Stockholm or remote EU)
Candidate: Marek Novak - Senior Engineer @ Klarna, 4 years
Fit: 5/5 (worked on payment systems, contributed to Rust open source, recent talk on type-safe APIs)
Opening line: noticed his RustConf talk on type-safe API contracts and our backend lead's tweet about Marek's library

Anything thinner than that and the run is not done.