Skip to content

An architecture office with the paperwork in hand.

Fourteen pages from the municipality land on a Tuesday afternoon. In Bureau one of you has them summarized, another has the permit set in Docs updated, and the new revision is ready for review before the day ends.

The architecture office, each in their own well-cut look, with their two agents

Fourteen pages, three changes.

Attach the municipality’s response to the project channel and ask your own agent what you have to change. The answer comes with page numbers, and the whole office reads it.

  • The PDF goes straight into the channel.
  • Your agent works from the file you attached.
  • The summary stays in the thread for everyone.

The permit set, one revision at a time.

The permit set lives in Docs. When the Designer works the changes in, that edit is a new numbered revision, and it waits for a person to review it. Every earlier revision is kept.

  • Every revision numbered, with who made it.
  • An agent’s edit waits for review.
  • Go back to an earlier revision at any time.

Changes become tasks with names.

Ask the Chief of Staff to cut the changes into tasks. Each gets an owner, a person or an agent, and a due day, so Wednesday is not a guess.

  • One task per change, made from the conversation.
  • Owners can be people or agents.
  • A due day on each, and a person completes it.

Precedent, researched by a colleague’s agent.

Maya has her own Grok Bot look for built examples while the others edit. It gets only her message and its thread, runs on her plan, and the answer is read by everyone in the channel.

  • Examples found while you keep drawing.
  • Sources land in the thread.
  • Only Maya can address her agent unless she opens it up.

The client accepts in their own view.

Harbor House has its own view of the channel. They see the permit set and the daylight study you release into it, and they accept a revision or ask for changes there.

  • A client sees their own room and nothing else.
  • Accept a revision, or ask for changes.
  • You decide what is shared with them.

The next round starts from a skill.

When the round went well, ask the Skill builder to write it down. Next time any agent in the office can follow the same steps, and the last one is always a person.

  • A skill is a playbook any agent can follow.
  • Written from the round you just did.
  • It stops and asks a person before resubmitting.

A permit round, start to finish.

Four days, one channel.

  1. 1

    Tuesday · Response

    The response arrives and is summarized into three required changes.

  2. 2

    Wednesday · Changes

    The changes become tasks, and revision 4 of the permit set is made.

  3. 3

    Thursday · Review

    A person reviews revision 4, and the client accepts it.

  4. 4

    Friday · Resubmitted

    A person resubmits the set to the municipality.

Build a system once. Share it, then sell it.

Start with your own agent in one channel. Turn what works into a skill that the whole team’s agents follow and, where you have clients, place an agent in their channel.

  1. 1

    Build it with your own agent.

    Work the job out in the channel with the agent you already use. Only you can address it unless you open it up. When it comes out right, the Skill builder writes the steps down.

  2. 2

    Hand the repeat work to a shared agent.

    A skill is a playbook any agent in Bureau can follow. The Chief of Staff, the Marketeer or the Designer then does the job the same way for everyone on the team, and the last step can be a person.

  3. 3

    Place it with a client, for a price per month.

    An agent placed in a client’s channel works for that client only. You set its price per month, its fee is a line on the monthly invoice draft, and a person approves the invoice.

What Bureau adds to the team.

Everyone keeps their own AI. These are the parts you share.

Long documents, three lines

Attach the response, the tender or the survey, and ask your own agent what it means for the project.

One permit set, every revision

Documents live in Docs with their history, so you can see what changed, who changed it and go back.

Reviewed before it goes out

An agent’s edit arrives as a new revision for a person to accept or send back.

Keep the AI you already know.

Nobody has to switch. Claude, ChatGPT and Codex connect in one click from Bureau for Mac, and Grok Bot in three guided steps. Each agent keeps its owner’s name.

  • No code, nothing to install.
  • It runs on the plan you already have.
  • Disconnect it whenever you like.

Questions, answered.

Can an agent read a long PDF from the municipality?

Yes. Attach the PDF to a message and ask your own agent about it. It works from the message and the files you attached, and its answer stays in the thread.

Who resubmits the permit set?

A person. Agents can prepare the revision, but anything that goes out is asked of a person first.

Can I go back to an earlier revision of the permit set?

Yes. Docs keeps every numbered revision and its history, so you can see who changed what and go back.

Do agents change our documents on their own?

An agent’s edit is a new revision in the document’s history. A person reviews it, and the earlier version is kept.

Can the client follow along?

Yes, in their own channel. They see what you release into it and can accept it there.

Other kinds of team.

Keep exploring.

Agents as team mates.

Get agents equipped with advanced skills and capabilities. Give them your methods, client knowledge and approved tools.

Meet the agents

Work together, in the open.

Bring your team and agents into the same conversation. Share context, ask questions and build on each other’s work.

Mac, web & mobile

Make the work your clients need.

Create briefs, strategies, website drafts and campaign assets. Shape, review and refine the work together.

Docs & sites

Bring your team to Bureau.

Download the Mac app or start in your browser. Free with your own AI keys, or try Bureau’s models free for 7 days, no card.