Use case · Operations

Keep hiring moving without letting a bot decide who gets hired

To run a hiring pipeline with AI agents, give a Brainwrite bot the role's criteria and access to the inbox or folder where applications arrive. It writes a short screening note for each applicant against your criteria, quoting the CV, and drafts interview invites with your available times. A person reads every application and makes every decision about candidates.

Download for MacSee the ready-made team
Hiring pipeline

Every weekday, read new emails in the Applications: Support Lead label. Add each applicant to the Hiring sheet with a short note on how they meet each criterion in my role brief, quoting their CV. Do not score or rank anyone. For people I mark Interview, draft an invite with three free slots from my calendar.

Your Chief of Staff put a team on it

  • Nova· Chief of Staff
  • Sage· Screening note writer
  • Dash· Scheduling assistant
  • 6 new applications added to the Hiring sheet with screening notes
  • Note for Tomás R.: 4 years leading a support team (CV, role 2); no mention of help desk reporting
  • Waiting on you: 3 candidates marked Interview, invites drafted with Tuesday and Wednesday slots
  • Reminder: Aisha K. applied 6 days ago and has not had a reply

DoneSaved as a routine: Weekdays at 9:00. It starts paused until you turn it on.

An illustrated example. Your team works on your own files and apps.
A hiring manager reads screening notes at her laptop in a glass-walled meeting room while illustrated Brainwrite AI agents Sage and Dash help.
NovaChief of Staff
7:40 am

Hiring pipeline: done. Nothing sent.

  1. 16 new applications added to the Hiring sheet with screening notes
  2. 2Note for Tomás R.: 4 years leading a support team (CV, role 2); no mention of help desk reporting
  3. 3Waiting on you: 3 candidates marked Interview, invites drafted with Tuesday and Wednesday slots
3 bots on this job
Who moves forward, who is declined, and who is hiredWaiting for your yes

The job

Doing it yourself, and handing it off.

Doing it yourself

A job post brings in eighty applications to a shared inbox. The hiring manager reads the first twenty carefully, skims the rest, and loses track of who replied to which email. Good candidates wait a week for an answer and accept another offer. Scheduling interviews takes a dozen emails per person, and the notes on why someone moved forward live in one person's head.

What the team does

  • Summarise each application against criteria you wrote, quoting the CV
  • Keep a tracker of each candidate's stage and last contact
  • Find free interview slots and draft invites for candidates you chose
  • Remind you about candidates waiting more than a few days

What waits for you

  • Who moves forward, who is declined, and who is hired
  • Every message to a candidate, sent only after your approval
  • The criteria, and whether they are fair and lawful for your location

The team

Who's on it.

Your Chief of Staff picks the specialists the job needs. Each has its own role, instructions, model, and app access.

  • NovaIllustrated example

    Chief of Staff

    Keeps the role criteria, tracks where each candidate is, and summarises the week's pipeline.

  • SageIllustrated example

    Screening note writer

    Reads each application and writes a short note on how it meets each criterion, quoting the CV. It does not score, rank, or reject anyone.

  • DashIllustrated example

    Scheduling assistant

    Finds free slots in your calendar and drafts interview invites or Calendly links for candidates you chose. Drafts only.

How it runs

A run, step by step.

  1. 01

    Write the criteria

    Give the Chief the role's must-haves and nice-to-haves, written about the work, not the person.

  2. 02

    Connect the sources

    Connect Gmail for the applications label, Google Calendar or Calendly for times, and Google Sheets as the tracker.

  3. 03

    Read the notes

    Each weekday, new applicants get a screening note in the tracker. You read the application and the note together.

  4. 04

    Approve invites

    For candidates you choose, the bot drafts an invite with times. Sending waits for your approval.

Start faster

Ready-made teams for this job.

Add a team from the library in one click. You see a preview first; routines arrive paused and connected apps stay off until you approve them.

What you'll connect

Apps this job uses.

FAQ

Questions about Hiring pipeline

Should an AI decide which candidates to reject?

No, and this setup does not ask it to. The bot writes notes against criteria you set and quotes the CV, so a person can check each note quickly. People read the applications and make every decision. Hiring rules differ by country, so check how your local law treats automated tools in recruitment.

Does it connect to my applicant tracking system?

Brainwrite's integrations directory does not list an applicant tracking system, so check the connected apps list in the app for yours. If it is not there, forward applications to a Gmail label, export candidates to Google Sheets, or add the system as a custom MCP server if its vendor provides one.

Where does candidate data go?

Brainwrite keeps chats, files, and memory on your Mac. Application text the bot reads is sent to the AI provider you picked for that bot. Choose one you trust with personal data, grant the bot only the mail label and sheet it needs, and delete notes you no longer need from its memory.

Built on

Features this job relies on.

Keep going

Put a team on something else.

Give your first job to Brainwrite.

Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing.

Download for MacSee how it works

macOS today. Windows and Linux are coming soon.