Brevo Pricing: Model Sends, Seats, and Add-Ons
Summarize with AI
Brevo pricing is primarily a send-volume decision, not a contact-count decision. The current US pricing page shows Starter at $9 per month and Standard at $18 per month on monthly billing for the default 5,000-email selection. Professional starts much higher because it begins at 150,000 emails per month, while Enterprise is quoted. That structure can be economical for a large database contacted selectively, but the approved budget still needs to include seats, branding removal, credits and any dedicated-IP requirement.
Read the published Brevo pricing correctly
The Brevo pricing page presents monthly and yearly billing, a currency control and a monthly-email-volume selector. The US-dollar figures below were checked on September 20, 2026 with monthly billing selected.
| Plan | Published monthly entry point | Starting volume or status | Decision-relevant inclusion |
|---|---|---|---|
| Free | $0 | Up to 300 emails per day after sending approval | Campaign and transactional access with a daily ceiling |
| Starter | $9/month | 5,000 emails/month | Email and transactional messages, email support |
| Standard | $18/month | 5,000 emails/month | Automation, A/B testing, advanced reporting and web tracking |
| Professional | $499/month | 150,000 emails/month | 10 seats, phone support and 3 deliverability-specialist hours per year |
| Enterprise | Custom | 1 million or more contacts | Dedicated IP, multi-account controls, SSO and tailored onboarding |
Brevo displays yearly equivalents of $8.08 for Starter, $16.17 for Standard and $449.08 for Professional, each marked as 10% below monthly billing. Those are monthly equivalents within an annual commitment, not independently cancellable monthly prices.
Our view: Brevo's low entry point is useful only when the selected volume represents the real workload. Approving the default 5,000-email card for a program that expects 40,000 sends answers the wrong procurement question.
Build one combined send forecast
Brevo says all plans can use transactional email features, including REST APIs, SMTP and outbound webhooks. It also labels the plan selector as monthly email volume for campaigns and transactional messages. In other words, a password-reset stream and a newsletter can draw from the same selected allowance.
Start with a workload table rather than a plan name:
| Traffic source | Normal month | Peak month | Timing risk |
|---|---|---|---|
| Marketing campaigns | Forecast sends | Forecast sends | Launches and promotions |
| Transactional messages | Forecast sends | Forecast sends | Product usage spikes |
| Automations | Forecast sends | Forecast sends | New workflow enrolment |
| Testing and internal copies | Forecast sends | Forecast sends | Template and release cycles |
The peak column is the purchasing input. A normal-month estimate can hide a launch that doubles transactional traffic while a campaign is already scheduled. The vendor's allowance is measured in emails sent, so each recurring workflow belongs in the model even if nobody thinks of it as a campaign.
Separate subscription volume from email credits
Brevo also offers pay-as-you-go email credits. Its pricing FAQ says those credits do not expire and that one email sent consumes one credit. The page describes credits as an option for organisations that send infrequently, and states that phone support is not included with that route.
That makes credits a separate operating choice rather than a universal overage mechanism. A seasonal sender may prefer credits because unused inventory remains available. A steady sender may prefer a monthly plan because recurring volume is easier to forecast and support access may matter. Ask Brevo to confirm how credits interact with the chosen subscription before relying on them for a peak, because the public page does not establish every account-level billing edge case.
Do not enter an unknown credit requirement as zero. Put the expected quantity and the currently displayed credit price in the approval sheet, then preserve a screenshot or dated quote with the purchase record.
Add sales seats and branding as separate lines
The default Starter configuration displays optional removal of Brevo branding at $12 per month on monthly billing. The same page displays Sales Free at $0 with one seat and Sales Essentials at $31 per month with one seat in the plan customiser. These extras are not part of the email-volume allowance.
This matters when Brevo is being evaluated as both an email platform and a lightweight sales workspace. The Brevo sales platform page lists custom pipelines, calls, meetings, automation, a shared inbox and sales reports. Those capabilities may reduce another software line, but only if the team will actually use them and the required seats are priced.
Model the purchase as:
monthly operating cost = email plan + sales seats + branding removal + credits + other quoted add-ons
Keep taxes, implementation work and any negotiated support outside that formula until Brevo supplies them. Unknown is more defensible than an assumed zero.
Decide whether a dedicated IP is really required
The current pricing comparison lists a dedicated IP in Enterprise. It does not show one as included with Starter, Standard or Professional. If an isolated sending reputation is a requirement, obtain written confirmation of availability, eligibility and price for the exact plan under consideration.
A dedicated IP also creates a ramp obligation. Amazon's dedicated IP warm-up documentation explains that mailbox providers consider the sending IP's reputation and that new addresses must build a positive history gradually. The budget therefore needs an operating line for warm-up and monitoring, not only a vendor line for the IP itself.
Price support against the incident you may face
Starter lists email support, while Professional lists phone support and three hours per year with a deliverability specialist. The difference has little value during a clean setup and much more value when a time-sensitive transactional stream is throttled or authentication fails after a DNS change.
Write a short incident scenario before choosing the tier. Name the message stream, the business consequence of delay, the acceptable response time and the person responsible for escalation. Then ask whether the listed support channel can meet that requirement. This is a buyer test, not a claim that a particular tier will resolve incidents faster than another.
Brevo's transactional email page documents SMTP relay, API access, real-time webhooks, inbound parsing and authentication support. It also makes performance claims about delivery. Treat those figures as vendor claims unless your own controlled traffic confirms them.
Record commitment, renewal and exit
Brevo says monthly subscriptions run for 30 days and are charged at the beginning of each period. It also says buyers choose monthly or yearly commitment and can cancel from the account. Before approval, record the billing cadence, renewal date, selected email band, add-ons and downgrade procedure rather than relying on the card's monthly equivalent.
Run an exit check before committing. Confirm how contacts, templates, transactional logs, suppression records and webhook history can be exported. The pricing FAQ says transactional access includes unlimited log retention, but the format and effort required to retrieve useful evidence still belong in the evaluation.
Approve the workload, not the smallest card
Brevo pricing can fit a large contact database with selective sending because the main plan choice follows email volume. The trade-off is that mixed campaign and transactional traffic must be forecast together, while seats, branding, credits, support and a possible dedicated IP need separate decisions. Approve the peak-month workload and preserve every unknown as a question for the vendor.
LeadHaste can turn your send forecast, seat count, support requirement and reputation plan into a quote-ready operating model. Book your free ICP and campaign-fit discovery call →
Frequently Asked Questions
A modern outbound stack includes: data enrichment (Apollo, Clay, ZoomInfo), email infrastructure (Google Workspace, custom domains), sending tools (Smartlead, Instantly), warm-up services (Warmbox), LinkedIn automation (Expandi, Dripify), CRM integration (HubSpot, Salesforce), and analytics platforms. Most agencies use 15–30 tools orchestrated together.
Building your own stack costs $3K–5K/month in software alone, plus a dedicated person to manage it. With a managed service, you get all the tooling plus the expertise to orchestrate it, often at lower total cost. The key question: can you afford to spend 6–8 weeks setting up instead of generating pipeline?
There's no single 'best' tool. It depends on your volume, budget, and integration needs. Smartlead and Instantly are popular for high-volume sending. Apollo doubles as a data and sequencing platform. The real advantage comes from how tools are orchestrated together, not from any single tool choice.
Look for three things: (1) Do you own the infrastructure they build? (2) Are the engagement terms clear, including what happens after the initial build-and-learn period? (3) Can you see transparent metrics and real case studies with specific numbers? LeadHaste starts with a three-month engagement, then moves month-to-month. Avoid vague reporting and providers that own your domains.
Data enrichment is the process of taking basic company or contact data and adding layers of detail: job titles, direct emails, phone numbers, technographics, intent signals, company size, funding stage, and more. Enrichment tools like Apollo, Clay, and ZoomInfo pull from multiple data sources to build a complete prospect profile before outreach begins.
Jacob Martinez
GTM Engineer, LeadHaste
Builds the machinery behind client campaigns: scraping, enrichment, lead scoring and the automations that keep a list clean before anyone gets emailed.
