Send · Channels
Verify a sending domain. Connect LinkedIn when you are ready.
Access is by waitlist. Once your seat opens, attach a sending subdomain, publish its DNS records, verify it and add a sender. LinkedIn uses a separate connected account with its own ramp and daily limits.
62 days old · today’s ceiling comes from the age band
31 days old · today’s ceiling comes from the age band
9 days old · today’s ceiling comes from the age band
2 days old · today’s ceiling comes from the age band
What is actually going on
Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.
Email is domains and senders, not mailboxes
You attach a sending subdomain, never the root. Publish the records the vendor returns, and verify it. A sender is a from-address on that domain, each its own connection row, so rotation, pacing and the age ramp all apply per address.
The consequence of an automation breach lands on your account
That is why the LinkedIn ramp is enforced by default rather than suggested. It is a per-connection switch you can turn off, and an attestation you can set if the account is genuinely old, but the default is the safe one.
The compliance footer is appended by the transport, not the caller
A caller able to omit an unsubscribe link eventually will. Both email transports refuse a send without an unsubscribe URL and a postal address.
Instagram left the motion entirely
Meta requires the correspondent to start the conversation, so there was no compliant cold path to lose. SMS is the named next channel. Phone and paid ads are closed.
Step by step
How email & linkedin runs
- 1
Attach
A sending subdomain, with receiving enabled so it can take replies.
- 2
Publish
The DNS records the vendor returns. Verification is a live check, not a stored string.
- 3
Add senders
One from-address per row, each with its own pacing and its own ramp.
- 4
Connect LinkedIn
A credential form inside the product. LinkedIn offers no OAuth, so the password is forwarded within one request and never stored.
The numbers
Facts, not adjectives
Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.
- LinkedIn ramp
- 5/day week one, 10 to day 30, 20 to day 60, then your own limit
- Domain ramp
- 10 → 25 → 50 → your ceiling
- Weekly limit
- Five ramped days
- Reply-to
- reply@your-subdomain, on every send
- Metered as
- One action credit per send
Email & LinkedIn, honestly
Can I connect a Gmail or Outlook mailbox?
No, and that is deliberate. Email runs entirely on a sending-domain stack, which is what lets cold volume spend a dedicated domain's reputation rather than your company mailbox's.
Can I override the LinkedIn ramp?
Yes, per connection. It is a switch and an attestation date, not a support ticket. The default is on because the downside lands on your account.
Send
Out through your own accounts, at a safe pace
Keep reading
All featuresEmail & LinkedIn is one part of it. The rest runs too.
Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.