Appcues Pricing: Appcues Cost Per MAU, the Spark Plan, and Appcues vs Pendo on Price

Appcues does not publish a price on its pricing page. The page shows three plans, Start, Grow and Enterprise, described only by monthly active user bands, how many experiences you can publish at once, and how far back your reporting history goes. One real US price does exist: the Spark plan for teams of 25 or fewer is $3,600 a year for up to 1,000 MAU, plus a $250 one-time implementation fee, published on a separate page linked in small print under the plan cards. Procurement data puts the median Appcues contract far above that, at $15,000 a year across 135 purchases. Read first-party from a US connection on 21 September 2026.

How much does Appcues cost?

The honest answer for most buyers is that you will not know until you book a call. Appcues removed its published rate card, and the pricing page now sells on inclusions rather than dollars. Every plan gets every experience type, every feature and every integration from day one, and what you are really buying is scale.

That makes the guides currently ranking for this query actively misleading. Most of them still describe an Appcues plan called Essentials at $249 a month for 2,500 monthly active users, and a Growth plan at $879. There is no plan called Essentials on the Appcues site today, and there is no $249 anywhere on it. If a comparison page quotes those figures, it has not been re-read in a long time.

What you can pin down is the structure, the one published small-team price, and what other companies have actually signed. Those three together get you close enough to walk into a sales call with a number in mind.

What are the Appcues plans?

Three plans on the pricing page, plus a fourth aimed at small teams that sits on its own page.

Read the table as a ladder of three things rather than a feature ladder. Appcues is explicit that there is no feature gating: "Every plan includes every experience type, feature, and integration from day one." What changes is how many users you can reach, how many experiences you can run at the same time, and how much history you can look back at.

The published experience cap is the one people underestimate. Ten live experiences sounds generous until you count what a real onboarding program contains: a welcome modal, three tooltips, a checklist, a feature announcement, an NPS survey, an upgrade prompt and two empty-state nudges is already nine. Grow triples that allowance, and for many teams that ceiling, not the MAU count, is what forces the upgrade.

The Appcues Spark plan: $3,600 a year

This is the number almost nobody quotes, because it is not on the pricing page. Under the three plan cards there is a single line asking whether your team is under 25 people, linking to a separate Spark plan page. That page prices the plan openly.

Spark is $3,600 a year for up to 1,000 monthly active users, with a $250 one-time implementation fee. It includes the full Appcues platform, every experience type and every integration, 10 published experiences, 12 months of reporting history, guided onboarding to get the first flow live, and free email up to 1,000 sends. Appcues says most teams go from setup to a first live flow in a day.

Two things to do before you quote it back to a rep. First, the arithmetic: $3,600 for 1,000 MAU is $3.60 per monthly active user per year, or 30 cents a month. In year one, with the setup fee, it is $3,850, or $3.85 per MAU. Second, the contradiction: the Spark page sells the plan "for up to 1,000 MAUs" in the price block, then its own FAQ answers the question "What if we exceed 3,000 MAUs?", which is the Start plan allowance rather than the Spark one. That is leftover copy, but it means the ceiling on your plan is ambiguous in writing. Get your actual MAU limit into the order form.

What counts as a monthly active user in Appcues?

Appcues defines an MAU as any user who signs into your product in a given month, and states that dormant users sitting in your database do not count. That is a narrower and more buyer-friendly definition than some competitors use, and it matters more than it sounds.

Pendo, for comparison, counts unique visitors who were active in your app at least once over the last 30 calendar days, where active means any engagement rather than a sign-in specifically. If a meaningful share of your product usage happens before a login, on a logged-out surface, or inside an SSO session that persists without a fresh sign-in, the two vendors will produce different counts for the identical product. Count your own users both ways, on sign-in events and on any-interaction events, before you compare quotes. The gap between those two numbers is the size of the budgeting error you are about to make.

There is a second meter that is easy to miss. Appcues states that pricing is based on monthly active users, number of installations and published experiences. Installations is a separate axis, so a company running several products should ask directly how multi-product deployments are counted. Pendo takes the opposite position and says applications and sessions do not affect its price at all, which our Userpilot vs Pendo vs Appcues pricing comparison sets out side by side.

What do Appcues customers actually pay?

Vendr, which negotiates software contracts on behalf of buyers and publishes aggregate data per vendor, reports a median annual Appcues contract of $15,000 across 135 purchases, with observed deals from $6,213 to $44,200 and an average negotiated saving of 21.07%.

Hold that next to the one published price. Spark is $3,600 a year. The median signed contract is more than four times that. The explanation is simply volume: 1,000 MAU describes a pre-revenue product, and the companies that run a procurement process have far more users than that. If you are modeling a budget for a funded B2B product, $15,000 is a more realistic planning figure than anything on the pricing page.

The 21.07% average discount is the other useful number. It says list is not final, and that a buyer who negotiates lands roughly a fifth below the opening quote. For a $15,000 contract that is about $3,200 a year, which is worth one uncomfortable phone call.

These are third-party figures describing companies large enough to have a procurement function, not vendor figures. Read them as a planning anchor rather than a quote.

What happens if you go over your Appcues MAU limit?

Nothing breaks, which is unusually generous for this category. Appcues says it keeps your experiences running and reaches out about moving to the Grow plan at your next billing cycle, with no surprise overage charges.

That is worth comparing to how others behave at the cap. Pendo on a paid plan also keeps running and has a rep contact you about a contract adjustment, but Pendo on its free tier stops you creating new guides, NPS surveys or segments until you upgrade. Several survey and replay tools simply stop collecting data when you hit the ceiling, which means a gap in your record that you cannot backfill. Appcues not charging punitive overage, and not cutting you off mid-campaign, removes a real risk from a launch month.

Is Appcues cheaper than Pendo or Userpilot?

Against Pendo, yes, and by a wide margin at the median. Against Userpilot it depends entirely on your user count.

The first row and the second are the interesting pair. Appcues Spark and Userpilot Starter are $12 a year apart in total cost, and Userpilot includes twice the monthly active users. Per user, Appcues Spark costs almost exactly double. What the extra buys is guided onboarding, a dedicated experience manager and every feature unlocked, where Userpilot Starter withholds autocapture, funnels, retention, path analysis, custom dashboards, A and B testing and workflows, and caps you at ten segments. Our Userpilot pricing guide and Pendo pricing guide go through each ladder in full.

Pendo sits in a different bracket. Its median buyer signs $48,597 a year, roughly three times the Appcues median, and it concedes the least in negotiation of the three at 12.1% on average. If budget is the binding constraint, Appcues is the safer shortlist entry. If you want a broader platform and have the budget to match, that gap is what you are paying for.

How to negotiate an Appcues contract

Go in with four things settled. Your own MAU count, measured on sign-ins, since that is the definition Appcues bills on. The number of experiences you actually need live at once, because that cap is what usually forces the tier. A budget figure anchored on the $15,000 median rather than on the Spark price. And one competing quote, because the 21.07% average discount in the procurement data is not given away unprompted.

Then get four answers in the order form rather than on a call: the MAU ceiling in writing, how installations are counted if you run more than one product, what happens to the rate at renewal, and whether the implementation fee applies to your plan. Renewal is the one people skip. An annual SaaS contract that reprices quietly at year two is the most common way a good deal turns into a bad one, and it is worth watching every software line item against its original contract once the invoices start arriving rather than discovering the increase a year later.

If you are still deciding whether Appcues is the right category fit at all, our Appcues alternative page covers what else solves the same job, and the product adoption software page covers what to check across the category.

What an adoption tool will not tell you

Appcues is good at what it claims: shipping in-app experiences without engineering time, and measuring whether they moved a number. If your problem is that new users never find the feature that makes the product click, a tooltip and a checklist genuinely fix it.

What it does not do is explain why users stall in the first place. A funnel report showing 40% abandonment at step three does not tell you that the same accounts filed support tickets about that screen last month, mentioned it in their NPS comments, and wrote about it in a review. Those records sit in four different systems, and adoption tooling reads one of them.

UserInsight reads product usage, support tickets, reviews, survey answers and feedback together, groups them into named themes with counts, and ranks each theme by how many customers and accounts it touches, with every theme traced back to the evidence behind it. It runs alongside an adoption platform rather than replacing one. The adoption tool tells you where people stop. The theme ranking tells you what they said about it, and how much revenue is sitting behind the complaint you have not prioritized yet.