Platform · Sales engagement
Your cadence cannot swarm an account.
Nine channels on one sequence model, two editors over it, and a send path that will not put a second sequence email into the same account on the same day. The limits are enforced where the send happens, not in a setting a rep can raise at the end of a quarter.
Included at $499 per seat per month
How fast a new mailbox is allowed to send
emails per day
hard ceiling 50
5
10
20
30
40
day 0
day 7
day 14
day 21
day 28
The cap holds flat for seven days, then steps. No milestone may be more than twice the one before it, so nobody can hand-edit a mailbox onto a cliff. The ramp tops out below the ceiling on purpose: the ceiling exists to catch a configuration, not to be reached.
How it runs
One sales engagement model. Two editors. Nine channels.
Build a cadence as a linear list or as a node canvas, whichever suits the shape you are after. They are not two products. The canvas compiles to the same executable steps the list writes, so a cadence drawn on one opens correctly in the other and neither is the one that merely draws.
One step, nine things it can be
sequence_steps.channel
Pick one. The rest of the cadence does not change.
- Emailsend window
- Callsend window
- AI callno window
- SMSsend window
- LinkedInno window
- Socialno window
- Manualno window
- Waitno window
- Taskno window
Three of the nine carry an automated send window and the engine holds a due step until the contact reaches that hour where they live. The other six carry no time of day constraint, because a LinkedIn touch or a call task belongs to a person and a wait step is nothing but time.
Five cadences that ship
A Cloud Scheduler job wakes the engine every five minutes. It claims due enrollments with FOR UPDATE SKIP LOCKED and leases each one ten minutes forward, so two ticks that overlap take disjoint batches and a slow run cannot send the same step twice. Every touch below is a real day and channel table you can open and edit, not a shape suggested in a doc.
- Enterprise cold-to-meeting18 touches, 45 days8 email, 4 LinkedIn, 3 SMS, 3 phone
- Account-based multi-stakeholder18 touches, 50 days9 email, 4 LinkedIn, 3 phone, 2 SMS
- SMB owner fast-track17 touches, 30 days7 email, 4 SMS, 3 LinkedIn, 3 phone
- Re-engagement12 touches, 30 days6 email, 2 LinkedIn, 2 SMS, 2 phone
- Inbound lead fast-track8 touches, 14 days4 email, 2 phone, 1 SMS, 1 LinkedIn
Why this is different
The brakes sit below the rep, not in a settings page.
Restraint that lives in a configuration screen is not restraint. It is a default, and a default loses to a quota. The two guards that decide whether your outbound reads as considerate or as a swarm are enforced in the send path itself, which is why they still hold on the last day of a bad quarter.
Send windows, in the contact's local day
Two hours out of twenty four for email. The engine resolves their timezone first, then holds a due step until that hour arrives where they are.
Four colleagues at one account
The reservation is taken at dispatch under a lock, so the second, third and fourth email defer a day each. Nobody chose to be patient and nobody can choose not to be.
One per account per day, at dispatch
A database function holds a lock on the workspace, the account and the day, and refuses a second sequence email into that account inside it. Colleagues get staggered across days instead of blitzed in one morning. It runs at the send, not in the planner, so two overlapping ticks cannot both win.
Their clock, not yours
Send windows resolve against the contact's own timezone before any hour is compared, so an 08:00 email means 08:00 where they are. A cadence built in one city does not land at 3am in another, and nobody has to remember to set that per campaign.
One reply stops every channel
A reply on any channel pauses the whole enrollment, not just the channel it arrived on. The follow-up SMS does not go out after the prospect already answered the email, which is the failure that makes a company look like a machine that is not listening.
The questions buyers actually ask.
- MOST ASKED
One of nine channels: email, call, AI call, SMS, LinkedIn, social, manual, wait or task. That list is not aspirational. It is the channel set the builder exposes and the database CHECK constraint on the step row allows, so a tenth cannot be typed into a sequence without a migration.
We will not quote you a meeting rate. We will show you the brakes.
Bring the sequence you run today. We will rebuild it on the canvas in front of you, run the launch gate against it, and show you exactly which of the blockers your current setup would trip and why. If the answer is that you do not need us, you will know inside the call rather than inside a trial.