Launch HN: Loops (YC W22) – Email for SaaS Companies
151 points| chrisfrantz | 2 years ago | reply
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!
[+] [-] santiagobasulto|2 years ago|reply
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!
[+] [-] chrisfrantz|2 years ago|reply
[+] [-] daniel_sushil|2 years ago|reply
[+] [-] winrid|2 years ago|reply
[+] [-] mrweasel|2 years ago|reply
[+] [-] siva7|2 years ago|reply
[+] [-] adamkaz|2 years ago|reply
[+] [-] MattyMc|2 years ago|reply
Also: More than 5000 contacts, “CONTACT US”.
[+] [-] shash7|2 years ago|reply
[+] [-] adamkaz|2 years ago|reply
[+] [-] mfkp|2 years ago|reply
[+] [-] alx-ppv|2 years ago|reply
That's why Sendy is a good option for me.
[+] [-] adaml_623|2 years ago|reply
[+] [-] chrisfrantz|2 years ago|reply
thanks for giving us a try :)
[+] [-] candiddevmike|2 years ago|reply
FWIW, your service seems priced in a way that encourages spam (send unlimited emails to an address).
[+] [-] adamkaz|2 years ago|reply
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.
[+] [-] tomahony|2 years ago|reply
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)
[+] [-] chrisfrantz|2 years ago|reply
[+] [-] pembrook|2 years ago|reply
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?
[+] [-] chrisfrantz|2 years ago|reply
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.
[+] [-] deofoo|2 years ago|reply
[+] [-] rusl1|2 years ago|reply
[+] [-] chrisfrantz|2 years ago|reply
Click "view pricing tiers" for all tiers up to 100K :)
[+] [-] xmattx|2 years ago|reply
Runs kinda counter to your business-case I suppose, but might help someone (me) out :)
[+] [-] adamkaz|2 years ago|reply
[+] [-] chrisfrantz|2 years ago|reply
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.
[+] [-] ponyous|2 years ago|reply
[+] [-] acomms|2 years ago|reply
[+] [-] adamkaz|2 years ago|reply
[+] [-] petecooper|2 years ago|reply
I understand the reasoning for it being there, but perhaps kick it further down the page so the service / offering is the focus.
[+] [-] chrisfrantz|2 years ago|reply
Will certainly place it in the footer and switch off the upvote portion in the future.
[+] [-] j45|2 years ago|reply
[+] [-] ilrwbwrkhv|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]
[+] [-] o-o-|2 years ago|reply
* 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?!
[+] [-] adamkaz|2 years ago|reply
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.
[+] [-] hu3|2 years ago|reply
I would expect API to parse JSON with variables to replace in the templates.
[+] [-] mtmail|2 years ago|reply
[+] [-] robflaherty|2 years ago|reply
[+] [-] chrisfrantz|2 years ago|reply
[+] [-] a-l-e-c|2 years ago|reply
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.
[+] [-] chrisfrantz|2 years ago|reply
[+] [-] kylegalbraith|2 years ago|reply
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".
[0] https://depot.dev/
[+] [-] chrisfrantz|2 years ago|reply
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...
[+] [-] Multiplayer|2 years ago|reply
[+] [-] chrisfrantz|2 years ago|reply
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.
[+] [-] ignoramous|2 years ago|reply
[0] https://www.ycombinator.com/companies/mailmodo
[+] [-] nibab|2 years ago|reply