Start with one operator, grow into seats.
Self-serve plans include 1 seat. When you add people, Enterprise gives unlimited seats, and workspaces up to 25, then arranged with us. One cadence library everyone works from, one place every reply lands, and a review step that records who approved what.
Three problems that only appear above one rep
Six reps, six versions of the same cadence
Everyone edited the template a little. When the numbers come back, you cannot tell whether the message underperformed or the person did, so you cannot fix either.
The week lives in a dozen inboxes
Activity is spread across personal mail, a sequencer, a spreadsheet and a chat thread. RevOps reconstructs what happened by asking people, which is not a reporting process.
You are asked to vouch for what went out
Legal, a customer, or your own board wants to know that nothing improper was sent in the company's name. Today that answer is a promise rather than a record.
Standard where it should be, supervised where it matters
The cadence is the same for everyone so the comparison is fair. The approval is human so the record is real.
- 1
One library everyone starts from
Twelve built-in cadences to fork, or your own. A rep starting on Monday runs the same structure as the one who has been here a year, so a comparison between them means something.
Sequences - 2
Everyone sends from their own address, at a safe pace
Each rep connects their own Google mailbox. Each one carries its own daily quota rather than the team's enthusiasm: fifty a day by default, lower if the mailbox says so. Automatic mailbox warmup is not available yet: a new mailbox starts at the cap, not below it.
Settings → Warm-up & deliverability - 3
The cadence runs itself; the approval does not
Once started, steps and waits advance on schedule without anyone nudging them. Each outgoing message still waits in a queue, and the approval is stored against the exact version that sent.
Campaigns → Message review - 4
Replies arrive tagged, meetings land on the calendar
Every reply is tagged interested, question, objection, not interested or neutral, with a draft answer ready to edit. Booked calls appear on Google or Microsoft calendar with a Meet or Teams link, in the right timezone for both sides.
Inbox · Meetings - 5
Read the numbers that are actually measured
Sends, replies, delivery failures and booked meetings, per cadence and per rep. Reports cover the last seven days in daily buckets and can be saved and rerun.
Analytics
And where the answer already is
These are the questions that are hard to answer once activity is spread across a stack. Here they are properties of the message itself.
Did it send?
Delivery, per message
- Queued, dispatched, sent, failed and blocked
- Failures shown rather than absorbed
- Per-mailbox daily quota, enforced before dispatch
- Nothing counted as sent until it is
Who approved it?
Accountability, per message
- The approver's name and the time, when a person approves
- The exact version of the text that went
- Rejections keep their stated reason
- Unapproved drafts expire instead of sending
Did it work?
Only measured signals
- Replies, tagged by what the person wanted
- Meetings booked onto real calendars
- Delivery failures and blocks
- No open or click rates, because none are tracked
Reports cover the last seven days in daily buckets, UTC, and can be saved and rerun. A selectable date range is not built yet.
What you get once the whole cycle sits in one place
You can finally tell the message from the messenger
When everyone runs the same cadence from the same library, a difference in results is a difference you can act on rather than a story you have to guess at.
Every approval has a name attached to it
When a person approves a message, their name, the time and the exact version are recorded with that message as the work happens. The audit log is separate: it lists sign-ins, workspace switches and account changes, not approvals.
The cycle keeps running while the team is in meetings
Cadences advance on their own schedule, enrichment is processed in the background, replies come in tagged, and booked calls appear on the right calendar with a working link.
The gaps are labelled rather than papered over
The CRM step does not fail quietly; it names what is missing rather than reporting a success nobody had. A number the platform cannot measure is left blank rather than printed as a zero.
Read this before you sign up.
A good fit if
- Several reps run outbound and you need them comparable
- Every rep can connect their own Google mailbox
- Someone will be asked to account for what was sent
- Replies and booked meetings are the metrics you manage on
Not yet if
- Open and click rates are your primary metric; nothing here tracks either
- You want prospect scoring; it is not available yet
- You need an API or webhooks your systems can rely on; a public API is not available yet, and webhooks are in beta
- You want reporting over a custom date range; reports cover the last seven days
- Your reps will not keep a browser open — LinkedIn sending runs in each rep’s extension, and the cloud relay covers one LinkedIn account per workspace
Professional is $99 a month for one seat, 15,000 contacts and 50,000 emails. Above that, Enterprise removes the contact and seat caps and agrees email volume with you. See pricing.
Put one team on it and compare the two halves.
Run a standard cadence with a handful of reps for a month, then look at the record: what sent, who approved it, and what came back. That is the whole argument.