The real cost of Appcues for a 10,000 MAU SaaS
You hit 10,000 monthly active users. Your PM wants to ship an onboarding flow by next quarter. Someone on the team Googles "product tour tool" and Appcues shows up first.
The pricing page says $249/month. Reasonable. You click around, run the numbers, and realize that price is for 2,500 MAU on a feature-stripped plan. At your scale, the real number starts at $18,000/year and can climb past $30,000 once you account for seat caps, premium support, and the features you actually need.
We built Tour Kit as an open-source alternative, so take everything here with appropriate skepticism. But every number in this article comes from public sources: Appcues' own pricing page, Vendr contract data (127 real purchases), and G2/Capterra reviews. You can verify all of it.
npm install @tourkit/core @tourkit/reactThe problem: Appcues pricing doesn't scale the way you'd expect
Appcues publishes three tiers, all priced per MAU, but the entry prices are misleading at scale. A 10,000 MAU SaaS pays dramatically more than 4x the base-tier price because Appcues uses non-linear scaling: doubling your MAU more than doubles your cost. As of April 2026, Growth plan pricing at 2,500 MAU is $879/month, but at 5,000 MAU it jumps to $1,150+, a 31% increase for 2x the users (Userorbit, 2026).
| Line item | Annual cost (10K MAU) | Source |
|---|---|---|
| Growth plan (list price) | $18,000-$24,000 | Userorbit + Vendr extrapolation |
| Unlimited Seats add-on | $2,400 | Userorbit pricing guide |
| Premium Support (15%) | $2,700-$3,600 | Vendr marketplace data |
| Year 2 escalator (5%) | +$1,155-$1,500 | Vendr (3-7% typical) |
| Implementation services | $0-$10,000 (one-time) | Vendr marketplace data |
| Total Year 1 (realistic) | $23,100-$40,000 |
Vendr's marketplace data across 127 real Appcues purchases shows a median annual contract of $15,000 with mid-market companies (5K-25K MAU) paying $12,000-$40,000/year (Vendr, 2026). The average negotiated discount is 21% off list price, so if you're paying sticker, you're overpaying.
The feature gates that inflate your bill
Appcues' Essentials plan exists mainly as a pricing anchor, not a usable product for growth-stage SaaS. At 10,000 MAU it scales to roughly $599/month ($7,188/year), but that price locks out A/B testing, checklists, Salesforce integration, custom CSS, and caps your audience segments at five. The features you need to actually improve onboarding conversion all live one tier up.
You can't run A/B tests on onboarding flows. No Salesforce or Slack integrations. Custom CSS? Locked out.
Any team serious about optimizing onboarding is forced into the Growth tier. That 253% price jump from Essentials to Growth isn't a premium for advanced features, it's the price of a usable product (Userpilot, 2026).
And if your SaaS serves multiple languages? Localization is gated entirely to Enterprise. No Growth-tier option exists. A multilingual product at 10K MAU is looking at custom Enterprise pricing, which starts the conversation at $15,000/year and goes up from there.
The costs that aren't on the pricing page
Beyond list pricing, three categories of hidden costs catch teams off guard after they sign an Appcues contract. SDK placement inflates your MAU count, seat caps force add-on purchases, and analytics gaps require a second paid tool. Together, these can add $10,000-$30,000/year to the sticker price.
MAU inflation from SDK placement. Install the Appcues SDK on your marketing site or any unauthenticated page, and every visitor counts against your MAU quota. Appcues' own documentation warns against this, but teams regularly discover it mid-contract when they get a surprise overage notice.
There's no per-user overage fee. Instead, Appcues force-upgrades you to the next MAU tier for the remaining months on your contract.
Seats at scale. Growth plan caps you at 10 seats. At 10,000 MAU, your product org likely has more than 10 people who touch onboarding: PMs, designers, CS reps, growth marketers. The Unlimited Seats add-on costs $2,400/year. Individual seats are $480/year each (Userorbit, 2026).
Analytics that need a supplement. Multiple reviewers report Appcues' built-in analytics can't do proper funnel analysis or cross-journey attribution. One reviewer put it plainly: "Connecting goal completions across multiple journeys or building proper funnels just isn't possible in Appcues" (Hopscotch, 2026).
So teams run Appcues alongside Mixpanel or Amplitude, adding $6,000-$24,000/year in analytics tooling. The true cost is Appcues plus whatever analytics tool fills the gap.
If you're already evaluating the total cost of onboarding software, these hidden costs deserve a line in your spreadsheet.
The counterargument: when Appcues is worth the money
Appcues exists because building onboarding from scratch is genuinely expensive, and for certain team profiles the SaaS approach saves more than it costs. Writing off Appcues entirely would be dishonest, so here's the steelmanned case for buying it at 10K MAU.
A product-led growth team that needs to ship onboarding flows in two weeks, doesn't have frontend engineering bandwidth, and is growing fast enough that the annual cost is a rounding error on revenue? Appcues is a reasonable choice. The visual builder genuinely speeds up iteration for non-technical PMs.
Appcues' own case studies back this up: Litmus reported a 22x increase in feature adoption, and n2y saw 400% reduction in support contact ratio within five months (Appcues case studies, 2026).
And Appcues' build-vs-buy argument has a kernel of truth. Their cost calculator estimates $33,800 minimum in team time for building onboarding from scratch (Appcues blog, 2026). An independent estimate pegs it higher: one UX designer plus one developer for two months costs roughly $60,000 (Userpilot, 2026).
But those estimates assume building a full onboarding platform from zero. Not integrating a library.
The math changes with a library
The build-vs-buy framing presents a false dichotomy that Appcues' own marketing reinforces. Your actual options are three, not two: buy a SaaS platform, build from scratch, or integrate an open-source library that handles positioning, state management, and accessibility while you own the UI and data.
Here's a back-of-envelope calculation for the library approach:
| Cost component | Appcues Growth (10K MAU) | Tour Kit + engineering time |
|---|---|---|
| Year 1 license/tooling | $18,000-$24,000 | $0 (MIT core) |
| Initial integration (sr. dev, $150/hr) | $0 (included) | $6,000 (40 hrs) |
| Annual maintenance | $0 (included) | $9,000 (5 hrs/mo) |
| Year 1 total | $18,000-$24,000 | $15,000 |
| Year 2 total | $18,900-$25,200 (+5%) | $9,000 (maintenance only) |
| 3-year total | $56,700-$75,600 | $33,000 |
Over three years, the library approach saves $23,700-$42,600 compared to Appcues Growth. Year 2 is where the gap widens, because SaaS renews at escalating rates while maintenance time typically decreases as the codebase stabilizes.
We calculated similar numbers in our build vs buy calculator and in the developer time cost breakdown for open-source onboarding.
Tour Kit isn't the right fit for every team. You need React developers on staff (React 18+ only). There's no visual builder, so PMs can't edit flows without touching code. The community is smaller than Appcues' or React Joyride's.
If your team is PM-led with zero frontend engineering capacity, a SaaS tool probably makes more sense. But if you already have React developers building your product? The question isn't "can we afford to build?" It's "can we afford $18K/year for something we could own?"
What to do if you're evaluating right now
Whether you buy Appcues, pick another SaaS tool, or go the library route, the worst outcome is signing a contract without understanding what you're actually paying. Here's what we'd recommend based on where you are in the decision.
If you're about to sign an Appcues contract: Negotiate hard at quarter-end. Vendr data shows a 21% average discount. Ask specifically about MAU counting on unauthenticated pages, what happens when you exceed your tier, and whether localization is included. Get the answers in writing.
If you're on Appcues and rethinking it: The migration guide walks through replacing Appcues with code-owned onboarding step by step. Budget 2-4 days for a typical 10-step tour migration.
If you're starting fresh: Try Tour Kit's headless approach before committing to a SaaS contract. The core is 8KB gzipped, works with your existing design system, and your onboarding data stays in your infrastructure. No MAU pricing. No vendor lock-in.
// src/components/OnboardingTour.tsx
import { TourProvider, useTour } from '@tourkit/react';
const steps = [
{ id: 'welcome', target: '#dashboard', title: 'Welcome aboard' },
{ id: 'sidebar', target: '#nav-menu', title: 'Navigation' },
{ id: 'create', target: '#new-project', title: 'Create your first project' },
];
function App() {
return (
<TourProvider steps={steps}>
<YourApp />
</TourProvider>
);
}Understanding why onboarding tools charge per MAU helps you evaluate any SaaS option, not just Appcues.
FAQ
How much does Appcues cost at 10,000 MAU?
Appcues Growth plan at 10,000 MAU costs approximately $18,000-$24,000 per year at list price, based on Vendr data across 127 real contracts. The Essentials tier scales to $7,188/year but locks out A/B testing, checklists, and Salesforce integration. Average negotiated discount is 21% off list.
Is Appcues worth it for a startup?
Appcues delivers value for PM-led teams that need to ship onboarding quickly without engineering support. But at 10,000 MAU, the $18K+ annual cost eats into runway. Teams with React developers on staff often find that an open-source library costs less in Year 1 and significantly less from Year 2 onward.
What are the hidden costs of Appcues?
The biggest hidden costs are MAU overage from SDK placement on unauthenticated pages, seat caps (Growth plan limits to 10 seats), localization locked to Enterprise tier, annual price escalators of 3-7%, and the need for a separate analytics tool since Appcues' built-in analytics lack funnel analysis capabilities.
How does Appcues compare to open-source alternatives?
Appcues provides a visual builder, managed hosting, and non-technical editing. Open-source libraries like Tour Kit offer full code ownership, zero MAU pricing, and TypeScript-first APIs but require React developers. Over three years at 10K MAU, the open-source approach costs roughly $33,000 versus $57,000-$76,000 for Appcues.
Can you negotiate Appcues pricing?
Yes. Vendr data shows an average 21% discount off list price across 127 contracts. Quarter-end and fiscal-year-end negotiations yield better terms. Ask for multi-year locks at current MAU tier pricing to protect against growth-triggered price jumps.
Internal linking suggestions:
- Link FROM:
/blog/mau-pricing-onboarding-tool(add a "see also" pointing to this cost breakdown) - Link FROM:
/blog/best-alternatives-building-onboarding-in-house(add this as a supporting resource) - Link FROM:
/blog/onboarding-software-cost-2026(cross-reference the Appcues-specific data) - Link TO: Already linked above to 5 internal articles
Distribution checklist:
- Dev.to: Cross-post with canonical to tourkit.dev
- Hacker News: Submit as "The Real Cost of Appcues for a 10K MAU SaaS"
- Reddit r/SaaS, r/startups: Share as cost analysis post
- Indie Hackers: Share in build-vs-buy discussions
- LinkedIn: Format key cost table as carousel
Related articles
TCO comparison: 3 years of Appcues vs 3 years of Tour Kit
We modeled the full 3-year total cost of ownership for Appcues and Tour Kit at three MAU tiers. See every line item, the compounding effects, and where each tool wins.
Read article
The developer's calculator: DIY tour vs library vs SaaS
Calculate the real cost of DIY tours, libraries, and SaaS tools. Compare 3-year TCO with sourced numbers before committing engineering hours.
Read article
How to calculate onboarding software ROI (2026)
Calculate onboarding software ROI with concrete formulas, benchmark data, and a fill-in worksheet. Includes build vs buy cost comparison for 2026.
Read article
Data ownership in onboarding: who owns your tour analytics?
Examine who actually owns your product tour analytics data when using SaaS onboarding tools. Compare vendor custody, GDPR roles, and code-owned alternatives.
Read article