Iterable Plans: Seats, Channels, and Qualifying Tiers

Choose your Iterable plan by mapping must-haves to seats, channels, and qualifying features — not homepage “from” tiles — then confirm on the pricing page.

By Lee M.Updated Aug 17, 20266 min readFact-checked

Quick answer

Choose a Iterable package by listing day-one must-haves, mapping them to contacts and send limits on researched tiers, and picking the cheapest package that clears every gate — then confirm list price on the pricing page. Homepage “from” tiles are not a bill of materials.

List day-one must-haves
Map contacts and send limits
Highest gate sets the tier
Soft-check usage limits
Confirm on pricing page
Defer unused packs

Iterable plans takeaways

Packaging is often usage-shaped — Researched plans: Growth, Enterprise, Enterprise Plus. Confirm credit and seat limits in writing.
Must-haves set the tier — Our research does not flag plan-gated capabilities for Iterable, but confirm your must-haves — including contact tiers and send limits — against the packaging you actually intend to buy.
No invented totals — Never invent list prices here — confirm seats, contacts/channels, and quote terms on /pricing/iterable/.
Seat discipline still matters — Count who prospects or dials weekly — not the whole org chart — before you compare Iterable packages.

Iterable plan anatomy

Iterable must vs nice

Must-have

Campaigns + marketing ↔ CRM sync
Campaigns or automations

Nice-to-have

Extra optional add-ons
AI assistance

Iterable checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1List day-one must-havesData, outreach, sync that must ship without unused enterprise.
2Map contacts and send limitsUse researched plan names — not marketing tiles.
3Confirm on pricing pageList price and contact-tier upgrades live there — not in this guide.

1. List day-one must-haves before you open pricing tiles

Iterable plans diagram 1. — Must-haves decide the Iterable floor — not the homepage starting tile.

Write five day-one jobs for the marketing team.
Mark which require seats vs contacts/channels vs add-on packs.
Circle the highest gated must-have — that sets the floor tier.
Our research does not flag plan-gated capabilities for Iterable, but confirm your must-haves — including contact tiers and send limits — against the packaging you actually intend to buy. Worked example: a 6-person growth marketing team needs campaigns, marketing ↔ CRM sync, and automations on day one in Iterable. Extra segmentation and AI are nice later, so they refuse to let those upsells set the package.

2. Count weekly users and expected credit burn

Iterable plans diagram 2. — Seat and credit discipline beats vanity headcount for Iterable.

Count who builds campaigns, segments, or automations weekly — not headcount.
Estimate list builds and campaigns per week (orders of magnitude, not fake precision).
Check researched capacity notes. Confirm contact/send caps for Iterable on the pricing page.
Never invent list prices here — confirm seats, contacts/channels, and quote terms on /pricing/iterable/. Worked example: a 6-person growth marketing team counts 6 daily users and 2 managers, defers view-only execs, and refuses any package that cannot explain contact-tier renewals in writing.

3. When packaging is opaque, demand written gates

Iterable plans diagram 3. — Refuse to compare Iterable on a homepage tile alone when contacts/channels matter.

Our snapshot lists researched plans (Growth, Enterprise, Enterprise Plus), but still confirm live terms. 1. Named SKUs / editions on the quote.

Seat definition (full vs light) and contact/send definition.
What happens when contacts/channels exhaust mid-month.
Exit / export rights for lists you built. Worked example: a 6-person growth marketing team delays shortlisting Iterable until send/contact exhaustion behavior and export rights appear in writing.

4. Defer unused packs; confirm the live price last

Iterable plans diagram 4. — Confirm Iterable on the pricing page — this guide never invents dollars.

Buy contacts/sends required for the day-one loop.
Defer AI packs, extra channels, and unused add-ons until day 30+ evidence.
Annualize only after you have written terms — never invent monthly×12 from a marketing tile.
Final check: /pricing/iterable/ Worked example: a 6-person growth marketing team scopes the first Iterable invoice to seats + core contact tiers, parks the AI add-on, and only revisits packs after two Friday reviews.

5. Map must-haves to plan names in writing

Map must-have workflows to the Iterable plan that unlocks them — demos often run above the tier you can afford.

Compare Growth, Enterprise, and Enterprise Plus on the same headcount assumption.

Worked example: Enterprise B2C brands comparing Braze for engagement screenshots the plan shown in demo and matches it to /pricing/iterable/.

6. Model seats, usage, and add-ons together

Custom quote / contact sales only (typically MAU + messaging). No public list-price floor. Confirm live. Add usage units and add-on SKUs to the same sheet before comparing vendors.

7. Get a written quote on the qualifying configuration

Ask Iterable for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.

Worked example: Enterprise B2C brands comparing Braze for engagement files quotes in the same folder with identical date and headcount headers.

8. Map must-haves to plan names in writing