4 inboxes. 1 Claude session. 4 Gmail MCPs. Every email linked, every hour time-blocked, every action one click away. Built on Tiago Forte's One-Touch method + Cal Newport's Time-Block Planner + Dickie Bush's Monthly Review, powered by Claude Cowork Scheduled Tasks.
Ethan has 4 Gmail accounts. Here are the options for connecting them — and our recommendation for where to start.
One session, 4 Gmail connectors, shared TASKS.md, one time-block schedule, one shutdown ritual. The full vision.
Risk: Connecting 4 MCPs takes time. May hit auth issues. Debugging infrastructure before Ethan has even tried the system.
4 separate Claude accounts, each with its own Gmail connector. Works — but requires sign-out/sign-in to switch.
Problem: No shared tasks, no shared calendar context, no unified schedule. Each account is its own island.
1 Claude session. 1 Gmail MCP (Pod Plug — the busiest inbox). Get it fully working first: briefs, time blocks, collection columns, shutdown.
Why: Let Ethan use it for a week. See if it fits. Then expand to the other 3 accounts when the system is proven.
This blueprint shows the full 4-account vision so Ethan can see where we're going. But the setup guide starts with Pod Plug only. Everything scales — the same system that works for 1 inbox works for 4.
Ethan runs 4 email accounts across franchise/City Launcher operations, real estate, community, and personal life. Without a system, important things get buried across inboxes. With Claude as EA, every inbox is pre-sorted, pre-drafted, and pre-linked every morning — Ethan just makes decisions.
Switches between 4 Gmail accounts. 80+ unread across all of them. Misses a lease renewal in Black Label. Forgets a franchise/City Launcher lead in Pod Plug. Inbox anxiety all day.
Opens 4 Claude briefs back-to-back. Each one pre-sorted with links. P0s first, drafts ready, batch archive links. All 4 inboxes at zero by 9:20 AM.
One Claude Cowork session with 4 Gmail MCP connectors — each authenticated to a different Google account. Everything lives in one place. Same system, same logic, same brief format — all 4 inboxes scanned by one Claude session via 4 Gmail MCP connectors.
| Account | What It Handles | Gmail MCP | Scan Order |
|---|---|---|---|
| POD PLUG | Franchise/City Launcher ops, sales leads, vendors, compliance, support, orders | Gmail MCP #1 | 1st |
| PERSONAL | Personal email, "Reading" label, subscriptions, personal admin | Gmail MCP #2 | 2nd |
| VENDPRENEURS | Community, member inquiries, content collaborations, event coordination | Gmail MCP #3 | 3rd |
| BLACK LABEL | Real estate, tenant communications, lease renewals, property management | Gmail MCP #4 | 4th |
One Claude session connects to all 4 Gmail accounts via 4 separate Gmail MCP connectors. One set of scheduled tasks scans all inboxes in sequence — morning brief, midday sweep, shutdown ritual. No switching accounts, no staggering, no friction. Ethan wakes up at 9 AM, opens them back-to-back: Pod Plug → Personal → Vendpreneurs → Black Label. 20 min max.
Ethan's morning (9:00–9:20 AM): ~7 min Pod Plug (highest volume) + ~4 min Personal + ~2 min Vendpreneurs + ~3 min Black Label + ~4 min TASKS.md = ~20 min total across all 4 inboxes
Claude is a prep layer, not an autopilot. It reads, categorizes, drafts, and links — but Ethan presses every button. Here's exactly what Claude can and cannot do with the Gmail MCP:
Every email in the morning brief includes a direct Gmail link using the message ID. Ethan clicks the link → lands on the exact email → takes action (send draft, archive, label). No searching, no scrolling. The brief is a clickable action list.
create_event, list_events, find_meeting_times, find_my_free_time, delete_event — shared across all sessions via one GCal connection.
Claude's built-in task manager. Tasks from all 4 inboxes funnel into one TASKS.md. Max 3 per day, following Tiago's 7 rules.
There's no separate dashboard, no website, no switching between accounts. One Claude Cowork session IS the interface. 4 Gmail MCP connectors feed into that one session. Ethan opens the Claude app and everything is right there.
Scheduled task runs at 8:00 AM → Claude scans all 4 inboxes in sequence using 4 Gmail MCPs → 4 briefs appear as Claude's messages in one chat. Ethan wakes at 9 AM, opens the session → briefs are already there. All Gmail links are clickable. No account switching.
Claude outputs the schedule in the chat AND creates real Google Calendar events for each block using the Calendar MCP. Ethan sees blocks on his phone, watch, and laptop. Calendar is the source of truth during the day.
When plans change, Ethan messages Claude: "vendor call ran long, reblock afternoon" → Claude outputs Column 2 and updates the Google Calendar events — deletes old blocks, creates new ones. All in the chat.
Ethan can ask Claude "show me all my tasks" anytime and Claude reads from TASKS.md and displays the full backlog. During shutdown, Claude shows the full list and Ethan picks the next day's top 3. Every morning, Claude re-ranks by urgency + deadlines and surfaces the new top 3.
Ethan never opens a separate tool or switches accounts. One session is where he gets all 4 briefs, reviews tasks, edits his schedule, and does the shutdown ritual. If he needs something — he just asks. "What's on my plate?" "Move the 3pm block to tomorrow." "Add a task: order new wraps for ATX machines." Claude handles it and updates TASKS.md and Google Calendar accordingly.
Five phases. The goal: every email gets touched exactly once. Claude handles phases 1-4 overnight. Ethan handles phase 5 in the morning. This system runs identically on each of the 4 inboxes.
Identify obvious noise — newsletters never read, automated receipts, marketing blasts. Claude flags them for archive with one-click links.
Unsubscribe candidates identified. Claude lists them with links — Ethan clicks to unsubscribe from Gmail directly.
Route emails to the right system: Calendar event? Task? Read Later? Claude pre-routes and creates drafts/events/tasks. Ethan confirms.
Draft replies for anything that needs a response. Templates for common patterns (franchise/City Launcher inquiries, tenant questions, vendor follow-ups).
Ethan opens each brief. Every item has a link. Click → decide → next. Six possible decisions per email.
Every email routes to one of four systems. Claude works with Ethan's existing labels — no new labels created.
| System | Tool | Connector | Status |
|---|---|---|---|
| Calendar | Google Calendar | Google Calendar MCP | Available |
| Tasks | TASKS.md | Built-in | Ready |
| Notes / Reference | Apple Notes | Shortcuts bridge | Workaround |
| Read Later | "Reading" Gmail label | Ethan applies manually | Manual |
Claude respects these labels — never creates, removes, or modifies them.
Two layers per inbox: Claude prepares, Ethan executes. Every email gets a direct Gmail link.
1. Scan Inbox
search_messages → get all unread. Save every message ID for linking.
2. Read & Categorize
read_message each → assign triage decision (archive, reply, calendar, task, reference, read later).
3. Flag P0s
Check for deadline triggers, money signals, legal/gov, account alerts. Flag as P0.
4. Draft Replies
create_draft for emails needing response. Calendar events via GCal. Tasks to TASKS.md.
1. Review P0s
Click link → review draft → Send.
2. Batch Archive
Click batch link → select all → archive.
3. Send Drafts
Click each → edit if needed → send.
Claude pre-assigns a decision. Ethan confirms or overrides. Every row has a link.
| Decision | What Claude Does | What Ethan Does | Link Type |
|---|---|---|---|
| Archive | Lists in "Archive These" with link | Clicks batch link → select all → archive | Batch search link |
| Reply | Creates draft reply via create_draft | Click link → review draft → Send | Direct message link |
| Calendar | Creates event via GCal MCP | Confirms in calendar | Email + GCal link |
| Task | Adds to TASKS.md with email link | Reviews top 3 tasks | Email link in task |
| Reference | Extracts key info for Apple Notes | Runs Shortcut to save | Email link + text |
| Read Later | Lists in "Reading" section | Click → apply "Reading" label | Direct message link |
Claude runs this logic on every email in every inbox. Each question is a yes/no gate. First "yes" wins.
First yes wins. Claude evaluates top-to-bottom. A P0 email that also needs a reply gets flagged as P0 (with the draft still created). An email can only land in one category — no duplicates.
Claude scans every email across all 4 inboxes for high-priority signals. P0s always appear first.
password reset, security alert, account suspended, verification required, unusual activity
due by, expires on, deadline, final notice, last chance, renewal date, action required by
wire transfer, payment received, invoice overdue, refund, chargeback, past due, NSF
from *.gov, subpoena, compliance notice, cease and desist, regulatory, audit, tax notice
investors, lawyers, franchise/City Launcher partners by name, key vendors, accountant, landlords, tenants
machine down, out of stock, delivery failed, shipment delayed, system outage, lease violation, maintenance emergency
One Claude session runs these scheduled tasks. Each task scans all 4 Gmail accounts in sequence. Ethan wakes at 9 AM — briefs are already waiting. Day runs 10 AM – 7:30 PM in 30-min blocks.
Scan all 4 inboxes in sequence via 4 Gmail MCPs → read each → categorize → flag P0s → create drafts → build 4 briefs with Gmail links. Runs before Ethan wakes at 9.
0 0 8 * * *Pull today's events from GCal. Review TASKS.md (tasks from all 4 inboxes). Surface top 3. Review weekly plan, Rocks, Scorecard, V/TO, Accountability Chart.
0 15 8 * * *Generate today's time-block schedule for 10 AM – 7:30 PM. 30-min minimum increments. GCal events + top 3 tasks + free slots → block plan. 2 hrs deep work (peak energy), 4x 15-min breaks (2 snack), 3x shallow work blocks, lunch, content, reading/writing time, Gemini call review, shutdown. 15-min postmortem after each meeting.
0 20 8 * * *Quick scan across all inboxes for new P0s since morning. Urgent = flag now, otherwise queue for tomorrow.
0 0 12 * * *Step 1: Clear email inboxes — scan all 4 for anything missed. Flag unsent P0 drafts. 3 min
Step 2: Check calendar (-1 week / +1 week) — any missed follow-ups? Prep needed? 2 min
Step 3: Google Chat — Ethan checks manually and crosses off. Claude cannot access Google Chat. 3 min
Step 4: Time-block planner — review today's blocks, note schedule fixes, draft tomorrow's blocks. 5 min
Step 5: TASKS.md: choose solo to-dos for tomorrow. Max 3. Go with energy. 3 min
Step 6: Record daily metrics → Shutdown complete ☑
Full 11-step weekly review: clear inboxes (5 min) → check calendar -2/+4 weeks (2 min) → clear desktop/downloads (3 min) → process photos/Loom (3 min) → process Apple Notes/Google Drive/Dropbox inboxes (10 min) → review projects + areas (5 min) → review Rocks + Scorecards (2 min) → "Waiting For" follow-up (2 min) → create Dex reminders (3 min) → extract ebook highlights (15 min) → TASKS.md: choose to-dos for the week (5 min).
Weekly — Sunday60-minute monthly reflection. 5 questions: (1) Biggest wins? (2) Biggest realizations? (3) Most/least satisfied? (4) Do more of? Less of? (5) Thinking about for next month? Plus: Review Rocks (10 min), update project list (10 min), review areas of responsibility (5 min), review someday tasks (2 min), reprioritize tasks (3 min), extract ebook highlights (15 min).
Monthly — 1stClaude generates one brief per Gmail account — all in the same chat, one after another. Pod Plug → Personal → Vendpreneurs → Black Label. Each has its own P0s, drafts, and batch archive links.
Links use: mail.google.com/mail/u/0/#inbox/MESSAGE_ID
Each Gmail MCP connector's search_messages returns message IDs. These map to Gmail deep links:
https://mail.google.com/mail/u/0/#inbox/18e4f2a3b7c8d9e0
Batch archive links use Gmail search queries per account:
https://mail.google.com/mail/u/0/#search/from:morningbrew+OR+from:shopify+OR+from:stripe
Each inbox gets its own batch link. Ethan clicks → select all → archive. One batch per account.
Same process, 4 times. Ethan doesn't want to spend more than 20 min here. Pod Plug is the longest (~7 min). The other 3 are lighter (~2-4 min each). Then 4 min reviewing TASKS.md.
Highest volume account. Open brief → handle P0s → batch archive → review/send drafts → confirm calendar → tasks.
Batch archive newsletters → send drafts → apply "Reading" labels.
Community emails — typically lower urgency. Batch archive → done.
Real estate/property emails. P0 check → review draft → archive rest.
Claude added tasks from all 4 inboxes. Pick top 3 for today. Rest stays in backlog.
Tiago Forte's complete weekly review. Systematically processing every inbox, project, and area of responsibility. Claude automates the scanning, Ethan does the thinking.
Claude scans all 4 inboxes, pulls calendar -2/+4 weeks, reads TASKS.md for the "Waiting For" list, surfaces ebook highlights from the week, and pre-populates the weekly to-do selection. For steps that require manual access (desktop, photos, Apple Notes, Dex), Claude presents the checklist and Ethan works through it while Claude tracks completion.
Tiago Forte handles what comes IN (email → triage → downstream systems). Cal Newport handles what goes OUT (how Ethan spends his working hours). Claude automates both.
"Effective executives do not start with their tasks. They start with their time." — Peter Drucker (via Newport)
Claude generates a daily schedule at 8:20 AM for 10 AM – 7:30 PM. 30-min minimum blocks. 2 hrs deep work (peak energy), 4x 15-min breaks (2 snack), 3x shallow work blocks (phone, WhatsApp, email, GChat, IG, iMessage), lunch, TASKS.md batch, content + script approval, reading (WSJ 30 min + reading 30 min), writing 30 min, Gemini call review, shutdown. 15-min postmortem after each meeting. Email gets its own dedicated block — never done in parallel (Newport's Tip #3).
Digital version of Newport's "tasks" and "ideas" columns. Ethan messages Claude mid-day: "add task: call accountant re Q2" or "idea: test QR codes on machines". Claude writes it to TASKS.md instantly — 5 seconds, no context switching. All captured items are surfaced at the 7 PM shutdown.
Claude prompts Ethan to record his 13 daily metrics during the shutdown ritual. Trends tracked over time — streaks, dips, patterns. Includes writing time, slow carb, and Gemini call reviews.
Newport's most important habit. A scheduled task fires at 7:00 PM — Claude automatically scans all 4 inboxes, pulls calendar data (-1/+1 week), reads TASKS.md, surfaces today's captured items, and walks Ethan through each step in the chat. Google Chat is the one manual step — Claude cannot access it, so Ethan checks and crosses it off himself. Ethan reviews, picks tomorrow's top 3 tasks, confirms the schedule, and logs metrics. Claude does the prep, Ethan makes the calls.
Recorded during the shutdown ritual. Claude prompts each one and logs the values.
Scheduled task fires at 7:00 PM. Claude automatically scans all 4 inboxes, pulls all data, and presents the shutdown checklist in the chat. Ethan opens the session and walks through it conversationally — Claude does the heavy lifting, Ethan reviews and confirms.
The goal isn't to stick to the original schedule no matter what. It's to always have an intentional plan. When things change — and they will — you "fix" the schedule. Claude can help:
Pad by 20-30%. Claude automatically inflates block sizes for new task types. After a few weeks, it learns Ethan's actual pace and adjusts.
Email gets its own block. Never done in parallel with deep work. The morning brief triage is one dedicated block. Midday sweep is another.
Conditional blocks. If a task might take 1 or 2 hours, Claude schedules the first block for the task + a second "conditional" block: if done early, it becomes admin time; if not, it's overflow.
Newport's weekly planning pages complement Tiago's ECNT review. After the ECNT sweep, Claude generates:
An optional, Ethan-initiated reflection prompt. Not scheduled — Ethan triggers it when he wants to. All responses are captured in a document that Trisha (Ethan's personal brand manager) picks up to write content from.
OPTIONAL — Ethan-initiated only. Never auto-triggered./mnt/outputs/brain-dumps/YYYY-MM-DD-brain-dump.md — include the date, all 10 bullets verbatim, all 5 questions with Ethan's answers, and a "Top content angles" summary at the bottom that Trisha can scan quickly.
Fixed commitments that Claude must account for when generating time-block plans. These events repeat weekly (or biweekly) and should be protected — never scheduled over.
When generating time-block plans, Claude checks Google Calendar for these recurring events first. They are treated as immovable — blocks are built around them, never over them. If a recurring event conflicts with a meeting, Claude flags it: "Heads up — your stretch session overlaps with the 3 PM call. Want to move stretch to Thursday?" Claude also uses these events to calculate available deep-work hours for the week, so Ethan always knows his real capacity.
On the 1st of every month, a 60-minute deep reflection using Dickie Bush's 5-question framework plus an operational review of all projects, areas, and quarterly Rocks. Claude prepares the data; Ethan does the thinking.
These are the core reflection questions. Claude presents them one at a time and captures Ethan's answers. The goal is honest self-assessment — not performance metrics.
Celebrate progress. Name specific accomplishments — deals closed, machines placed, content milestones, personal wins. Claude can pull data from TASKS.md completed items, email threads, and calendar to jog memory.
Mindset shifts, lessons learned, things that clicked. What do you know now that you didn't know 30 days ago? Claude surfaces brain dump themes from the month for reference.
Honest assessment across all areas — business, health, relationships, content, personal growth. The "least satisfied" part is where next month's priorities come from.
The 80/20 life audit. What activities produced the most results? What was wasted time? Claude can reference time-block data to show where hours actually went vs. where Ethan thinks they went.
Forward-looking. Goals, experiments, changes. This becomes the seed for next month's Rocks and priorities. Claude captures this and references it when generating the first week's time-blocks.
After the 5 reflection questions, Ethan does a systematic review of all operational systems. Claude pulls the data and presents it; Ethan makes decisions.
/mnt/outputs/monthly-reviews/YYYY-MM-monthly-review.md — full 5 questions + answers, operational review decisions, updated Rock status, and next month's top priorities. Also update TASKS.md with any reprioritization.
These rules are programmed into every Claude session's task creation logic.
From zero to a fully operational AI EA session with all 4 Gmail accounts in 5 days.
Create one Claude Cowork session. Add 4 Gmail MCP connectors — each authenticated to a different Google account. Connect Google Calendar MCP. Initialize TASKS.md. Test Apple Notes Shortcut bridge.
Create the morning scan scheduled task: start with Pod Plug Gmail MCP — scan + categorize + draft + brief with links. Include P0 keyword list. Set cron to 6:45 AM. Test with yesterday's emails. Verify Gmail links work.
Expand the morning scan task to use all 4 Gmail MCPs in sequence — Pod Plug, Personal, Vendpreneurs, Black Label. Add calendar preview and task surfacing. Wire GCal event creation for time blocks.
Create midday P0 sweep (scans all 4 MCPs), 7 PM shutdown ritual task, and collection column processing. Test full daily cycle end-to-end.
Create Friday weekly review prep. Fine-tune P0 keywords per account (Black Label gets "lease" and "tenant"; Pod Plug gets "machine down" and "franchise/City Launcher"). Adjust thresholds. Go live.
Built for Ethan Kohan by Trisha — Powered by Claude Cowork
Blueprint v8 — April 2026 — Tiago Forte + Cal Newport + Dickie Bush + Claude = Ethan's AI EA.