Built for · Recruiting & people
Less admin. More hires.
Bash screens, schedules, briefs the panel, drafts the offer.
Nami keeps every candidate and what the panel said.
Bash · on its own machineWorking
YouSend Ines the offer
Pull the approved band and start date off the req
Build the offer doc from the template — comp, equity, start
Write the note the way Owen writes, three sentencesHold the whole thing for your wordHeld · waiting on you
Offer, drafted and unsent“Ines — the panel was unanimous, and Marina has not stopped talking about your payments walkthrough. We would love you here. The numbers are attached, and you can call me on any of it.”
Held for your wordWatch it work
WhatsAppBrief Owen on the backend candidate↵Delegate
Read Ines Marchetti’s profile — seven years, two payments teams
Skim the repos she linked — what she actually writesPull the screen notes and her scorecardSend Owen one page: fit, gaps, the question to ask
One ask. The whole loop.
Pick a delegation — Bash runs the loop end to end, held where it matters.
WhatsAppBrief Owen on the backend candidate↵DelegateRead Ines Marchetti’s profile — seven years, two payments teamsSkim the repos she linked — what she actually writesPull the screen notes and her scorecardSend Owen one page: fit, gaps, the question to askBrief · ready in Owen’s inbox
Ines Marchetti · Senior Backend
Seven years, both of them on payments at scale — 40m authorisations a day at Kessel. She has never had direct reports, and this role asks for two by June. Ask her what she would do in her first month with an on-call rota she inherited.
Done · 14 seconds
From wherever you areWhatsApp11:06 AM
#hiringMon 9:14GmailFwd
or press ⌃ ctrl anywhere on your Mac
Text it between interviews. It’s done before the next one.
Between interviews — WhatsApp, Slack, Gmail, iMessage, Telegram, or a key on your desk.
WhatsApp11:06 AMwhere are we with ines11:06 AM
All four scorecards are in. Unanimous yes — Marina 5, the rest 4. Offer doc is built at the approved band with Owen’s note. Held for you.11:06 AM · 9 seconds
#hiringMon 9:14@Bash book Ines’s panel for Tue and Wed9:14 AM
Four invites out, two backup slots held Thursday. Ines has the schedule in CET with every name and the question each one owns.9:20 AM
GmailFwdFwd: Re: Can we move Wednesday? — can you handle this?3:22 PM
Thursday 09:00 works for all four. The reply to Ines is written and held for you — invites move when you say.3:23 PM
or press ⌃ ctrl anywhere on your MacSigned into your world
Works inside your stack, as you.
The ATS, the inbox, the calendar — and a thousand more, a click away.
LinkedInSource the shortlist, read the profile, catch what the CV hides.
GmailAnswer the candidate, draft the offer, send on your word.
Google CalendarFind the slots, book the panel, move it when life happens.
NotionKeep the pipeline, file the scorecard, run the onboarding checklist.
SlackChase the panel, post the debrief, open the new hire’s channels.
Google DocsWrite the job post, build the offer, share the brief.
ZoomRun the interview, pull the recap, file the scorecard.
WhatsAppAsk between interviews — the brief lands before the next one.
Google SheetsTrack the pipeline, check the band, count days in stage.
— and 1,000+ moreSee everything it connects to
Teams
Stripe
Salesforce
X
InstagramSay it like this
Delegate in plain words.
No setup, no syntax — it already knows your reqs, your panels, your voice.
Screen the twelve new applicants on the Senior Backend req against the scorecard, shortlist five, and give me one line each on why.
Screen
Book Ines’s four-person panel across Tuesday and Wednesday, send the invites with each stage, and email her the schedule in her timezone.
Panel
Draft the offer for Ines at the approved band with a warm three-sentence note from Owen. Hold it for me.
Offer
Chase the four scorecards from Ines’s panel, write the debrief, and post it to #hiring before Friday’s huddle.
Debrief
Run Nadia’s day one: channels, her week-one page, a buddy, and five meetings booked on Monday.
Day one
Rewrite the Senior Backend job post to sound like us, cut it to 300 words, and tell me which requirements are scaring people off.
Job post
Routines that fire themselvesFive days after the panel with no answer from us → a short, honest update drafted in your voice and held for your word.Notion → Gmail · held
On a schedule, or on a signal.
Set it once. You hear about it when it’s done — and only then.
Daily8:00
Read against the scorecard, ranked with the line that earned the rank. Shortlist and replies drafted, in your inbox before you open the ATS.ScheduledOvernight applicants, screened
Wed16:00
Scorecards chased, four written into one page, posted to #hiring the night before the huddle so nobody reads it cold.ScheduledPanel debrief
TriggeredA candidate goes quiet
Notion → Gmail · heldFri17:00
Every open req by stage and days in stage. Stalled candidates flagged, offers outstanding counted, the number you take into Monday.ScheduledPipeline, honest
Nami · the keeperSami Okada, Bea Lindqvist · req R-114 · nothing since Aug 10Screen on Aug 4, panel on Aug 12LinkedIn · 40 minutes ago
It remembers every candidate. So nobody waits a week.
People, reqs, stages, what the panel said — filed once, and noticed when it changes.
Nami · entity
Ines Marchetti
RoleSenior Backend Engineer · req R-114 · stage: offer
PanelMarina 5 · Owen 4 · Halle 4 · Theo 4 · unanimous yes
Asked"How does on-call actually work here?" — panel, Aug 12
WantsFour weeks’ notice at Kessel · remote Fridays · start after Sep 8
FilesCV · payments walkthrough · 4 scorecards
Kept since her first replyNoticed on its own
Two candidates have sat in screen for nine days. Send them an answer?
Sami Okada, Bea Lindqvist · req R-114 · nothing since Aug 10Not nowHandle it
Noticed on its own
Ines asked about on-call twice and nobody answered. Draft the answer?
Screen on Aug 4, panel on Aug 12Not nowHandle it
Caught a change
Ines set her profile to open to work. Worth moving the offer today?
LinkedIn · 40 minutes agoNot nowHandle it
Asks before it matters
It sends nothing you haven’t seen.
Offers, rejections, anything a candidate reads — held until you say go.
Held · waiting on you
Send Ines the offer from Owen?
To ines.marchetti@fastmail.comRe Senior Backend Engineer · offer
Ines — the panel was unanimous, and Marina has not stopped talking about your payments walkthrough. We would love you here. The numbers are attached, and you can call me on any of it…
EditHoldApprove & sendGmail · as Owen
Only the tools you connectLinkedIn, Gmail, Calendar, Notion — nothing else. Disconnect any of them, any time.
Every step, in the openThe plan, each tool call, the draft — visible while it works. Peek in, or take the wheel.
Candidate data stays yoursApplications, scorecards and salary notes live with you, not with a model. Switch minds; the work comes along.
Taught once, done your way
Candidate careA reply inside a day, scheduling without the back-and-forth, an honest update when the loop slips — in your voice, every time.RepliesSchedulingUpdates
Job posts & briefsJob posts that sound like your company, scorecards worth filling in, hiring-manager briefs that fit on one page.Job postsScorecardsBriefs
Create your ownYour playbook, encoded. Teach it how you screen, when you reject, what a strong hire looks like here — in plain words.Your rulesYour voice
Install the Recruiting playbook. Or teach it yours.
An Ability is everything the job needs — bundled, installable in a click.
Candidate careA reply inside a day, scheduling without the back-and-forth, an honest update when the loop slips — in your voice, every time.RepliesSchedulingUpdatesJob posts & briefsJob posts that sound like your company, scorecards worth filling in, hiring-manager briefs that fit on one page.Job postsScorecardsBriefsCreate your ownYour playbook, encoded. Teach it how you screen, when you reject, what a strong hire looks like here — in plain words.Your rulesYour voiceRecruiting & people · FAQ
Questions, answered.
Does it message candidates on its own?
Not unless you tell it to. Offers, rejections, anything a candidate reads is drafted and held for your word. Scheduling, invites, chasing scorecards and pipeline hygiene keep moving. Once a routine has earned it — the interview-schedule note, say — you can loosen that one and leave the rest held.
Does it work with our ATS?
Yes. Ashby, Greenhouse, Lever, Workday, BambooHR — your ATS connects the same way your inbox does, and Bash works inside it with your permissions, not through a bot seat. Teams running the pipeline in Notion or a sheet get the same treatment; it reads where the truth actually lives.
Will it screen fairly?
It scores against the scorecard you wrote, and it shows its work — the line in the CV, the repo, the answer from the screen. It never invents a reason, and it never guesses at anything you did not ask it to weigh. When you disagree, say why once; Nami keeps it for the next req.
What does it know about our hiring on day one?
Whatever’s in the tools you connect: the open reqs, the applications, the threads, the calendar, the scorecards already filled in. From there Nami keeps building — who asked what, who is on notice, which panel runs slow — so no candidate starts from a blank page.
Where does the work run?
On its own computer in the cloud — a real machine with a browser, files and a terminal — or on yours when the job lives there. Its screen streams as it works; you can peek in or take the wheel.
The door
Come back to hired.
Tell us which reqs are open. We’ll show you what Bash would own, what Nami would keep, and how many days come off your loop.