Brevo Pricing 2026: Volume-Based Value, Multichannel Breadth

Brevo (formerly Sendinblue) prices by emails sent, not contacts stored — the inverse of Mailchimp-style geometry and the reason budget-conscious teams with big lists gravitate to it. Verified September 2026: Free covers 300 emails per day with unlimited stored contacts, Starter plans begin around $9/month from 5,000 emails/month, automation-capable tiers from roughly $18/month, and Enterprise is custom-priced (listed around $499/month and up). Source: brevo.com/pricing. Confirm live figures before budgeting — Brevo reprices volume bands periodically.

Who this guide is for

Brevo's geometry rewards one profile and punishes another. Work out which one you are before reading the meters below.

The common thread: Brevo wins when contacts dwarf sends, and loses when sends dwarf contacts. Everything else in this guide follows from that sentence.

Pricing geometry explained

Brevo meters delivered volume rather than stored records: contacts are unlimited and free to hold, while every email counts against a monthly band — starting at 5,000 emails on the entry paid tier.

Two gates sit on top of that meter. The free tier caps you at 300 emails per day, which throttles launch days and one-off blasts regardless of monthly headroom. And automation itself is tier-gated: workflows, A/B testing, send-time optimization, web tracking, and landing pages unlock at the automation tier around $18/month rather than on Starter.

This produces the inverse risk profile of Mailchimp-style tools. A 100,000-contact list mailed twice monthly is cheap here and expensive there; a 5,000-contact list mailed daily is expensive here and cheap there.

The practical planning consequence: export ninety days of send history and map it to Brevo's bands before choosing a plan. List size is the wrong input for this platform's arithmetic.

One useful release valve — pay-as-you-go email credits that never expire. Seasonal spikes can be absorbed with credits instead of a permanent tier jump, which is exactly the flexibility per-contact platforms do not offer.

Model monthly send volume with twenty percent headroom. Unlike per-contact tools, under-buying here shows up as throttled campaigns rather than surprise overage — which is honest, but only if you planned for it.

Plan-tier ladder

1. Free300 emails/day. Validate deliverability, run transactional tests, and prove one campaign. Upgrade the moment daily caps throttle your calendar.
2. Starter $9Volume unlocks from 5,000 emails/month with branded templates and segmentation. Right for newsletters and notifications without complex automation.
3. Automation $18Unlimited workflows, A/B tests, send-time optimization, web tracking, landing pages. This is where Brevo becomes a real lifecycle tool for general use cases.
4. ProfessionalFrom ~150,000 emails/month: AI segmentation, contact scoring, multi-user seats, phone support, deliverability specialist hours.
5. Enterprise $499+Custom volume, dedicated IP, SSO/SAML, multi-account brand management, custom data integrations, named support. Annual terms available with ~10% yearly-billing savings on self-serve tiers.

Worked cost shapes

Brevo's geometry wins whenever contacts dwarf sends. It loses its edge for daily high-frequency programs, where per-email metering compounds — always model monthly send volume, not list size.

Hidden fees & fine print

Brevo's transparency is real — public bands, no quote wall — but the gates around volume and features still catch teams planning from the headline price alone.

• Daily send caps: the free tier's 300 emails per day cannot be worked around with monthly headroom; launch days fail first.
• Automation tier gates: unlimited workflows, A/B testing, send-time optimization, web tracking, and landing pages start around $18/month, not on the $9 Starter.
• Volume band steps: cadence growth pushes you through bands even when the list is unchanged.
• Professional tier entry: AI segmentation, contact scoring, phone support, and specialist hours begin from roughly 150,000 emails per month.
• SMS and WhatsApp credits: multichannel messaging meters separately from email volume.
• Branding and feature ladders: removing Brevo branding and unlocking deeper capabilities are tier properties, not usage properties.
• Annual billing savings: roughly 10% on self-serve tiers applies only when you commit annually — monthly pricing is the higher number.
• Enterprise is custom: dedicated IP, SSO/SAML, multi-account management, and named support sit behind negotiation around the $499 listing.
• Shared-pool deliverability: cheap entry inherits pool-mate risk; dedicated IP strategy is a top-tier conversation.
• Log and support limits: retention and support depth vary by tier — verify both against your compliance needs before choosing.
• Multi-account management: brand-portfolio features sit at Enterprise, so multi-brand teams outgrow self-serve tiers.

Ask which gates you will hit in month one rather than month twelve. Teams routinely buy Starter, discover the automation ceiling within a quarter, and pay a second upgrade fee they could have priced into the first decision.

The pattern here is gentler than per-contact tools: nothing bills silently for records you forgot. Exposure comes from gates you crossed, not meters you misread — which is a solvable planning problem.

Cost scenarios

Read the following three monthly examples as budget shapes, then re-open Brevo's band selector before signing: the vendor changes thresholds periodically. The pricing index supplies the comparable ladders when you test the same list against another provider.

Row two is the decision point: staying on Starter keeps costs minimal but leaves workflows ungated, while the automation tier roughly doubles the entry price and unlocks the lifecycle capabilities most teams came for.

Row three shows why Brevo appears on cost shortlists at all — the same held contacts that punish you elsewhere are free here, and only the sends you actually make are billed.

Always model with ninety days of real send history plus twenty percent headroom. List size tells you almost nothing on this platform, which is both its virtue and its planning trap.

One final note for teams consolidating vendors: because transactional API and SMTP are included, Brevo can absorb receipts and notifications without a second contract — but confirm webhook, bounce, and retention behavior for that traffic before moving it.

Cost-control playbook

Volume-priced platforms reward cadence discipline rather than list hygiene — the levers are different, but they are real.

• Export ninety days of send history and map it to bands with 20% headroom before choosing a tier.
• Track sends per day, not just per month: the 300/day free cap breaks launch calendars first.
• Gate SMS and WhatsApp behind proven flows only; credit meters surprise more people than email bands do.
• Use pay-as-you-go credits for seasonal overflow instead of permanent tier jumps.
• Decide early whether automation gating justifies the jump from the $9 tier to the $18 tier.
• Compare annual against monthly pricing at renewal; the roughly 10% annual saving is worth re-deciding each cycle.
• Watch cadence creep quarterly — newsletters quietly becoming twice-weekly programs change bands.
• Suppress hard bounces and chronic non-openers from sends even though storage is free; reputation still costs.
• Forecast transactional and campaign volume on one sheet, since both spend the same meter.
• Re-map volumes whenever a new product line, locale, or brand launches.
• Track cost per delivered email against last quarter to catch band drift early.
• Revisit the tier only after two stable cycles so you are negotiating against real data.
• Document which features you actually use; unused tier benefits are cost, not value.
• Re-check the free 300/day cap against any new automated send you add — caps bind per day, not per month.

Teams that review volume monthly rarely need the next band up. Teams that review annually discover the jump retroactively, on an invoice that already cleared.

Enterprise fit

Brevo fits cost-conscious multichannel teams: email plus SMS, WhatsApp, chat, and a lightweight CRM under one bill, with transactional API included rather than split into a second product. GDPR-friendly EU data posture, unlimited contact storage, and pay-as-you-go credits make it a pragmatic default for newsletters, notifications, and early automation. The AI surface covers subject lines, copy drafting, send-time optimization, and segment suggestions — practical, not architectural.

It does not fit billing-driven SaaS lifecycle. There are no native subscription-event triggers, no dunning playbooks, and no upgrade attribution; wiring Stripe events through API middleware recreates the fragility Brevo buyers thought they were escaping. Data teams wanting warehouse-native orchestration will outgrow it toward Customer.io, and commerce teams wanting predictive depth will outgrow it toward Klaviyo. Enterprise security (SSO, dedicated IP, custom objects) exists but only at the top tier.

Migration checklist into Brevo

• Model send volume first: export 90 days of send history and map it to Brevo's volume bands with 20% headroom before choosing a tier.
• Migrate transactional endpoints (SMTP/API) before campaigns; verify webhooks, bounce handling, and log retention on day one.
• Authenticate SPF, DKIM, DMARC; warm with engaged segments since Brevo's shared pools punish cold starts.
• Rebuild automations as unlimited workflows; gate SMS and WhatsApp behind ROI-positive flows only — credit meters surprise.
• Import suppressions and consent evidence; use pay-as-you-go credits for seasonal overflow instead of permanent tier jumps.

How Brevo compares by operating model

Brevo's central advantage is simple arithmetic: stored contacts are unlimited, while the bill follows email volume. That geometry suits a seasonal list, a large audience with modest cadence, or a team that wants transactional API and campaign sending under one account. It also makes a ninety-day send-history export more useful than a contact-count snapshot when you are choosing a tier.

The breadth is practical rather than deeply specialized. Email, SMS, WhatsApp, chat, lightweight CRM, transactional API, webhooks, and AI helpers cover a broad generalist brief. Automation tiers add unlimited workflows, A/B tests, send-time optimization, web tracking, landing pages, and branding removal. Teams should still test the exact workflow and channel limits they need because volume and feature gates are separate decisions.

Brevo needs more integration work when a SaaS program is driven by subscription events, product usage, or warehouse state. There are no native subscription-event triggers or dunning playbooks in the verified facts for this page, so those flows depend on API middleware and governance. Data teams seeking warehouse-native orchestration should compare Customer.io; commerce teams seeking predictive depth should compare Klaviyo. The comparison is about operating model, not a generic feature checklist.

Model the plan at real monthly volume with headroom, then add SMS and WhatsApp credits and any enterprise controls. A public band is useful only when the input is honest; the operating model should include quiet months, launch spikes, and the transactional traffic you will move into the account.