by Albright Labs
Sending tools demo on the wrong things.
The demo shows sequences building themselves, variables filling in, and a dashboard climbing. All of that is real and none of it is what separates a tool that protects your sending from one that quietly damages it.
The features that matter are boring, and a few of the exciting ones should be turned off.
What It Must Do
Send through your own mailbox provider. Mail that travels the path ordinary business email travels looks like ordinary business email. A tool that sends through its own shared infrastructure attaches your reputation to everyone else using it. Read your provider’s terms before you send bulk email through it, though. Google Workspace’s acceptable use policy prohibits unsolicited mass email, and Postmark requires permission-based lists.
Support a custom tracking domain. Link rewriting is standard, and by default the rewritten links point at a domain shared across the vendor’s entire customer base. That means the reputation attached to your links belongs to strangers. This is one setting and it is among the most consequential in the tools that have it.
Stagger sends by default. Firing a batch in one burst is the clearest available signal that a machine is sending. A tool that makes staggering optional will be used without it, because the option is off by default and nobody finds it.
Stop automated follow-ups on reply, bounce, or unsubscribe. Sending the third email of a sequence to someone who already replied is the error recipients remember. This should be automatic and not a setting.
Attach a working unsubscribe mechanism. Both a visible link and the headers mailbox providers read. Not one or the other. The headers are not optional for larger senders: Google and Yahoo require anyone sending around 5,000 or more messages a day to their users to support one-click unsubscribe as defined in RFC 8058, and Yahoo also wants a visible link in the body.
Report bounce and complaint rates per campaign, daily. These are the two numbers that decide whether you can keep sending. A tool that buries them behind open rate is optimizing its dashboard for the wrong outcome.
What It Should Not Do
Send from a shared pool. Convenient, and it means your delivery depends on the behavior of the vendor’s least careful customer.
Fake the personalization. Tools that generate a “personal” line for each recipient from whatever data they can find produce sentences that could be sent to anyone, which is exactly what the recipient detects. Personalization is the output of knowing the reader, and a tool cannot do the knowing.
Optimize send time per recipient. Sold as a feature, and in practice it clusters sends into narrow windows and undermines the stagger.
Add tracking pixels by default without saying so. Open tracking loads an image, which adds a remote resource to a plain message. It is worth having, and it is worth being a decision rather than a surprise.
Import without validating. A tool that accepts a spreadsheet with malformed addresses and sends to them anyway has handed you a bounce rate.
The Features Nobody Demos
Three things decide day-to-day operation and never appear in a sales conversation.
Whether the unsubscribe link actually works on every path. Worth testing rather than assuming. A footer link that renders but leads nowhere is worse than none, because a recipient who tries to opt out and fails reaches for the spam button instead.
Whether follow-ups carry the same protections as the first email. Follow-up sending is often implemented separately from the initial send, and protections applied to one do not always exist on the other. If three of your four emails are follow-ups, a gap there covers most of the sequence.
What happens when the provider rejects a recipient. A tool that treats a permanent rejection as a retry will keep sending to an address that already refused, which is the fastest way to turn a bad address into a reputation problem.
Ask about all three before buying. The answers reveal whether anyone has operated the tool at volume.
Automation Is Not the Value
The sequencing engine is the easiest part of a sending tool to build and the part every vendor leads with.
The value is in the guardrails: the stagger, the reply detection, the suppression, the bounce handling, the unsubscribe plumbing. Those are what stand between a working sending domain and a burned one, and they are invisible in a demo because they only show up when something goes wrong.
A tool that automates sequences without those is an efficient way to damage a domain.
Owning the Tool Changes What You Notice
We built and run our own sender, Sendly, which was not the plan and has been instructive.
Operating the thing that sends the mail surfaces problems that are invisible from the outside. One example: rejections were classified in a way that produced retries against addresses that had already refused. We fixed it, and a recipient the server rejects as unknown is now recorded as failed rather than retried. That problem would not have been findable in an evaluation, and it affected deliverability. The general lesson holds whether or not you build your own: the important behavior of a sending tool is what it does at the edges, and the only way to know is to test the edges yourself.
A Buying Checklist
Before committing:
- Sends through our own mailbox provider, not a shared pool, and our provider’s terms allow what we plan to send.
- Custom tracking domain supported and configured.
- Stagger on by default, adjustable.
- Follow-ups stop on reply, bounce, and unsubscribe, automatically.
- Unsubscribe link and one-click headers both present, and tested on a real send.
- Follow-ups carry the same headers and suppression as regular campaigns.
- Bounce and complaint rates visible per campaign, daily.
- Permanent rejections are not retried.
Test the fifth and sixth yourself on a live send rather than accepting an answer.
Where Sendly Stands
Held to that list, Sendly is honest about its gaps. It sends only through your own SMTP server or provider, adds an unsubscribe link to every campaign, stops an automated follow-up sequence (Pro and up, sending through Brevo) for anyone who replies, and does not retry rejected recipients. It does not have a custom tracking domain, staggered delivery is an option you turn on rather than the default, and each campaign page shows bounces and unsubscribes but not a complaint rate, which you read from your provider.
A Simple Rule of Thumb
Buy the guardrails. The automation is table stakes and every vendor has it.
Final Thoughts
A sending tool’s job is to make your mail look like ordinary correspondence and to stop you doing the things that make it look otherwise.
Most of that is defaults and suppression rather than features, which is why it does not demo well and why it decides the outcome.
The setup side is in The Email Setup That Decides Whether You Reach the Inbox.