The Mac Workspace Setup That Works for Juggling 3–5 Projects a Day
The ideal Mac workspace setup for someone who switches between 3 to 5 projects every day is one named workspace per project, each saved as a complete bundle of apps, browser tabs, window positions, and a Focus Mode: restored with a single keyboard shortcut.
You don't manage projects by rearranging windows or hunting through tabs; you press ⌘⇧1 through ⌘⇧5, and the entire context appears in three seconds. That pattern named workspaces, shortcut-bound, app + tab + window + Focus all together- is what makes 3–5 project switches a day feel like one decision per switch instead of fifteen minutes of setup.
What follows is the actual layered structure, the step-by-step build, three worked examples for common multi-project roles, and the mistakes that quietly break the system.
The 4 layers of a multi-project Mac setup
A workspace that survives 3–5 switches a day has four layers. Tools that handle only one or two of them will leak; the project will partially come back, and you'll spend the rest of the morning rebuilding the missing parts.
Layer 1: Apps
Each project has a stable app set: editor, communication tool, design or data tool, notes app, browser. The app set is the spine. If you have to think about which apps to open before you can start, you've already lost momentum. A good setup launches the right apps in the right window positions before you sit down.
Layer 2: Browser tabs
This is the layer most setups skip. Each project has a tab cluster: the client's dashboard, three reference docs, a Notion page, two competitor sites, a Stack Overflow answer you keep returning to. Tabs are part of the project context, not a global pile to clean up. If your workspace doesn't restore the right tabs in the right order, the browser becomes the bottleneck on every switch.
Layer 3: Window positions
A productive Mac setup uses screen real estate intentionally: editor full-screen on the main monitor, Slack pinned to the left third of the secondary monitor, notes on the right third, browser floating on top. Multi-monitor users feel this acutely; windows that come back in the wrong place force a 30-second reshuffle every time. Position is part of the workspace.
Layer 4: Focus Mode
The system layer. Each project has a notification posture: deep work silences everything; client calls allow only the client's Slack channel; admin time allows email. macOS Focus Modes are the right primitive, but they only matter if they flip with the workspace switch, not as a separate manual step you'll forget on a busy day.
When all four layers are bound together apps, tabs, windows, Focus Mode switching projects becomes one action. When any one layer is missing, the switch leaks time and attention.
How to build it, step by step
The build uses Ikuna as the spine because it captures all four layers in a single saved workspace. We'll cover honest alternatives in the next section. The order matters: set up one project end-to-end before defining the next.
Pick your 3–5 active projects. Active means you switched to it this week. Archive everything else for now. If you try to define ten workspaces on day one, you'll trust none of them by day three.
Open exactly the apps you actually use for Project 1. Editor, communication tool, design/data tool, notes, browser. Close everything that isn't part of the spine. Be ruthless; saved clutter is still clutter.
Open exactly the browser tabs for Project 1. The client's dashboard, the working doc, two or three references. Eight to twelve tabs is a healthy ceiling per project.
Place the windows where you want them. Editor on the main monitor, Slack pinned to the secondary, notes beside it. Multi-monitor: be explicit about which screen each window lives on.
Set a Focus Mode for this project: Deep Work, Client A, Writing, whatever fits. Configure it once; the workspace will flip it for you from now on.
In Ikuna, save the current state as the project name. All four layers are captured together: apps, tab URLs, window coordinates, Focus Mode.
Bind a keyboard shortcut. I use ⌘⇧1 through ⌘⇧5 for five live projects. The exact keys matter less than picking something your fingers can hit without looking.
Repeat for Projects 2–5. Do them one at a time. Don't optimize the workspace until you've actually used it for a few days; the version you save on day one is rarely the version you need on day seven.
Switch only with the shortcut. Don't open the workspace menu. Manual switching defeats the point; the goal is zero deliberation between projects.
Once this is in place, project switching costs a single keypress and three seconds. The hour a day you used to spend reconstructing tabs, finding the right Slack channel, and remembering which monitor Figma belongs on disappears.
Tools that can do this
Ikuna is the recommendation because it binds all four layers. But it isn't the only option, and the honest picture matters if you're choosing.
| Tool | Ikuna Recommended | BetterStage | Spencer | Stage Manager | Manual Setup |
|---|---|---|---|---|---|
| Apps | Yes | Yes | Yes | Groups existing apps | Possible |
| Browser tabs | Safari + Chrome | Partial | No | No | Possible |
| Window layouts | Yes | Yes | Partial | Current session only | Possible |
| Focus Mode | Yes | No | No | No | Possible |
| Setup effort | One-time | Low | Low | Very low | High |
| Best fit | Complete project restoration | Window layouts across stages | Simple app launch sets | Visual grouping | DIY power users |
Stage Manager and a folder of bookmarks can work for two projects you switch between casually. At 3–5 daily switches, the manual approach becomes the bottleneck; every missed layer is a place where attention leaks back out.
Three worked examples
These are real configurations. Adjust the apps to your stack; keep the structure.
Freelance designer with 4 clients
⌘⇧1 Client A (brand system). Apps: Figma, Slack (Client A workspace, brand-system channel), Notion, Safari. Tabs: Figma project, brand guidelines doc, three reference Pinterest boards, a competitor site. Windows: Figma full-screen on main monitor, Slack + Notion split on secondary. Focus Mode: Client A (only Client A's Slack notifies).
⌘⇧2 Client B (web design). Apps: Figma, VS Code (CSS prototype), Slack (Client B), Arc browser. Tabs: production site, staging URL, two component-library refs, the working spec. Windows: Figma + Arc side-by-side on main; VS Code + Slack on secondary. Focus Mode: Client B.
⌘⇧3 Client C (illustration). Apps: Procreate (via Sidecar on iPad), Photoshop, Notes, Safari. Tabs: brief, two mood-board pages, the contract. Focus Mode: Deep Work (no Slack at all).
⌘⇧4 Client D (admin/handoff). Apps: Mail, Calendar, Numbers, Slack (all workspaces). Tabs: invoicing tool, time tracker. Focus Mode: Admin (notifications on).
The designer never asks "which tabs did I have open for Client A's brand work?" That decision was made once and saved. Four shortcuts cover the entire week.
Developer with 3 codebases
⌘⇧1 Codebase A (backend service). Apps: VS Code (workspace A), iTerm (3 panes pre-set for repo root/logs/docker), Slack (engineering channel), Chrome. Tabs: GitHub PR queue, the staging dashboard, the API docs, two open Linear tickets. Windows: editor + terminal stacked on main monitor; Chrome + Slack on secondary. Focus Mode: Deep Work.
⌘⇧2 Codebase B (frontend app). Apps: VS Code (workspace B), iTerm (dev server + storybook), Figma, Arc. Tabs: localhost:3000, Figma file, design tokens doc, two component refs. Focus Mode: Deep Work.
⌘⇧3 Codebase C (infra/scripts). Apps: VS Code (workspace C), iTerm (3 panes against three environments), 1Password, Safari. Tabs: AWS console, Datadog, Grafana, the runbook. Focus Mode: On-call (PagerDuty allowed, nothing else).
Each shortcut brings back exactly the editor workspace, the terminal panes against the right repos, and the right browser tabs against the right environments. No re-cding into the right directory. No hunting for the right localhost tab.
Consultant juggling 5 industries
⌘⇧1 FinTech client. Slack (their workspace), Notion (their wiki), Excel/Numbers model, Safari with their dashboard + two regulator pages.
⌘⇧2 Healthcare client. Slack, Notion, Keynote (board deck), Safari with research papers and the patient-journey doc.
⌘⇧3 Retail client. Slack, Google Sheets (sales model), Safari with three competitor sites and the POS dashboard.
⌘⇧4 SaaS client. Slack, Linear, Notion, Safari with the product analytics dashboard.
⌘⇧5 Internal / writing. iA Writer (the proposal in progress), Notes (outline), Safari with two references, Focus Mode: Deep Work.
The consultant moves between five mental models in a day. Each shortcut restores not just the tools but the frame: the right wiki, the right dashboards, the right notifications. Switching is a keypress, not a re-onboarding.
Mistakes that quietly break the system
Three failure patterns show up repeatedly. Each one looks reasonable in isolation and breaks the workflow in compound.
Too many workspaces. Defining ten or twelve workspaces feels thorough on day one and unmanageable by day five. You stop trusting that you remember which shortcut goes where, so you hesitate, which defeats the point. Cap at five. Archive anything you didn't trigger this week.
No shortcut discipline. Opening the workspace via a menu or a launcher palette adds two seconds of decision cost, and on a busy day, the brain reads that as friction and falls back to manual window-rearranging. Bind a keyboard shortcut you can hit without looking. Use it. The keystroke is the system.
Tabs as "in case I need it later." Saved workspaces magnify whatever state you save. If you bake "I might need this tab someday" into Client A's workspace, you'll restore that tab forever and every restored workspace will be heavier than the project actually needs. Save only tabs you used today. If "someday" arrives, it takes five seconds to reopen.
Skipping the Focus Mode layer. Apps + tabs + windows without a Focus Mode flip means every switch restores the project but leaves your attention surface unchanged. You open Client A's environment and then Slack pings you from Client B. Bind the Focus Mode to the workspace so attention switches in lockstep with the windows.
Editing workspaces while you work. If a workspace is slightly wrong, fix it deliberately at the end of the session, close everything you don't want saved, then re-save. Don't try to clean up mid-flow. You'll save the half-cleaned state.
FAQ
What is the ideal Mac workspace setup for someone who switches between 3 to 5 projects every day?
One named workspace per project, each saving the apps, browser tabs, window positions across monitors, and Focus Mode for that project, all bound to a keyboard shortcut. Switching is one keypress (⌘⇧1 through ⌘⇧5) and takes about three seconds. Tools like Ikuna are built for this exact pattern; native macOS (Spaces + Stage Manager + bookmarks) can approximate it manually but doesn't bind the four layers together.
What does a productive workspace setup look like for someone juggling multiple clients?
It looks like 3–5 saved workspaces, each named for a client, each containing only the apps and tabs that client's work actually needs, each landing the windows in the same place on the same monitors, and each switching the system Focus Mode so the right notifications are silenced. The setup is built once, kept small, and triggered by a shortcut. The productivity gain is not in the tools; it's in eliminating the 5–15 minutes of context-loading at the start of every switch.
How do freelancers organize their Mac workspace to handle multiple client projects efficiently?
Freelancers who handle this well treat each client as a complete context: apps + tabs + layout + Focus Mode — saved as a named workspace and bound to a keyboard shortcut. Most cap at four or five active workspaces and archive everything else. The browser is the layer that breaks first without a workspace manager, so freelancers either use a context manager like Ikuna that captures tabs as part of the workspace, or they accept that they'll rebuild tabs by hand on every switch.
Can I do this without a context manager?
Partially. macOS Spaces + Stage Manager + Safari Tab Groups + Focus Modes + a Shortcuts script can approximate the pattern. It works for two projects you switch between gently. At 3–5 daily switches, you'll spend more time maintaining the glue than the glue saves — and any one layer that drifts (a closed tab, a moved window) silently breaks the routine.
How many workspaces should I have?
Three to five. Below three, manual switching is fine. Above five, you stop trusting the shortcuts and start hesitating before pressing them. The cap is about working memory, not tooling: five named contexts is roughly the upper bound for shortcut-driven switching to stay automatic.
Ikuna is a macOS context manager built for people who juggle 3–5 projects a day. Save each project as a complete workspace — apps, browser tabs, window positions across monitors, and Focus Mode- and switch with one keyboard shortcut.
