Lovable built your app. Who's building your emails?

Featured: Exclusive interview with founders of Dreamlit who are building a way to send beautiful transactional emails without touching code

Hey everyone 👋

Bolt and Lovable let you ship apps without code. But they left one problem unsolved: transactional emails.

Think: sign up, password reset, onboarding emails — the stuff that makes your app actually work. Supabase integration is great (just 1-click) but is extremely limited in its power. Plus, no shade on Supabase, but frankly the design of these emails is... not great (understandably because it’s not their main focus).

The moment your app needs to send a single automatic email to the user, you’re back to being a developer. Reading docs. Configuring APIs. Debugging SMTP.

I’ve experienced this pain myself — wrangling through existing platforms that didn’t let me simply “vibe code” or prompt my way into setting up beautiful transactional emails like I wanted. The “vibe code dream” just died at the email infrastructure layer.

That’s why today, I’m excited to share a featured interview with Ajay Sohmshetty and Andrew Kim, Co-Founders of Dreamlit — and to announce that I’m backing them as an advisor and helping them launch on Product Hunt.

Dreamlit lets you set up all your app’s email automations simply by describing what you want in plain English. Connect your Supabase account and just say “Send a welcome email when users sign up” or “Remind users if they haven’t completed onboarding in 3 days” — and Dreamlit builds the entire thing. Database triggers, workflow logic, beautifully designed emails, production-ready deployment. No code. No configuration. No documentation rabbit holes.

Starting as Notika with engineers as their target customer, the founders had a pivotal moment when they put their product in front of vibe coders. They realized they’d built something that was a total unlock for this emerging builder community — and it warranted a complete rebrand and strategic shift.

I was curious about their journey from the “Stella mafia” to building the easiest way to add welcome emails, broadcasts, and auth emails to vibe-coded apps, so I sent them a few questions that turned into this interview.

---

1. In simple terms, what does Dreamlit do?

Dreamlit lets you setup all of your app’s email automations simply by describing what you want in plain English. Think: Lovable for automated email. It’s one-click to connect your Supabase database, and the easiest way to add welcome emails, broadcasts, auth emails, and general app notifications to your vibe coded app.

2. How did you both meet?

We met nearly a decade ago as early engineer hires at a startup called Stella AI. That startup failed to rise to its AI aspirations, but it was a great place to meet some really smart people. We went our separate ways – Ajay to Google & Harmonic while Andrew went to Netflix. The density of talent was great at Stella, and we like to joke about the “Stella mafia” that spawned out of that failed startup.

3. Give us the backstory - what frustrated you enough about existing email tools that you decided to build Dreamlit from scratch?

Email sucks. It’s always been a necessary evil at every startup we’ve worked at. It’s a source of tech debt and friction between teams. Notifications are fundamentally a product and marketing function, yet too much of it requires engineering support. We asked ourselves, what if engineers never needed to worry about notifications in the first place, and could focus on the fun stuff: building product?

4. Can you share a wild “aha moment” or turning point in Dreamlit’s journey so far?

Not many people know this, but before Dreamlit, we were actually called Notika. Being engineers ourselves, we thought our ideal customer profile were engineers - but when we put the product in front of vibe coders (like KP!) we had an “aha moment”. We realized it was a total unlock for vibe coders, and felt it warranted a rebrand and shift in strategy to help support vibe coders.

5. What’s the most surprising or counterintuitive thing you’ve learned about how vibe coders actually want to handle emails?

As professional software engineers, we were surprised to see the quality of the apps being generated on these vibe coding platforms. But when we went to sign up for an account, the auth fell on its face. Turns out it was because the emails were not properly configured!

6. Walk us through your biggest “this is way harder than we thought” moment while building Dreamlit.

Producing a cinematic promotional video! From finding the right production agency, hiring the right talent, writing the script, aligning on vision, day-of shooting, and post-production, putting together a short 2 minute video to accompany our launch was way harder than we thought. Fun fact: we had a 14 person film crew crammed into my tiny NYC living room for much of the shoot.

7. What’s one piece of hard-earned advice you’d give to founders building developer tools based on your Dreamlit experience?

Talk to customers early. Don’t spend too many cycles in development mode without getting feedback, especially early on - or you risk wasting your own time.

8. Can you share a fun or memorable story from your team while building Dreamlit - maybe a late-night debugging session or customer interaction that stuck with you?

Actually, one of our first meetings with KP comes to mind here. He screenshared and walked us through exactly where he got stuck setting up emails via Resend. In that moment, it became crystal clear that nothing else on the market that truly served vibecoders and their email needs.

9. What’s the most unexpected feedback or use case you’ve gotten from early Dreamlit users that made you rethink something?

Vibe coders told us they were embarrassed to send their users the default Supabase Auth email templates. While not on the original plan, we saw an opportunity to uplevel these emails for our customers - and give us a GTM wedge.

10. Looking at the broader developer tools landscape, what non-obvious insight do you have about where email automation is headed that others might be missing?

In an AI native world, it’s all about context. Traditional API based solutions require you to manually package context. With databases, you get context out of the box - since they’re your source of truth. There’s no need to sync user info or package data. In this new era of AI computing, a database driven approach is superior.

11. Where can people learn more about Dreamlit and its latest PH launch?

Product Hunt launch link: https://www.producthunt.com/products/dreamlit

And we’re building in public on X:

• https://x.com/AjaySohmshetty

• https://x.com/andrewk17

---

That’s a wrap on this featured interview — hope Ajay and Andrew’s journey sparked some ideas for you on how personal frustrations can become powerful product opportunities.

Try It Yourself

Would love for your feedback, support and comments on the launch page as it can help more people discover Dreamlit! Link here: https://www.producthunt.com/products/dreamlit

Thanks for reading!