Is this a newsletter tool?

Not really. It sends one mailing to a set of records you already own and work with. There is no subscriber management, no signup widget and no list hygiene product. The record is the subscriber, and the filter is the list.

Do I need my own mail server?

You need SMTP credentials, which almost every domain already has. Set them once on the account, or per user where people should send under their own name.

What about consent? This is bulk email, after all.

It is, and it is treated differently from the mail a flow sends to somebody who just asked you something. Three things the platform does rather than leaves to you: an unsubscribe is recorded against the email address for the whole account and honoured by every later campaign, the unsubscribe page carries your brand and works for years because the link never expires, and open tracking is off until you switch it on, because a counting pixel is a processing operation that not every consent covers. What you are allowed to send, and to whom, depends on your recipients and your jurisdiction rather than on us. We are describing what the tool does, not advising you on that.

Does an unsubscribe apply to everything?

Yes, and it is stronger than you might expect: it is recorded against the email address for the whole account, not against one record and not against one campaign. The same person sitting on two records is covered by one unsubscribe, and every later campaign skips them without anybody doing anything.

Campaigns

Lead nurture campaigns from the records you already have

A campaign goes to a set of records, and the set is the filter you already use in the list. No export, no second address book, no second tool that charges per contact for people you already own.

The audience is a filter on your records, not an uploaded list
Sent from your own mailbox over your own SMTP
One delivery row per recipient, frozen when the campaign starts
An unsubscribe is honoured everywhere, not per campaign

Create your account

app.leadflip.net

Leadflip

Overview

Funnel

Forms

CRM

Records

Pipelines

Campaigns

Distribution

Routing

Partners

Billing

Platform

Entities & fields

Team & roles

Campaigns4 campaignsUnsubscribesNew campaign

Subject	State	Recipients	Opened	Clicked	Unsubscribed	When
September: what a grid connection actually costs	Sent	1,284	—	163	7	24 Sep
Three questions before you sign anything	Sent	1,301	—	208	11	10 Sep
August: the rule change, in plain words	Sent	1,188	—	141	5	27 Aug
October draft	Draft	—	—	—	—	—

The tools were never the problem

Process mail cost extra, so a second and cheaper mail tool got bought. From then on the audience was an export that started ageing the moment it was uploaded, and an unsubscribe existed in two places that never told each other about it.

We ran a lead generation business on six of them. This is the part that cost us the most and showed up on no invoice.

You pay per seam: Every tool in the chain has its own subscription, and the one feature you actually needed is usually one price tier up.
A field is not one change: Add it in one place and it has to be added in the others. Miss one and nothing fails loudly: it fails the next time somebody filters on it.
Someone else's release is your outage: An API changes, a mapping stops matching, a webhook starts returning something new. You hear about it from the person who was waiting.

Audience

Everyone you have not lost, minus everyone who said stop

While somebody works a record, the same contact gets something to read in parallel that does not sell. The audience for it is not a list anybody maintains, it is a condition: everyone of this entity, except the lost ones, except the ones who unsubscribed. It is resolved when the mail goes out rather than when you built it, so it never knows a stale export.

The same condition language. As the list, the board and the rules of a distribution.
Counted before it sends. How many records match, right now.
Nobody twice. A record that already got this campaign does not get it again.
Unsubscribed is unsubscribed. Across every campaign, on the record, not in a list.

Who gets it

the same conditions as in the record list

EntityRooftop DE

Stageis not Lost

Addedbefore 1 Sep 2026

Records in the audience: 1,412
without an email address: −38
unsubscribed: −71
same address more than once: −19

will get the email1,284

Resolved when it goes out, not when you built it.

Sender

your mailbox, your decision on counting

Fromhello@rooftop.dethe account’s SMTP

Reply toempty, so replies go to the sender

When25 Sep, 09:00

Track clicksAddresses in the text then run through a counting redirect. The unsubscribe link does not.

Track opensThrough a tracking pixel. Only switch it on if your consent covers it, which is why it is off by default.

Sending

From your mailbox, not from ours

Mail leaves over the SMTP you configure, per account or per user. That is the reason people end up with a second, cheaper mail tool in the first place, because the CRM charged for the mail it should have sent.

Your SMTP and your domain. So replies come back to you and your reputation is yours.
Templates with your fields. The same placeholders the rest of the platform uses.
A footer per account. Set once, on every campaign and every process mail.
Replies land on the record. Over IMAP, matched by a reference in the subject.

Measurement

What it did, per recipient

Every recipient gets a row, frozen the moment the campaign starts: the masked address, whether it went out, was skipped or failed, and why. That row is the proof of who got what, and it outlives the campaign.

Open tracking is off until you turn it on. A counting pixel is a processing operation, and not every consent covers it.
Click tracking is on. That a link was clicked and when, not a profile of which ones.
An unsubscribe page that is yours. It carries the account's name and logo, not a platform shell.
Three reasons to skip, all named. No address, unsubscribed, or the same person twice in one audience.

Report

one row per recipient, frozen at the start

Recipients

1,284

Delivered

1,281

Skipped

128

Failed

m.k***@example.dedelivered24 Sep, 09:01
s.d***@example.dedelivered24 Sep, 09:01
c.n***@example.deskippedunsubscribed
a.r***@example.defailedmailbox does not exist

How a campaign is built, sent and read

Who receives it, what happens on send, what became of it afterwards, and who gets no more bulk email.

5 articles, written against the product and shown inside it too.

CampaignsA campaign goes out once, to many. That is what separates it from an automation, which writes to one person in response to an event. You put together the audience, write the text and send it.AudienceYou put the audience together with the same conditions you use in the record list. From it comes the recipient list, after three deductions the application sets out openly.SendingBefore sending you decide who the mail comes from and when it goes out. After that the application works through the recipient list in batches.ReportAfter sending comes the report: how many recipients, how many delivered, skipped or failed, and, if you switched it on, how many opened and clicked.UnsubscribesAn unsubscribe applies to your whole account and permanently. It stops bulk email, not the post from ongoing case work.

Pricing

What Campaigns costs

You pay for what you send in a month, not for how many contacts you keep. A list that just sits there costs us nothing, and charging for it would punish exactly the collecting this is for. Mail goes out from your own address, over your own mail account, so it arrives as you and not as us.

MonthlyYearlysave 17%

Campaigns, 2,000

$15.83/mo

billed yearly · $19.00/mo billed monthly

Save 17% vs monthly

Create your account

2,000 deliveries a month
Audience from the same filter
Your own sender

Above that: $0.006 a delivery

Questions people ask

If the answer you need is not here, the help center has the long version.

Open the help center

Is this a newsletter tool?: Not really. It sends one mailing to a set of records you already own and work with. There is no subscriber management, no signup widget and no list hygiene product. The record is the subscriber, and the filter is the list.
Do I need my own mail server?: You need SMTP credentials, which almost every domain already has. Set them once on the account, or per user where people should send under their own name.
What about consent? This is bulk email, after all.: It is, and it is treated differently from the mail a flow sends to somebody who just asked you something. Three things the platform does rather than leaves to you: an unsubscribe is recorded against the email address for the whole account and honoured by every later campaign, the unsubscribe page carries your brand and works for years because the link never expires, and open tracking is off until you switch it on, because a counting pixel is a processing operation that not every consent covers. What you are allowed to send, and to whom, depends on your recipients and your jurisdiction rather than on us. We are describing what the tool does, not advising you on that.
Does an unsubscribe apply to everything?: Yes, and it is stronger than you might expect: it is recorded against the email address for the whole account, not against one record and not against one campaign. The same person sitting on two records is covered by one unsubscribe, and every later campaign skips them without anybody doing anything.

Bring the month you would rather not talk about

Set up your own entity, your own fields and one routing rule, and see what it does with a record you put through it.

Create your account