First day

The first thirty minutes, in plain English.

No fine print, no hidden steps. Here is exactly what happens between downloading SwarmMarshal and your first useful draft.

0–5 min

Install and meet the dashboard

Run the Windows installer or open the macOS app bundle. The welcome screen explains what is about to happen, in plain language. Nothing is connected yet, nothing is indexed, no agent is running. You are looking at an empty desk.

Reassurance: No data leaves your computer until you connect an account.

5–15 min

Connect one mailbox

Pick Gmail, Outlook, or a regular IMAP account. SwarmMarshal walks you through the sign-in. If the OAuth flow stumbles, the app explains the next step in English instead of throwing a stack trace.

Reassurance: You can disconnect at any time. Disconnecting does not delete the local copy of your messages.

15–25 min

Let it read the pile, in the background

Indexing turns your inbox into a searchable, agent-readable map. You can keep using the app — search starts working as the index fills, and you can watch progress on the status pill.

Reassurance: Indexing runs locally. Nothing is uploaded to a server while it works.

25–30 min

Turn on one agent for one job

Start with the morning sorter or the reply drafter. Pick the inbox it watches and confirm it is draft-only. The first time it has something to show you, it shows up as a draft you can edit, not as a message that already left.

Reassurance: Drafts never send themselves. The first time anything goes out, you press the button.

What about…

The four "what if" questions everyone has on day one.

These are the worries SwarmMarshal is built around. The answers are not policy; they are how the product behaves out of the box.

If you have ten minutes a day

Open the daily briefing in the morning, approve the drafts you like, edit the ones you do not, and close the app. That is enough to get value.

If you forget to check it for a week

Nothing dramatic happens. The agent has been preparing work and waiting. When you come back, the queue is what is waiting on you, ordered by urgency.

If an agent gets it wrong

Reject the draft, recategorize the sender, or flip the approval. The agent learns from the correction. You do not need to write rules.

If something feels off

Pause the agent from the team dashboard. Pausing is one click. Nothing keeps running while you decide what to do.

First week

A gentle, optional path through the rest of the week.

Nothing here is required. They are the small experiments that make the value visible without taking over your week.

  1. Day 2 Pin three senders as VIPs so the briefing surfaces them first.
  2. Day 3 Try a plain-English search like 'what did I promise the school last fall?'
  3. Day 4 Add the calendar so promises and dates start landing as reminders.
  4. Day 5 Try Vibes for one tracker you keep in a sticky note or spreadsheet.
  5. Day 6 Approve a draft, then a few; notice what the agent gets right.
  6. Day 7 Decide if a second agent has a real job to do for you.

Ready to spend thirty minutes on it?

You can stop after the first useful draft and decide if it is worth keeping around. That is the only commitment that matters.