Turn an afternoon of LinkedIn research into a finished list

Profiles in, structured list out

Give a companion your criteria, “heads of ops at Series B logistics companies” or “backend engineers with marketplace experience open to Copenhagen”, and it works through the profiles the way you would, pulling out role, tenure, signals, fit notes and source links.

For recruiters that is the slate-building grind compressed into a review pass, the workflow behind our recruiting use case. For sellers it is top-of-funnel prospecting with a reason attached to every row.

How does profile context reach your other tools?

The profile you are reading needs to end up somewhere: the CRM record, the outreach doc, the interview brief. A companion reads the LinkedIn tab and stages the update in the destination, an enriched contact, a note on the deal, a row in the tracking sheet, without you re-typing anything.

Before a call it works in reverse, assembling who you are meeting from their public profile plus your own email history, so the first two minutes are not spent asking what their headline already answers.

Outreach drafts that read like you did the homework

The difference between ignored and answered outreach is specificity.

A companion drafts connection notes and messages grounded in what it actually read, the career move, the post, the mutual context, and queues them for you.

You edit, you send. The same drafting works for replies: when a conversation starts, the companion proposes the next message with your pipeline context already in it.

Why is the browser the right place for this?

A companion uses your real session, sees only what your account can see, works at a human pace, and stops at an approval card on the consequential steps.

It is also better at the job, because the agent that reads the profile can update the CRM, draft the email and file the sheet in the same pass, across your other tabs. A LinkedIn account can additionally be authorized as a connected account for whatever the LinkedIn API exposes, with the credential kept encrypted outside Strawberry.

Frequently asked questions