Loops vs Brevo

How the pricing models behave

Loops and Brevo ask you to measure different things. Loops asks how many subscribers the product team wants to keep in the audience. Brevo asks how many emails the team will send in a month, then applies a contact allowance to smaller tiers. A team that sends two onboarding emails to 10,000 active users and a team that broadcasts ten campaigns to 10,000 stored contacts may look identical in a spreadsheet while landing on different plans.

Loops lists the Early Stage Plan at $0 with unlimited contacts and up to 4,000 sends in any rolling 30 days to the 1,000 newest contacts. That is a useful launch shape for a product with a small active audience and a clear newest-user cohort. The free plan has a small Loops footer and lists a 10 emails-per-second limit. When the team pays, Loops lists unlimited sends to subscribers and transactional sends to users outside the audience as included on paid plans.

Brevo lists Free at $0 with 300 sends per day and storage for up to 100,000 contacts. Brevo's Free plan limits automation to 2,000 contacts. A large imported address book does not mean every record can enter an automated onboarding flow. Brevo lists Starter from $9 per month at 5,000 emails and up to 500 contacts, and Standard from $18 per month at the same starting volume with automation, A/B testing and advanced reports.

Write three numbers for each tool: records stored, records eligible for automation and emails sent in a representative month. Add transactional messages separately. For Brevo, record the selected volume tier and its stored-contact allowance; for Loops, record the subscribed audience and the exact slider readout. Do not compare $9 and $99 without preserving those assumptions.

Worked cost scenario: 8,000 contacts and 32,000 sends

Consider a product-led B2B SaaS company with 8,000 stored contacts. Each contact receives two onboarding or product messages per month, for 16,000 lifecycle sends. The company also sends two newsletters to the full audience, adding 16,000 broadcasts. The monthly total is 16,000 + 16,000 = 32,000 email sends. Suppose 8,000 records are subscribed users and the remainder are dormant or transactional-only; this distinction matters because the vendors price the audience differently.

For Loops, the Growing Audience Plan lists $99 per month at 9,998 subscribers. The stated 8,000-subscriber audience is below that published readout, but Loops does not publish an exact 8,000 slider price. The honest calculation is: Loops monthly cost = the exact Growing Audience Plan price for 8,000 subscribers, with pricing on request here rather than an invented interpolation. The paid plan’s included sends mean there is no separate 32,000-send multiplication.

For Brevo, 32,000 monthly sends fall between the published 30,000 and 50,000 Starter readouts. Brevo lists Starter at $39 per month for 30,000 emails and $56 per month for 50,000 emails, both monthly billing. A team needing a published tier above 32,000 would use the next listed volume: $56 per month for 50,000 emails. The arithmetic is one Brevo Starter subscription at $56 × 12 = $672 per year before add-ons. The readout lists up to 500,000 contacts in the 20,000-to-100,000 volume range, so 8,000 stored contacts fit that allowance.

This scenario does not declare a universal winner. Loops may be simpler when product events and transactional mail are central, while Brevo may be cheaper on the published email-volume tier and adds broadcast channels. If the team needs SMS, WhatsApp or a sales pipeline, model those requirements as Brevo scope rather than treating the email row as the complete cost. If Loops is selected, budget a separate provider and engineering work for non-email channels.

• Audience: 8,000 subscribed users plus 8,000 dormant or transactional-only records.
• Send arithmetic: 8,000 × 2 lifecycle emails = 16,000; 8,000 × 2 newsletters = 16,000; total = 32,000 per month.
• Loops: use the exact contact readout for 8,000 subscribers; Loops lists $99 at 9,998, with paid-plan sends included.
• Brevo: choose the listed 50,000-email Starter tier at $56 monthly; $56 × 12 = $672 yearly before add-ons.

Event-driven onboarding versus broadcast-heavy use

The important product question is what starts a message. A Loops-shaped onboarding flow starts with an application event: account_created enters a welcome path, workspace_invited adds a collaboration reminder, first_project_created exits setup education, and no_activity_after_signup starts a timed nudge. The product can keep the message aligned with what a user has done. That requires an event contract, reliable identity and an owner for instrumentation.

A Brevo-shaped onboarding flow often starts with a contact entering a list, gaining an attribute or engaging with a message. That works for a broadcast-heavy team with a strong calendar and moderate product context. It becomes less direct when the journey asks whether a report was created, a teammate was invited or a trial reached a usage threshold. The application must sync those facts into Brevo before the automation can act.

For a mixed model, separate journeys. Put activation and trial education behind product events. Put a monthly product newsletter and quarterly digest behind a campaign calendar. Keep transactional notices tied to application actions. Then decide whether one vendor can own all three without making consent, suppression, event replay and reporting harder to understand.

Measurement follows the same distinction. Product onboarding should report activation, retained use, trial completion and plan change alongside delivery and clicks. Broadcast work may focus on reach, clicks and unsubscribes, then join those results to product analytics or CRM. Neither tool can turn a weak event model into a reliable lifecycle simply by adding another automation step.

1. Name the product event or campaign trigger for every message.
2. Write identity, timestamp and properties, including the missing-property path.
3. Test a new user, activated user, unsubscribed user and deleted user before enabling the flow.
4. Define one product outcome for each lifecycle path and one audience outcome for each broadcast.

Implementation and migration notes

Starting with Loops, implement a thin vertical slice instead of importing every historical contact. Send one server-side account event, one transactional invitation and one lifecycle message. Verify that a duplicate event does not duplicate a message, a changed email preserves identity, and an unsubscribe cannot be undone by a later event. Once those checks pass, add activation and trial branches one at a time.

Starting with Brevo, decide whether the existing stack should use API or SMTP relay for transactional mail. Create an attribute dictionary before importing contacts. Include user ID, plan, role, trial end, activation state, consent and source. Build one welcome automation, one broadcast list and one suppression test. Add SMS, WhatsApp or sales objects only after the email path is stable.

Moving from Brevo to Loops is not a one-click translation when the old account is broadcast-heavy. Export templates, contacts, consent, suppression, lists and automation history. Map each recurring campaign to a Loops lifecycle path or product-newsletter process. Decide where SMS, WhatsApp and CRM records will live, and tell owners which workflows disappear at cutover.

Moving from Loops to Brevo requires the opposite translation. Export event names and payload examples, then identify contact attributes or integration events that represent them in Brevo. Rebuild transactional templates through API or SMTP, preserve suppression state, and check the stored-contact allowance of the selected email tier. Importing a list does not reproduce an event-driven journey.

For both directions, keep a dated export and rollback path. Test a password reset, invitation, activation message, broadcast, unsubscribe, hard bounce and deleted account. Record owners for event delivery, copy, consent, variables, channel configuration and reporting. A migration is complete when the team can explain a message from trigger to outcome, not when a row count matches.

1. Inventory contacts, consent, templates, suppression, events, lists and owners.
2. Map each message to a product event, campaign trigger or transactional call.
3. Pilot an opt-out, bounce, duplicate and deleted user.
4. Freeze changes, export, cut over in stages and keep the old system read-only until a full cycle completes.

How to choose for a B2B SaaS team

Choose Loops when the product is the source of truth for customer state, the team wants a compact email operating model, and event-driven onboarding is more valuable than a broad channel catalogue. The Early Stage Plan gives a startup a $0 entry point with a bounded send allowance. The paid model follows subscribed contacts while including sends to subscribers and transactional messages on paid plans. This fits a product team that can maintain event definitions and wants marketing messages to follow real usage.

Choose Brevo when email volume and broadcast operations are the primary planning unit, or when SMS, WhatsApp and sales tools belong in the same account. Brevo’s Free plan can hold a large contact book, but the automation limit and daily send cap still need attention. Starter and Standard list low starting prices, then move with selected volume. The broader product is useful when there are owners for campaign calendars, consent, messaging channels and CRM data.

If the team is split, run a two-week proof with the same journey in both products. Emit account_created, first_value and trial_ending events, send one transactional invitation and publish one newsletter. Ask marketing to change copy, engineering to replay an event, an operator to suppress a user and a manager to read the outcome report. The friction is more useful than a checklist of feature names.

Make the decision legible. Write audience, sends, automation contacts, channels, integrations, owners and annual arithmetic beside the recommendation. Loops is the better fit when a lean event-driven email layer is the requirement. Brevo is the better fit when broadcast volume and multi-channel breadth are requirements that the team will actively operate.

• Pick Loops for product-led onboarding, lifecycle context and focused developer-to-marketer ownership.
• Pick Brevo for broadcast-heavy marketing, SMS or WhatsApp, and a CRM add-on path.
• Say pricing on request when Loops does not publish the exact audience readout needed.
• Treat consent, event ownership, suppression and reporting as part of the product decision.