How to calculate monthly email sends

Quick answer: Add the planned recipients of each distinct email delivery, including newsletters, targeted campaigns, the automation steps people actually reach, tests and any resends you choose to make. Then check the busiest day separately. In the worked month below, four newsletters, three targeted sends and a welcome sequence total 54,600 planned deliveries. That is a forecasting number; confirm the provider’s usage rules before treating it as a billable quota total.

Important constraint: Stored contacts are not monthly sends. One person can receive several different messages; each intended delivery adds to the send plan. Meanwhile, a daily cap can block a large single-day campaign even when the month’s total looks affordable. Brevo’s Free plan documentation illustrates this with 300 daily sends that do not roll over: thirty days of unused allocation do not fund a 9,000-recipient campaign on one day.

Start with the campaign calendar, not the contact database size or a plan’s headline allowance. A contact list is an inventory of people or addresses. A send budget is the sum of messages you intend to deliver across dates, segments and automated paths. Brevo’s quota documentation separately describes stored contacts and unique automation entrants, which is a useful reminder that neither is the same as outgoing email volume.

Choose the unit: one message to one recipient

For planning, use one intended email to one eligible recipient as one delivery unit. If 12,000 people receive a newsletter, write 12,000 in the ledger. If 2,000 of those people also receive a separate offer that week, add another 2,000: the overlap is two different messages, not a duplicate in the monthly sum. If an address appears twice within the same intended delivery, deduplicate it so the forecast reflects one desired message to that address.

Brevo describes a prepaid email credit as one email to one contact and says its prepaid credits can cover marketing and transactional email in its plan documentation. That is a concrete vendor example, not a rule for how every provider charges a blocked, failed, bounced, suppressed or retried message. Keep the forecast of intended deliveries separate from the provider’s recorded usage until you have checked its actual accounting.

Use the eligible audience at send time, not every stored address. A 20,000-contact account may contain people excluded by consent, suppression or segment rules; a 12,000-person campaign should be budgeted from the 12,000 eligible recipients on its planned date. Conversely, a small list can generate many sends if it receives frequent campaigns. The row-by-row ledger makes both effects visible.

Build the monthly send ledger

Create one row for each planned campaign or automation step. Record the date or trigger, the eligible recipients, the number of occurrences during the month, and the resulting intended deliveries. Keep one-off tests, resends and operational messages in their own rows rather than hiding them inside a percentage. The example below is hypothetical, so replace its counts with your schedule.

The formula is sum of eligible recipients for every actual delivery event. The newsletter and targeted audiences can overlap; that does not reduce the total because they receive different content. The base month excludes resends, test sends and transactional mail. Add those only when they are part of your operation and the platform’s relevant quota includes them.

Avoid a shortcut such as list size × campaigns unless every list member is eligible for every campaign and every automation message. A row for each send also helps identify a day when two campaigns collide. If the targeted campaign is meant to reach only people who did not receive that day’s newsletter, express that exclusion in its eligible-recipient count. The ledger should reflect the intended audience rule, not a blanket assumption about overlap.

Count automation at the step people reach

Automations are a common source of overstatement and understatement. “200 people enter a three-email welcome flow” gives a maximum of 600 planned messages only if all 200 reach every email step within the same month. If 200 receive step one, 150 reach step two, and 100 reach step three, budget 200 + 150 + 100 = 450 for those steps. If step three happens next month for some people, put those deliveries in next month’s ledger. The entry count, step-level recipient count and monthly send count serve different purposes.

Branches need their own rows. Suppose 80 of the 200 entrants follow a purchaser path and receive a follow-up, while the others receive no further message. That follow-up adds 80, not 200. If a person can move between branches, design the workflow to prevent unintended duplicate messages and forecast the messages that each branch actually sends. Review each trigger, delay and exit condition before multiplying entrants by a maximum sequence length.

Brevo’s quota page also distinguishes unique contacts entering automations from stored contacts. A plan limit on entrants can affect whether the workflow can run even when the send-volume arithmetic appears sufficient. Check both constraints for the chosen provider and plan; do not translate an entrant allowance into an email allowance.

Let the calendar reveal five-send months and peak days

A weekly newsletter does not always mean four send dates in a calendar month. Place the actual dates on the calendar. If the month has five newsletter dates, the newsletter row rises from 48,000 to 12,000 × 5 = 60,000. With the same three targeted sends and 600 welcome messages, the total becomes 66,600. That is 12,000 more than the base month, not a small rounding difference. A simple weekly × 4 shortcut would miss it.

Now examine the busiest day. If a 12,000-recipient newsletter and a 2,000-recipient targeted campaign share one date, the planned demand is 14,000 that day, before automation, test or transactional traffic. A monthly allowance of 54,600 or more does not by itself establish that the account can send 14,000 on that date. Check daily caps, sending-window rules and any operational pacing the provider applies. The Brevo Free plan’s 300-per-day, nonrolling allocation is an especially clear example of why monthly arithmetic cannot replace a daily check.

You may want a growth scenario, but choose it deliberately. If the entire base workload grows by 20% while the mix stays the same, 54,600 × 1.20 = 65,520. This is an alternative scenario, not a universal “safe buffer.” It is also different from the five-newsletter calendar case of 66,600. Do not add both uplifts automatically unless your actual forecast expects both a fifth issue and 20% audience growth. A targeted growth assumption may be more realistic: increase only the newsletter audience, only automation entrants, or only the segment sends, then recalculate the affected rows.

Keep tests, resends and transactional traffic explicit

Add a row for internal previews and tests if the platform counts them against the relevant allowance. Add intentional resends to people who did not open or receive a campaign only if that action is in the plan, and estimate its recipient group separately. A resend is another planned delivery, not a way to retroactively change the first send’s audience. Do not automatically double the campaign row because a retry might occur; determine which retries are platform-managed and how they appear in usage.

Keep transactional email—receipts, password resets and similar operational messages—visible in a separate row. Forecast it from the relevant business events and then ask whether it shares the same quota or credit pool as marketing messages for the selected account. Brevo’s prepaid description covers both marketing and transactional email, but another plan or provider can account for them differently. If the quota treatment is unknown, mark the row unknown rather than quietly treating it as free or included.

Forecasting and usage reports will rarely match perfectly. An address can be suppressed before send time; a delivery can bounce; a provider can accept or reject a message; tests and retries may be counted in specific ways. Providers can count these outcomes differently, so confirm how your account records each one. During the first cycle, capture the platform’s actual usage total and classify the differences: audience change, automation step reach, tests, resends, transactional traffic or provider accounting. Update the next forecast from that reconciliation.

Take a complete worksheet to plan selection

Before comparing plans, keep three numbers beside each other: the expected monthly delivery total, the highest realistic single-day demand, and any independent contact or automation-entry limit. Note the month with the most scheduled dates and a separate plausible growth scenario. Record the assumptions behind each number: eligible audience, send calendar, branch completion, tests, resends and whether operational mail shares the allowance.

That worksheet is enough to ask a provider precise questions: “Can this plan handle 14,000 planned sends on our busiest day?” and “How are suppressed, failed, retried and transactional messages reflected in usage?” After one real month, compare the forecast with the provider’s report and correct the rows that drifted. The email hub covers the next choices once the volume and constraints are clear.