What is it
Per-mailbox pricing is a billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
A mailbox here is not a user seat — it is a sending identity: a configured, warmed-up email account that routes outbound messages to prospects. The distinction matters because deliverability, not compute or storage, is the primary constraint in outbound email. A single salesperson may run three to six mailboxes in parallel to spread send volume and protect domain reputation, so platforms that acknowledge this reality bundle mailbox counts alongside contacts and seats as a first-class capacity dimension.
The three corpus vendors split on how visibly they price it. AiSDR and Juicebox bundle a mailbox ceiling into each tier that scales with the plan’s contacts and seats; Smartlead takes the opposite approach, refusing to charge per connected mailbox at all — a deliberate move to remove the per-mailbox anxiety that drives churn in the cold-email category. Choosing a mailbox as a value metric is a specific bet about what customers will pay for; the trade-offs are covered in choosing the right usage metric.
How it works
In platforms that treat mailboxes as a billing dimension, the mailbox count is usually a hard capacity ceiling bundled into each plan tier rather than a per-unit overage meter. The table below shows how the three companies in the corpus express mailbox capacity across their plans.
| Company | Plan | Mailbox allotment | Relationship to other meters |
|---|---|---|---|
| AiSDR | Solo ($250/mo) | 3 mailboxes | Paired with 200 AI-researched contacts/mo, 1 domain |
| AiSDR | Explore ($900/mo) | 6 mailboxes | Paired with 800 contacts/mo, 2 domains, 5 LinkedIn accounts |
| AiSDR | Scale ($2,500/mo) | 18 mailboxes | Paired with 2,500 contacts/mo, 6 domains, 20 LinkedIn accounts |
| Juicebox | Starter ($139/seat/mo) | 1 mailbox | Paired with 250 contact + 250 export credits/mo |
| Juicebox | Growth ($199/seat/mo) | 3 mailboxes/seat | Paired with 1,000 contact + 1,000 export credits/seat/mo |
| Juicebox | Business (custom) | 6 mailboxes/seat | Paired with unlimited contact credits |
| Smartlead | Unlimited Smart ($144/mo) | Not metered (add-on) | Gated on 150,000 email sends/mo instead |
| Smartlead | Unlimited Prime ($315/mo) | Not metered (add-on) | Gated on 5,694,000 email sends/mo instead |
The practical unit math in a mailbox-constrained model looks like this:
Capacity ceiling: maximum sustainable send volume ≈ mailboxes × daily send limit per mailbox. A warmed mailbox safely sends about 30–50 emails per day. AiSDR’s Scale plan with 18 mailboxes can therefore sustain roughly 540–900 sends per day before deliverability degrades — a ceiling that maps directly to the 2,500 contacts/month the tier promises.
Mailboxes appear as a billing dimension, rather than being unlimited like storage, because each one is a real setup investment — and AiSDR leans on exactly that, defending the quarterly commitment on its Explore and Scale plans by citing the ~30-day warm-up window a new mailbox needs before it can safely carry volume. For how bundled-allowance billing units like this fit into the broader model landscape, see the introduction to usage-based pricing.
Companies using this
Three companies in the corpus include mailboxes as a billing dimension: AiSDR (AI SDR for outbound email and LinkedIn), Juicebox (AI recruiting platform with built-in outreach), and Smartlead (cold-email infrastructure for agencies). All three operate in outbound sales and sales infrastructure — the category where mailbox capacity is a meaningful constraint on the product’s core function.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| AiSDR | Autonomous AI SDR for outbound email and LinkedIn outreach | No | 2026-06-21 | ||
| Artisan | Ava — an autonomous AI BDR/SDR that finds leads, enriches data, and runs outbound campaigns | No | 2026-07-14 | ||
| Juicebox | AI recruiting search platform (PeopleGPT) with natural-language candidate sourcing, outreach, and autonomous agents | Yes | 2026-07-21 | ||
| Smartlead | Cold-email outreach and deliverability infrastructure with unlimited mailboxes, warmup, and a unified master inbox | No | 2026-07-14 |
Explore this theme in the knowledge graph
FAQ
What is per-mailbox pricing?
Per-mailbox pricing is a billing unit used by AI outbound sales and email automation platforms where each connected email account, or sending mailbox, is counted as a capacity dimension in the plan. The mailbox represents sending capacity, warm-up investment, and deliverability risk, which is why vendors meter it separately from the seat or contact count.
Which companies price on mailboxes?
In this corpus, AiSDR, Juicebox, and Smartlead all treat mailboxes as a billing dimension. AiSDR bundles 3 mailboxes on its $250/mo Solo plan up to 18 on its $2,500/mo Scale plan; Juicebox bundles 1 mailbox per seat on Starter ($139/seat/mo), 3 per seat on Growth ($199/seat/mo), and 6 per seat on Business; Smartlead sells mailboxes as add-on infrastructure rather than metering them in its core tiers.
Do all outbound email tools charge per mailbox?
No. Smartlead explicitly does not charge per connected mailbox on its core plans — its tiers are gated by contacts stored, emails sent per month, and verified-prospect emails instead. AiSDR and Juicebox bundle mailbox counts as a per-tier capacity ceiling that scales alongside seats and contacts rather than billing each mailbox as an independent line item.
Why do vendors meter mailboxes at all?
Each mailbox is a real investment: a domain, DNS records (SPF, DKIM, DMARC), and a roughly 30-day warm-up sequence before it can safely carry volume. Because deliverability degrades if a single mailbox sends too much, a warmed mailbox only sustains around 30–50 emails a day, so the mailbox count acts as a hard ceiling on sustainable outbound throughput.
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.
- 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.