Your domain, your mailboxes, your reputation to keep.
MyLeadTeam has no shared IP pool. You connect your own SMTP accounts, the platform ramps each one gradually, verifies authentication, rotates sending across accounts, and stops a mailbox the moment it starts to look unsafe.
No payment method. No recurring charge. Your own SMTP, your own data.
- Sending model
- Bring your own SMTP
- Credentials
- AES-256-GCM at rest
- Authentication
- SPF, DKIM and DMARC checks
- Safety valve
- Automatic pause on threshold
- Sequences and approval
- Replies and inbox
- Mailbox requirements
- Suppression list
- Bounce handling
- Account rotation
- Sending windows
- How data is handled
A campaign does not fail loudly. It just stops landing.
Nothing on the screen tells you a domain has been throttled. The send counter keeps moving, the reply rate flattens, and by the time anyone investigates, the domain is the problem rather than the copy.
A new domain sending at full volume on day one
A mailbox with no history that suddenly sends dozens of messages a day is the single most common way an outbound programme burns a domain in its first fortnight.
Authentication that was never checked
SPF, DKIM and DMARC are set once during setup and then assumed. A DNS change, a new sending host or a typo silently removes the thing that made your mail trustworthy.
Bounces that keep getting retried
Sending again to an address that already hard-bounced is a direct signal to the receiving provider that the list is not maintained.
Opt-outs living in somebody's inbox
When a removal request is handled by hand, it is handled inconsistently. The second message to someone who asked to be left alone is the one that gets reported.
Four things happen around every send, without anyone remembering to.
The Sender agent never sends in isolation. Warmup governs how much it may send, the suppression list governs who it may reach, and the bounce handler governs when it must stop.
- 01
Connect and encrypt
You add your own SMTP and IMAP credentials for each mailbox. Passwords are encrypted with AES-256-GCM before they touch the database, and the connection is tested from the settings panel before the mailbox is used for anything.
- 02
Ramp, do not sprint
The Warmup agent raises each mailbox's daily allowance step by step instead of opening it at full volume, and re-checks SPF, DKIM and DMARC on the accounts you have connected.
- 03
Rotate and space out
Sending is spread across the accounts attached to that project rather than hammering one mailbox, with sticky reuse so a thread continues from the address that started it.
- 04
Stop before it costs you
Hard and soft bounces are detected and the lead is updated. Accounts are paused automatically when bounce or spam rates cross a safe threshold, and the organisation-wide suppression list is checked before every single send.
Every connected mailbox has a state, not a status light.
Ramping, steady and paused are the three things you actually need to know about a sending account. The panel tells you which stage a mailbox is at and why it stopped, rather than reporting a green tick that means nothing.
- Daily allowance rises gradually instead of opening at full volume
- SPF, DKIM and DMARC are checked on the accounts you connect
- A mailbox that crosses the bounce or spam threshold is paused rather than warned about
- Credentials stay yours: no shared IP pool, no platform sending domain
Delivery is the start of the job, not the end of it.
Replies are matched back to the lead and the sequence, bounces update the lead status, and removal requests land on a permanent suppression list. None of that depends on a person reading an inbox.
- IMAP is polled every five minutes for replies and bounce notices
- Replies are classified so an objection is not treated like a meeting request
- Hard bounces stop further sends to that address
- Opt-outs are organisation-wide and permanent, not per campaign
The difference is that nothing depends on someone noticing.
One sending identity you control
Your domain, your mailboxes, your DNS records. Nothing is sent from an address you do not own, so a neighbour's bad campaign cannot damage your reputation.
A ramp instead of a launch
New mailboxes climb to volume over days. The pace is the point: it is the difference between a mailbox that becomes an asset and one that is unusable in a fortnight.
Authentication that is re-checked
SPF, DKIM and DMARC are verified on connected accounts rather than assumed from setup day.
Bounces that end the conversation
A hard bounce updates the lead and stops the sequence. There is no queue of retries quietly telling a provider that the list is stale.
One suppression list for the whole organisation
A removal request from one campaign protects every other campaign and every other project, permanently.
An automatic stop, not an alert
When bounce or spam rates cross the threshold, the account is paused. Nobody has to be at a desk for that to happen.
What happens when it goes wrong
Deliverability is mostly a set of failure paths. These are the ones that matter and how the platform behaves in each.
What the sending layer actually is
The short version, without marketing adjectives, for the person who has to sign off on connecting a production mailbox.
- Transport
- Your SMTP accounts
- Reply channel
- Your IMAP accounts
- Credential storage
- AES-256-GCM encrypted
- Connection test
- From the settings panel
- Ramp
- Gradual daily allowance
- Auth records
- SPF, DKIM, DMARC
- Rotation
- Across project accounts
- Reply polling
- Every 5 minutes
- Unsubscribe
- RFC 8058 one-click headers
- Suppression
- Organisation-wide, permanent
- Auto-pause
- On bounce or spam threshold
- Shared IP pool
- None
What the deliverability part of your stack stops needing to be.
| Today | In MyLeadTeam |
|---|---|
| A sending tool with its own shared pool, where your reputation depends on other people's campaigns. | Your own mailboxes only. No shared infrastructure between you and the recipient. |
| A separate warmup subscription that runs beside the tool that sends. | The ramp is part of the same pipeline that does the sending, on the same accounts. |
| A DNS checklist someone worked through once during onboarding. | SPF, DKIM and DMARC checked against the accounts you connected. |
| Unsubscribes forwarded to whoever is on support that week. | One-click unsubscribe headers plus a permanent organisation-wide suppression list checked before every send. |
| Finding out about a bounce problem from a reply rate that quietly fell. | The account pauses itself when the bounce or spam rate crosses the threshold. |
Questions people ask about this
Get started
Send from a domain that is still worth sending from.
Connect your own mailboxes, let the ramp do its work, and let the pipeline stop itself before a bad list becomes a bad domain.
No payment method or recurring charge during early access.