chrisfrantz

Series A starts the treadmill. Now you have compounding growth requirements and you can’t afford to retool product when things slow down.

So you shut down onboarding because conversion rates are always better when users are being handheld and that doesn’t break product.

That logic stacks as you scale and the pressure from VC’s mount.

FWIW, I run a competing company in the space and we skipped the Series A specifically because we have gone down this path before. That doesn’t mean we have a better product by default but we don’t have those same pressures and we can just retool things when needed. Almost 5 years in and we don’t even offer annual plans unless someone really twists our arm, our time is focused on product vs revenue growth.

That is a hard line to walk if you’re on the VC climb.

FWIW, didn't have any luck with the generator at the bottom, could be user error.

Over the next six months we rebuilt on plain AWS: EKS for the Next.js app, Aurora Postgres in-VPC, SQS for jobs, all managed with Terraform. A Cloudflare Worker mirrored an increasing slice of live traffic to Kubernetes until everything looked solid, then a DNS flip made it the source of truth.

Supabase data flowed into Aurora via logical replication; once lag was near zero we swapped the connection string and retired the old stack without users noticing. Costs are predictable now and we control most knobs.

We put this post together as a bit of a retro and to help if you're evaluating a similar path for your company.

We removed our previous plan tier of $1 per 2,000 sends.

Example: You have 4,000 users and you send an automated onboarding email along with an occasional product update every month or two.

Your product also generates daily rollup emails, along with product notifications, and other standard transactional emails, maybe 100,000 emails a month total.

That's now available at the same price, just $49.

Say next month you gain another 500 users and you send 200,000 emails. That's still just $49 a month.

Our goal is to help you send all your emails from one platform for a single price point and this gets us one step closer.

>the IPCC Sixth Assessment Report states "It is very unlikely that gas clathrates (mostly methane) in deeper terrestrial permafrost and subsea clathrates will lead to a detectable departure from the emissions trajectory during this century".

Highly recommend checking out the docs for the new API and playing around, it's fun! https://platform.openai.com/docs/guides/vision

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...

Sorry that wasn’t more clear!

Click "view pricing tiers" for all tiers up to 100K :)

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

https://loops.so/docs/add-users/api-reference#rest-api

Shoot me an email (chris@loops.so) and happy to walk you through any questions you may have.

thanks for giving us a try :)