Brevo review for a small business

Verdict: Brevo is worth a small business trial when one team needs newsletters, a welcome flow and a modest sales pipeline in the same account. Its documented Free and paid plans cover those jobs, but the practical fit depends on the selected contact-and-send tier, the automation-entry limit and whether your team can complete sender setup and reporting tasks. This review draws on Brevo’s plan documentation and clearly attributed outside reviews; use the evaluation below to decide how it works in your account.

Brevo’s appeal is breadth. A small shop can keep contact records, create campaigns, run marketing automation and use limited built-in sales tools without assembling a separate application for every task. That same breadth creates a question that a feature checklist cannot answer: are the relevant tools included at a capacity and price the business can use? A newsletter with a few hundred recipients and a shop with thousands of stored customers can see the same feature name while reaching different plan limits.

Who should put Brevo on the shortlist?

Consider it if campaigns and a straightforward welcome sequence are central to your customer communication and you also want to track a small number of sales deals. Brevo lists free built-in sales features, including a limited pipeline and deal allowance. That may be enough to evaluate whether the marketing and sales records belong together. It is not a reason to assume the free tools replace an established CRM with more elaborate permissions, reporting or pipeline requirements.

The strongest reason to pause is a mismatched limit. A large stored list does not imply a large daily Free sending allowance. On paid tiers, the selected monthly-send level also sets how many contacts can be stored. A team that needs many people to enter automations, multiple marketing seats, specialized reports or a landing-page program should check the applicable paid plan before migrating. If the primary workload is order receipts and password resets rather than marketing campaigns, assess Brevo’s transactional-email setup and its separate operating requirements, rather than buying a marketing plan on a newsletter assumption.

The plan guide and automation quota guide provide the first three rows; Brevo’s report guide describes report access. A table can narrow a shortlist, but a business still needs to build the one campaign and one flow it would really run.

Campaigns: count storage and timing as well as sends

Brevo Free allows 300 sends per day and up to 100,000 stored contacts. Those are different numbers. A 1,000-person customer list can be stored on Free, but a same-day announcement to all 1,000 does not fit its daily sending allowance. Staggering the announcement may be acceptable for an evergreen note; it may fail for a one-day opening or promotion. The business must decide whether the delayed schedule is useful before calling Free an adequate trial.

Brevo’s paid Starter and Standard plans have monthly-send tiers paired with stored-contact capacities. The current help table lists 5,000 sends with 500 contacts, 10,000 sends with 1,500, and 15,000 sends with 2,500 on those plans; higher send tiers raise the storage ceiling. A team with 2,000 contacts and a light campaign calendar can therefore need a higher send tier solely to hold its list. This is a reason to configure the plan with the actual stored count, not a reason to buy a particular tier from a starting-price banner. Brevo also describes automatic tier upgrades when the first three paid contact caps are reached, with a corresponding cost increase. Leave headroom for foreseeable growth or check that mechanism before purchase.

Suppose a bakery keeps 1,200 contact records and sends four campaigns to 800 consenting customers each month. That is 3,200 planned campaign sends, before welcome messages or tests, while its stored-contact requirement is still 1,200. The 5,000-send tier has enough sends but its 500-contact cap fails. The published 10,000-send/1,500-contact pairing can hold both figures; whether Starter or Standard is warranted depends on workflow rights, reporting and seats. For a detailed capacity worksheet, use the 50,000-email guide if your calendar reaches that scale.

Automation can be the real plan boundary

The new-editor quota limits unique contacts entering active automations to 2,000 on Free and Starter; Standard is unlimited for that measure. The quota does not mean only 2,000 contacts may be stored or that the system can send only 2,000 automated emails. If 150 new subscribers enter a three-email welcome sequence, the sequence uses 150 entrants and plans 450 messages, subject to the actual timing and other sends. Loading an entire existing database into the flow at once could cross the entry limit even when ordinary monthly signups would not.

Before choosing Standard for its larger quota, sketch the behavior you need: which event starts the flow, what happens if a contact already bought, whether a message can be skipped, and what should stop the sequence. Then build that exact small version in the editor and check the current plan’s rights. A business with a few hundred new entrants may find Starter’s documented entrant limit sufficient; another using several flows or a large one-time backfill may need Standard. Neither conclusion follows just from the stored list size.

The attraction of having campaigns and automations in one account is operational: a marketing generalist may prefer fewer exports and fewer tools to coordinate. Whether Brevo’s editor saves that particular team time is account-specific. EmailTooltester’s long-use review values the automation breadth and basic CRM while also describing migration work. Its impressions provide trial questions, not evidence that your existing flow can be transferred unchanged.

Reports: useful numbers need interpretation

Brevo documents campaign views for opens, clicks and delivery-related information in its report guide. That helps a small team inspect whether a campaign was sent and which links drew activity. Some detailed breakdowns are available only from Standard upward. Check the exact view you need before paying for a reporting upgrade.

An open count is especially easy to overread. Brevo says Apple Mail Privacy Protection and bot activity can be included by default in reported opens and clicks. If a weekly report is meant to tell an owner how many humans read an offer, the default count cannot be treated as that number without understanding its filters. Compare a test report’s available fields, use click and site outcomes where appropriate, and keep the measurement limitation next to any performance decision. The presence of advanced reports does not establish better campaign results by itself.

For a two-person team, reporting also raises an access question: can the owner view the necessary report while the marketer builds campaigns, and what does that combination cost? Brevo’s Standard plan and add-ons describe additional seats, while exact checkout choices can change the total. EmailTooltester raises multi-user cost as a drawback in its own review. Verify current permissions and the quote for the actual people involved rather than carrying over its price judgment.

Import, domain setup and sending continuity

Moving a real list into a new platform has two separate acceptance checks. First, Brevo’s contact-import instructions provide a route to load records, but an imported count alone does not confirm consent states, segments and custom fields. Second, sender-domain authentication requires the business to complete DNS-related setup. Brevo notes that a guided authentication flow is rolling out, so exact screen labels may vary. An authenticated domain is an operational prerequisite to verify, not a promise that every message reaches an inbox.

Brevo also documents account or campaign suspensions following its checks, and says a paid subscription may remain active while sending is suspended. This is a possible failure path to plan for, not a frequency estimate. Keep a copy of the consent evidence, know who can respond to an account notice, and avoid scheduling the first important campaign immediately after an untested migration. A backup channel for a time-sensitive customer notice may be useful for any provider.

Outside reviews add perspective but can go stale. TechRadar’s February 2026 review reports occasional import or interface lag as its own experience. Its broad contact-cap description does not match Brevo’s current tier table, so use Brevo’s live help for limits. EmailTooltester likewise describes the work of migration and possible multi-user expense. Neither review can tell you how your particular data and network will behave; the small acceptance pack below can.

A seven-step small-business evaluation

Use a consented sample and a noncritical campaign. Record the plan selected, the person doing each task, whether it passed, and any blocker. This gives the team evidence for its own purchase rather than a general comfort score.

1. Import a sample. Include at least one normal subscriber, a suppressed or unsubscribed record where your process permits it, and the custom fields used in an actual segment. Compare counts and states with the export before enlarging the import.
2. Authenticate the sender domain. Have the person who controls DNS complete Brevo’s current instructions and confirm the account recognizes the domain. Save the changes and their owner for later troubleshooting.
3. Build one representative campaign. Use a normal segment, brand assets, reply address, tracked link and unsubscribe path. Preview it with the colleague who approves production emails.
4. Run a small welcome-flow check. Enroll approved test contacts through the intended trigger. Observe entry, message timing, purchase or exclusion logic and exit. Note whether the chosen plan permits the needed entrants and steps.
5. Inspect the report. Confirm the team can see the needed send, click and export fields, then note how MPP and bot activity affect interpretation. Check whether a desired breakdown is available on the chosen tier.
6. Try the sales pipeline if it matters. Create one sample deal, move it through the real stages, and check whether its user permissions and limits fit the team. Skip this step if Brevo would only handle marketing.
7. Prove an exit path. Export the sample contacts and identify what would need separate reconstruction—flows, templates, suppression rules and reports—if the team left. Keep the original system available until the new account has passed its first meaningful campaign.

Do not promote a test-contact success into a deliverability claim. The valuable result is narrower: the team knows which tasks work, which tier it used, and which setup or data-mapping problem still blocks a launch. A failed suppression or sender check is a reason to stop a migration; a cosmetic editor preference is a choice the team can weigh against price and workflow.

The purchase decision

Brevo suits a small team that can use its campaigns, limited sales tools and automation in one account at a qualifying tier. It may be the wrong consolidation if a specialized sales system is already working, the team needs a feature on a much higher plan, or its required account tasks fail the evaluation. The current plan guide lists Starter from $9 and Standard from $18 per month, excluding tax, but neither starting rate quotes the contacts, sends, seats and extras this business might select. Price the configuration only after the seven-step fit check has identified what it needs.

If the central question is which vendor to choose rather than whether Brevo itself is credible, compare the same workload across products; the Brevo–Kit guide does this for a creator selling digital products. For this small-business review, the practical next move is to run the sample through Brevo and save its current configured quote alongside the pass/fail notes.