# Brevo vs Loops Source: https://wraps.dev/versus/brevo-vs-loops One is a broad European suite that will also do SMS, WhatsApp and a light CRM. The other does one job for one kind of company. Breadth and focus are both defensible, and they produce very different bills. These two disagree about how much a marketing tool should try to be. Brevo is a suite: email, SMS, WhatsApp, chat, a light CRM, priced on the volume you send and aimed at a small European business that would rather have one invoice. Loops is deliberately narrow: lifecycle and transactional email for a software company, priced on contacts with sending unlimited. The comparison is not really about features, it is about whether consolidation or focus is the thing currently costing you time. ## At a glance |   | Brevo | Loops | | --- | --- | --- | | What it is | EU marketing platform with a transactional API attached | Product + marketing email for SaaS, priced per contact | | Published pricing | Priced on send volume rather than contacts. Starter runs from roughly $9/mo at 5,000 emails to roughly $69/mo at 100,000; the Business tier is roughly double at each volume and is where automation and A/B testing live. | Free at 1,000 contacts and 4,000 sends/mo. Paid plans price on subscribed contacts with unlimited sends — $49/mo in the 1K–5K band, $99/mo in the 5K–10K band, rising from there. | | Best for | Small EU teams wanting email, SMS, and a light CRM on one invoice. | SaaS teams who want lifecycle and transactional in one tool and never want to count sends again. | | Watch out for | The headline tier is not the one you need — automation and removing the Brevo logo are both a step up. Shared-pool deliverability draws mixed reports. | You pay for contacts, not sends, so a large dormant free list stays on the bill. It is a product rather than a primitive, with less low-level control than an email API. | Prices are each vendor's published list prices, verified August 2026. Check the vendor's own page before you sign anything. ## Where they actually differ ### What the meter counts, and which list shape it punishes Brevo Send volume. A contact costs nothing until you mail them, so a large quiet audience is cheap and a small engaged list mailed constantly is not. For a business with seasonal campaigns to a big list this is plainly the better shape, and it means every send decision carries a small cost calculation. Loops Subscribed contacts, with sending unlimited. You stop counting messages, which measurably changes behaviour — more experiments, more splits, less hesitation. The symmetric cost is that dormant free-tier signups sit on the invoice forever, so list pruning becomes a billing decision as much as a hygiene one. ### The tier where the feature you assumed lives Brevo Automation and A/B testing sit on the Business tier rather than the entry one, and so does removing Brevo's own logo from the footer of your emails. The headline price is therefore not the price of the product most people are evaluating, and this is the single most common way a Brevo comparison ends up wrong. Loops One product, one shape. What you can do does not change much between plan bands, because the bands are about how many contacts you hold rather than which features are unlocked. That makes the comparison honest and it also means there is no upgrade path to buy your way out of a capability gap. ### Everything that is not email Brevo SMS, WhatsApp, a chat widget and a light CRM on one account and one invoice. For a small business that would otherwise be assembling three vendors, that consolidation is the entire pitch and it is a real one. The depth of each piece is modest next to a specialist, which is usually acceptable and occasionally not. Loops Email, and nothing else, on purpose. The day somebody decides a notification should also go by text, you are adding a vendor. That narrowness is why the product is pleasant to use and it is a genuine constraint rather than a roadmap gap. ### Who the product was drawn around Brevo A small business of almost any kind — a shop, an agency, a clinic, a local service — which is why the surface is broad and the concepts are generic. Contacts, lists, campaigns, automations: a model that fits everybody reasonably and nobody perfectly. Loops A software company with subscribers. Onboarding sequences, trial nudges, feature announcements, a monthly update. Because the assumed customer is that specific, a great deal of configuration simply does not exist and the defaults are usually right. A business outside that shape feels the absences immediately. ### European data handling Brevo Brevo is a French company operating under EU regimes, which for organisations whose real requirement is about who they contract with and under which law is a shorter conversation than a region toggle inside an American platform. It does not replace reading the data processing agreement and it does shorten the meeting. Loops Loops is a smaller, newer vendor and the residency answer is whatever its documentation currently states. If you have a hard requirement rather than a preference, verify it directly and get it in the agreement, because with a young company the honest position is that the answer may still be evolving. ### Transactional mail on the same account Brevo Brevo has a transactional API and SMTP relay alongside the marketing product, so receipts and campaigns can share a vendor. Keep them on separate subdomains regardless, because sharing a vendor is sensible and sharing a sending reputation between bulk and transactional mail is not. Loops Transactional and lifecycle live in the same tool against the same contact record, which is the consolidation small teams actually want: one view of everything a person received. It also means your password resets depend on your marketing tool being available, which is a trade worth stating out loud. ### The developer surface Brevo A large API covering the whole suite, plus SMTP, plus SDKs, with the surface area and the occasional inconsistency of a product that has grown by addition over many years. Everything is reachable; some of it takes reading. Loops A small, current API aimed at identifying contacts and sending events so the tool can react. The scope is deliberately compact and appropriate to the product. It is not a general-purpose sending platform and there is no pretence otherwise. ### Deliverability posture Brevo Shared sending pools draw mixed reports, which is the ordinary condition of a platform serving an enormous number of small senders of wildly varying quality. Authenticate properly, warm deliberately, and consider whether your volume justifies dedicated sending, because on a broad shared pool your neighbours matter and you cannot audit them. Loops A smaller, younger sending operation with a shorter public record and a customer base that skews toward software companies mailing their own users, which is a comparatively clean traffic profile. There is no widespread pattern of complaint about arbitrary account action, which counts for something in a category where sudden suspension is the dominant fear. ### What happens when you outgrow it Brevo You outgrow Brevo when you need genuine behavioural journeys rather than list-and-trigger automations, or when the breadth stops compensating for the depth. The usual next step is a specialist lifecycle platform, with Brevo sometimes retained for SMS or the CRM. Loops You outgrow Loops when conditions stop being expressible as filters, when you need per-tenant isolation, or when a legacy system needs an SMTP host. The ceilings arrive at a predictable size, which is an argument for choosing it deliberately as a stage rather than pretending it is a permanent answer. ### What the free tier is actually for Brevo Getting a small business sending. Brevo's free allowance has a daily cap under it and is a genuine starting point rather than a demonstration, which is why so many small organisations run on it for months before ever paying. The visible cost is that the vendor's logo sits in the footer until you move up two tiers, which some businesses mind and many do not. Loops Proving the shape fits before you commit. The free band holds a modest number of contacts with a monthly send allowance, enough to wire the integration, build an onboarding sequence and watch it run against real signups. Because the paid plans are bands of contacts rather than unlocked features, what you build on the free tier is what you keep — there is no discovery later that the thing you designed around was a paid capability. ### Reporting, and the question you ask next quarter Brevo Campaign-level statistics with the usual opens, clicks, bounces and unsubscribes, plus per-contact activity, and enough filtering to answer most questions somebody asks in a Monday meeting. History is retained on the vendor's terms, and because the suite spans several channels the reporting is broad rather than deep on any one of them. Loops Per-contact timelines showing what a person was sent and what they did, which is the shape a SaaS team actually asks questions in: did this user get the activation nudge, and did it work. Aggregate reporting is lighter than a mature platform's, and the honest answer to a long-range analytics question is to send the events back into your own warehouse and ask them there. ## Pros and cons, side by side ### Brevo Strengths - A quiet audience costs nothing until you mail it, so a company with a large seasonal list is not paying monthly rent on people it contacts twice a year. - Four channels and a small contact database arrive under one supplier relationship, which is a genuine reduction in paperwork for an organisation that buys software slowly. - The surface is generic enough to suit a clinic, an agency or a shop, which is why a business in no obvious software category still finds it usable. - There is always a higher band, so a capability you discover you need in month four is usually a purchase order rather than a change of supplier. Trade-offs - The features an evaluator assumes are included sit above the plan whose price they compared, which is the commonest way a shortlist involving this product turns out to have been wrong. - Another company's mark sits in the footer of mail leaving your own domain until you have climbed two steps of the plan ladder. - Breadth has accumulated over many years and the interface shows it: everything is reachable, and some of it takes an afternoon of reading to reach. - The shared pool holds an enormous number of small senders whose list practices you can neither inspect nor influence. ### Loops Strengths - What you can do does not change between bands, so whatever you build during the trial is what you keep and nothing waits behind an upgrade. - Teams stop weighing whether one more send is worth paying for, and the measurable consequence is more experiments rather than fewer. - The concepts are few enough that a founder builds and sends something without a walkthrough, on a team where nobody's title contains the word email. - Receipts and announcements leave through one system against one record, so a single screen answers the question of what this person has been sent. Trade-offs - A dormant signup from two years ago is rent, every month, whether or not you ever intend to write to them. - The day somebody decides a notice should also arrive by text you are adding a supplier, because the product has no intention of growing that way. - The company is young enough that a residency answer describes where things currently run, which is a weaker thing than a commitment about where they will. - There is no band to buy when a capability turns out to be missing, so a gap found in month four is a gap you keep. ## Pick in thirty seconds ### Choose Brevo if - You want email, SMS and a light CRM on one invoice rather than assembling three vendors. - Your list is large and quiet, so paying per contact for people you rarely mail would be the worse deal. - Contracting with a European company under European law shortens a conversation you have to have anyway. - Campaigns are seasonal or occasional rather than a constant cadence to a small audience. ### Choose Loops if - You are a software company and the emails that matter are onboarding, activation and product updates. - You want lifecycle and transactional sends against one contact record in one tool. - Not counting sends is worth more than not paying for dormant contacts. - You would rather a tool with no unlockable tiers than a headline price that is not the price of the product you need. ## What actually moves when you switch In roughly the order you would do it. The expensive parts of an email migration are never the send call. 1. Model the two meters against your own list before reading another feature page, because the crossover is sharper than either pricing page implies and it settles most of this. One side multiplies people by nothing and messages by frequency; the other multiplies people by a monthly rate and messages by nothing. Fifty thousand contacts written to each quarter and three thousand written to each week land on opposite answers, and the second figure — how often you genuinely send, not how often you intend to — is the one teams get wrong by a factor of two. 2. Find out whether somebody who unsubscribed still counts toward a contact-priced band, and get that from the vendor rather than from a forum thread. On a meter that charges for people instead of for messages, the population you are billed for and the population you are permitted to write to are two different sets, and the gap between them widens every month. A list that has been collecting signups for three years carries a quantity of dead weight that is invisible on a send-metered bill and expensive on the other kind. 3. Check the daily ceiling underneath a monthly free allowance against your burstiest single day, not against your monthly average. A free tier generous enough to run a small product on is usually shaped as a monthly figure with a much tighter per-day limit below it, and a launch, an incident notice or an end-of-month billing run is exactly the traffic shape that fits the month and fails the day. Find the daily number, double your worst day, and see whether what you are looking at is a plan or a demonstration. 4. Inventory the text-message sender registrations before assuming that channel travels with you. Sender identifiers, per-country approvals and the paperwork behind them belong to the account that applied for them rather than to your company, and several jurisdictions take weeks to grant one. A team treating text messaging as a feature toggle finds at switchover that the channel is dark for a month in its two largest markets. If it matters at all, start the replacement registrations before giving notice on anything. 5. Search your own website for embedded scripts pointing at the supplier you are leaving. Hosted signup forms and landing pages are convenient precisely because they are somebody else's code running on your pages, and they keep running until the account closes — at which point a form quietly stops collecting and nobody notices for a fortnight, because forms fail silently and nobody monitors a thing that has never broken. List every embed, then decide for each whether it is being rebuilt, replaced or retired. 6. Decide what your password resets do when the messaging tool is unavailable, because folding transactional and lifecycle sending into one product turns that into an operational question rather than a theoretical one. One supplier and one contact record is a real simplification, and it couples the mail your product depends on to the availability of the tool your marketing runs in. Either accept the coupling deliberately, with somebody named to notice it, or keep a second path configured and dormant for the messages a customer cannot do without. 7. Get the residency answer into the agreement rather than reading it off a documentation page, because with a young company the honest position is that it may still be moving. A mature European supplier answers this by corporate nationality and a signed processing agreement, which is a fact about the company. A newer one answers it by describing where things currently run, which is a fact about this quarter. Those are different grades of assurance, and only one of them survives the supplier changing where it hosts. 8. Establish what happens when a capability turns out to be missing, because the two sides answer that very differently and only one answer costs money. A product with a ladder lets you buy out of most gaps, which is precisely why its headline price is not the price you end up paying. A product with one shape and bands of people cannot — the gap you find in month four is the gap you keep, and the remedy is a second supplier or another move. Neither arrangement is wrong. Knowing which one you bought is what keeps the discovery from being a crisis. ## Questions to ask before you sign Put these to a sales rep, or find the answer in the documentation before anyone quotes you a number. 1. How many contacts do we hold, how often do we genuinely send, and which of the two meters does that pair of numbers favour? 2. Does a person who unsubscribed still count toward a contact-priced band, and who at the vendor confirmed that in writing? 3. What is the daily ceiling under the free allowance, and what did our single busiest day look like last quarter? 4. Which text-message sender registrations belong to the account we would be leaving, and how long does a replacement take to grant? 5. Where on our website is a form or a landing page served by the supplier's own script, and who rebuilds each one? 6. If the messaging tool were unavailable for six hours, which of our messages would a customer actually miss? 7. Is the residency answer in a contract or on a documentation page, and would it survive the company changing where it hosts? ## Common questions ### Is Brevo's entry plan enough? Only if you are sending campaigns and nothing else. Automation and A/B testing live on the Business tier, and so does removing Brevo's logo from your email footer. If your plan involves any sequence that triggers on its own, or you object to another company's branding on mail from your domain, the tier you are actually buying is the higher one and the comparison should be priced there. Doing this arithmetic first is the single most useful step in evaluating Brevo. ### Which one is cheaper? It depends entirely on the shape of your list, and the crossover is sharper than people expect. Model it with your own numbers: contacts multiplied by nothing on one side, sends multiplied by frequency on the other. A business with fifty thousand mostly dormant contacts mailing quarterly is far cheaper on send-based pricing. A business with three thousand engaged users receiving a weekly sequence is far cheaper on contact-based pricing. Neither vendor's pricing page will run your version of this. ### Can a non-engineer run either of these? Yes, with different learning curves. Loops is obvious on first open because there are few concepts and one way to do most things. Brevo is broader and more generic, so the first campaign takes longer to find your way through, and once learned it does considerably more. If nobody on the team has time to learn a platform, that difference is worth more than any feature comparison in this list. ### How do I handle unsubscribes if I run two tools? Decide explicitly which system holds the authoritative consent record and make the other read from it rather than maintaining its own view. Two systems each keeping their own opinion about who opted out is how somebody unsubscribes from a newsletter and then stops receiving order confirmations, which is a support problem and possibly a compliance one. Write the decision down, because this is exactly the piece of institutional knowledge that leaves with the person who set it up. ### What should I export before switching either direction? Contacts with their consent status and opt-in timestamps first, because when somebody consented is the one record you cannot reconstruct and the one a regulator asks about. Then your suppression list, imported before the first production send rather than after. Templates and automations cross no paradigm boundary and have to be rebuilt by hand, so budget that as real work rather than a migration step. Finally, list every place your application calls the old API — the background job nobody remembers is what keeps sending from an account you thought you had closed. ### Do unsubscribed contacts count toward a per-contact bill? Ask, because it is the difference between two quite different invoices and the pricing page rarely says. Some products bill on everybody stored, some on everybody currently subscribed, and a few draw the line at anybody who has not hard-bounced. On a list that has been accumulating for three years the unsubscribed and unreachable population can be a meaningful fraction of the total, which means the same audience produces two figures depending on where the vendor counts from. The practical step is to pull your own numbers first: total records, currently subscribed, unsubscribed, hard-bounced, and never-engaged-in-a-year. Then ask which of those the quote is based on. If the answer is the largest one, you are paying to store the evidence of people who asked you to stop, and the remedy — deleting them — collides with the fact that you need to keep proof of the opt-out. ### Can a small product run on either free tier indefinitely? Often yes, and the figure that decides it is not the one on the pricing page. A free allowance is usually quoted monthly with a much tighter daily ceiling underneath, and ordinary product traffic is not evenly spread — a launch announcement, an incident notice or a billing run all arrive as a single day's spike that fits inside the month and does not fit inside the day. Work out your worst single day over the last quarter, double it, and check that against the daily limit rather than the monthly one. The second thing to check is what happens when you cross it: sending that queues and catches up is an inconvenience, and sending that is silently dropped is an outage in the messages your customers most notice missing. ### What happens to my text messaging if I switch suppliers? It stops, and then it takes longer to restart than anyone expects. The registrations that let you send under a recognisable sender name are held per country, granted to the account that applied, and in several jurisdictions they involve documentation, a waiting period and occasionally a local entity. None of that transfers. A team that thinks of text messaging as another channel on the same invoice tends to discover this at switchover, when the messages start arriving from an unrecognised number or stop arriving at all in the markets with the strictest rules. If the channel matters, treat it as its own migration with its own timeline: start the replacement registrations first, run both accounts in parallel while the approvals land, and only then move the email. ### Which of these is the safer bet over three years? They are risky in opposite directions, which is more useful to know than a verdict. The broad European suite is the safer bet on continuity — it is an established company with a large customer base and a diversified product line, and it is not going to disappear. Its risk is drift: the plan you are on gets re-cut, the feature you depend on moves up a tier, and the breadth that attracted you means any individual piece is maintained by a small part of a large organisation. The focused product is the safer bet on the thing it does — one shape, no tiers of capability, nothing that can be taken away by a repricing — and the riskier bet on the company, because a young vendor with a narrow product has fewer places to go when growth slows. The mitigations differ accordingly. Against drift, price the tier containing your real requirements and re-check it annually. Against vendor risk, send from your own domain, keep your own copy of the consent record, and make sure the integration is a module somebody could replace in a week rather than a dependency woven through the codebase.