Customer.io vs Loops: Which Email Tool Fits Your List Size and Budget

For most SaaS teams that send lifecycle and product email to a list of up to a few tens of thousands of people, Loops is the better pick. Its Early Stage plan costs $0 and covers up to 4,000 sends in any rolling 30 days, and its Growing Audience plan is listed at $99 a month with all features included. Customer.io is the better pick when you need email, SMS, push and in-app messages run from one workflow builder. Its Essentials plan starts at $100 a month, and profile-based pricing runs from $145 a month at 10,000 profiles to $505 a month at 50,000 profiles and above.

The short version: choose Loops when email is your main channel and you want to be live in an afternoon. Choose Customer.io when your messaging spans several channels, when you need branching journeys that depend on many behavioural events, or when you have someone who can own the data model. The rest of this page explains the trade-offs, shows what each option costs at realistic list sizes, and gives a setup checklist for each.

Prices below come from each vendor's pricing page, checked on 7 October 2026. Vendors change plan limits, so confirm the current numbers on the linked pricing page before you commit.

The Two Tools at a Glance

Customer.io and Loops both send marketing and product email to people who use your application. They differ in what they count, what they include, and how much work they expect from your team.

The table hides one important difference. Customer.io counts profiles, which are the people and records it stores with their events and attributes. Loops counts contacts, which are the people on your list. Those two numbers are rarely the same for a product company, and the gap matters when you compare bills. Before you run any calculation, check which number your application would produce for your database.

Customer.io: Where It Earns Its Place

Customer.io is a behaviour-first messaging platform. Its strength is that a message can depend on what a person has done in the product, what they have not done yet, and what other channels have already reached them. A typical SaaS use case is an onboarding journey that waits for a team to invite a second user, sends a short email if the first integration is not connected within three days, and switches to an SMS reminder for accounts that opt in to text messages. Customer.io can express that logic in one visual workflow.

For this audience, the main advantages are the following. Multi-channel delivery means the same event can drive email, SMS, push and in-app messages without a second vendor. Workflow depth supports conditional branches, waits based on user behaviour and sequences that stop automatically when a goal is reached. Segmentation can use the attributes and events you already send from your application. Essentials includes the visual workflow builder and basic data integrations, and the AI Agent core skills listed on the pricing page are included at that tier.

The limitations are real. Setup takes longer than a simple email tool because you need an event schema, a naming convention and a clear idea of which events represent progress. Teams that skip that planning end up with journeys nobody trusts. Costs also rise as profiles accumulate, so a company with a large anonymous visitor base can pay for records it never emails. The Premium plan, listed at $1,000 a month, is priced on custom profile volume and includes premium support and elevated AI Agent limits. It is designed for larger programmes, not for a first email tool.

Price: Essentials is listed at $100 a month and is billed monthly on the pricing page. Profile-based Essentials tiers are listed at $145 a month for 10,000 profiles, $235 for 20,000, $325 for 30,000, $415 for 40,000 and $505 for 50,000 and above. Premium is listed at $1,000 a month. The pricing page is at customer.io/pricing.

Loops: Where It Earns Its Place

Loops is built for teams that want to send well-written email to their users without first building a data platform. Its interface is organised around a contact list, a set of sequences and one-off broadcasts. For a founder who wants to send a welcome series, a monthly product update and a re-engagement email to dormant users, Loops asks for less configuration than most enterprise tools.

For this audience, the main advantages are these. Setup is quick because you connect your contact data, build a sequence and publish. Transactional sends to users outside your audience are part of the paid Growing Audience plan, so one tool can handle product notifications and marketing email. Both plans include all features, so you do not have to upgrade to unlock a sequence type or an integration. The free Early Stage plan is useful for testing a launch before you spend money.

The limitations matter for growing teams. Loops is email only, so SMS, push and in-app messages need another product. Its workflow depth is lower than Customer.io's, which means very long branching journeys can become awkward to maintain. The Early Stage plan also restricts sending: it allows up to 4,000 sends in any rolling 30 days, and sends go to the 1,000 newest contacts. That is enough for a small list but restrictive for a product with a large, active base. The free plan also adds a Loops footer to your emails.

Price: Early Stage is $0 and includes up to 4,000 sends in any rolling 30 days, with a limit of 10 emails per second and the Loops footer on each message. Growing Audience is listed at $99 a month and includes unlimited sends to subscribers, transactional sends to users outside your audience and all features. The pricing page does not tie the $99 plan to a single contact count in the figures summarised here, so check loops.so/pricing for the contact range that applies to your list.

Pricing at Realistic List Sizes

The table below applies each vendor's listed prices to a set of audience sizes. Customer.io figures use its profile tiers. Loops figures use the Early Stage limit and the Growing Audience price. Where the pricing page does not give a figure for a size, the table says so rather than estimating.

Two calculations make the gap concrete. At 10,000 profiles, Essentials at $145 a month costs $46 more than Growing Audience at $99 a month, which is 12 × $46 = $552 a year, but only if your contact count falls in the range that Loops prices at $99. At 20,000 profiles, the difference is $235 − $99 = $136 a month, or 12 × $136 = $1,632 a year, on the same condition. Confirm the Loops range before you rely on either number.

The free plans change the picture for very small products. Loops' Early Stage plan is free within its send limit, while Customer.io offers no standard free plan. Customer.io's Startup Program gives eligible early-stage companies that have raised under $10M 12 months free. If you qualify, that offer can outweigh the Loops price for the first year, but it is not a general free tier.

Budget for more than the subscription. Customer.io's total cost includes the engineering time to send clean events, and the team time to design journeys. Loops' total cost includes the time to write sequences and keep your contact data in sync. For a two-person team, the staff hours often matter more than the list-size tier.

Choosing Between Them

The decision usually turns on three questions: which channels you need, how complex your journeys are, and who will run the tool day to day. The table below maps common situations to a pick and gives the reason.

Consider two realistic scenarios. In the first, a bootstrapped B2B tool with 6,000 contacts wants a welcome series, a weekly product digest and a renewal reminder. The main channel is email, the volume fits the free plan for part of the year, and one person handles marketing. Loops is the sensible choice, and the upgrade to Growing Audience at $99 a month becomes relevant when sends outgrow the free limit.

In the second, a consumer SaaS app with 30,000 active profiles wants to send an email, then an SMS if the email is not opened, then a push notification when a trial is about to end, and to stop all of these when the user upgrades. This is a multi-channel, behaviour-driven journey. Customer.io's workflow builder is designed for it, and the profile tier at this size is listed at $325 a month. The team must, however, plan the event schema before building the journey.

Setup and Migration Checklist

Both tools can be live quickly, but the work differs. The checklist below lists what each one asks for before you send your first message. Use it as a planning document, not as a promise about how long your project will take.

Migration deserves special care whichever tool you choose. Export your unsubscribe and suppression lists first, because re-importing them incorrectly is the fastest way to email people who asked not to hear from you. Then rebuild your sequences rather than trying to copy them, since the trigger logic differs between platforms. Keep the old tool running for a short overlap only if you are confident the two are not sending duplicate messages to the same people.

Where Segment Fits

Some teams compare Customer.io with Segment, which is a customer data platform that collects events and sends them to destinations. Segment is not a messaging tool in the same sense. It is a data layer that can feed Customer.io or other tools. Its pricing is custom and is not published on its pricing page, so the price is on request. If you already run Segment, Customer.io can receive the same events, which avoids a second data pipeline. If you do not run Segment, you do not need it to use Customer.io or Loops.

What Each Choice Commits You To

Choosing Customer.io commits you to a data discipline. Its strengths come from clean, well-named events, and its costs grow with the profiles you store. Plan for a review every quarter to remove stale profiles and check that your journeys still match the product. Choosing Loops commits you to a simpler workflow. You will spend less time on data design, but you may hit the limits of its branching logic or need a second tool once you add SMS or push. Both choices are reasonable. The mistake to avoid is buying the more powerful tool and using it as a simple email sender, or buying the simpler tool and then forcing it to run journeys it was not designed for.

If you are unsure, start with the cheaper option that covers your next six months of plans, and set a date to revisit the decision. Write down the channels you expect to add, the size of your list at that point and the number of people who will edit journeys. Those three facts tell you more than any feature table.

You can compare other email tools on the main comparison page.

Frequently Asked Questions

Is Loops really free?

Loops has an Early Stage plan at $0 a month. It includes up to 4,000 sends in any rolling 30 days, sends to the 1,000 newest contacts, and the Loops footer on emails. Paid use starts with the Growing Audience plan, listed at $99 a month, on the pricing page at loops.so/pricing.

Does Customer.io have a free plan?

Customer.io does not list a standard free plan. Eligible early-stage companies that have raised under $10M can receive 12 months free through its Startup Program. Check the pricing page at customer.io/pricing for the eligibility rules.

Why does Customer.io charge by profiles?

Customer.io prices its Essentials tiers by the number of profiles, which are the records it stores with their attributes and events. Its pricing page lists tiers from 10,000 to 50,000 profiles, and above 50,000 the figure shown is $505 a month or more. Anonymous or inactive profiles count toward the total, so the number that matters is the one your application creates.

Can Loops send transactional emails?

Loops includes transactional sends to users outside your audience on its paid Growing Audience plan. The original version of this comparison also listed transactional email as separate for Customer.io, which points to Parcel, a separate product priced per user on its pricing page at $29 a month for building production emails and $56 a month for teams working at scale.

Which tool is better for SMS and push notifications?

Customer.io handles email, SMS, push and in-app messages from one platform, which makes it the better fit when those channels need to run in the same journey. Loops is email only, so you would need another product for SMS or push.

How long does setup take?

Setup depends on your data and how many journeys you build. A basic Loops sequence can be published quickly once your contacts are imported. Customer.io usually takes longer because you need to define events and attributes from your application before building a journey. Plan the event schema before you start, and treat the first journey as a test of that schema.

Can I move from Loops to Customer.io later?

Yes, but migrate carefully. Export your contacts and suppression lists first, rebuild the sequences with Customer.io's trigger logic rather than copying them, and confirm that unsubscribed people stay unsubscribed in the new tool before you send anything.

Is Segment required to use Customer.io?

No. Customer.io can receive events directly from your application. Segment is a separate customer data platform with custom pricing, and it is only useful if your team already uses it or needs a shared data pipeline across several tools.