Sendrealm Pricing: Usage-Based Email Billing Explained

Sendrealm prices email around actual sending rather than charging for the number of contacts stored. That distinction is useful for teams with large databases or many segments, but “usage-based” does not mean costs manage themselves. You still need to forecast transactional and broadcast traffic, monitor unusual volume, and understand the plan resources your team uses.

Use the live Sendrealm pricing calculator for current rates. Prices and plan allowances can change; this guide explains the model and how to budget it.

The units that drive email cost

Sendrealm separates:

• transactional email, sent for application or user events;
• broadcast email, sent as a campaign to an audience.

Each category has its own free monthly allowance and paid usage rate. Stored contacts do not incur a contact fee, so importing or segmenting a contact does not itself create email usage. Delivery attempts do.

Other plan limits—such as team members or sending domains—are different from metered email volume. Review the complete plan when forecasting, not only the per-email rate.

Why transactional and broadcast volume differ

Transactional volume is usually driven by product behavior:

monthly users
× average triggering events per user
× recipients per event
× retry/duplicate safety factor

Broadcast volume is driven by campaign operations:

reachable recipients per campaign
× campaigns per month
+ test and seed sends

Do not multiply the total number of stored contacts by campaign frequency unless every contact is subscribed, reachable, and targeted. Use audience previews and historical reachable counts for a better estimate.

A forecasting example

Suppose a SaaS product expects:

• 18,000 password, invitation, receipt, and alert emails;
• two broadcasts to 6,000 reachable contacts each;
• 500 internal tests and operational sends;
• a 15% buffer for growth and unexpected retries.

The planning volumes are:

Transactional: (18,000 + relevant tests) × 1.15
Broadcast: (2 × 6,000 + relevant tests) × 1.15

Enter the resulting category totals in the live calculator rather than applying an old rate copied from an article. Keep transactional and broadcast estimates separate because their allowances and pricing differ.

Include the costs that email volume does not show

Provider billing is only one part of operating cost. A realistic comparison also considers:

• engineering time for integration and migration;
• DNS and deliverability operations;
• template and campaign production;
• support investigation time;
• observability and incident response;
• the commercial impact of delayed or missing critical messages.

A lower per-email rate can still be expensive if a fragmented workflow creates manual reconciliation across several tools. Conversely, a unified platform is valuable only if the team uses its operational controls.

Monitor usage by cause

A monthly total tells finance how much was used; it does not tell operators why. Keep an internal view of usage by project and message type so the team can distinguish healthy growth from defects.

Investigate changes such as:

• a new retry loop sending duplicates;
• a dynamic audience becoming unexpectedly broad;
• staging traffic using production credentials;
• a launch or seasonal event increasing legitimate demand;
• a new lifecycle campaign adding recurring volume;
• a compromised key or unauthorized integration.

Compare provider usage with product events and campaign recipient counts. The three sources do not need to be identical, but large unexplained differences deserve attention.

Set operational guardrails

Before production launch:

• define a monthly forecast and a peak-day estimate;
• assign an owner for billing and usage alerts;
• set internal anomaly thresholds by project;
• use scoped keys so a compromised service cannot operate everywhere;
• keep staging separate from production;
• review large campaign audience counts before scheduling;
• make retries bounded and idempotent;
• define who can approve an unusually large send.

An alert should lead to an action. Document when the team pauses a campaign, disables a key, investigates a queue, or contacts Sendrealm support.

Compare pricing models correctly

When evaluating another provider, put costs into the same scenario:

1. Choose one forecast month and one peak month.
2. Use the same transactional and campaign volumes.
3. Account for whether unsubscribed or inactive contacts count toward the competing plan.
4. Include required add-ons, dedicated resources, seats, or domains.
5. Apply published overage rules.
6. Recalculate at the next growth milestone.

Contact-based pricing is not inherently wrong; it can bundle marketing features a team values. Usage-based pricing is not automatically cheaper at every send profile. The advantage of the Sendrealm model is that contact growth and email consumption are separate economic events.

Review billing on a regular cadence

A monthly review can be short:

• actual versus forecast transactional volume;
• actual versus forecast broadcast volume;
• top changes by project or message type;
• audience growth versus reachable campaign volume;
• incidents, duplicates, or retries that created waste;
• forecast for the next product launch or seasonal peak;
• current plan fit using the live pricing page.

Include product, lifecycle, engineering, and finance owners when a change crosses their area. Billing visibility is useful when it produces an operational explanation, not only an invoice approval.

Pricing and billing checklist

• current rates come from the live pricing page;
• transactional and broadcast usage are forecast separately;
• stored contacts are not confused with delivery attempts;
• plan resources beyond email volume are included;
• forecasts cover normal and peak months;
• product events, campaign counts, and billed usage are reconciled;
• anomalies have owners and response procedures;
• provider price is evaluated with engineering and operational cost.

Usage-based billing makes cost follow communication activity. The disciplined approach is to connect that activity back to product events and campaign decisions, then use the live calculator whenever volume or pricing changes.