Email outreach platform with a cap you set and it cannot pass

Most platforms give you a throttle. A throttle is a number somebody can raise on a Thursday afternoon when the quarter is behind, which is precisely when it gets raised. This one is a ceiling, and the agent has no way past it.

Run it on a prospect

A throttle and a ceiling are not the same control

They look identical in a settings screen: a box with a number in it. They behave differently on the one day it matters, which is the day somebody decides the number is the reason the pipeline is short.

The cap here is set per mailbox, enforced by the queue, and there is nothing inside the agent that can exceed it. No burst mode, no catch up after an outage, no quota it is working towards.

Throttle compared with a ceiling
On the day it matters	A throttle	A ceiling
Behind on the number	Raised	Unchanged
After an outage	Catches up	Starts again tomorrow
Set by	Whoever has access	You, and it is a policy on Enterprise
The agent can exceed it	Sometimes, to hit a target	No
What the record shows	The last value	The value at the time of each send

What happens between the draft and the send

Five things, in this order, on every message. Four of them can stop it, and three of those four stop it before it has cost you anything.

Suppression, at draft time

The address is checked against your suppression list before the draft is written, not after. A suppressed contact never enters a queue, never consumes a slot in your cap, and never appears in a report as a message you nearly sent.
The claim check

Every factual sentence in the draft is cited or marked unverified. An unresolved unverified claim holds the message. There is no setting that releases it.
The rule checks

Unsubscribe line, postal address block, subject line honesty. Each one fails the draft on its own, whatever the rest of the message scores.
The cap

A clean draft joins the queue for that mailbox and goes out inside your ceiling. When the ceiling is reached, the queue waits for tomorrow rather than borrowing from it.
The record

The message, the ledger, the verdict and the source line behind each cited claim are stored together, as they stood at that moment.

The queue, this morning

Sent today 6 of 40
Queued, cleared every check 4 drafts
Held, claim without a source 1 draft
Never drafted, suppressed 3 contacts
Stopped on reply 2 threads

A stored sample. In the product these are your numbers, per mailbox, per day.

How to choose the number

The usual approach is to decide how many emails you want to send. The better one is to decide what complaint rate you are willing to run at, and let that set the volume.

Start lower than feels useful

A new mailbox on a new domain sending forty a day on day one is the pattern filters are built to catch. Start well under your plan ceiling and let the record earn the increase.

Watch the rate, not the volume

Google Postmaster Tools reports your spam rate. Google tells senders to keep it under 0.30% and to aim below 0.10%. That number, not your send count, is the one that decides what happens to your domain.

Raise it slowly, and only upward from evidence

Several weeks under the threshold is a reason to raise the ceiling. A short quarter is not. The whole point of a ceiling rather than a throttle is that the second reason cannot move it.

Caps by plan are on AI SDR software pricing: up to 40 a day per mailbox on Solo, 80 on Team, 150 on Scale, and set per domain on Enterprise. Those are ceilings you may set, not targets anyone is aiming at.

What this platform does not include

Named here so it is not discovered in week two.

No mailbox warmup

No warmup network and no reciprocal pool. Those work by generating fake engagement, and volume here is managed with the cap instead.

No inbox placement testing

The checks read the draft. They cannot tell you which folder a message landed in. That needs a delivery testing product.

No contact data

No database, no email finder. You bring the list and the sources.

No shared sending pool

Mail goes from your own connected mailbox on your own domain. Your reputation is yours, which is the point of capping it.

The whole product

What it is, why it holds a draft, and the demo it all runs in.

AI SDR

What it costs

Flat monthly, never per seat, and nothing is charged on this site.

AI SDR software pricing

The guide on this

Sequence length, spacing, what each step is allowed to say, and why the bump that only says "thoughts?" is the one that gets complaints.

cold email sequences

The rest of the product, by job

The same product, entered from the job you came here to do. Each page states its own limits rather than repeating the pitch.

AI email writer
The drafting side on its own page: what it writes, and what it refuses to assert without a source.
Spam score checker
What the score is made of, line by line, and the two things it deliberately does not test.
CRM automation
Activity logging, deal notes and next steps, written from the thread instead of from memory.
Prospecting tools
Where a research tool ends and a list vendor begins, and which one this is.
Cold email software
The four things a cold email has to get right before volume is even worth discussing.
Sales automation tools
What to automate, what to review, and what a person still has to decide.

Set the ceiling before you need it.

Getting started connects a mailbox and asks you for one number. Everything on this page follows from that number, and nothing in the product can move it but you.