Every client's data, cleanly separated.
Run a workspace for every client from one admin account. Each client's files, CRM connection, and history stay in their own space, and it all bills to your one Agency plan.
A workspace per client, one admin account.
You hold the admin account and reach every client. Each client is its own workspace, so files, mappings, and CRM connections never cross over, and every job is billed to your Agency plan.
One account, every client
Isolated workspaces, side by side.
Give each client its own space and logo. Files and CRM connections stay separate; credits are drawn from your shared Agency pool.
| Client | Status | Members | Verify credits | Job credits | Actions |
|---|---|---|---|---|---|
Northbeam Analytics B2B SaaS | Capped | JD | 1,240 / 4,000 | 32 | Settings |
Vantage Capital Financial services | SP | 860 | 21 | Settings | |
Meridian Consulting Consulting | Capped | JD | 3,100 / 5,000 | 44 | Settings |
Talentforge Recruiting | MR | 540 | 12 | Settings | |
Corewave IT Managed IT | MR | 2,015 | 58 | Settings | |
Harbor & Cole Legal services | SP | 1,180 | 27 | Settings |
Your controls
Set the guardrails per client.
Assign your own team to each client, and cap their credits per cycle so no one account runs the pool down.
Push into each client's own CRM.
Connect each workspace to the CRM that client actually uses. Map their columns, push a clean file straight in, and one client's connection never touches another's.
- HubSpot, Salesforce, or Pipedrive. Each client connects its own account.
- Push from Operelio. Send a clean, mapped file into their CRM without leaving the app.
- Kept separate. A connection lives in one workspace and is never shared to another client.
HubSpotConnected
SalesforceConnect
PipedriveConnectSkip the CSV handoff and the systems project.
When a campaign delivers, the leads have to reach the client's CRM. Agencies usually get there one of two hard ways.
The usual way
The weekly CSV email
Every send means getting the file into that client's exact format, attaching it to an email, and leaving the import to them. Multiply it by every client, every week, and hours of your retainer go into a deliverable that's still just an attachment.
The technical way
Wire the two CRMs together
A direct CRM-to-CRM link means developers, middleware, and field mappings nobody on the account team can touch. Weeks of setup, repeated for every client.
With Operelio
One approval from your client
Your client approves a standard OAuth connection to their CRM, the same consent screen any app uses. After that, the weekly delivery takes minutes: the saved mapping formats the file, and the data is in their CRM the moment you push. Nothing to attach, nothing for them to import.
Build it once, use it for every client.
Set up a CRM template, a column mapping, or a workflow once and share it across every client workspace. Build it in one client and promote it to the whole Agency, so no one rebuilds from scratch.
- Templates, mappings, and workflows. Share your setup across the whole Agency.
- Promote from any client. Build it once in a client space and share it with the rest.
- Read-only where it's shared. No one edits your master by accident.
Three client files land. Each goes to the right place.
The same account, three clients, no mix-ups. Every file lands in its own workspace and leaves formatted for that client's CRM.
Three files arrive
A fresh list from each client hits your account before your coffee's cold. Assign each one to its owner with a due date, so nothing sits unclaimed.
Each lands in its own workspace
No copy-pasting between accounts. One client's data never touches another's.
Formatted to that client's CRM
Each file leaves mapped to the CRM that client actually uses, ready to import.
Northbeam → HubSpotVantage → SalesforceMeridian → PipedriveEvery client's data stays walled off.
Each client lives in its own workspace. Files, jobs, CRM connections, and history stay inside it, so nothing leaks between clients or back to you. When you're handling data on a client's behalf, that separation just matters.
Isolated files and jobs
One client's uploads and runs never appear in another's space.
Separate CRM connections
Each workspace connects its own CRM. Nothing is shared across clients.
Per-client history
Usage and billing are broken out per client, and stay even after you archive one.
Enough room for a full book of clients.
The Agency plan is sized for the throughput an agency runs in a month, with the queue priority and the API to match.
Client workspaces come with Agency.
One plan covers your whole book of clients, billed from a single place.
- Up to 25 client workspaces
- 10 seats included, $25 per extra
- 12,000 verify credits
- 2,000 jobs a month
- Batch processing and priority queue
- API access, 5,000 calls a month
The things agencies ask first.
How does the workspace-per-client model work?+
You run one admin account with a separate workspace for each client, up to 25. You can reach every client workspace, and each client's files, mappings, and CRM connections stay inside their own space.
Do I need to keep each client's data separate?+
It's the safe default. Handling a client's data usually makes you a processor acting on their behalf, and rules like GDPR and CCPA, along with the agreements you sign with clients, expect each client's records to stay in their own space rather than pooled together. Client workspaces give you that separation by default: every client's files, CRM connections, and history stay inside their own workspace. This isn't legal advice and doesn't replace your own contracts, but it's the structure most data rules assume, and if a client asks for a Data Processing Agreement, we have one ready.
Can my clients log into their own workspace?+
No. You assign your own Agency team to the clients they handle, so you stay in control. It's a clean separation on your side, not a client login.
Does each client connect its own CRM?+
Yes. Each workspace has its own HubSpot, Salesforce, or Pipedrive connection, and you push into that client's CRM from Operelio. One client's connection never touches another's.
How do I get access to a client's CRM?+
Your client approves a standard OAuth connection, the same consent screen they'd see connecting any app to their CRM. No developer setup on either side, no API keys to manage, and they can revoke the access from their CRM whenever they choose. The connection lives in that client's workspace only.
Can I reuse templates and workflows across clients?+
Yes. Share a CRM template, mapping, or workflow across every client workspace, or build one in a client and promote it to the whole Agency. Shared items are read-only where they're inherited, so no one edits your master by accident.
How do credits work across clients?+
All clients draw from your shared Agency pool. You can optionally cap verify and job credits per client, per cycle, so no single client runs the pool down.
What's included in the Agency plan?+
2,000 jobs a month, up to 150,000 rows per file, 12,000 verify credits, 10 seats, batch processing (50 files, 500,000 rows), the public API (5,000 calls a month), and priority processing. Email verification runs up to 25,000 rows per day.
Is everything billed together?+
Yes. Every client workspace is billed to your one Agency plan from a single place, and you get a per-client usage breakdown so you can see where the credits went.
Give every client a clean, separate space.
One account, one bill, every client kept apart.