Mise en Place: Office Automation Starts with a Folder, Not a Robot

Here's a pattern we watched fail over and over during years of office work at a small company. Someone discovers AI agents, gets excited, and asks for the obvious thing: "automate my weekly report." The agent asks where the numbers live. The answer: some in the ERP screen, some in email attachments, some in a messenger thread, one in a phone call from Tuesday, and two in a coworker's head.

The automation dies right there. Not because the agent is weak — because the ingredients were never in the kitchen.

Signal flare: this recipe is for readers with a day job — the ones whose work lives scattered across six systems they don't control. If that's you, you're closer to real automation than you think, but the first step isn't the one everyone tries.

The three layers of office automation

Strip any office job down and most of the automatable work stacks into three layers:

1. Data arrives — from outside: invoices, statements, official letters, attachments. From inside: ERP records, emails, messages, call notes, meeting minutes.
2. Reports go up — someone (you) compiles that data into status views and decision documents. Weekly reports. Cash positions. Order summaries.
3. Responses go out — customers and vendors ask things; someone (you) looks up the history and writes back.

Notice the dependency: layers 2 and 3 are only automatable if layer 1 is solved. A report is just a query over data the agent can reach. A response draft is just a lookup plus manners. Everyone tries to automate the glamorous layers and skips the boring one — and the boring one is the whole game.

Cooks have a name for the boring layer: mise en place. Everything chopped, labeled, within arm's reach — before the heat goes on. No chef sautés while running to the market.

Layer 1: one folder, dumb on purpose

You don't need a data platform. You need one folder tree your agent can read, fed by habits:

work-data/
├── inbound/      # invoices, statements, letters — PDFs land here
├── erp-exports/  # weekly CSV exports (every ERP can export *something*)
├── meetings/     # notes as plain text, one file per meeting
├── threads/      # important email/messenger decisions, pasted as text
└── contacts/     # who's who at each vendor/customer, one file each

Files in folders. That's it. Files are the universal interface — no integration project, no IT ticket, no API keys. Your ERP is locked down? A weekly CSV export is still a copy-paste job. Calls don't transcribe themselves? A three-line note after each call beats a perfect system you'll never build. Start with whatever you re-search for most often — that's your highest-value ingredient.

Two weeks of this habit and something quiet happens: your work has a single place where it's true.

Layers 2 and 3: now the heat goes on

Once the folder exists, the magic feels almost unfair:

• The weekly report becomes one sentence. "Read erp-exports and meetings from this week, write the status report in our usual format, flag anything unusual." The agent reads everything, every time — it never forgets Tuesday's call note the way tired humans do.
• Decision views become questions. "Which vendors are late this month, and what did they say last time?" is now answerable in seconds, because the answer lives in one place.
• Response drafts write themselves against history. "Draft a reply to this vendor email — check their file and our last three orders first." You review, you send. The agent does the looking-up; you keep the judgment and the signature.

This is the honest meaning of "full automation" for office work: not a robot replacing you, but you keeping the decisions while the gathering, compiling, and drafting run on prompts. The person who does this first at a small company becomes, very quickly, the person everyone asks about AI.

The honest notes

1. Company data has rules — respect them. Before anything leaves a company system, know your workplace's policy. Personal notes about your own tasks are one thing; exporting customer databases is another. When in doubt, ask. Automate your corner first.
2. Strip what shouldn't travel. Resident registration numbers, bank details, salaries — keep them out of the folder or mask them. The folder should be useful, not radioactive.
3. Calls and hallway decisions are the leaky pipe. Accept imperfection: a three-line note within five minutes of the call captures 90% of the value.
4. Don't announce a revolution. Build your own mise en place quietly for a month. Show results, not plans.

Order up

Paste this into your agent tonight:

Help me build a mise en place for my office work — one folder my
agent can always cook from.

1. Interview me: what are my 5 most repeated tasks, and for each one,
   where does its data actually live today? (systems, inbox, chats,
   calls, my head)
2. Design a simple folder structure for a "work-data" directory that
   would hold that data as plain files (CSV exports, PDFs, text notes)
   — and create it.
3. For each folder, tell me the exact 1-minute habit that feeds it
   (e.g. "after each call, one 3-line note here").
4. Flag anything that should NOT go in: personal data, anything
   against company policy — and suggest how to mask or skip it.
5. In two weeks, I'll ask you for my first fully-automated weekly
   report from this folder. Note what "done" will look like.

The folder is boring. The habits are small. And a month from now, your weekly report writes itself while your coworkers are still alt-tabbing between six windows — ingredients first, heat second.

Which of your work's data is the most scattered right now? Tell us at @AgentKitchenHQ.