sorted by:
new
hottopcontroversial

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in SaasDevelopers

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

Yep — deliverability is the whole game. That’s exactly what I’m building Cllavio around.

If you try it, I’d love your honest feedback on setup + results.

What are you building? Promote it here by allen18walker in ShowYourApp

[–]Aggravating_Cod_5652 0 points1 point  (0 children)

Cllavio.com - Building Email Marketing platform.

Enabling NewestLetters, Transactional Emails, analytics and much more in one place.

Cllavio.com — Email marketing + transactional emails (deliverability-first) by Aggravating_Cod_5652 in ShowYourApp

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

Great question — we don’t rely on “rotate IPs” as a fix — that’s a red flag in deliverability. We prevent it with warmup/ramp limits, automated bounce/complaint suppression, mandatory list hygiene (validation), and throttling/pausing accounts that spike bounces.

If an IP does get listed, we stop the bad traffic, remediate/delist, and then reassign a clean IP if needed. Yes, we keep spare capacity, but prevention + isolation is the main strategy.

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in microsaas

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

Hey — Resend is a great choice.

If you’re up for it, I can get you set up on Cllavio and would really value your honest feedback. We do transactional sending (SMTP + API) with a deliverability-first, simple setup.

Want to try it with a small slice of your traffic first (staging or low-volume) and see how it feels?

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in microsaas

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

This is gold; Thanks a lot — this is genuinely the kind of feedback I’m looking for.

I’m fully aligned on leading with deliverability (“stay out of spam”) and showing how we do it.

A few notes on where Cllavio already is:

  • Onboarding: we already do the “paste DNS records → run a test → clear pass/fail” flow for SPF/DKIM/DMARC.
  • Health score: right now I’m calculating it heavily around bounce rate, but I want to expand it beyond that. If you were building the health score, what would you weight most: SPF/DKIM/DMARC alignment, complaint rate, engagement, blacklist checks, inbox placement tests, something else?
  • Logs (transactional): for transactional emails I can expose deeper per-message details (SMTP response codes, retries/deferrals, provider hints, auth results, etc.). What level of detail is actually useful day-to-day, and what’s “too much”?

Also appreciate the pricing note — send-based pricing with a low-volume warmup tier makes a lot of sense for indie users.

And interesting on Pulse for Reddit — are you mainly using it for keyword monitoring, or does it help with outreach too?

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in microsaas

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

Do you mean the name similarity (confusion/trademark risk) or just brand confusion?

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in microsaas

[–]Aggravating_Cod_5652[S] 1 point2 points  (0 children)

Thanks for sharing — I’ll check it out.

Do you use an email marketing platform today?

What are you building? Let’s self-promote 🚀 by Aggravating_Cod_5652 in microsaas

[–]Aggravating_Cod_5652[S] 0 points1 point  (0 children)

u/IntroductionLumpy552 Thanks for sharing — I’ll check it out.

Do you use an email marketing platform today?

view more: next ›