Klaviyo for Nonprofits: No Nonprofit Pricing, and a Model Built Around Orders

Klaviyo publishes no nonprofit pricing. We looked for it: there is no discount programme on the pricing page, none in the help centre's billing documentation, and no nonprofit page among the industry pages the vendor does publish, which cover retail, restaurants and wellness.

That absence is the most important fact on this page, because the billing model it leaves in place is the one least suited to how nonprofits actually hold a list.

Why the active-profile model is harsh here

A profile bills when it can still receive at least one kind of marketing. Not when it opens, not when it gives. When it is reachable.

Nonprofit lists are large, old and rarely mailed. A donor who gave once in 2019, never unsubscribed and receives two appeals a year is a fully billable profile twelve months a year. A commercial list of the same size is mailed weekly and earns its keep; a donor list of the same size is mailed eight times and costs the same.

That is the structural mismatch. No configuration removes it. The platform charges for reach, and the nonprofit case is one where reach is held for a long time and used rarely.

The published lever is suppression or deletion, timed before the billing cycle closes ^[5]. For an organisation whose stewardship model says never delete a donor, that lever is in tension with the mission.

## What the free tier gives you, which is more than it looks

Start here, because for a small organisation it may be the whole answer.

The free plan carries 250 active profiles, 500 email sends a month, five dollars of mobile messaging and five dollars of Composer usage, renewing monthly ^[2]. It is a real tier rather than a trial, with no expiry.

It is also the only part of the product where the bill cannot move. Exceeding the limit stops sending rather than charging: "If you are on the free Profiles & Email plan and are over your profile limit, you won't be upgraded but you also cannot send emails (or set flow emails live) until you are under your active profile limit" ^[5].

For a volunteer-run organisation with a committee of 200, that constraint is a feature. The budget cannot be exceeded by accident, which is not true of any paid tier.

The architecture does not fit a donation

Klaviyo's segmentation runs on orders. Purchase history, browsing behaviour, predicted value, abandoned checkout, post-purchase flows, review requests, loyalty balances: every one of those assumes a transaction with a product in it ^[12].

A donation is a transaction without a product. It has an amount, a date, often a designation and sometimes a recurrence, and none of those map to the fields the pre-built machinery expects.

You can model it. The data platform lets you "Add memberships, appointments, subscriptions, and other custom data to customer profiles, then activate it across segmentation and automation" ^[12], and the events API writes arbitrary events onto a profile. Recurring giving maps reasonably onto subscription, and membership maps onto membership.

But you are building, not configuring, and the pre-built flows that make this platform fast for a store will mostly not apply to you. Budget development time or an agency, and weigh that against a tool built for fundraising.

## Where it genuinely helps

Two things, and for the right organisation they are worth the awkwardness.

The first is channel breadth on one profile. Email, SMS, push and WhatsApp against a single supporter record, with consent managed once ^[14]. For emergency appeals and campaign moments, reaching supporters where they actually are matters more than it does for most commercial senders, and the alternative is usually two tools with two definitions of the same person.

The second is behavioural segmentation, if you can feed it. Lapsed donors by recency and amount, supporters who open every email and have never given, people who attended an event and nothing since. Those segments are standard practice in fundraising and surprisingly hard in most nonprofit email tools.

What it costs, and what to compare it against

The entry plan is twenty dollars a month, published in the terms of a discount rather than on the pricing page ^[4]. Above it, the rungs appear only inside support-article examples: $80 for 35,000 monthly emails, $100 for 5,000 profiles and 50,000 emails ^{[6] [8]}.

The profile ladder is what will bill you, because a nonprofit's supporter count usually exceeds what its send volume would justify. At 5,000 supporters you are looking at roughly a hundred dollars a month on the vendor's own published example, for a list you mail monthly.

Compare that against fundraising-native platforms rather than against Mailchimp, because the relevant question is not which sends email more cheaply but which handles a gift, a pledge and a tax receipt without custom work. Several of those platforms publish explicit nonprofit pricing, which Klaviyo does not.

## The configuration that protects you

If you do proceed, three settings matter more than anything else, and all three are free.

Replace auto-upgrade with flexible sending plus auto-downgrade. Auto-upgrade is the default ^[11], and a campaign that grows the list will move the plan up and leave it there. Auto-downgrade returns it automatically, and the two cannot run together.

Note the billing cycle date. A downgrade made inside the last twenty-four hours "will not take effect" ^[5], and there are no refunds for mid-cycle downgrades.

And decline the add-ons. Customer Hub, Helpdesk, Customer Agent and Marketing Analytics total one hundred and eighty dollars a month at their entry prices ^[5], and all four are built around a shopper. For a nonprofit they are cost without function.

Consent, retention and the data you are agreeing to hold

Nonprofits carry a different compliance weight from retailers, and this platform is built to accumulate rather than to minimise.

The data platform exists to deepen a profile over time, adding "memberships, appointments, subscriptions, and other custom data", resolving anonymous visitors to known profiles, and retaining behaviour across years ^[12]. For a commercial brand that is the value proposition. For an organisation holding records about vulnerable beneficiaries, donors with protected characteristics, or anyone who gave in a sensitive context, it is a policy question before it is a product one.

Two practical consequences. First, decide your retention rule before you import, not after: what comes in is easy and what goes out requires deliberate work. Second, note that suppression and deletion are also the billing levers ^[5], which means your data-minimisation policy and your cost control point in the same direction here. That is a rare alignment and worth using.

Also settle who in your organisation can export. Thirteen of a hundred Trustpilot reviewers describe account suspension and difficulty retrieving data afterwards ^[20]. We cannot verify individual cases, but for an organisation whose supporter file is its most valuable asset, a documented export routine run quarterly is cheap insurance regardless of vendor.

## What to ask a fundraising platform instead

If this page has pointed you away from Klaviyo, the comparison is more useful with the right questions, and they are not the ones a feature grid asks.

Does it handle a gift as a first-class object, with amount, designation, appeal code and recurrence? That is the thing Klaviyo models as a generic event and a fundraising platform models natively.

Does it produce tax receipts, and in your jurisdiction? This is unglamorous and it is the requirement that most often decides the choice.

Does it publish nonprofit pricing, and on what basis: a percentage discount, a capped rate, a free tier by organisation size? Klaviyo publishes none, and a vendor that does has usually thought about how your list differs from a retailer's.

Does it bill on contacts, on sends, or on funds raised? Billing on sends suits a large file mailed rarely, which is the typical nonprofit shape and exactly the shape active-profile billing treats worst.

Answer those four and the shortlist builds itself.

The free tier arithmetic, done properly

Worth doing with real numbers, because the answer surprises people in both directions.

The free tier covers 250 active profiles and 500 sends a month ^[2]. Those two limits bind differently. A list of 250 mailed twice a month uses 500 sends exactly, so the tier is balanced for a monthly or fortnightly newsletter to a small supporter base and nothing more.

At 400 supporters mailed monthly you are over on profiles and under on sends, and the profile limit is the one that stops you: exceeding it blocks sending until the count comes down ^[5]. At 200 supporters mailed weekly you are over on sends and comfortable on profiles, and the same stop applies.

So the question is not how many supporters do we have but which of the two ceilings you hit first. For most small charities it is profiles, and it arrives sooner than expected because the count includes everyone reachable rather than everyone engaged.

Above that, the first paid rung is twenty dollars ^[4], and the ladder from there is published only inside support-article examples. A thousand supporters mailed monthly is a perfectly ordinary small-charity profile and its price is not on the internet.

A realistic recommendation

If you are a small organisation with a list under 250 and a simple appeal calendar, the free tier is genuinely good and costs nothing. Use it.

If you are a mid-sized nonprofit with a merchandise shop, an events programme or a membership scheme, anything that produces a real transaction, Klaviyo's machinery starts to fit and the behavioural segmentation is a real upgrade on what you probably have.

If you are a traditional fundraising organisation with a large donor file, infrequent appeals and no commerce, this is the wrong shape of product at the wrong price, and the absence of nonprofit pricing tells you the vendor agrees. We score Klaviyo 3.88 as an ecommerce platform. Scored against a fundraising job, it would not come close, and that is a statement about fit rather than about quality.

If you do use it: the four things to build

For an organisation that has decided the fit is good enough, these are the pieces that earn their place, in order.

A welcome sequence for new supporters, triggered on the first action rather than on the first gift. Most nonprofit lists contain many people who signed up and never gave, and they are already billable, so the question is not whether to mail them but what to say.

A lapsed-donor segment by recency and amount. This is standard fundraising practice and genuinely hard in most nonprofit email tools, and it is the single place where Klaviyo's behavioural segmentation earns its price for this sector.

A recurring-giving flow modelled on subscription, which is the one piece of the commerce machinery that maps cleanly. Renewal dates, failed payments and upgrade asks all have equivalents the platform already understands.

And an annual suppression routine. It is a stewardship decision as much as a billing one, but a supporter who has not opened an email in three years is costing money every month and is not going to be reactivated by a fourth year of appeals.

Build those four and leave the rest of the platform switched off.

## The question to settle first

Before evaluating features, answer one thing: does your organisation have transactions, or only gifts?

If there are transactions, tickets, merchandise, memberships, courses, Klaviyo's model has something to hold on to and the rest of this page is a configuration exercise. If there are only gifts, every advantage described here has to be rebuilt by hand, and a platform built for fundraising will cost less and do more.