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.
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.
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. For early-stage products testing whether onboarding flows move activation rates, the cost is low enough to experiment.
- 3,000 MAU, Starter annual: 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.
- 10,000 MAU: Pricing typically hits $4,000-$5,000+ annually before considering Business-tier features.
For exact numbers at your user count, use the slider directly. The ranges above calibrate expectations — they are not quotes.
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.
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 every release cycle.
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.
The Pendo Product Benchmark Report found poor documentation is among the top reasons users fail to complete feature activation. Stale in-app guides don't just waste maintenance time — they actively undermine the activation rates the tool is supposed to improve.
When ProductFruits makes sense financially
ProductFruits is a solid choice when the conditions align: under 5,000 MAU, a product UI that changes infrequently, 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.
The OpenView PLG Index consistently shows that product-led teams get the best returns from onboarding investments when they can maintain guide accuracy over time. ProductFruits delivers the tooling. Maintaining it requires a clear process for catching and updating stale content after each release.
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 hard to argue against. It sets up without developer involvement and covers the essential onboarding primitives at a fraction of what enterprise DAPs charge.
When the math doesn't hold
The value calculation weakens when three conditions stack: high MAU counts, frequent releases, and documentation spread across both in-app guides and a Help Center.
ProductFruits is not a searchable Help Center. It creates 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.
What to verify before signing
Three numbers to know before committing to an annual contract: your current MAU count, your product release cadence, and how many flows you expect to document. If you ship weekly and plan to document more than 20 flows, calculate the annual labor cost of guide maintenance alongside the subscription.
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. More at happysupport.ai.
