Email management

Two inboxes, three hats: managing multiple email accounts.

Fractional roles, side projects, and board seats each come with an inbox. How to run several without living in tab-switching purgatory.

By Mathias CelisAugust 14, 20265 min readLast updated September 2026
TL;DR

Multiple accounts multiply every email cost: separate checking loops, separate backlogs, and switching overhead between them. What works: process all accounts in the same fixed windows (one session, N tabs), keep one external task and waiting-for system spanning all of them, set per-account response standards by role, and never forward accounts together into one blurred archive if separation matters legally.

The fractional CFO has three. The consultant has one per client plus her own. The founder advising two boards has four, and one of them is a Gmail from 2011 that important people inexplicably still use. Multiple email accounts used to be an edge case; portfolio careers made them normal, and nobody updated the advice.

Why is a second inbox more than twice the work?

Because every account replicates the full cost structure: its own checking loop, its own backlog, its own notification stream, plus a new cost none of them had alone: switching. Each hop between accounts is a context switch, and the research prices those at roughly 23 minutes of refocus (UC Irvine). Three inboxes checked reactively is a day spent commuting between them.

Unify the rhythm, not necessarily the mail

The core move: all accounts get processed in the same fixed windows, as one session with N tabs. Two or three windows a day, every account to zero decisions, done. The batching method doesn't care how many tabs are open; what it removes is the per-account checking loop, which is where the multiplication lived.

Whether to also merge the mail (forwarding everything into one inbox) is a separate call: fine for simple personal setups, wrong wherever separation carries meaning: client confidentiality, employer property, the clean exit when an engagement ends. Merge attention, keep custody separate.

One system above the inboxes

Tasks and waiting-fors from all accounts belong on single lists, because deadlines don't care which address they arrived at. The Tuesday commitment from the board seat and the Tuesday commitment from the client engagement need to fight for the same Tuesday, visibly. Per-account response standards can differ (same-day for clients, 48 hours for the advisory role), but the system that tracks them is one; the solo consultant setup runs on the same principle.

The multi-account layer Pidgy holds

Pidgy connects to Gmail and Outlook accounts and gives each the identical treatment: arrivals sorted, tasks and promises extracted, waiting-fors tracked, routine replies drafted in your voice for approval. The practical effect is the one that matters: three inboxes stop being three jobs and become one short review, with custody of each account exactly where it legally belongs.

Frequently asked questions

Should I merge all my email accounts into one inbox?

Merge the rhythm, not necessarily the mail: processing every account in the same scheduled windows removes most of the cost while keeping accounts separate where separation matters (clients, employers, legal clarity). Full forwarding suits simple personal setups more than professional ones.

How do people with multiple jobs handle email?

With one system above the inboxes: a single task list and waiting-for list spanning all accounts, so commitments live in one place regardless of which address they arrived at. The inboxes are just arrival bays; the system is unified.

Can Pidgy handle more than one email account?

Pidgy connects to Gmail and Outlook accounts and gives each the same treatment: sorted arrivals, extracted tasks, tracked waiting-fors, drafted replies for approval. The practical effect is that three inboxes stop being three jobs.

Pidgy on top of the panel, looking through binoculars

Let Pidgy read your inbox so you don't have to.

Pidgy turns what lands in Gmail and Outlook into clear next actions, waiting-fors, and reference. One place, nothing slips.

Join the waitlistSee how Pidgy works