Pendo doesn't publish prices. That's intentional. The company moved to a fully sales-led model around 2019 and has stayed there. What teams actually pay comes from procurement databases, community forums, and SaaS deal-sharing communities, and the range is wide enough to make most blog posts about "Pendo pricing" nearly useless. This article uses verified contract data from Vendr's procurement marketplace alongside community-reported deal data to give you real numbers. Not estimates. Not guesses from 2022.
The short version: Pendo's median contract is $48,695/year. Contracts range from $18,140 to $147,575. Very few teams under 150 employees get meaningful value out of that spend unless product analytics is a core strategic function, not a nice-to-have.
How Pendo pricing actually works
Pendo prices on Monthly Active Users (MAU), the number of unique users who interact with your product in a given month. More MAU means a higher tier and a higher bill. The model has three structural implications that matter more than the plan names:
First, the pricing is additive. You don't pay one flat rate for "Pendo." You pay for a base MAU tier, then add modules: product analytics, in-app guidance, session replay, NPS, A/B testing. Each module is its own line item in enterprise deals. What looks like a single price on a competitor comparison article is usually a bundled quote with multiple add-ons already included.
Second, contracts are annual, typically with a 5-10% escalation clause at renewal. Multi-year deals (two or three years) often come with 15-30% discounts off list price, which is part of how Pendo's sales team justifies longer commitments during a buying process. The savings are real. The lock-in is also real.
Third, there's no public trial path to a paid plan. The free tier exists (up to 500 MAU) and is genuinely useful for testing the platform before any commercial conversation. But there's no self-serve monthly subscription for small teams. Every paid engagement goes through sales.
What Pendo actually costs: verified contract data
Based on Vendr's SaaS procurement data from 537 verified Pendo purchases, here are the real numbers. These are not guesses, they are actual deal data from buyers who shared their contracts through Vendr's platform.
The range matters. A team paying $18,140/year is almost certainly on a Starter tier with a limited MAU count and minimal add-ons. A team at $147,575 has a full enterprise deployment with multiple modules, a high MAU ceiling, and probably multi-app support.
Why the "median" number is misleading
The $48,695 median represents the midpoint across all deal sizes, including large enterprise deployments that push the average up. For a B2B SaaS company at 30-100 employees, the relevant benchmark is the lower end of the range, $18,000-$25,000/year for a basic Growth tier deployment with core analytics and in-app guidance. Not $48,000.
Still, even $18,000/year is a significant infrastructure investment for a team whose primary need is keeping documentation accurate. That context matters when you're evaluating Pendo against alternatives.
The per-MAU math at realistic company sizes
Most teams evaluating Pendo land somewhere between 1,000 and 15,000 MAU during their evaluation window. Here's what the cost structure looks like at each inflection point.
Under 500 MAU: the free tier is real
Pendo's free tier supports up to 500 MAU with basic in-app guide functionality and limited product analytics. No credit card required. For very early-stage teams validating whether in-app onboarding is worth investing in, this is a genuine no-risk evaluation period.
What the free tier excludes: NPS surveys, advanced segmentation, session replay, A/B testing, and, critically, any support beyond documentation. You're on your own. For teams that need production-grade onboarding right now, the free tier is a proof-of-concept tool, not an operating option.
500–2,000 MAU: the Starter math
Starter tier deals in the 500-2,000 MAU range typically run $7,000-$12,000/year based on community data. That's $583-$1,000/month for in-app guides and basic analytics at a scale where most teams are still figuring out their onboarding playbook. The cost question at this stage: is a $10,000/year commitment justified before you know what your activation funnel looks like?
The honest answer depends entirely on whether product analytics is a core function or a support tool. If you're running systematic onboarding experiments with dedicated product ops capacity, yes. If you're trying to reduce support tickets and keep documentation current, that $10,000 buys a lot of alternatives.
2,000–10,000 MAU: the Growth tier zone
This is where most mid-market SaaS teams land when they're seriously evaluating Pendo. Growth tier deals start at $20,000/year and climb based on MAU count, feature modules, and negotiation leverage. The $20,000-$60,000 range is realistic for this cohort.
At $30,000/year for a 5,000 MAU deployment, you're paying $6/MAU/year, or $0.50/user/month. That math starts making sense when each user represents significant revenue, when activation rates directly drive expansion, and when you have the analytics infrastructure to actually act on Pendo's data. It's a harder number to justify for teams where documentation maintenance is the bottleneck.
10,000+ MAU: enterprise territory
Above 10,000 MAU, Pendo deals enter Portfolio territory. These contracts typically run $75,000-$200,000+/year and are structured around multi-app deployments, custom data retention, enterprise security compliance, and dedicated customer success. The analytical value at this scale is genuine, you're getting product intelligence that meaningfully affects roadmap decisions. The question of whether it's the right tooling depends on the business, not the feature list.
What's included vs. what costs extra
Pendo's add-on structure is one of the most buyer-unfriendly parts of the pricing model. Core tier pricing often excludes features teams assume are standard. Understanding the inclusions before the sales call saves significant negotiation time.
Included at Starter and above
In-app guides (tooltips, modals, banners, and lightboxes), basic product analytics (page views, feature usage tracking), NPS surveys, and Pendo's resource center widget. These cover the core onboarding use case for most SMB teams.
Add-ons that cost extra
Session replay is a common Growth-tier add-on, not a standard inclusion. A/B testing on guide variants is typically Growth or above with specific configuration. Data integrations with warehouse tools like Snowflake or BigQuery are enterprise-level features. Advanced user segmentation based on custom event data requires developer configuration and may be priced per event volume at scale. Mobile in-app guidance (iOS/Android) is frequently a separate module from web guidance.
The practical impact: a quote that looks like $20,000/year for Growth often ends up at $28,000-$35,000/year once session replay, integrations, and mobile support are added as line items. Push for an all-in quote during the evaluation, not a base-tier price.
Hidden costs: implementation, onboarding, and renewal escalation
Implementation and developer time
Pendo requires developer installation. The standard deployment involves adding Pendo's JavaScript agent to your application, configuring event tracking for the features you want to analyze, and setting up data schemas for your product entities. According to the GitLab DevSecOps Survey, engineering teams at companies under 150 employees average 20-40% of development time on internal tooling and infrastructure. Pendo setup typically takes 2-4 weeks of active developer involvement for a production-grade deployment.
That's 80-160 hours of engineering time before your first guide is live. At a loaded developer cost of $80-$120/hour, the implementation cost alone runs $6,400-$19,200, not including the learning curve on guide creation and analytics configuration.
Guide maintenance overhead
Pendo's in-app guides are overlay-based: they identify UI elements by class names or text strings and display guide steps on top of existing product screens. When your product ships a UI change, a button renames, a navigation item moves, a form field updates, affected guides reference the old element until someone manually reviews and updates the guide logic. Pendo doesn't detect this automatically.
For teams shipping weekly, this creates a standing maintenance obligation. The documentation decay cost doesn't appear in any pricing table, but it scales directly with release velocity. A product with 30 active guides on a weekly release cadence generates roughly 60-90 guide maintenance events per year, at roughly 30-60 minutes each. That's 30-90 hours of maintenance work annually, at a loaded staff cost of $2,400-$7,200/year alongside the subscription.
Annual renewal escalation
Pendo contracts include standard 5-10% annual price escalation clauses. A $30,000/year Year 1 contract typically becomes $33,000-$35,000 in Year 2 without negotiation. Multi-year commitments lock you into the escalation formula upfront, which is worth understanding before signing a three-year deal even if the Year 1 discount is attractive.
Three-year total cost of ownership
A realistic TCO model for a B2B SaaS team growing from 2,000 to 8,000 MAU over three years, on a Growth tier contract with standard inclusions:
Subscription costs over 3 years
Year 1 at 2,000-3,000 MAU: $20,000-$25,000. Year 2 at 4,000-5,000 MAU with renewal increase: $23,000-$30,000. Year 3 at 6,000-8,000 MAU: $28,000-$40,000. Three-year subscription total: $71,000-$95,000.
Implementation and ongoing labor
Initial developer setup: $8,000-$15,000. Annual guide maintenance (60 hours at $80/hour): $4,800/year, or $14,400 over three years. Total implementation plus labor over three years: $22,400-$29,400.
Combined 3-year TCO estimate
$93,000-$124,400 for a mid-market B2B SaaS product growing from 2,000 to 8,000 MAU. This doesn't include a separate Help Center for self-service documentation, which Pendo doesn't replace. If you need both in-app onboarding and a searchable external Help Center, add that cost separately.
When Pendo's pricing makes sense
The math works for specific company profiles. If your team is optimizing activation rates with systematic A/B testing, tracking feature adoption cohorts to drive expansion revenue, or building product-qualified lead models based on in-app behavior data, Pendo delivers analytics capability you won't find in cheaper alternatives. The product is genuinely excellent at what it does.
The companies where Pendo earns its price: PLG businesses with dedicated product operations teams, enterprise SaaS companies where user paths directly inform roadmap decisions, and high-growth companies where even a 2-3% improvement in activation rates translates to significant ARR impact. If you have the analytics infrastructure and the team to act on the data, the spend is justified.
When Pendo's pricing doesn't make sense
For B2B SaaS teams under 150 employees where documentation accuracy is the primary goal, Pendo is an expensive tool for the wrong problem. The issue isn't the analytics, it's that you're paying $20,000-$60,000/year for a platform whose differentiating value is product intelligence, not documentation maintenance.
According to the Salesforce State of Service report, 83% of customers expect to resolve complex issues through self-service. Getting there requires accurate documentation, guides, articles, and contextual help that reflect what the product actually does today. Pendo helps with the in-app layer. It doesn't solve the Help Center staleness problem that drives most support ticket volume at the product documentation layer.
The teams that regret the Pendo commitment most are those who signed a two-year Growth contract to solve a documentation problem, then discovered the analytics required dedicated attention they couldn't provide. The platform sat underused while the guide maintenance backlog kept growing.
Alternatives at each price point
Under $5,000/year
ProductFruits covers the core onboarding toolkit (tours, tooltips, checklists) starting at $864/year for 1,500 MAU. No developer required for basic guides. Lacks Pendo's analytics depth, but delivers 80% of the onboarding functionality at 5-10% of the cost for teams in this range.
$5,000-$15,000/year
Userpilot's Starter tier starts at $299/month ($3,588/year) for up to 2,000 MAU. Growth tier pricing is custom but community data puts it at $7,600-$60,000/year depending on MAU and feature set. More feature-complete than ProductFruits, less analytically deep than Pendo.
The documentation freshness alternative
For teams whose primary problem is keeping help content accurate across weekly releases rather than measuring product analytics, purpose-built tools that connect to the deployment pipeline address a structurally different problem. The self-updating Help Center model, where documentation updates when code ships rather than when a team member notices it's stale, solves a problem that no in-app guide tool addresses at any price point.
Pendo pricing vs. alternatives: what you get per dollar
The most useful way to contextualize Pendo's cost isn't the absolute number, it's the cost per unit of value delivered relative to what alternatives charge for equivalent functionality.
For in-app guide creation (tours, tooltips, checklists): ProductFruits delivers this at $864-$1,344/year for teams under 5,000 MAU. Userpilot delivers it at $3,588/year for up to 2,000 MAU. Pendo starts at $7,000-$12,000/year for the same MAU range, plus developer implementation costs. The guide creation functionality is roughly equivalent across all three platforms. The price differential is 5-10x, paid almost entirely for Pendo's analytics depth.
For product analytics: Amplitude and Mixpanel are the dedicated analytics alternatives. Both offer more granular event tracking and more flexible analysis than Pendo's analytics suite, at prices that are often lower than a comparable Pendo contract. If analytics is the primary value driver, Pendo's bundled analytics plus guidance model means you're paying for guidance functionality you may not need, and analytics depth that a dedicated analytics tool may deliver better.
The bundling is Pendo's core business model: by combining analytics and guidance into one platform, the company avoids being compared directly against either category. That's smart positioning. It also means that teams whose primary need falls clearly in one category or the other are overpaying for the capabilities they don't use.
The teams where Pendo's bundled value is genuinely compelling: those that need deep analytics AND in-app guidance, don't want to manage two separate platforms, have developer resources for implementation, and have the product operations capacity to act on the data Pendo produces. For that profile, the single-platform approach is worth the premium. For everyone else, the alternatives cover the specific need at significantly lower cost.
What to do before the Pendo sales call
Pendo's sales process is designed to move fast. A few things to have ready before the first call save weeks of back-and-forth.
First, know your actual MAU count from your analytics tool. Not an estimate, a real 30-day rolling average. This is the number that determines your tier and gives you negotiating leverage.
Second, request an itemized quote that separates the base tier from add-on modules. A "Growth bundle" quote that includes session replay, integrations, and mobile guidance should show each line item so you can selectively drop features that don't fit the use case.
Third, push for a pilot period before committing to a 12-month contract. Pendo's complexity means the implementation period is real, and you want to validate that the analytics workflow actually fits your team's process before you're locked in.
Fourth, ask specifically about the renewal escalation formula and whether multi-year pricing is available at the same feature tier. Pendo's sales team has flexibility on this, the standard contract isn't the only option.
The core question to answer before signing: is product analytics a strategic function at your company, or a support tool? If it's the former, Pendo is worth evaluating seriously. If it's the latter, there are better-priced tools for the actual problem you're trying to solve.
HappySupport addresses the guide maintenance problem that compounds with any MAU-based DAP: the cost of keeping in-app guides accurate when the product ships weekly. Where Pendo and similar tools require manual re-recording when the UI changes, HappySupport uses DOM/CSS recording to capture guides as structured metadata rather than pixel screenshots. HappyAgent connects directly to your GitHub repository and flags affected guides when deployments change the application state. For teams evaluating Pendo primarily because onboarding guides keep going stale after releases, HappySupport was built around that specific problem.
