Lever StrawberryClean up your Lever pipeline with an AI agent
Forty opportunities read in one pass, the eleven that have not moved in three weeks named, each sorted into the archive reason your team already uses.
Forty opportunities are parked in Recruiter Screen. Eleven have not moved in three weeks, four are people you already spoke to and liked, and one is a referral from your CTO that nobody answered.
A companion reads all forty. It resolves your real stage ids first, pulls every opportunity with its note history, and hands back the stalled ones sorted into the labels you would have picked: wrong level, timing, went elsewhere. Then it posts a note on each.
| Job | Lever itself | A Strawberry companion |
|---|---|---|
| Read a profile and its history | You, clicking | Natively, in bulk, with the note history |
| Research a person on the open web | Not its job | In your signed-in browser session |
| Sort a stalled pipeline into your own archive reasons | You, one profile at a time | One pass, with the reason against each name |
| Have the hiring-manager brief ready before the sync | You assemble it | A routine that runs before the meeting |
| Write to the opportunity record | Full record editing | Notes only, as a named user |
| Nurture campaigns and candidate email | Native | Never sends to candidates |
Where did the candidates in Recruiter Screen go?
The pass starts with the stage list, because guessing stage names is how an agent reads the wrong bucket. With real stage ids in hand, a companion lists the opportunities in each, reads the profile and the note history, and splits the stalled from the quiet.
It also pulls your configured archive reasons, so the list arrives labelled the way you would have labelled it. You do the archiving, in Lever, where a bulk mistake cannot happen.
Source a candidate and land the research on the record
The useful half of sourcing happens outside the ATS: reading someone’s public work, checking whether the two-year gap is a sabbatical or a stealth startup, finding the conference talk that says more than the CV. A companion does that in the accounts you are already signed into.
It then checks the person against Lever by email, so you learn you spoke to them in March before writing the outreach. If they exist, the research lands as a note under a real recruiter’s name. If not, it goes into your doc as a reviewed list. Pair it with candidate research.
What does a companion write, and what does it never touch?
The whole surface in three lines: what it reads, the one thing it writes, what it never touches.
- Reads: postings and a single posting in full, opportunities and a single opportunity with its stage, the configured pipeline stages, archive reasons, and the user directory.
- Writes: one note on an opportunity, visible to the rest of the recruiting team, performed as a specific Lever user.
- Never: creating opportunities, advancing or archiving candidates, sending candidate email, or touching offers.
Get the hiring-manager brief before the sync
The weekly sync usually opens with someone reading the pipeline aloud off a shared screen.
Set a routine instead: the posting in full, every opportunity grouped by stage, who has been waiting longest, and the two candidates whose public work deserves the manager’s attention.
Keep Awake finishes that run with the lid shut, so the brief exists before the meeting rather than during it. The recurring mechanics are in operations, aimed at one posting.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents