Most ProductFruits pricing articles describe the tiers. This one does the math. There's a difference: tier descriptions tell you what a plan is called. Math tells you what a team your size will pay annually, and what that number looks like when you factor in the maintenance work that no pricing page mentions.
ProductFruits is one of the more affordable Digital Adoption Platforms on the market. For early-stage SaaS teams that want structured onboarding without a five-figure contract, it's often the most defensible starting point. This article covers the current 2026 pricing structure, the per-MAU math at realistic team sizes, and the full three-year TCO calculation that reveals why the subscription cost is rarely the largest number in the equation.
What ProductFruits charges per plan
ProductFruits updated its pricing structure in early 2026. Three paid tiers, Starter, Pro, and Business, replace the older Sprout/Garden/Forest naming. All plans are priced on Monthly Active Users (MAU), with a slider on the pricing page adjusting cost as user count changes. Annual billing saves 25% over monthly rates.
These are the base prices at the 1,500 MAU entry point. As you move the MAU slider up on productfruits.com/pricing, the monthly cost increases. The pricing increments are not publicly listed per-tier, you need the slider to get an exact number for your user count. A 14-day free trial is available with no credit card required.
What each plan actually covers
Starter ($72/month annual at 1,500 MAU base)
The Starter plan covers the essential onboarding toolkit: product tours (15 max), tooltips (50 max), checklists (2 max), in-app announcements, and a basic knowledge base widget. It includes NPS surveys and 20 monthly AI text conversations for an AI-powered assistant layer. At 1,500 MAU on annual billing, the Starter plan costs $864/year, which is the most competitively priced entry point in the DAP category for small teams.
The limits on Starter are real: 15 tours means you can document 15 distinct flows, which covers most seed-stage products. When your product grows past that, you're either upgrading to Pro or living with coverage gaps. The 2-checklist limit is the most constraining for teams running multi-step activation workflows. If your onboarding program requires more than two distinct checklists, Pro is the effective entry tier.
Pro ($112/month annual at 1,500 MAU base)
Pro removes most of the Starter limits: 100 tours, 500 tooltips, unlimited checklists, and 10 active knowledge base sources. It adds advanced user segmentation (20 segments), 5-language localization, custom CSS for branding control, advanced analytics, and deeper integrations including Intercom, HubSpot, Mixpanel, Amplitude, Slack, and Zapier. At 1,500 MAU on annual billing, Pro costs $1,344/year.
Pro is the right tier for teams with a complex product that has multiple distinct user types (each needing a different onboarding path), international users (requiring localized guides), or a content team that needs to brand the help experience consistently. For most Seed and early Series A SaaS companies, Pro covers the full onboarding program without needing enterprise features.
Business (custom pricing)
Business tier removes all limits: unlimited tours, tooltips, checklists, 40-language support, 400 monthly text conversations, voice onboarding (100 minutes), 100 knowledge base sources, unlimited segments, white-label customization, dedicated support, custom SLAs, and security audits. The pricing is custom and requires a sales conversation. Business is the tier for multi-product deployments, enterprise security requirements, or white-label use cases where the ProductFruits interface needs to disappear entirely behind your branding.
The per-MAU math at real team sizes
Running the numbers at realistic MAU counts reveals where ProductFruits is genuinely affordable and where it starts to require a harder ROI conversation.
- 1,500 MAU, Starter annual: $864/year, roughly $0.048/MAU per month. This is the most defensible price point. For early-stage products testing whether onboarding flows move activation rates, the cost is low enough to experiment without a significant budget commitment.
- 3,000 MAU, Starter annual: Based on the tier structure, annual cost moves to the $1,400-$1,600 range. Still competitive within the DAP category for basic flows.
- 5,000 MAU, Starter/Pro: Annual cost climbs to approximately $2,000-$2,500 depending on plan. At this range, you're in the same budget territory as many Help Center tools, which serve a different but overlapping documentation need.
- 10,000 MAU: Pricing at this scale typically hits $4,000-$5,000+ annually before considering Business-tier features. More than many small-team support stacks for comparison.
For exact numbers at your user count, use the slider directly on the pricing page. The ranges above calibrate expectations, they are not quotes, and MAU band pricing changes with each tier transition.
Comparing ProductFruits to other DAPs at equivalent price points
At the Starter price point, ProductFruits has no direct competition at equivalent feature depth. Pendo's free tier covers up to 500 MAU with limited features. Userpilot's Starter is $299/month ($3,588/year), covering up to 2,000 MAU but with a significantly higher entry price. For teams under 3,000 MAU with a limited tooling budget, ProductFruits occupies essentially a category of one for functional DAPs with transparent pricing.
The no-developer-required setup is one of ProductFruits' most practical advantages. Most teams can have their first tour running within a day using the JavaScript snippet or npm package install. No custom event tracking configuration, no engineering sprint to deploy the guide system. For teams without a dedicated engineering allocation for tooling setup, this is a meaningful difference.
The cost the pricing page doesn't show
ProductFruits captures product tours using screen recording. Every guide is a snapshot of your UI at the moment you recorded it. When your product ships a change, a button moved, a menu renamed, a flow restructured, affected guides show the old state until someone on your team finds and re-records them manually. ProductFruits does not detect this automatically at any tier.
According to the GitLab DevSecOps Survey, 65% of software teams ship weekly releases or more frequently. A team with 25 documented flows on that cadence has a standing maintenance obligation: identify which guides broke, re-record them, and verify the updated versions before users encounter the stale ones.
This is the documentation decay cost, and it applies to every screen-recording-based tool, not just ProductFruits. At a conservative two hours per week of guide maintenance at $60/hour, that's $6,240/year in labor alongside the subscription. At 5,000 MAU, the subscription might be $2,400/year. The maintenance labor runs more than twice that.
Stale in-app guides don't just waste maintenance time. They actively undermine the activation rates the tool is supposed to improve: a product tour pointing to a button that moved leaves new users confused at the exact moment you're trying to show them the product's value.
How to calculate your real ProductFruits maintenance overhead
The subscription cost is fixed and visible. The maintenance cost requires a calculation. Here's how to do it with your actual numbers before committing to an annual contract.
Take your planned guide library size. Estimate the fraction that are product-UI-facing (showing your actual product's interface, as opposed to generic process documentation). Multiply by your releases per year: weekly cadence is roughly 50 releases. Estimate the hit rate per release: for an actively developed product, 20-30% of releases touch at least one documented UI element. Multiply by time to re-record an affected guide: typically 20-40 minutes for a simple flow.
An example calculation: 30 product-facing guides, weekly releases, 25% hit rate, 30 minutes per update event. That works out to roughly 90-100 update hours per year. At $60/hour loaded cost, that's $5,400-$6,000/year in maintenance labor on top of the subscription. If the subscription is $1,344/year at Pro, the real annual cost of the deployment is around $6,700-$7,300. The pricing page shows less than 20% of that number.
Three-year total cost of ownership
The one-year view understates the real cost. The three-year TCO makes the maintenance overhead more visible because it compounds.
- Year 1: ProductFruits Pro at 1,500 MAU: $1,344. Maintenance labor: $5,400-$6,000. Year 1 TCO: $6,744-$7,344.
- Year 2: MAU growth to 3,000, subscription approximately $1,800-$2,000. Maintenance overhead grows with guide library: $6,000-$7,500. Year 2 TCO: $7,800-$9,500.
- Year 3: MAU at 6,000, subscription approximately $2,400-$3,000. Maintenance overhead: $7,000-$9,000. Year 3 TCO: $9,400-$12,000.
- Combined 3-year TCO estimate: $24,000-$29,000 for a product scaling 1,500 to 6,000 MAU on a weekly release cadence with 30 active guides.
For context: that three-year cost includes zero Help Center infrastructure. ProductFruits is not a searchable Help Center with category navigation, SEO optimization, or the self-service infrastructure customers expect when they're looking for answers independently. Teams that also need that layer run a second platform alongside ProductFruits, which adds both subscription cost and maintenance overhead.
When ProductFruits makes sense financially
ProductFruits is a solid choice when the conditions align: under 5,000 MAU, a product UI that changes infrequently (meaning your flows stay stable between releases), and a use case focused on initial onboarding rather than ongoing contextual help. For that combination, the subscription pricing is competitive and the maintenance overhead is manageable.
For seed-stage and early Series A teams with under 2,500 MAU and a lean, stable product, the Starter tier at $864/year is genuinely difficult to argue against. It sets up without developer involvement and covers the essential onboarding primitives: tours, checklists, in-app hints, at a fraction of what enterprise DAPs charge. For teams that are unsure whether structured onboarding moves their activation metrics, this is a low-risk way to find out.
When the math doesn't hold
The value calculation weakens when three conditions stack up together: high MAU counts, frequent releases, and documentation spread across both in-app guides and a Help Center.
ProductFruits is active guidance: walkthroughs and tooltips that live inside your product. Teams that also need users to find answers independently still need a separate Help Center tool. At 10,000 MAU, combining ProductFruits with a Help Center typically pushes the annual documentation budget past $8,000-$10,000 for basic coverage, with two separate systems both requiring manual updates after every UI change.
The subscription cost line is one number. The maintenance labor across both systems is a larger one that doesn't appear until someone starts tracking time spent on documentation maintenance in quarterly reviews.
ProductFruits pricing vs. alternatives: what you actually get per dollar
The most useful cost comparison isn't plan name vs. plan name. It's: what does each tool deliver at your actual user count, and what does each cost for that user count?
At 1,500 MAU: ProductFruits Starter at $864/year is roughly 4x cheaper than Userpilot Starter ($3,588/year) for a comparable user count. Pendo's minimum paid tier starts at $7,000-$12,000/year community-reported. For teams at this MAU range, ProductFruits isn't just the budget option, it's the only sensibly priced paid DAP.
At 5,000 MAU: ProductFruits runs approximately $2,000-$2,500/year. Userpilot Growth (custom) typically runs $10,000-$15,000/year at this count based on community data. Pendo Growth runs $20,000-$30,000/year. If the feature set you need is product tours, checklists, tooltips, and basic NPS, ProductFruits delivers it at 15-20% of the Pendo cost for a 5,000 MAU product. If the feature set you need includes A/B testing, advanced funnel analytics, or session replay, Pendo's cost is justified by capability that ProductFruits doesn't offer.
The decision framework is simpler than most comparison articles make it: what specific feature do you need that the cheaper tool doesn't have? If the answer is "nothing on this list matters to us right now," start with ProductFruits. The switching cost is low, the price difference is significant, and you can always move up when you've validated that in-app onboarding is actually moving your activation metrics.
The counter-argument to starting cheap: if your product is growing fast and you expect to hit the ProductFruits limits within 6-9 months, the onboarding investment of migrating platforms (rebuilding all your flows in a new editor) may outweigh the cost savings. Evaluate your expected MAU trajectory before committing. A team at 1,500 MAU growing 30% month-over-month will be at the Userpilot level within a year. Starting there directly may be worth it.
How ProductFruits pricing scales: the MAU slider in practice
Unlike tools with rigid tier cutoffs that trigger abrupt price jumps, ProductFruits uses a continuous MAU slider for pricing. This is one of the more buyer-friendly pricing mechanics in the DAP category: you can see your exact price at any MAU count before entering a sales conversation. No "contact us for pricing" above a certain size.
The slider adjusts in MAU bands, not individual users, and the increments aren't published per-band. What this means practically: budget predictability is good, but you'll need to check the slider regularly as your user base grows to catch when you're approaching the next price inflection point. Setting a calendar reminder to check your current MAU count against the slider every quarter is worth doing before annual renewal.
The annual billing discount is consistently 25% across all tiers. That's a more significant discount than many SaaS tools offer (typically 15-20%), making the annual vs. monthly comparison particularly favorable. At $864/year vs. $1,152/year for Starter at 1,500 MAU, the $288 annual saving is meaningful at the price point. For teams that are certain they'll use the product for at least six months, annual billing is the obvious choice.
ProductFruits free trial: what 14 days actually tells you
The 14-day free trial with no credit card required is one of ProductFruits' most useful onboarding features. It gives you enough time to build at least one complete onboarding flow from scratch, test it with internal users, and evaluate whether the editor fits your team's workflow before committing to a subscription.
What a useful trial looks like: pick one specific onboarding flow that's currently broken or missing (a key feature that new users frequently miss, a workflow that generates recurring support tickets), build the tour in ProductFruits, and measure whether internal testers can complete the flow successfully without help. If yes: the tool works for your use case. If no: evaluate whether the issue is the tool's limitations or the guide's design, and decide accordingly.
What a wasted trial looks like: clicking around the editor without completing a real flow, then signing up because the editor felt intuitive. The real test is whether the guide works at the UI state your product is actually in today, and whether it will still work after your next release. The trial period can't fully answer the second question, but it can give you a baseline for how quickly re-recording is needed after a typical release.
What to verify before signing
Three numbers to know before committing to an annual ProductFruits contract: your current MAU count (for an accurate price from the slider), your product release cadence (to model maintenance time), and how many flows you expect to document (which determines maintenance scope).
If you ship weekly and plan to document more than 20 flows, calculate the annual labor cost of guide maintenance alongside the subscription. That sum tends to be the more informative cost comparison, especially when evaluating tools that handle the maintenance problem differently.
HappySupport takes a different approach to self-updating documentation: guides built on DOM/CSS code recording rather than screenshots update automatically when the product ships, without manual re-recording after each release. If guide maintenance overhead is the primary concern, that's worth comparing against any subscription cost in this category.
