Creative Toolkit All articles
Tools & Reviews

Your Laptop Doesn't Need a Twin: Splitting Client Work Into Its Own Space on One Machine

Creative Toolkit
Your Laptop Doesn't Need a Twin: Splitting Client Work Into Its Own Space on One Machine

Photo: Aleksi Tappura a, CC0, via Wikimedia Commons

There's a moment in every freelancer's life when you look at your desktop — 43 files, two open client decks, a half-finished invoice and a photo of your mate's dog — and think: I need a second machine for work.

You probably don't. A second laptop means a second backup routine, a second set of licences and another grand and a half you could spend on fonts. What you actually need is separation, and separation on a single Mac or PC is mostly a matter of three layers stacked in the right order.

What this is really solving

Be honest about the problem before you start moving files around, because the fix differs depending on which bit is annoying you.

Layer one: a separate user account

This is the big lever and it takes five minutes.

On a Mac: System Settings, Users & Groups, Add Account. Choose Standard rather than Administrator. That's deliberate — a standard account can't install software or change system settings without an admin password, which is precisely the friction you want when a trial installer is whispering to you at 11pm.

On Windows: Settings, Accounts, Other users, Add account. When it asks for a Microsoft account, choose 'I don't have this person's sign-in information' and then 'Add a local account without a Microsoft account'. Name it something like Studio rather than your own name.

Log in for client work. Log out at the end of the day, or use fast user switching — Control-Command-Q on a Mac, or the account switcher on the Start menu — so the boundary is a real action rather than a tab.

Be aware of the trade-offs. Disk space is shared across accounts, so you're not creating a private drive. Some apps licence per user account rather than per machine, so check before you assume a second installation is covered. Fonts activated through a manager may behave differently depending on the account. And cloud sync can be confusing, because iCloud Drive's Desktop & Documents syncing is per account — if you move a project into the Studio account, it stops appearing in your personal iCloud until you set something up deliberately.

Layer two: browser profiles

Half of work separation is really login separation. A profile per client, or at minimum one for work and one for everything else, keeps agency dashboards out of your personal bookmarks bar.

Chrome and Edge both support multiple profiles with their own extensions and saved passwords. Firefox has Multi-Account Containers if you prefer to stay in one window. Recent versions of Safari have profiles too, tucked under the File menu.

One genuinely useful trick: keep an empty 'Review' profile with no extensions at all. Load the client's site there and you see roughly what they see, and any screen share shows a clean window rather than your entire digital life.

Layer three: a folder structure that does the thinking

Build this at the root of your drive, not buried three levels into Documents. Something like:

Studio 2026/
  00_Admin/
  Clients/
    Client Name/
      0_Brief/
      1_Working/
      2_Review/
      3_Final/
      4_Handover/
  Assets/

The numbering matters more than the naming. It forces alphabetical sorting to match the actual order of a job, so 'Brief' never ends up below 'Working' in a list.

The rule that makes it work: if it can't be handed over, it isn't client work. Personal admin, invoices to your accountant and that half-finished font experiment belong somewhere else.

Trials, licences and the audit you never do

Install trials inside the Studio account. Note the expiry date in the admin folder the moment you install — a two-line text file is enough. Then, twice a year, spend fifteen minutes listing what's installed there, which items are on subscription, which are trials that quietly rolled over, and which are legacy installs you've stopped opening.

Fonts deserve their own note. Knowing which foundry licence covers which client is the difference between a confident email and a very awkward one, and the desktop licence almost never covers the client's web use.

The 30-minute setup checklist

  1. Create the Studio account as a standard user, with its own password (5 min).
  2. Turn on FileVault or BitLocker if it isn't already — the encryption runs in the background for hours, so start it early (2 min).
  3. Build the folder skeleton with the numbered subfolders (5 min).
  4. Create one browser profile per active client, plus a bare Review profile (6 min).
  5. Move existing client files into the skeleton, leaving anything personal behind (10 min).
  6. Drop a read-me in each client folder with the job code, PO number and deadline (2 min).
  7. Set a monthly reminder to empty Downloads and check the trial list (1 min).
  8. Test it: log out, log back in, confirm you can reach everything you need and nothing you'd rather not show (5 min).

When one machine genuinely isn't enough

There are real cases. If a client contract requires data segregation, if you're handling sensitive personal data at any scale, or if you're doing app development with two mutually hostile SDK versions, that's when a second machine or a virtual machine earns its place — Parallels or UTM if you need Windows on a Mac.

For everyone else, the account, the profile and the folder will do. It's less glamorous than a new laptop, and it takes half an hour on a Tuesday. But it means the next handover is a zip file rather than a scavenger hunt.

All Articles

Related Articles

Someone Else's Folder, Your Problem: A Field Guide to Taking Over a Half-Built Design Project

Someone Else's Folder, Your Problem: A Field Guide to Taking Over a Half-Built Design Project

One Folder, Two People: Building a Studio Library That Survives the Second Week

One Folder, Two People: Building a Studio Library That Survives the Second Week

Your Final Files Shouldn’t Need a Rescue Party: Build a Handover Folder That Works

Your Final Files Shouldn’t Need a Rescue Party: Build a Handover Folder That Works