A push notification is almost weightless. It slides onto a screen, asks for a tap, then disappears. The invoice behind it can be surprisingly heavy. For a serious consumer business, that little rectangle may depend on identity resolution, real-time event streams, campaign logic, frequency limits, multiple channels, compliance controls and a support team ready when a holiday promotion goes sideways. Braze and Iterable package that machinery for marketers. Neither currently offers the kind of public, self-serve price table that lets a buyer swipe a card and start sending.
That opacity is often treated as a nuisance, but it contains a useful clue. These products are not priced like writing tools or project trackers. They are closer to private utilities for customer attention. What matters is the audience passing through the system, the actions the company wants to take, and the amount of data required to decide which action belongs to whom.
The supplied market context places Braze’s enterprise entry point around $50,000 a year and cites a roughly $32,000 historical average for Iterable. Those are directional procurement benchmarks, not current list prices. Public evidence now points higher for specific configurations. AWS Marketplace lists a twelve-month Braze package at $75,000 and an Iterable package at $115,000. The packages are not directly comparable, but they make the category’s economic shape visible.
The best question in an enterprise pricing call is not “How much?” It is “What makes the meter move?”
Braze sells an active audience and a pool of actions
Braze’s public pricing language is unusually clear about the mechanism, even while withholding a universal dollar figure. A customer chooses a platform edition - Go, Select, Pro or Enterprise - and the price scales with monthly active users. Braze distinguishes an active user from a stored profile, a meaningful detail for an app with a large dormant audience. A brand can retain context on old customers without necessarily treating every profile as an active billing unit.
Then come Action Credits. Braze says those credits can be used across combinations of email, SMS, in-product messaging and certain AI products. The point is commercial flexibility: a marketing team can change the channel mix without renegotiating every experiment. The buyer still needs to model consumption. Flexibility does not remove the meter; it moves several meters into one wallet.
The current AWS listing gives the model a concrete scale. Its $75,000 package covers 100,000 monthly active users, five million emails, two IP addresses, 750,000 US SMS messages and message notifications. AWS says usage above the entitlement is billed in arrears. This is one marketplace configuration, not a floor for every Braze deal. Still, it tells a buyer where to look: the customer definition, the channel allowance and the overage language.
Iterable makes the limits visible inside the product
Iterable arrives at a similar destination through a different vocabulary. Its support documentation describes a Usage and Billing screen organized around messaging, users, custom events, journey events, catalogs and Smart Ingest. Contractual limits appear as progress bars. The bar turns red when usage passes the allowance. Some categories use a high-water mark, recording the highest level reached during a billing period rather than only the final day’s level.
That detail should wake up anyone who has watched a growth campaign go viral. A one-week spike can matter even if the audience settles down later. Iterable advises customers to review usage regularly and notes that overages may apply depending on the agreement. The platform’s billing interface is therefore also a management tool: it tells operators when enthusiasm is becoming a procurement event.
Iterable’s AWS package is $115,000 for twelve months and includes five million users, 75 million emails, two IP addresses, 750,000 US SMS messages, 250 million push messages, setup and support. Again, it is a bundle, not a price list. It also illustrates why the cheaper-looking contract can become the more expensive operating model, or vice versa. One buyer may have millions of stored users but a small active audience. Another may have fewer people and a very chatty product. The denominator decides the bargain.
A procurement benchmark adds another lens. Vendr’s current marketplace page lists an average Iterable contract value of $91,984 across its dataset. That figure has moved well beyond the roughly $32,000 average in the supplied context, a reminder that benchmarks age, product mix changes and enterprise datasets skew toward the buyers represented in them. Use an average to challenge a quote, never to pretend your workload is average.
The feature comparison misses the expensive part
A conventional evaluation asks whether each platform supports email, push, SMS, in-app messaging, segmentation, experiments and journeys. It should. The more revealing comparison follows one campaign from idea to invoice. Which event triggers the journey? Where does identity get resolved? How many profiles are stored? How often do they become active? What happens when a message crosses channels? Does an AI decision consume a separate credit? What data must be retained, and for how long?
Those questions turn a feature matrix into a cost model. They also expose organizational readiness. A team with loose identity rules can create duplicate profiles. A team that sends every campaign to everyone can burn through allowances while teaching customers to ignore it. A team that keeps every event forever may pay to preserve data nobody uses. The platform does not create those habits, but sophisticated infrastructure makes them easier to scale.
Implementation belongs in the same conversation. A messaging platform touches product engineering, data engineering, marketing operations, privacy, deliverability and analytics. The software subscription may be the cleanest line item. SDK changes, event taxonomy, template migration, IP warming and staff training are where schedules stretch. The true competitor is sometimes the competent system already in place, even if it has fewer features.
Build a meter map before asking for a demo
Buyers can make the sales process much more productive by arriving with a one-page forecast. It need not be precise. It needs to make assumptions visible and connect each assumption to a contract term.
- Count active users, stored profiles and anonymous visitors separately.
- Forecast each channel by month, including seasonal peaks.
- List custom events, retention windows and ingest frequency.
- Price dedicated IPs, setup, support and carrier fees.
- Write down overage rates and the moment they activate.
- Model the renewal at base, growth and spike scenarios.
Then ask both vendors to price the same workload. Request the definition of every metered unit in writing. Ask which features are edition-gated, which actions consume pooled credits, whether unused capacity carries forward, and whether a temporary spike changes the following year’s baseline. A discount is less useful if the committed capacity is inflated. A higher unit rate can be economical when the contract allows a smaller, truer commitment.
The first contract buys software. The usage model writes the renewal.
Braze’s active-user model may appeal to a brand with a large archive and a smaller engaged audience. Iterable’s broad usage dashboard may appeal to an operator who wants contract consumption visible across the program. Neither observation chooses a winner. Architecture, channel strategy, governance and negotiation will decide more than the logo on the slide.
The larger lesson is about attention. Customer engagement platforms promise relevance at scale. Their economics encourage buyers to define what relevance is worth before they scale it. If a company cannot name the journeys that change retention, conversion or service cost, the platform will be expensive at almost any price. If it can, an enterprise contract may be easier to defend than a pile of disconnected tools and manual work.
The next notification your phone receives will still look free. Somewhere, though, a marketer chose an audience, a data engineer supplied an event, a platform counted an action and a finance team accepted the meter. That is the product Braze and Iterable are really selling.
Buyer questions, answered
Does Braze publish a self-serve price?
No conventional public rate card is posted. Braze explains that pricing scales with platform edition, monthly active users and Action Credits, then directs buyers to request pricing.
Does Iterable publish list pricing?
Iterable does not currently expose a stable public self-serve price table. Its support documentation instead describes contractual limits and usage tracking.
Are the AWS prices universal starting prices?
No. They are specific public packages with different audience and channel entitlements. They are evidence of real configurations, not universal floors or like-for-like quotes.
What should a buyer model first?
Start with active and stored audiences, monthly volume by channel, event and data usage, seasonal peaks, implementation, support and overage terms.
Which platform is cheaper?
There is no responsible universal answer. The cheaper platform depends on how each contract counts your audience, messages, data and required features over the full term.