Multi-workspace is not multi-tenancy (and why operators care about the difference)

Most CRMs treat 'multiple businesses' as 'multiple accounts'. You log into one, log out, log into another. Your context is fragmented. Your follow-ups are slower. You start losing track. That's the default the industry inherited from the early 2010s, and it's quietly the reason operators who work across more than one workspace either over-rely on a single CRM (and watch their categorisation rot) or churn between tools every six months.

There's a better shape, and the difference between the two is worth naming.

Multi-account is the wrong shape

Multi-account means each workspace has its own login, its own session, its own credentials. The operator who needs cross-workspace context is forced to do it in their head, in a spreadsheet, or in some hand-rolled middleware that breaks the day they upgrade. Switching costs are baked into every action — every tab, every search, every report.

Multi-account also breaks at the boundaries. Where does a contact who works in both workspaces live? What happens when the same lead exists in two places? Which workspace's tags apply when you merge? Most tools answer these by punting — 'pick one and accept the data debt'. That's the wrong answer for an operator who genuinely works across workspaces.

One user, many workspaces

Briefi's model is one user, many workspaces. I switch between the workspaces I'm a member of in the sidebar — same browser tab, same login. My calendar, inbox, pipeline, and CRM stay segregated per workspace. Membership in each workspace is its own grant; my role can differ (owner here, member there). The data never bleeds.

A workspace doesn't have to be a separate registered business. It might be a consulting engagement, a personal project, a board seat, a brand inside a larger company, or just a context I want kept distinct. The criterion isn't 'is this a different legal entity'. It's 'are these meetings and contacts qualitatively different enough that I want a switch between them, not a filter'.

What stays separate, what stays unified

Per-workspace, segregated: calendar events, contacts, deals, email threads, briefs, discovery guides, CRM connections, scheduling pages, IMAP mailboxes. Each workspace can have its own Google account, its own CRM provider (HubSpot here, Salesforce there), its own discovery guides, its own brand colour.

Unified across workspaces: my identity (one login, one MFA factor, one billing relationship), my voice profile (so AI-written emails sound like me everywhere), and Command — the cross-workspace search that's been quietly the most-used feature since I started dogfooding. Command is what makes the multi-workspace model viable; without it, you'd be doing parallel mental searches every time you remember someone's name.

The per-workspace integrations point

The integrations layer is where multi-workspace earns its keep. Each workspace can connect to a different CRM — one to HubSpot, one to GoHighLevel, one to Monday, one to Salesforce. Each workspace can have its own Google account for invites + Gmail. Each workspace can have its own IMAP mailbox for non-Google inboxes. The plan caps the totals; the architecture handles the segregation.

The same shape lets a consultant working with five clients keep five distinct CRM destinations from one Briefi login. It's the cleanest way to handle 'every client has a different stack' without the operator paying a context-switching tax all day.

A workspace is a role, not a company

If you only ever work in one workspace, none of this matters. If you work in two, you'll feel the difference in week one. If you work in three or more, this is the architecture you want.

The mental model I keep is: a workspace is a role, not a company. The director-of-marketing role at a partner brand is one workspace. The board-seat role at a non-profit is another. The personal-venture role is a third. Each one has its own rhythm, its own contacts, its own outcomes — and a single tool that supports all three without making me log in and out is the difference between sustainable and exhausting.

The full multi-workspace setup is on the product page. Connecting each workspace to its own CRM is documented under integrations. And for the founder's reasoning behind the architecture, see why I built Briefi.