Multi-Accounting for Consultants: One Freelancer, Many Clients
Freelance consultants juggling multiple client logins face real risk from shared browsers. Here's how to isolate client accounts properly.
A marketing consultant, an outsourced HR specialist, a business coach, a financial advisor, a virtual assistant — all these professions share a problem that rarely gets written about: the person works not in their own account, but in a dozen other people's accounts, all inside one browser on one laptop. Agencies have a team and processes for this. A freelancer has only themselves and tab after tab.
The difference from agency-style multi-accounting is fundamental: there's no department issuing access and enforcing rules. One person logs into Client A's CRM, Client B's ad account, and Client C's email — all physically in the same Chrome instance where their personal bookmarks, saved passwords, and cookies live. If you've already looked at similar cases for accountants and lawyers in our post on client portals for accountants and lawyers or for IT outsourcing in access to clients' SaaS consoles, the logic will feel familiar — except here everything rests not on team processes, but on one person's discipline.
What goes wrong in a single browser
If you run five to ten clients through regular tabs or even Chrome profiles, sooner or later one of three things happens.
Context bleed. You're logged into a client's LinkedIn, you open a second tab for your personal account — and the platform sees both logins from the same browser fingerprint and IP almost simultaneously. For social networks and ad platforms, that's a trigger for account linking, even if you're technically doing nothing wrong — just handling your work and your personal life in parallel.
Actions sent from the wrong identity. A post to a client's social account published from your personal profile, an email sent from the wrong inbox, a comment left under a competitor's project from a work profile — classic freelance mistakes when ten tabs are open at once and attention is split. For a consultant whose entire pitch is trust and precision, that kind of slip costs more than it looks like it should.
Autofill leaks. The browser suggests Client A's password when you log into a service for Client B with a similar-looking interface. Address and card autofill work the same way: one wrong click and someone else's data lands in the wrong form.
Chrome profiles partially solve the cookie-separation problem, but they share a device fingerprint, a shared IP, and have no real access management if a client asks you to be temporarily disconnected from their account. The difference between ordinary browser profiles and isolated ones is covered in Chrome profiles vs. an antidetect browser — for a consultant handling clients' money and reputation, the line between "regular profiles are enough" and "isolation is needed" gets crossed fairly early.
What a client profile looks like
The practical rule is simple: one client, one profile, regardless of how many services that client uses. The profile holds the cookies, history, bookmarks, saved passwords, and extensions that belong specifically to that client.
What travels with the profile as a whole
- Cookies and sessions — imported at the start of the engagement if the client has already granted active access, or created fresh on first login. JSON or Netscape format works for moving sessions between tools if a client switches contractors.
- Bookmarks — links to dashboards, documentation, internal wikis. A bookmark template is worth setting up once and reusing for new clients of the same type (all Shopify clients, say, get the same set of links to admin, analytics, and billing).
- Extensions — some clients require a specific plugin: a time tracker, a CRM add-on, a corporate SSO tool. Keeping it only in that client's profile, rather than in all of them, makes sense both for privacy and for browser performance. There's a separate breakdown of the upside and risk of extensions in profiles in extensions in antidetect profiles.
- Client password and 2FA — if a client set up two-factor authentication on their account and shared the secret key with you, it belongs in the profile's key vault, not in a phone's notes app or a shared password manager where it risks ending up in the wrong folder.
Proxy and geography matched to the client
If a client operates in a different country or city — say, you're running local marketing for a business in another region, or setting up geo-targeted ads — it makes sense to attach the profile to a proxy with the matching exit IP. Time zone, interface language, and browser geolocation follow from that same IP automatically, so the client's account sees a visit from their region, not from yours.
This matters especially for ad accounts and analytics: Google Ads, Meta Ads, and similar platforms show different interfaces and available features depending on the account's country, and some local services (delivery, classifieds, marketplaces) block access entirely from outside their region. Different proxy types for different tasks are covered in proxies for multi-accounting — for a consultant with a handful of clients, a couple of static IPs per regional client is usually enough, without paying for rotation you don't need.
Organization: groups, templates, order
With five clients, you can keep order in your head. With fifteen, you can't. A sensible structure looks like this:
- Group by client, not by platform. Inside the "Client A" group sit all of that client's profiles: one for the CRM, one for social media, one for email, split further by task if needed.
- A consistent naming convention and tag inside the profile — client name, engagement start date, access level (full / read-only / temporary). Once you have more than ten clients, searching by name is faster than remembering which tab was which.
- A template for new projects — if you regularly take on similar clients (say, you always set up the same stack: a Shopify site, Google Workspace email, Meta ads), a pre-built profile with the right bookmarks and extensions saves fifteen minutes at the start of every engagement.
- A monthly review — closed projects shouldn't sit around as active profiles with live sessions. Once a client's access is closed, export the profile if you need the history for a report, then delete or archive it.
There's a separate piece on scaling this logic to hundreds of profiles, for when one consultant grows into a small studio with subcontractors — organizing profile pools at scale. The jump from "just me" to "me plus two subcontractors" usually happens faster than expected, and that's when you need roles and limits rather than just tidy folders — covered in roles, limits, and profile handoff.
What it costs for one person
The economics are simple for a freelancer, unlike the team-budget math in the unit economics of multi-accounting. At the start, with one or two clients, the free plan's three profiles are enough. Once you pass three clients — which happens within the first month or two for an active consultant — the Starter plan makes sense: 20 profiles for $5 a month. That covers roughly 6–10 clients if you set up two or three profiles per client for different services.
| Plan | Profiles | Price/mo | Best for |
|---|---|---|---|
| Free | 3 | $0 | Trial period, 1–2 clients |
| Starter | 20 | $5 | Active freelance, 6–10 clients |
| Base | 100 | $44 | Consultant with subcontractors or a larger client roster |
If you bring in a subcontractor — an assistant who handles routine tasks for some of your clients — role separation and limiting access to only the relevant profiles, rather than the whole pool, becomes useful. That's team functionality, available from higher plans, described in detail on the team page.
Security: the thing consultants promise clients but rarely can prove
A client who grants you access to their ad account or CRM is, formally, trusting you with more than just your actions — they're trusting you with the safety of their data. If a laptop gets stolen and client passwords were sitting in a text file or unprotected browser autofill, that's not an abstract risk — it's a real incident you'll have to explain to the client.
Profiles with on-device encryption remove part of that risk: profile data is encrypted with the account password right on the device, and even if sync runs through a server, the server can't read the profile's contents. That doesn't replace basic hygiene — a strong password, system updates — but it does close off one specific scenario: compromise of the storage service itself. More on how encryption and the 2FA key vault work in profile security, and a general description of the mechanism on the security page.
Common mistakes consultants make when switching to profiles
Setting up a profile only for "sensitive" clients. The logic of "this client needs isolation, this one doesn't" eventually breaks down — it's often the "simple" client whose account ends up linked to the consultant's personal profile because of a shared IP or leftover cookies from a previous session in a regular browser.
Not splitting profiles within a single client. If a client has both an ad account and personal correspondence with their team, plus a CRM holding sensitive data about their own customers, lumping it all into one profile isn't always right. Each service carries a different risk level and different access rules.
Forgetting to close access when a project ends. The client switched contractors, but the old profile with an active session keeps sitting on the consultant's disk. That's both a security risk for the client and clutter that makes it harder to navigate your own profile pool.
Using the same proxy for every regional client. If two clients from different countries log in through the same exit IP, that's noticeable both to the platform's anti-fraud systems and to the clients themselves if they check access logs.
When profiles are overhead, not help
If you have one steady client and occasional quarterly projects, a dedicated antidetect profile for each one is overkill. Ordinary browser profiles with separate passwords are fine as long as the number of simultaneously active clients stays at two or three and none of them are in security-sensitive fields (finance, healthcare, legal practice). The switch makes sense once the number of concurrently active client accesses starts getting in the way — that is, once you're spending time not working, but trying to remember which account you're currently logged into.
You can start on the free plan from the pricing page and set up two or three profiles for your current clients to see the difference before committing to a paid plan. The app runs on macOS and Windows and can be downloaded from the download page.
In short
A consultant without a team is solving the same problem an agency with ten employees solves — isolating client data and handling other people's accounts carefully — but without processes and without a security department. A profile per client, with its own cookies, proxy, passwords, and 2FA, closes most of the risk: context bleed, actions sent from the wrong identity, data leaks if a device is lost. It doesn't require complex infrastructure — just the discipline to set up a profile at the start of each engagement and close it at the end.
FAQ
Do I need a separate profile if a client only gave me read-only access? Yes, if you're logging into their account under their credentials even occasionally. The risk of account linking doesn't depend on your permission level — it depends on which device and IP you're logging in from.
What if a client asks me to just send the password instead of using a secure vault? Explain that you store access credentials encrypted and don't share them with third parties — that's a point in your favor, not an inconvenience. If the client insists, put it in writing: responsibility for security then shifts partly onto them.
Can I hand off a client's profile to another specialist if I leave a project? Yes — profile handoff exists exactly for this. Access transfers without rebuilding from scratch, keeping history and cookies if that's appropriate for the new person taking over.
How many profiles does one consultant actually need? A good rule of thumb is two or three profiles per active client: one for the main work account, one for communication (client email, messenger), and sometimes a separate one for analytics or an ad account if security requirements are high.