The unfortunate truth about freelancing in 2026 is that every client gives you an email address on their domain. After two years you have four. After five years you have eleven, three of which belong to clients who stopped paying you.
You wake up. You check four mailboxes. One has a 9 a.m. fire. Two have nothing. One has a contract you should have signed yesterday but missed because it was on the dormant account.
This is the freelancer's tax. Here is how to stop paying it.
The four-account anatomy
A typical freelancer's mail looks like this:
- Personal Gmail. Family, banking, the side project.
- Hello@yourstudio.com. Your business address. Goes through Workspace or Fastmail.
- You@client-a.com. A client gave you a seat in their Workspace.
- You@client-b.com. Another client gave you a seat. Different provider.
- iCloud or yahoo from 2008. The address you used in college, that some recruiters still find.
This is normal. We are not telling you to consolidate. Some of these you cannot consolidate. Client-a controls that domain.
The fix is at the client layer, not the address layer. Every account in one window. Every reply from the right address, automatically.
The three rules of multi-client mail
- Read all clients in one queue. Switching by client is what eats your morning. The triage layer should not care which client a thread came from.
- Reply from the address that received it. If client-a emailed you-at-client-a, your reply goes from you-at-client-a. No alias confusion.
- Bill the time you spend in inbox to the right client. Tag threads by client and use those tags as a billing input, not just a filter.
If you can do these three, your week gets shorter by hours.
What goes wrong with most setups
Native Apple Mail with all four accounts: you can do it, but switching identities on reply is fragile and you will, at some point, send a client's response from your personal Gmail. We have all done it. It is embarrassing.
Spark in unified mode: better. Still does not bill time per client.
Four browser tabs: fastest path to a stress headache.
Forward everything to your primary: breaks reply identity entirely. Now your client-a customer thinks you are responding from a strange Gmail.
There is no good native solution. This is why we built STAMP.
What STAMP does
We connect every account, including the dormant iCloud and the client Workspace seats, into a single triage queue. The seven threads needing your attention today are pulled from across all of them.
When you reply, STAMP picks the right outbound address automatically. You do not think about it. You just type.
Threads are auto-tagged with the client name, derived from the recipient address. You can search “client-a” and see every thread, ever, regardless of which mailbox it was in. You can export “hours spent in client-a threads this week” for billing.
If your inbox does not know which client an email is from, you are doing your invoicing twice.
A typical freelancer day with the system
It is 8:42 a.m. You open one window. STAMP says: “Working late, Maya. 6 need attention.”
- Top: client-a, frustrated, third follow-up. Tag: Reply needed, VIP. Reply.
- Next: client-b, contract attached. Reply with a sentence.
- Next: personal, from your accountant. Reply.
- Next: client-c, FYI thread, not asking you anything. Archive.
- Next: client-a, scheduling. Snooze to 2 p.m.
- Next: cold pitch from a recruiter on iCloud. Archive.
Twelve minutes. Six replies. Inbox at zero. Four clients, one window. You go back to the work clients are paying for.
Time-tracking from email
This is the freelancer-specific superpower most clients miss. STAMP tracks how long you have a client's thread open and active. Not as keystroke surveillance. As a friendly nudge.
At the end of the week, STAMP shows you: “You spent 4h 12m in client-a inbox, 2h 38m in client-b inbox, 1h 04m in client-c.”
You bill the right amounts. You stop forgetting that the “quick email” from client-a was actually 90 minutes of back-and-forth on Tuesday afternoon.
When you sunset a client
When a client wraps up and you lose access to their domain, STAMP keeps the historical threads, indexed and searchable, in a read-only state. Client-c stops sending you mail, but you can still find “that brief from June 2024” in two seconds.
Most clients lose this when the seat closes. We do not.
What to do this week, even without a tool
If you cannot install STAMP yet, three quick wins:
- Add every client account to a single email client (Apple Mail, Spark, anything that takes IMAP). Stop browser-tab-juggling.
- Set up reply-from-receiving-address as the default in your client's settings.
- Tag threads with a client label every time you read one. Friction, but useful for billing audits.
This is a manual version of what STAMP automates. It works at half the speed and full discipline.
Where to go from here
For the philosophy, multiple email accounts — the hidden cost. For the operator's version of the same problem, how operators handle 300 emails a day.
Or jump straight to STAMP for freelancers and try the unified inbox we built for this exact mess.
Four clients. One window. hello@stamp.email