One tool for receipts, password resets, drip campaigns, and broadcasts — built for SaaS, priced at $49/month for the entry tier, and increasingly the default in the indie founder stack. Pricing and capabilities verified against loops.so/pricing and the public docs.
Email is one of those areas where solo SaaS founders quietly end up paying for two or three tools that don’t talk to each other. Resend or Postmark for transactional. Beehiiv or Kit for the newsletter. Maybe Customer.io for product-led drip flows. Each one knows about a different slice of your users, and your “list” lives in three databases. Loops is the platform betting that this split is artificial — that one tool, with one customer record, can do every email a SaaS sends. After three years of growth, it’s become the default email choice across a meaningful chunk of the indie SaaS scene, and the case for picking it is clearer than it was even twelve months ago.
Methodology. This is a research-based overview. We have not personally built production apps with Loops; this article synthesizes the company’s documentation at loops.so/docs, public pricing at loops.so/pricing, public user reports from indie founders, and third-party benchmarks. Last reviewed: May 8, 2026.
Loops is a modern email platform built specifically for software companies. It was founded in 2022 and has spent its history positioning itself against two older categories at once: the developer-first transactional services (Resend, Postmark, SendGrid) and the marketer-first lifecycle platforms (Customer.io, Mailchimp, Intercom). The pitch is that those categories don’t need to be separate tools when your customer record is the same record either way.
What you get inside the product is one customer table, one event stream, and four ways to send mail to the people in it: a transactional API for receipts and password resets, broadcasts for one-off campaigns, loops (the lowercase-l product feature, distinct from the company name) for event-triggered drip sequences, and a visual audience builder for filtered targeting across all of the above. The whole thing runs on Amazon SES underneath with dedicated IPs at higher tiers, which is unremarkable infrastructure but matters when you’re thinking about deliverability.
The thing Loops sells, and the reason founders keep switching to it, is the elimination of friction between marketing and product email. In a typical split-tool stack, when a user upgrades from trial to paid, you have to push that event into Resend somehow (it doesn’t care), into Customer.io (so the “upgrade welcome” sequence fires), and into Kit or Beehiiv (so they get tagged as “customer” instead of “trial”). Three integrations, three places where the data can drift, three vendors to pay.
In Loops, that single upgrade event lives in one customer record. The transactional receipt fires from the same event. The drip sequence triggers off it. The broadcast next month can segment on it. Nothing has to sync because there’s only one source of truth. That’s a small story when you describe it abstractly and a meaningful relief in practice, especially for solo founders who don’t want to maintain three vendor integrations and a webhook bus to stitch them together.
Four primitives carry the product:
The interesting move is that these four primitives share infrastructure. A user property updated by a transactional event is immediately available in audience filters and loop conditions. A broadcast targeted at “people who clicked link X” works because that click data lives in the same database as the customer record.
The segmentation surface is where Loops feels most clearly built for SaaS. Filters compose across three axes: user properties (anything you’ve set on a contact, like plan or signup source), behavior events (anything you’ve fired through the API, like “completed onboarding” or “invited teammate”), and computed metadata (when they signed up, when they last opened mail, when they last received a campaign).
The combinatorics get useful fast. “Pro users who haven’t fired the ‘exported a report’ event in 30 days, signed up after January, and opened the last newsletter” is one filter. You can save it as a named audience, target a broadcast at it, or use it as the entry condition for a loop. None of that requires a data warehouse, a reverse-ETL pipeline, or a separate analytics tool.
The trade-off — and it’s real — is that Loops is not a replacement for a dedicated analytics or product-engagement tool. If your segmentation needs are deeply behavioral and span dozens of events, something like Customer.io will give you a more powerful query language. The Loops segmentation is calibrated for the email use case, not for cohort analysis.
The lowercase-l “loops” are the marketing-automation primitive. A loop is a directed graph: an entry trigger (an event or a user property change), a series of email steps, optional conditional branches, optional time delays, and optional exit conditions. The visual editor handles the construction; the engine handles the execution.
What makes the implementation feel modern, by reports from founders using it, is that loops are idempotent and observable. Editing a step doesn’t break in-flight users. You can see how many users are at each step in real time. Pausing a loop pauses every active execution rather than letting them drift. Compared with the Mailchimp-era model where automations were write-once and reading their state required exporting a CSV, this is genuinely better tooling.
A/B tests inside loops are first-class: pick a step, define two variants, set a split percentage, and the engine routes traffic and reports the lift. For drip optimization — which subject line, which CTA, which sequence length — this is the right shape. It’s not the most powerful experimentation tool in the world, but it covers 90% of what solo founders actually want to A/B test.
The template editor is a visual block-based builder, more in the Beehiiv lineage than the React Email lineage. You drag blocks (heading, paragraph, button, image, divider) onto a canvas, style them with theme tokens, and preview against test data. There are starter templates and a save-your-own template library.
For developer-heavy founders, this is the one place where Loops is less flexible than Resend. If you want to define your transactional emails in TypeScript with React Email, version-control them, and run them through CI like the rest of your codebase, Loops doesn’t natively support that workflow — you’re editing in the visual builder. Loops does let you pass HTML from the API for transactional sends, but the canonical workflow is the visual editor. For non-technical co-founders, that’s a feature; for solo founders who want everything in code, it’s a friction. We cover the React Email approach in the how to add Resend emails to Next.js guide for the developer-first take.
Loops publishes four tiers on loops.so/pricing. Always reconcile against the live page; pricing on this category shifts.
The two numbers worth fixing in your head: $0 for up to 1,000 contacts (real product-validation territory) and $49/month for up to 10,000 contacts with unlimited sends. The unlimited-sends part is the meaningful detail — most competing platforms meter on volume, not contacts, so heavy-sending products end up paying more.
Loops ships an official Node SDK, a REST API, webhooks for incoming events, and direct integrations with the products solo founders are most likely already using: Stripe (subscription events), Supabase (auth events), Clerk (user events), Segment (the standard event router). Zapier and Make connectors fill the long tail.
The practical pattern looks something like: when a user signs up via Clerk, a webhook fires into Loops with the user’s email and metadata; Loops creates the contact and triggers the welcome loop; transactional sends from your app hit the Loops API directly; subscription changes from Stripe sync as events on the customer record. None of those steps require building the customer data layer yourself, which is the part that usually eats the weekend.
Email deliverability is where reputation actually compounds. Loops uses Amazon SES underneath with dedicated IPs at the higher tiers, which is the same infrastructure foundation Resend and several others use. By public reports, deliverability is consistently good for the marketing use case — broadcast inbox placement is comparable to dedicated marketing tools.
For pure transactional volume, however, Postmark continues to have the edge. Postmark’s entire business is transactional reliability, and they invest in things (separate IP pools for transactional vs marketing, stricter sender policies, faster bounce handling) that show up at the margin in inbox placement for time-sensitive emails. If your product depends on a password reset arriving in under a minute every single time, Postmark is still the safer choice. We compare these in Resend vs Postmark. For most SaaS, Loops’ deliverability is more than sufficient.
Three product shapes where Loops is genuinely the right pick:
Three scenarios where a more specialized tool makes more sense:
Resend is developer-first transactional email with React Email templates and a clean API. It does transactional excellently and adds marketing capabilities (Audiences, Broadcasts) more recently. The choice between them comes down to where you sit on the marketing surface: if you want minimal marketing tooling and maximal developer ergonomics, Resend wins; if you want full marketing surface alongside transactional, Loops wins. We dive into Resend pricing in the Resend pricing breakdown.
Customer.io is a heavyweight customer engagement platform with multi-channel messaging, SQL-grade segmentation, and pricing to match (entry tier substantially higher than Loops). It’s the right answer for B2B SaaS with mature lifecycle programs and enterprise budgets. For solo founders, Loops covers most of the same use cases at a fraction of the price; Customer.io is overkill until you’ve outgrown the simpler tool.
Kit (formerly ConvertKit) is built for creators — newsletter authors, course creators, audience-first businesses. Its automation surface is real but the data model is creator-shaped (subscribers, tags, sequences) rather than SaaS-shaped (customers, events, plans). For a SaaS, Kit feels like the wrong shape; for a newsletter business, Loops feels equally off. They’re solving different problems despite both being in the email category.
For solo SaaS sending under 100,000 emails a month and wanting unified transactional and marketing email in one tool, Loops is genuinely the best choice on the market. The product is well-built, the pricing is fair, the integrations cover the modern stack, and the elimination of cross-tool data sync is a real time saver. The $49/month entry tier with unlimited sends is the kind of pricing that doesn’t make you flinch when traffic spikes.
The cases against it are specialized: pure transactional at high volume (use Resend or Postmark), enterprise lifecycle complexity (use Customer.io), or a newsletter-first business (use Beehiiv or Kit). For everyone in between — which is most solo SaaS — Loops is hard to beat. The platform fits naturally into the rest of the modern indie stack we cover in the best email marketing tools for SaaS roundup.
Email is a corner of the stack where consolidation is a real productivity win. Loops is the consolidation play that’s actually working.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.