What is it
Per-email pricing is a billing unit where the number of emails sent in a billing period sets the price or the plan cap, common in email marketing, lifecycle messaging, and cold-outreach tools.
The send is the unit an email vendor actually pays to deliver, which is why it is one of the oldest usage meters in SaaS. What varies is how directly a vendor exposes it. Brevo makes it the headline meter: its Free plan sends 300 emails a day (about 9,000 a month) and every tier, free or paid, carries unlimited contacts. Klaviyo sits at the other end. Its Email product is priced on active profiles, and the send count rides along as an allowance: $20 a month at 500 active profiles buys 5,000 emails.
Most of the companies here fall between those two, so the practical question for a buyer is which meter actually binds: the audience you store or the volume you send. The answer decides whether list growth or campaign frequency moves the bill. For the general mechanics of metering a usage unit like this, see the introduction to usage-based pricing.
How it works
Send volume enters the bill in one of four ways:
| Mechanic | How sends are billed | Example |
|---|---|---|
| Send allowance on a contact-priced plan | Monthly send cap set as a multiple of contacts; overages apply above it | Mailchimp marketing plans: Essentials 10×, Standard 12×, Premium 15× contacts |
| Included volume plus overage | A fixed send volume is included; each extra batch is billed at a posted rate | Customer.io Essentials: 1M emails/month included, then $0.12 per 1,000 |
| Prepaid blocks with volume bands | Sends are bought in fixed blocks whose unit price falls as total volume rises | Mailchimp Transactional (Mandrill): 25,000-email blocks, $20/block at 1–20 blocks down to $10/block at 161+ |
| Pure per-unit | Every send is billed at a list rate, with no plan | Twilio Email: $0.0013 per email |
Unit math: 2,000,000 transactional emails in one month
- Customer.io Essentials: $100 base (5,000 profiles, 1M emails included) + 1,000 × $0.12 for the second million = $220
- Mailchimp Mandrill: 2,000,000 ÷ 25,000 = 80 blocks, which falls in the 41–80 band at $16/block = $1,280, on top of a Standard or Premium marketing plan
- Twilio Email: 2,000,000 × $0.0013 = $2,600
The same workload spans a nearly 12× price range. Two things drive the gap: Customer.io’s overage rate is about a tenth of Twilio’s list rate, and its base fee already covers the first million sends.
Companies using this
Nine companies in the corpus list emails sent as a billing unit. Only a minority make send volume the primary price driver; for most, sends are a cap, an overage line, or a free-tier throttle next to a contact, profile, or active-user meter.
Patterns observed
- The audience meter binds before the send cap. Constant Contact advertises flat-looking $12 / $35 / $80 tiers, but its footnote says the price is “based on number of contacts and email sends. Overage fees may apply.” In practice list size moves the bill first: a Lite buyer who grows from 500 to 1,000 contacts sees roughly a 150% jump even if send volume stays the same. In six of the nine companies, the email meter sits next to a contacts meter.
- Vendors redefine the meter away from sends, not toward it. On February 18, 2025, Klaviyo stopped billing on profiles emailed or texted in the prior 90 days and started billing on every active profile in the account, capping any single email-plan increase at 25%. A send-linked definition gave way to a stored-audience one, so dormant contacts now count even if they are never mailed.
- Free tiers are rationed in sends, and the ration keeps shrinking. Mailchimp’s Free plan is down to 500 sends a month (250 a day) alongside a 250-contact limit, from 2,000 contacts in 2022. In April 2025 Twilio’s SendGrid replaced its perpetual “100 emails/day for free” plan with a 60-day trial, which removed the only forever-free plan in Twilio’s portfolio. The send cap is the lever vendors pull when they want free users to convert sooner.
Counterexamples & variants
Pure send-metering has cliffs of its own. Brevo avoids contact inflation entirely, but its ladder jumps from $18 a month on Standard to $499 on Professional, which starts at 150,000 emails a month and bundles 10 seats. A sender crossing into six-figure monthly volume pays for a seats-and-AI package it may not need, so unlimited contacts do not guarantee a smooth price curve.
Cold outreach uses sends as the tier separator. Smartlead sizes its four plans at 6,000, 90,000, 150,000 and 500,000 emails a month, and its two upper tiers drop the contact limit altogether. The implied cost per send falls from about $0.0065 on the $39 Base plan to under $0.001 on the $379 Prime plan. In cold email, send volume is also what drives deliverability risk, so it is metered and contacts are not.
The send can disappear into a credit pool. Braze does not price email on its own at all. Sends draw down a shared Action Credits pool that also funds SMS, in-product messaging and the BrazeAI Agent Console, and every edition is quote-only, so the buyer never sees a per-email rate. It is the credit-based variant of this unit.
Sends as a trial gate, not a price. Keap lists emails sent as a billing unit, but its $299-a-month plan is priced on contacts (1,500 included) and users. Sends matter only in the free trial, which is hard-capped at 25 emails. There the send cap acts as a demo limit, not a meter.
What this means for buyers vs vendors
For buyers
Work out which meter binds for your list. Divide your planned monthly sends by your contact count. If the ratio is well below the plan’s send multiple, you are paying for audience and a send-metered vendor may be cheaper. If you mail the same list many times a month, a contact-priced plan with a generous allowance usually wins. Ask every vendor three things in writing: what happens when you exceed the send cap (paused sending, automatic overage, or forced upgrade), whether unsubscribed and dormant contacts count toward the tier, and whether transactional email is a separate product with its own minimum plan. Model at least two volumes, today’s and 3× today’s, in the pricing calculator hub before you sign, and set usage alerts on send volume so an overage never shows up first on the invoice.
For vendors
Sends track your delivery cost well, but customers budget by audience. Decide which of the two is the price and which is the guardrail, and put both on the pricing card. A send cap buried in a footnote reads as a trap when it binds. If you meter sends, publish the overage rate next to the included volume and avoid tier gaps where one extra batch of mail forces a jump to a much larger plan. If you price on contacts, a send allowance expressed as a multiple of contacts is easy for buyers to check. Run transactional and marketing email on separate meters only if your product gives buyers a clear reason why. Our guide to choosing the right usage metric covers this trade-off between cost alignment and budget predictability.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Braze | Enterprise customer-engagement platform for cross-channel messaging (email, push, SMS, in-app), with BrazeAI (Sage AI) bundled. | No | 2026-08-15 | ||
| Brevo | All-in-one marketing, sales, conversations, and transactional email/SMS platform (formerly Sendinblue) | Yes | 2026-08-15 | ||
| Constant Contact | Email and digital marketing platform for small businesses, with a separate Lead Gen & CRM product (ex-SharpSpring) and a bundled AI content assistant | No | 2026-08-06 | ||
| Customer.io | Customer engagement platform combining Journeys (behavioral messaging), an AI Agent, and Data Pipelines (CDP) | No | 2026-10-06 | ||
| Keap | All-in-one CRM, sales, and marketing-automation platform for small businesses | No | 2026-07-06 | ||
| Klaviyo | B2C marketing CRM for email, SMS, and push, priced on active profiles plus channel volume, with bundled predictive analytics and Klaviyo AI. | Yes | 2026-09-23 | ||
| Mailchimp | Mailchimp (an Intuit company) is an email marketing and automation platform priced by contact count and plan tier, with AI content and optimization (Intuit Assist) bundled into higher tiers. | Yes | 2026-07-09 | ||
| Smartlead | Cold-email outreach and deliverability infrastructure with unlimited mailboxes, warmup, and a unified master inbox | No | 2026-07-14 | ||
| Twilio | Communications APIs plus Segment and CustomerAI | Yes | 2026-10-05 |
Explore this theme in the knowledge graph
FAQ
What is per-email pricing?
Per-email pricing is a billing unit where the number of emails you send in a billing period sets your price or your plan's cap. Some vendors charge for every send, some sell plans sized by monthly send volume, and many email marketing tools price on contacts but attach a monthly send allowance that triggers overages or an upgrade when you exceed it.
Is it cheaper to pay per email sent or per contact?
It depends on how often you mail your list. A large list you email rarely costs less on a send-metered plan such as Brevo's, which keeps contacts unlimited on every tier. A small list you mail many times a month costs less on a contact-priced plan, where sends up to the allowance are effectively free.
How much does it cost to send one email?
Across this corpus the posted rates run from about $0.00012 to $0.0013 per email. Customer.io charges $0.12 per 1,000 emails beyond the 1 million included on Essentials, Mailchimp's Transactional (Mandrill) add-on ranges from $20 to $10 per 25,000-email block, and Twilio Email lists $0.0013 per email. Plan-based tools like Smartlead only imply a per-send rate, from about $0.0065 on its $39 Base plan to under $0.001 on its $379 Prime plan.
Do free email marketing plans limit how many emails I can send?
Yes, and send caps are usually the tightest free-plan limit. Klaviyo's free plan allows 500 email sends a month, Mailchimp's free plan allows 500 a month (250 a day), and Brevo's allows 300 a day. SendGrid ended its perpetual 100-emails-a-day free plan in April 2025 and replaced it with a 60-day trial.
Why is transactional email priced differently from marketing email?
Transactional email (receipts, password resets, API-triggered notifications) is sent by developers in high, event-driven volumes, so vendors meter it per send or per block. Marketing email is sold to marketers who budget by audience size, so it is usually priced on contacts with a send allowance attached. Mailchimp and Twilio both run the two as separate products with separate meters.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.
- Data Ingestion PricingA billing unit where customers pay per gigabyte of logs, traces, metrics or other telemetry sent into the platform, usually before retention or query costs are added.
- Per-Site PricingA billing unit where each website, store, or licensed facility is billed as a separate unit, so spend scales with the number of sites rather than the number of users.
- Per-Host PricingA billing unit used by infrastructure-monitoring and DevOps platforms where each monitored server, VM, or node is billed per month, usually alongside ingestion-based meters.