Built by micro-SaaS founders who got tired of writing the same cronjob and db exports.

We build a lot of micro-SaaS products. Most of them are monday.com apps. If you have ever shipped a monday.com app, you know the shape of it: tiny teams, tight margins, and every percentage point of activation matters.

For almost every app we built, I would run into the same wall within a few months of launching. I would notice some pattern in our users. “If a user connects an integration but does not run a task within 24 hours, we should email them.” Or “If a user hits the plan limit twice in a week, we should show them Pro.” Or “If the admin invites teammates but the teammates never log in, we should nudge the admin.”

These emails always moved the needle. Every single time.

But shipping each one meant another few days of backend work. A new event to track. A new database collection to store it in. Sometimes a cronjob. Sometimes a migration. Sometimes a small admin screen just so I could debug why the email was not firing. I was building an email tool one email at a time, on every product I owned, and half my weekends were going into scaffolding the same primitives.

One night I looked at Customer.io. Great product. Priced for companies I was not running. At the volumes I was operating at, it would have eaten the margin on two of my apps combined.

So I looked at alternatives. Loops was closer on price but I needed real segmentation, not just lists. A couple of “developer-friendly” tools had clean APIs but no real segment engine, so I would still have been writing half the logic myself. I kept getting 70% of what I wanted, never the whole thing, and always at a price that did not make sense for a $500 MRR app.

The thought that followed was the dangerous one.

“What if we just built it?”

I could not stop thinking about it. If we got it right, it would save us thousands of dollars a year in email tooling across our products. Could we actually pull it off? How would we start? What happens if the segmentation breaks? It could fire thousands of wrong emails before we noticed.

We started anyway.

Five months later we had the first working version. Not pretty. Plenty of rough edges. We plugged it into one of our apps, found a pile of bugs, fixed them. Plugged it into a second app, found a smaller pile, fixed them. A third. A fourth. The bugs kept getting smaller. The feature requests started coming from our own team, instead of from survival mode.

That is where we are now. Stable. Boring. Running in production across several of our own products. Saving us real money every month.

We figured we are probably not the only ones in this spot. Bootstrapped founders. Micro-SaaS builders. Solo devs. People who need real behavioral email but do not want to stand up another engineering surface just to send a welcome sequence, and definitely do not want to pay $100 a month to get started.

So we are opening it up. The pricing is deliberately pocket-friendly because that is the whole point. If you run lean, we should help you run leaner.

That is the story.

If you want to try it, the free tier is real and has no credit card requirement. If you want to chat, email me directly at kevin@segmailer.com.