Use case · Operations
Put a hard decision on one page before you make it
To write a decision memo with AI agents, describe the choice to your Brainwrite Chief of Staff. It sends one bot to gather the facts from your docs, sheets, and public sources, and another to argue against the leading option. The Chief writes one memo: the question, the options, the evidence, the risks, and a recommendation. You make the decision.



We need to decide by Friday whether to move from monthly to annual-only pricing. Use the revenue sheet and the churn notes in Notion, check how three competitors price publicly, and have another bot argue against the change. Write a one-page decision memo in Google Docs with a recommendation.
Your Chief of Staff put a team on it
Nova· Chief of Staff
Atlas· Evidence researcher
Sage· Devil's advocate
- Question: move new customers to annual-only pricing from January, yes or no
- Evidence: 38% of current customers already pay annually (revenue sheet, tab Plans)
- Case against: monthly sign-ups are 3 times annual ones; annual-only may cut trials
- Recommendation: offer annual by default and keep monthly at a higher price; confidence medium
DoneThe decision itself, and who else needs to agree waits for you. Nothing was sent.

Decision memo: done. Nothing sent.
- 1Question: move new customers to annual-only pricing from January, yes or no
- 2Evidence: 38% of current customers already pay annually (revenue sheet, tab Plans)
- 3Case against: monthly sign-ups are 3 times annual ones; annual-only may cut trials
The job
Doing it yourself, and handing it off.
Doing it yourself
Big decisions get made in a long Slack thread or a single meeting. The facts are spread across a pricing sheet, two old docs, and someone's memory. Each option has a champion and nobody writes down the case against the favourite. Three months later, when the decision is questioned, there is no record of what was known at the time or why the other options lost.
What the team does
- Frame the decision as one question with clear options
- Collect evidence from your files and public sources, each with a source
- Write the strongest case against the leading option
- Draft a recommendation with the risks and what would change it
What waits for you
- The decision itself, and who else needs to agree
- How much weight each piece of evidence deserves
- Whether the memo is shared, and with whom
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 exampleChief of Staff
Frames the question with you, delegates the research, and writes the memo in your format.
AtlasIllustrated exampleEvidence researcher
Pulls the relevant numbers from your sheets and docs and public facts from the web, each with its source.
SageIllustrated exampleDevil's advocate
Writes the strongest case against the leading option and lists what would have to be true for it to fail.
How it runs
A run, step by step.
- 01
State the decision
Tell the Chief the question, the options you see, the deadline, and who has to agree.
- 02
Gather evidence
The researcher reads the docs and sheets you grant and public sources, and returns facts with links.
- 03
Argue the other side
A second bot, which can run on a different model, writes the case against the favourite.
- 04
Read and decide
The memo arrives as a Google Doc or Notion page. You choose, and record the reason in the memo.
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.

Google Docs
Bots create Google Docs from Markdown, read and search docs, edit sections, and export PDFs.

Notion
Bots search Notion, read and write pages, query databases, and add or update rows and comments.

Google Sheets
Bots read and write Google Sheets, append and upsert rows, and add charts to trackers and reports.

Slack
Bots search Slack, summarise channels and threads, and post or schedule updates once you approve.
FAQ
Questions about Decision memo
Why have one bot argue against the recommendation?
A single answer tends to agree with how the question was framed. Giving a separate bot the job of arguing against the leading option, with its own instructions and even a different model, surfaces risks that a friendly summary skips. You read both sides before deciding.
Can the bots make the decision for me?
They recommend, with a confidence level and the evidence behind it. The decision, and anything that follows from it such as a message to the team or a change in a tool, stays with you. Actions that touch connected apps wait for your approval in Ask mode.
Can I keep a record of past decisions?
Yes. Ask the Chief to save each memo to the same Notion database or Google Drive folder, with the date and the final call. You can also save your preferred memo format in its memory, so every memo follows the same structure.
Built on
Features this job relies on.
Chief of Staff
One bot takes your request, hands focused tasks to specialists, and returns a single summary.
Threads and groups
Up to three independent threads per bot, plus group chats where several bots share one brief.
Bring your own model
Claude, Codex, Grok, Cursor, local models and more, side by side. Your own logins, your own billing.
Memory
Plain-text memory per bot that you can read, fix and delete. No hidden profile.
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.







