Email is important but painful to manage. If you've ever dealt with the frustration of coding emails by hand, testing them across multiple clients, or integrating them into various SaaS tools, you might find our approach interesting.
We make it simple to design and send email to your users either manually in the app, via API or triggered via an integration. We offer unlimited team seats, so your product team can help align copy, your marketing team can send newsletters, your revenue team can work on dunning and your engineers can have a solid API to help orchestrate the sends.
Most of our competitors use email editors that are licensed from a third party. Our editor is built from the ground up on the Lexical text editor from Meta, extended beyond just text nodes. It supports mobile editing and dark mode, and it autosaves your changes.
Our REST API is straightforward, and we have integrations with tools like Segment and Census. Documentation is available at https://loops.so/docs. On our homepage, right under the fold, we list endpoints and sample payloads.
One issue we've worked hard to address is email compatibility across devices and platforms. It's a problem full of edge cases that we've mitigated by extending MJML, a markup language designed for responsive email, to be even more compliant across different platforms. We don't think you should have to code and test your emails. Email copy shouldn't live in your codebase.
If you're concerned about spam, we are too. We educate our users on CAN-SPAM rules and automatically add compliant footers to emails. We actively monitor to ensure our platform isn't used for spam, and we do not allow cold sales emails.
Our pricing is upfront and available on our website. You can try the platform for free without a credit card. We launched publicly a week ago. We're really interested in any technical feedback you have, as we aim to make this tool as developer-friendly as possible.
Looking forward to hearing your thoughts!
Have some friends also working in a somewhat adjacent space (Audienceful) so will be watching you guys closely.
But in general it seems email is pretty crowded these days and a lot of the sub-niches are also pretty crowded (eg. Klayvio in ecomm, Customer.io in Saas, Substack/ghost in newsletters, Convertkit for wordpress bloggers, etc).
And for the most part all these apps are just sending on the big API-based senders under the hood (Eg. Amazon SES or Sendgrid). Even the newcomer API-based senders like Resend are just a wrapper around Amazon SES. Which makes any claims around differentiated deliverability on any email platform dubious at best.
Is the plan to build your own sending infra long term?
You can do a lot to improved deliverability once you approach it at a platform level. We have access to various datapoints at scale that we can use to help individual users improve their deliverability vs working directly with the sending infra. Beyond that, we offer a platform that helps reduce pain and friction that might exist with more barebones, infrastructure focused services.
I understand the reasoning for it being there, but perhaps kick it further down the page so the service / offering is the focus.
Will certainly place it in the footer and switch off the upvote portion in the future.
Beyond that, our goal is to offer the single platform for email for your SaaS. So we’re focused on bringing together product, marketing and engineering in a single, hopefully cohesive and delightful, experience.
(I'm actually using Mailgun FWIW)
Also: More than 5000 contacts, “CONTACT US”.
Sorry that wasn’t more clear!
Runs kinda counter to your business-case I suppose, but might help someone (me) out :)
I think parts of the editor makes sense, including the MJML. We spent an entire weekend extending MJML for Superhuman and it would be cool to release that work some way.
* A user-friendly WYSIWYG template editor (web fonts = nice to have but not crucial). * An API that lets me set the to-address and the e-mail content in markdown.
How can this pose an edge case?!
Ideally, you'd be able to paste any markdown into our editor and have it render properly, but still something we need to work on.
A markdown to HTML (email) converter would be neat though.
I will say I find the pricing quite concerning. Free until 1000, 50 / 5000, but then I have to contact you? Am I understanding correctly, 5000 subscribed users doesn’t seem like that much.
For what it’s worth I went to customer.io to compare pricing and found there’s so confusing I was lazy to figure it out…so I do appreciate the simplicity
It needs to not be hidden behind a button, that’s on the list.
I'll be keeping a closed eye to you guys, it's pretty much what I wanted when I started my project.
In pricing, we try to simplify by ditching the tables and anchoring around one metric.
For engineers, our documentation is decent and updated regularly. We try to have a performant API, support the integrations you’re most likely to use and include a versioning system with our transactional email.
For marketing, we built our editor around a text-based interface and make it highly customizable. We also take the pain out of having to test across multiple platforms.
For product teams, we offer templates that cater to specific touchpoints in the SaaS lifecycle.
Across all of that we offer unlimited team seats so you can actually have your entire team onboard and technical support for when things don’t work as expected or you have questions.
We create slack connect channels with any team that needs one (we have almost 1,000) and try to provide fast, technical support.
I like it because it's easy. I'm not sure what the alternatives are, but I have the sense they'd all be more complex and more annoying to use (even if they might be cheaper).
Contact-based pricing is bad. You’re trying to create an email platform for SaaS, from the features perspective (yey!) but you’re charging just as mailchimp and everybody else does (nah!).
Instead, as a founder, I’d rather prefer “active user”. If someone tries my product, but they never return, I don’t want to be charged for. So, in any given month, count how many people I have emailed (during that period), and that counts as pricing.
Just my 2c. Good luck!
It seems the innovation here is making the management, editing and publishing of emails much more streamlined through your interface. That's great as it's definitely a frustration of creating emails.
But in the pricing you are focusing on contacts (and therefore "number of emails sent"). First of all, it's very difficult to guess what "contacts" are when considering transactional emails. What if a new user signs up but never uses the app again? Is that a new contact? If I send one marketing email it could be to 200k contacts, but I may only have 1000 transactional emails/contacts per month.
Instead of focusing the pricing around contacts and "emails sent" why not allow customers to "bring their own email platform". This would absolve you of having to worry about email pricing. A custom can connect SendGrid, MailGun or whatever they want. You can then focus your product on the publishing experience (and probably charge a lot more)
Click "view pricing tiers" for all tiers up to 100K :)
Shoot me an email (chris@loops.so) and happy to walk you through any questions you may have.
But this just means there's a market. It doesn't have to be special. Yay capitalism :)
Even without the borderline content, if it seems promotional, it may end up in promotions regardless.
I like them because they integrate quite nicely with their other product, React Email [1], where our devs can just write emails in React and it'll render to email-compliant HTML and CSS. I suppose you guys have a GUI as well but I believe they're looking to add that too.
You can upload MJML if you’d really like to, along with designing in Figma via an integration, but really your best bet is our editor.
If we can save a few engineering hours just by having the product person that needs to update the emails with new copy actually update the copy instead of pinging engineering, we think we’ve improved things.
If a competitor ends up building a GUI, glad to see they agree too :)
Just FYI since I happened to be looking into this recently as well :)
[0] https://www.npmjs.com/package/@react-email/render
[1] https://github.com/resendlabs/resend-node/blob/90a7225c21db9...
I came across your comments on Stripe on Hacker News and am reaching out in hopes you can assist with an urgent issue.
Account ID: acct_1N6UyxJ097OmyUsG
site：lovilds.com
Product: Women's Beauty and Skincare Products
My Stripe account has been closed, and $90,000 has been forcibly refunded to customers. I've been in touch with Stripe support, and they've told me my account is under review. It's been nearly two weeks.
Could you please help me understand:
1. Is there a chance for the $90,000 to be returned to my account? 2. Is there any possibility of my account being reinstated?
Your immediate attention to this matter would be greatly appreciated.
thanks for giving us a try :)
FWIW, your service seems priced in a way that encourages spam (send unlimited emails to an address).
We monitor our delivery platform wide and proactively contact customers if there are issues with their account.
As far as spam, yes, we allow you to contact within your own audience as much as you like but we do monitor this for abuse.
Had cases where the exact same campaign or template had to be created multiple times due to the client wanting a slightly different intro/closing or even entirely different products and services promoted based on user/account preferences.
Sure, it could be managed with multiple campaigns/templates/lists but these duplications could easily be avoided by using slightly more advanced "segmentation logic".
This is usually the case where tracking/stats aren't that important but rather making sure the user receives relevant content.
I think there are some logic things to get right at the API level, like should I use events or contact properties to trigger loops? We're working on some of that and wish the guidance was a bit better/clearer. At the moment, any properties you send with an event get added to the contact, so it seems like contact properties are the way to go.
My last request would be to support array properties on contacts, as a given contact could be in multiple "things".
We'll follow up on the API feedback separately, but you're welcome to trigger with either. We break down the differences here: https://loops.so/docs/loop-builder/loop-triggers#trigger-fre...
This is a neat concept - reminds me in some ways of mailgun when they were able to take a spin on email hosting to allow multiple domains relatively cheap but measure the number of emails.
I'll be signing up at least two things I can try it out with. The pricing information seems limited at present - until you realize it says 5000 poeple. Having one more paid category listed would be ideal.
I was looking for an API reference to see what I could do with your API, but didn't find one. It seems that information about API calls is scattered among more "how-to" oriented documentation. That's just fine, but it would also be nice to have some documentation oriented around endpoints and details of the API.
How has your experience been using Lexical? Would love to get a sense of where you've run into limitations/etc as we're exploring it (albeit, for a very different use case).
And to nerd out a bit - how was working with Lexical? We chose Slate.js for our editor in Kitemaker.co but it's not as actively maintained as it once was.
Pricing, performance and UX are the primary drivers for switching that we have seen so far.
We were on Slate previously and actually rewrote our editor to support our switch to Lexical. It’s very early but it’s a cool platform. Wish they had a community outside Discord but that’s more personal preference.
Just a few questions, how does this compare to Substack, Beehiiv, Mailchimp, etc, looking to create an automated newsletter, will Loops work for this usecase?
There are also quite a few strictly newsletters using us as well which we're happy to support! We own workspaces.xyz and publish that as well via Loops.
Any plans to support multiple channels? (SMS, push, etc) And are you in the long run looking to compete with Braze, Airship, etc?
Happy to share how we use it.
You can upload MJML if you’d really like to, along with designing in Figma via an integration, but really your best bet is our editor.
We've extended MJML to support additional platforms and it's lightning fast to just send an email.
If we can save a few engineering hours just by having the product person who needs to update the emails with new copy actually update the copy instead of pinging engineering, we think we’ve improved things.
We also support product and marketing email, along with transactional emails.
Happy to expand on it if you have additional q's
That's why Sendy is a good option for me.
