Five clients, five clean workspaces.
Each client gets its own workspace — its own offer, lists, sequences, inbox and LinkedIn limit — so nothing leaks from one to another. Each client's banned claims are written down once instead of remembered, and every approval sits next to the message it cleared.
Three failures that cost accounts, not just replies
The client reads your weakest writer
Your best rep is fine. The one who started in March writes a second paragraph you would never have signed off, and that is the email the client forwards to you.
The claim they banned goes out anyway
Every client has a line they will not have said in their name. Keeping that in four people's heads works until the week someone is covering for someone else.
Approvals vanish into chat threads
Sign-off happens in a thread, the send happens in another tool, and the reply lands in a third. When the client asks who approved what, nobody can answer without an archaeology dig.
Drafting is automatic. Approval is not, on purpose.
The repetitive half runs itself. The half a client would fire you over waits for a person.
- 1
A space per client, a role per person
Admin, manager and rep inside a workspace, plus an organization owner above them. A rep works inside the client they are assigned to and sees nothing of the others. Managers approve; reps draft.
Settings → Team - 2
Write the client's rules down once
Their offer, their sender, their tone, the claims that are off limits and any disclaimer that must appear. Drafts are written from that rather than from whatever a rep remembers.
Settings → Business context - 3
Reps build the cadence, drafting is done for them
Emails, waits and LinkedIn touches, with the copy drafted against that client's own offer. Once started, the cadence advances on its own and the follow-ups happen without a reminder.
Sequences - 4
A manager clears the queue, and that is the QA step
Every draft arrives with a quality score, flags on anything risky and a countdown. Approve, edit, or reject with a reason. What nobody approves expires instead of sending.
Campaigns → Message review - 5
The client report is the record you already made
Who approved which version, when it went, and whether it was delivered, failed or blocked. Replies arrive tagged by what the prospect actually wanted.
Analytics · Inbox
One workflow, three people in it
Roles are not decoration here: a rep cannot dispatch, and a manager's approval is recorded against the exact version that went out.
Your reps
Draft, never dispatch
- Build cadences inside one client
- Get drafts written from that client's offer
- Draft and build; clearing the queue is a separate permission
- See only the client they work on
Your managers
The sign-off
- One queue per client, with a countdown
- Flags on the drafts that need a second look
- Edit a line and approve it in place
- Reject with a reason that stays on the record
Your client
What they get to see
- Mail leaving from their own address
- Their banned claims honoured by default
- A record of what was sent and by whose approval
- Replies triaged by intent, not by volume
Client spaces included per plan — Free, Starter and Professional: 1. Ultra: 5. Enterprise: 25, then arranged with us. What a paid plan scales is volume and credits; it does not scale people. A space beyond what your plan includes is an Enterprise arrangement at $15 a month.
What you can promise a client and actually hold to
QA stops being someone reading everything at nine at night
The queue does the sorting: scored, flagged, and on a clock. A manager spends their attention on the drafts that were marked risky rather than on all of them equally.
A banned claim is a setting, not a memory
Write it into the client's rules once and it applies to every draft afterwards, including the ones written by whoever is covering this week.
Volume is a number you can point at, per client
Each client's mailbox carries its own daily quota, fifty by default and lower if the mailbox says so. LinkedIn carries a separate daily cap per client space, and that one starts closed rather than at a default. Automatic mailbox warmup is not available yet, so on a brand-new mailbox the first week's restraint is yours, not the product's.
A failed send is visible instead of quiet
Queued, dispatched, sent, failed and blocked are all shown against the message. You find out from the screen, not from the client three weeks later.
Read this before you sign up.
A good fit if
- More than one person touches client outreach
- A manager should sign off before anything leaves
- Clients hand you their own Google mailbox to send from
- You are asked, sometimes formally, who approved a given message
Not yet if
- You want client-branded reporting they log into themselves
- You report on open and click rates, which are not tracked anywhere here
- You want approvals to route automatically by rule; today a person clears the queue, or auto-approval clears it for everyone at once
- A client sends from Outlook — it connects for reading, but cadences do not send through it
- You expect LinkedIn work to run on a server with no one signing in: it runs in the browser of whoever is assigned to that client, or in a cloud browser once the owner of that LinkedIn account has signed it in
Ultra is $299 a month for 5 client spaces on one bill, with 45,000 contacts and 150,000 emails. Professional ($99 a month for one seat) holds 1 client space, so it fits a single client. Those monthly numbers belong to the organization, so any further spaces we set up draw on the same totals rather than adding their own. See pricing.
Run one client through it before you move the rest.
Set up a single client space, put one rep and one manager in it, and watch a week of drafts go through the queue. Then decide.