Use case · Operations

Write down how the work is done before the person who knows it leaves

To write standard operating procedures with AI agents, explain a task to a Brainwrite bot by typing, dictating, or on a call, and point it at the Slack threads, tickets, and docs where the work happens. It drafts a step-by-step SOP with inputs, tools, checks, and who owns each step, and lists the questions it could not answer. The person who does the work checks it before it is published.

Standard operating procedures

I want an SOP for how we process a customer refund. Interview me about it, then read the last ten refund tickets in Zendesk and the refunds channel in Slack to check what actually happens. Write the SOP in our Notion template with steps, owner, tools, and exceptions, and list anything you are unsure about.

Your Chief of Staff put a team on it

  • Atlas· Process interviewer
  • Sage· Evidence reader
  • Dash· SOP writer
  • SOP draft: Processing a customer refund, 9 steps, saved to Notion as a draft page
  • Owner per step: support lead approves refunds over 200; finance processes the payment
  • Found in tickets, not mentioned in the interview: refunds after 60 days need a manager note
  • Open question: who refunds marketplace orders, support or the marketplace team?

DoneWhether the procedure is right, checked by the person who does the work waits for you. Nothing was sent.

An illustrated example. Your team works on your own files and apps.
An operations manager checks a printed list in a warehouse office while AI agents Dash, Penny and Nova stand beside her.
NovaChief of Staff
7:40 am

Standard operating procedures: done. Nothing sent.

  1. 1SOP draft: Processing a customer refund, 9 steps, saved to Notion as a draft page
  2. 2Owner per step: support lead approves refunds over 200; finance processes the payment
  3. 3Found in tickets, not mentioned in the interview: refunds after 60 days need a manager note
3 bots on this job
Whether the procedure is right, checked by the person who does the workWaiting for your yes

The job

Doing it yourself, and handing it off.

Doing it yourself

The way invoices get approved, a client gets onboarded, or a refund gets processed lives in one person's head. When they are on holiday, things stall, and when they leave, the knowledge goes with them. Everyone agrees procedures should be written down, but writing a good one takes hours of careful recall, so the documents never get written, or are written once and never match reality again.

What the team does

  • Interview the person who does the task with short follow-up questions
  • Read real examples in Slack, tickets, and docs to fill gaps
  • Write the SOP with steps, owners, tools, checks, and exceptions
  • List the questions the draft could not answer

What waits for you

  • Whether the procedure is right, checked by the person who does the work
  • Where it is published and who maintains it
  • Changes to how the work should be done, not just how it is done

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.

  • AtlasIllustrated example

    Process interviewer

    Asks the person who does the task short questions, by chat or on a call, until each step, input, and exception is clear.

  • SageIllustrated example

    Evidence reader

    Reads the Slack threads, tickets, and docs where the work happens to fill gaps and spot steps people forget to mention.

  • DashIllustrated example

    SOP writer

    Writes the procedure in your standard format, with steps, owners, tools, checks, and exceptions.

How it runs

A run, step by step.

  1. 01

    Pick one process

    Choose a task that repeats and depends on one person, such as processing a refund.

  2. 02

    Talk it through

    Explain the task by typing, dictating, or on a Take turns call. The interviewer asks follow-up questions.

  3. 03

    Add the evidence

    Point the evidence reader at real examples in Slack, your help desk, or your docs.

  4. 04

    Check and publish

    The owner checks the draft and answers the open questions. You publish it in Notion or Confluence.

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.

FAQ

Questions about Standard operating procedures

Can an AI write an SOP from scratch?

It can write a well-structured draft, but only from what you tell it and the examples you share. The best SOPs come from interviewing the person who does the work and checking real tickets or threads. The bot lists what it could not confirm, and the owner checks every step before the procedure is used.

Can I explain the process by voice?

Yes. Dictate in the composer, which uses Apple's on-device recognition, or start a call. A Take turns call listens on your Mac and the bot answers in its own voice. Live calls use OpenAI GPT-Live with your own key, billed by OpenAI at about $0.05 a minute.

Where are the SOPs stored?

Wherever you choose. The Notion connector can create pages and add text, to-do, and table blocks, and the Confluence connector can create and update pages. You can also keep them as Markdown files in the bot's working folder on your Mac.

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.

macOS today. Windows and Linux are coming soon.