Vendor guide · Beginner friendly · verified pricing
Mailchimp Pricing Guide
The familiar front door to email — gentle to start, with a contact-tier model to outgrow deliberately.
Mailchimp onboards first-time senders better than anyone, but subscription automation stretches it thin. Verify bands on the official Mailchimp pricing page.
Who this guide is for
This guide is for founders, solo marketers, and small product teams who know the Mailchimp name already and want three specific answers: what it costs at your current list size, what the automation builder will genuinely support, and the moment when the contact-tier model starts taxing growth instead of funding it. If you are sending a monthly newsletter to a few hundred people, several of the gotchas below will not bite yet — read them anyway, because they compound quietly while the list is small.
It is equally useful if you are already a customer staring at a bill that grew faster than the list. The tier table and counting rules below usually explain the gap, and the migration timeline gives you a calm exit path if the explanation is not one you want to keep paying for.
We assume you are evaluating Mailchimp for lifecycle work — welcome series, trial nurture, conversion nudges, retention digests, win-backs — rather than for occasional broadcasts alone. The verdict changes with the job. Broadcasts and beginner journeys are a real strength; subscription billing workflows are the honest weak spot, and that is where this page spends most of its time.
If you are comparing several vendors in one sitting, read the pricing-tier section of each guide against the same twelve-month list projection. Vendors that look similar at 250 contacts can diverge sharply by 5,000 — and the divergence comes from the billing axis, not the feature checklist.
Where Mailchimp earns its place
Guided setup, preset journey templates, and the template library get a non-technical founder from zero to a published welcome series in an afternoon — with freelancer support available everywhere. For audiences, newsletters, and simple announcements rather than lifecycle orchestration, it remains a fine choice, and our 15-tool comparison says so plainly.
Under the friendliness sits a mature sending infrastructure: inbox placement tooling, domain authentication checklists, and audience hygiene prompts that prevent the classic first-year disasters. Teams that outgrow Mailchimp often say the same thing in retrospectives — the early months were smooth precisely because the product refused to confront them with branching logic they were not ready to operate.
Guided journey templates
Welcome, re-engagement, and purchase-oriented presets publish in an afternoon with copy already structured. You edit claims and timing rather than assembling a flow from blank nodes.
Audience and segment basics
Tags, groups, and saved segments cover the segmentation most small teams need: engaged versus cold, content interest, signup source. The vocabulary is learnable without a schema design session.
Beginner deliverability guardrails
Authentication prompts, list hygiene warnings, and sending recommendations catch the mistakes that used to torch a new domain's reputation before anyone understood what a complaint rate was.
Approval-friendly collaboration
Draft-and-review workflows and reusable content blocks let a founder write, a contractor design, and a stakeholder approve without a shared Figma file — useful when nobody owns email full time yet.
Knowing when you have outgrown it
Branching stays shallow next to automation-first tools, billing triggers need connectors, and per-contact pricing — inflated by the unsubscribed-counts and duplicate gotchas above — punishes list growth. SaaS teams typically migrate once trial nurture and dunning become revenue-critical; plan the exit early and warm the new infrastructure properly. Compare growth-friendly axes in our verified pricing snapshot.
The trigger to watch is not list size, it is event granularity. The day a product manager asks whether the nurture flow can branch differently for a first-time soft card decline versus a serially failing subscriber, or wait on trial days remaining rather than calendar delays, Mailchimp has hit its ceiling for your team — regardless of how comfortable the bill still looks.
There is no shame in the timing. Mailchimp is often the correct first platform precisely because it delays these questions until you have answers worth automating. The mistake is letting the migration decision make itself through a renewal you never modeled.
Two counting rules that inflate real bills: unsubscribed contacts still count toward your contact limit until you delete them, and the same person in two audiences bills twice. Both are invisible in a dashboard that shows "contacts" as a single friendly number.
- Audit the audience model — count contacts per audience, flag duplicates, and separate truly mailable people from parked records.
- Export with consent intact — preserve signup source and date fields so the new platform can honor the permissions you originally collected.
- Warm the new sending path — ramp volume over days, not hours, and keep the Mailchimp account active during the overlap.
- Dual-run critical flows — welcome and trial nurture send from both systems briefly so a mapping mistake surfaces before it costs a cohort.
- Cut over and decommission — pause Mailchimp automations first, keep broadcasts for one cycle, then close the loop on billing.
Pricing tiers and the billing axis
| Plan | Entry price | Send allowance | Reality check |
|---|---|---|---|
| Free | $0 — up to 250 contacts | 500 emails per month | Enough to prove one welcome series; too small to run lifecycle for a growing product |
| Essentials | From $13 per month, scaling by contact band | 10x your contact limit | Entry paid tier; the send ceiling moves only when your band moves |
| Standard | From $20 per month, scaling by contact band | 12x your contact limit | Deeper journey and segmentation options; still metered on stored contacts |
| Premium | From $350 per month, scaling by contact band | 15x your contact limit | Advanced reporting and hands-on support; the jump from Standard is the steepest on the page |
The billing axis is the story. Mailchimp sells you a contact band, then derives your monthly send ceiling as a multiple of that band — 10x on Essentials, 12x on Standard, 15x on Premium. You are therefore charged for people you can mail, including people who have stopped mailing you back, and your send headroom is a side effect of storage rather than a choice you make from your actual cadence.
For a SaaS funnel this axis punishes exactly the motion you want. Every free-trial signup and every dormant account you are nurturing back raises the bill before any of them convert. Unsubscribed contacts keep counting until deleted, and duplicates across audiences count twice, so the number on the invoice drifts above the number of humans you can actually reach. Teams that model twelve months of list growth against band steps — rather than against today's bill — are the ones who migrate on their own schedule instead of after a sticker shock.
The multipliers cut the other way for heavy senders: a team running weekly digests plus multi-step nurture can brush the Essentials 10x ceiling while the contact count still looks modest. Run your planned cadence times list size against each multiplier before choosing a tier, and re-check the official pricing page before every annual commit, since band breakpoints move.
A useful sanity check: divide your planned monthly sends by your expected list size. If the result is above 10, Essentials is the wrong tier even before you account for growth; if it is above 12, Standard does not save you either. The axis rewards low-frequency, high-storage programs and quietly penalizes the opposite shape.
Where it fits in the five-stage lifecycle
Read left to right, Mailchimp covers the first two stages well and the last one adequately. Welcome flows are the product's comfort zone: signup source, delay, a short sequence, one branch on engagement. Nurture stretches further with tags and segments, but trial-day countdowns, seat-count changes, and plan-state branches quickly become workaround logic spread across multiple automations.
Convert and retain expose the object model. Mailchimp understands purchases when a store catalog is connected; it does not understand subscription lifecycle — trial days remaining, invoice status, failed payments — unless a connector relays those events, and every hop adds latency and a new failure mode exactly where recovery emails must not fail. Win-back is achievable with re-engagement campaigns, though the contact-counting rules mean the cleanup you perform is also cost relief.
If your five-stage map is mostly broadcasts with one welcome track, Mailchimp's coverage is genuinely enough. If stages three and four are tied to billing state, price the connector maintenance alongside the contact band before you commit — or compare against a platform where those events arrive natively.
One lifecycle decision Mailchimp forces early is sunset policy: because cold contacts keep counting, deciding when to delete versus suppress is a budget conversation as much as a deliverability one. Teams that skip that policy discover it at renewal, when the invoice reflects two years of disengaged records.
Automation depth: what you can and cannot build
Honest assessment: Mailchimp's journey builder handles classic marketing automation well and subscription-lifecycle automation poorly. The distinction is not about the number of nodes — it is about what the system knows when a trigger fires.
Comfortable territory
Multi-step welcome series, time delays, tag and segment entry criteria, engagement-based branching, re-engagement sequences, broadcast campaigns with saved segments, and purchase-triggered flows for connected stores.
Possible with connectors
Trial-started and trial-expiring alerts, billing-state branches, and dunning-adjacent messages — all relayed through middleware such as Zapier or a custom webhook, which you now own operationally.
Out of reach natively
Branches that distinguish a first soft decline from a serial failing card, plan-change messaging tied to real subscription objects, seat-expansion triggers, and revenue attribution that closes the loop back to a specific flow.
Shallow branching is the practical ceiling. You can split on a handful of conditions, but deep decision trees — usage thresholds crossed, features adopted, seats added, invoice retried — either collapse into tag spaghetti or leak into external tooling. Every connector you add becomes a component with its own auth, rate limits, and silent-failure modes; the failed-payment moment is the worst possible time to discover one has stopped running.
- No native subscription, invoice, or plan objects — billing context must be translated into tags.
- Branching depth is limited; long conditional trees are better served by automation-first platforms.
- The send multiplier caps monthly volume as a function of stored contacts, not of what you planned to send.
- Unsubscribed and duplicate contacts inflate the contact basis the whole model prices from.
- Advanced reporting and the deepest support sit on Premium at $350 entry, far above the Standard tier.
Practical rule: if a flow needs to read subscription state at branch time — plan type, days remaining, payment status — Mailchimp needs a connector to translate that state into tags first. Budget the connector as part of the automation, not as an afterthought.
Where Mailchimp fits for SaaS
Mailchimp optimizes for the first campaign: friendly setup, template variety, and a guided path to a published welcome series. It is familiar and well-supported for newsletters and simple journeys on a small list; teams with complex trial nurture should budget connector work that translates product state into tags.
Neither tool is a downgrade from the other in absolute terms — they are optimized for different halves of the same job. Pick the half you are actually doing this quarter, and keep the other half on the roadmap where a migration can still be a decision rather than a fire drill.
Common mistakes when adopting Mailchimp
- Treating unsubscribed contacts as free. They count toward your limit until you delete them, so a list that "shrank" after a re-engagement purge can still carry the old bill if nobody removed anyone.
- Running multiple audiences for languages or products. The same human in two audiences is two contacts on the invoice — consolidate before scaling, not after the renewal surprise.
- Buying Premium for automation depth. Premium raises support, reporting, and the send multiplier; it does not add the billing-object model that dunning and plan-change flows require.
- Modeling sends against contact count instead of the multiplier. Essentials allows 10x contacts per month; weekly digests plus a five-email nurture consume that ceiling faster than most teams expect.
- Dumping full import history onto the Free tier's 500 monthly sends. Your welcome window for that cohort closes before the queue drains — segment the first ramp deliberately.
- Gluing dunning together with Zapier and discovering the failure modes during a failed-payment spike. Test connector latency with a real test subscription while volume is still low.
- Waiting until trial nurture is already revenue-critical to plan an exit. Warm the replacement infrastructure while Mailchimp is still comfortably adequate.
Mailchimp pricing FAQ
Do unsubscribed contacts count toward my Mailchimp plan?
Yes. Unsubscribed contacts remain in the audience and continue to count against the contact limit that determines your band. They stop receiving mail, but they do not stop being billed — deleting them is the only way to reclaim the capacity. Audit for them at every renewal; they accumulate fastest after re-engagement campaigns.
Is the free plan enough to launch a SaaS welcome series?
Free covers 250 contacts and 500 sends per month, which is enough to publish a welcome track and measure open and click behavior on a small cohort. It is not enough to run ongoing lifecycle for a product with active trial signups, because every new signup consumes both the contact seat and a meaningful share of the 500-send allowance. Treat free as validation, then step up before launch campaigns start queueing.
Can Mailchimp handle failed-payment dunning natively?
Not natively. Mailchimp has no subscription, invoice, or plan objects, so a failed payment must arrive as an event from your billing system through a connector or custom integration, usually encoded as tags and custom fields. Branches can then act on those tags, but you own the relay's reliability. Teams for whom dunning is a revenue line item generally prefer platforms with native Stripe, Paddle, or Lemon Squeezy triggers.
What does the 10x, 12x, 15x send multiplier actually mean?
Your monthly email allowance is a multiple of your contact limit: 10x on Essentials, 12x on Standard, 15x on Premium. A 2,500-contact Essentials account can send 25,000 emails per month. The ceiling moves only when your contact band moves, so cadence planning must be done against the multiplier — not against what you assume a "plan" should include. Exceeding it means upgrading bands or pausing sends.
Essentials or Standard — which tier makes sense?
Essentials from $13 is the entry paid tier with a 10x send multiple; Standard from $20 raises that to 12x and unlocks deeper journey and segmentation options. If your nurture design needs richer branching and your cadence brushes the 10x cap, Standard's jump is small relative to Premium at $350 entry. All three scale by contact band, so re-run the math whenever your list crosses a breakpoint on the official pricing page.
When should a SaaS team migrate off Mailchimp?
When trial nurture and dunning become revenue-critical and you find yourself maintaining connectors just to simulate billing events. The migration itself is manageable if you export consent data intact, warm the new sending path over days, and dual-run the critical flows for one cycle. Migrating on a calm schedule is far cheaper than migrating after a botched dunning cohort.