Several clients in one workspace, separated at the query.
Running outreach for several clients is not one job repeated. It is one workspace where every lead, mailbox and number has to belong to exactly one client, and where the separation cannot depend on whoever is at the keyboard.
No payment method. No recurring charge. Your own SMTP, your own data.
- Data model
- Organisation, projects, campaigns
- Roles
- Owner, admin, member, viewer
- Isolation
- Organisation on every query
- Sending
- Project accounts only
- Lead discovery
- Deliverability
- Replies and inbox
- How data is handled
- One project per client
- Roles and invitations
- Per-project analytics
- Shared knowledge base
Client separation usually lives in habits, not in the software.
The tooling treats every campaign as equal, so the only thing keeping one client's list, domain and numbers away from another is a naming convention and the attention of whoever opens the tab.
Everything in one flat list
Leads, sequences and campaigns for every client sit side by side. Finding this week's work for one account becomes a filtering exercise, and the filter is a prefix somebody typed by hand.
The wrong mailbox on the right campaign
One misselected sending account and a client's prospect receives outreach from a different client's domain. Recovery is a conversation, not a fix.
Access that is all or nothing
A contractor brought in for one account gets a login that reaches every account. The alternative is a separate tool per client, paid for and maintained separately.
Numbers nobody can attribute
A dashboard that totals every client together answers no question a client asks. Splitting it means exporting and rebuilding the report by hand each month.
Four decisions that keep client work apart by default.
The structure is deliberately small: an organisation holds projects, a project holds campaigns, and a project is how you represent one client. Everything else follows from that.
- 01
One project per client
A project is the container for that client's leads, campaigns, sequences, mailboxes, saved searches and analytics. Nothing sits above the project except your organisation, so there is no ambiguous middle ground where shared work accumulates.
- 02
Invite the team with a role
People join by email invitation and arrive with one of four roles. Owner and admin manage the team, a member creates and edits, and a viewer reads without being able to change anything.
- 03
Attach the sending accounts
Mailboxes belong to a project. A campaign can only start with email accounts from the same organisation and the same project, so a send for one client cannot leave from another client's domain.
- 04
Read the numbers per client
Analytics for sent volume and replies are filtered by project or by date range, and the Analyst agent describes the trend in plain language rather than leaving you to interpret a chart.
A client is a project, not a naming convention.
The workspace switcher is the whole model in one panel. Each project carries its own campaigns and its own role for the person looking at it, and the scope travels with every request rather than being reapplied by hand.
- Analytics, leads, sequences and settings each have a per-project view
- Saved searches and their schedules stay inside the project that owns them
- Switching organisation invalidates the query cache, so nothing lingers on screen
- Every query filters by organisation before anything reaches a screen
Every list you open already knows whose it is.
A lead pool, a pipeline board or a health view is scoped before it renders. The ProjectFilter control on pipeline, health and knowledge narrows the view to one client without changing what anyone is permitted to reach.
- Leads, campaigns and mailboxes are scoped to a single project
- ProjectFilter narrows pipeline, health and knowledge to one client
- A viewer sees the same data as a member and can change none of it
- The knowledge base is an organisation asset, filtered down per project
The gain is not a feature. It is one fewer thing to remember.
One login for the whole book of clients
Adding a client is a project, not another subscription, another set of credentials and another tool to keep in step with the rest.
Separation the software enforces
Scope is applied on the way to the database rather than by the person reading the screen. Discipline stops being the control.
A sending identity per client
Because mailboxes belong to a project, a campaign starts only with accounts from that client. Outreach never leaves from a domain that belongs to somebody else.
Access sized to the person
A freelancer can be a member on the account they work on, a client contact can be a viewer, and neither arrangement requires a separate workspace.
Answers per client, not per agency
Sent volume and replies filtered by project mean the monthly conversation starts from the product rather than from a spreadsheet somebody rebuilt.
Shared knowledge, scoped reading
Documents uploaded to the knowledge base stay an organisation asset while still being filtered per project, so a playbook is written once and applied where it belongs.
How the workspace behaves in practice
Multi-client work is a set of edge cases about who can reach what. These are the ones that come up first, answered plainly, including where the product is still early.
What the multi-client model actually is
The short version, without marketing adjectives, for the person deciding whether a client's list can live in here.
- Hierarchy
- Organisation, project, campaign
- One client
- One project
- Roles
- Owner, admin, member, viewer
- Viewer
- Read-only
- Team access
- Invitation by email
- Query scope
- Organisation on every query
- Project scope
- Leads, campaigns, mailboxes, analytics
- Sending accounts
- Same organisation and project
- Organisation switch
- Query cache invalidated
- Project filter
- Pipeline, health, knowledge
- Knowledge base
- Organisation-wide, filtered per project
- Plans and limits
- Not yet active
What keeping clients apart stops depending on.
| Today | In MyLeadTeam |
|---|---|
| A separate tool, login and invoice for each client you take on. | One organisation with a project per client, added without another subscription. |
| A prefix in a campaign name as the only thing marking whose work it is. | A project that owns the leads, campaigns, mailboxes and analytics underneath it. |
| Full access for everyone, because the tool has one level of permission. | Four roles, from an owner who runs the organisation to a viewer who can only read. |
| A sending account picked from a global list and occasionally picked wrongly. | Campaigns that can only start with accounts from the same organisation and project. |
| A monthly report rebuilt by hand from an export of everything at once. | Sent volume and replies filtered by project and date, described in plain language by the Analyst. |
Questions people ask about this
Get started
Give every client a workspace that ends at their own data.
Set up one project per client, invite the people who need it with the role they need, and let the structure do the separating.
No payment method or recurring charge during early access.