Choose a SaaS user engagement platform by the job it must do first

Most of the platforms below now offer guidance, analytics and surveys in some form, so feature lists no longer separate them. What still separates them is the job each was built around, the team it expects to run it and the unit it charges by. For a B2B product, decide which job comes first, then shortlist the tools built for that job.

At Tcules, we do not sell or resell any of these tools and have no affiliate relationship with any vendor named here. We have not used them for this article: every feature, plan and price below comes from the vendor's own pages, linked inline and checked on 13 October 2026. Plans change, so check the linked page before you rely on a figure.

Choose by the first job, not the feature list

A user engagement platform can do three different jobs inside a product:

• Guiding new accounts to value. Tours, checklists, tooltips and announcements that move a new account through setup to the first result it bought the product for.
• Understanding behaviour. Event and path analytics that show which accounts reach value, which stall and where.
• Talking to users in the product. Messages, support conversations, surveys and research prompts, where the response matters as much as the send.

The vendors' own pages show how far these have converged. Pendo sells analytics and in-app guides together. Amplitude, an analytics company, added in-app guides and surveys after acquiring Command AI in October 2024. Guidance tools such as Userpilot now include product analytics and session replay, and Intercom, built for support, sells product tours and surveys as an add-on.

Convergence makes the choice harder, not easier. Our judgement, which the pricing pages support but cannot prove, is that each platform still has a centre where its depth sits and a periphery that covers the rest well enough for a demonstration. Buying a tool for its periphery is the expensive mistake: an analytics platform bought mainly for onboarding tours, or a support messenger stretched into a product analytics system.

Two questions settle most shortlists:

1. Which job has to work first? If new accounts are not reaching value, guidance comes first, but only after you know which behaviour counts as value. If you cannot yet say which accounts are succeeding, analytics comes first. If you already know where people struggle and need to reach or hear from them, messaging and surveys come first.
2. Who will run it every week? A tool that product or growth managers can operate without engineering tickets fails differently from one that assumes an analyst, a support team or a customer success team. The pricing unit is a good clue: a tool priced per support seat expects a support team.

In a B2B product, value can belong to an account rather than a person. An account may count as activated only when an administrator has configured it and several roles are working in it. Whatever you choose must know which account a user belongs to, and on some platforms that capability costs extra (see [What it will cost](#what-it-will-cost)).

Before choosing any tool, define the behaviour that represents value, for the account as well as for each role in it. Without it, every platform below will measure and prompt activity, and activity is not the goal.

Guiding new accounts to value

These tools are built around in-app experiences that product, growth or customer teams can publish without a release. They suit a product whose path to value is sound but not obvious to a new account. They cannot repair a path that the product itself blocks.

**Userpilot** combines guidance with a growing analytics layer. Starter is listed at $299 a month for up to 2,000 monthly active users (MAU), with flows, checklists, segmentation, usage trends and an NPS survey. Growth starts at $849 a month and adds funnels, retention and path analysis, event autocapture, the resource centre, advanced surveys, email and session replay. In the plan table, HubSpot and Salesforce integrations are add-ons on Growth. It suits a team that wants guidance and first-level analysis in one place and will not need a separate analytics platform soon.

**Appcues** does not publish prices. Plans are named Start (up to 3,000 MAU), Grow (from 3,000 MAU) and Enterprise, and the page says pricing depends on MAU, number of installations and published experiences. The tiers cap published experiences at 10, 25 and 100 respectively, while every plan includes every experience type, feature and integration. The page also says every customer receives implementation services and a dedicated experience manager. It suits a team that wants a guided start and expects a modest number of well-chosen experiences rather than dozens.

**Userflow** now lists two self-serve plans, each with 1,000 MAU and unlimited team members: Essentials at $240 a month billed annually ($300 billed monthly), and Studio at $400 a month billed annually ($500 billed monthly), which adds all integrations including HubSpot and Salesforce, custom event trackers and a third environment. Further MAU are billed in blocks of 1,000, from $40 a month per block falling to $10 at volume. The pricing page says customers on its older Startup and Pro plans keep them. It suits a smaller team that wants predictable, published pricing and many people able to build.

**Chameleon** charges by monthly tracked users (MTU), which it defines as uniquely identified user profiles sent to Chameleon in the prior 30 days. Its Startup plan starts at $279 for 2,000 MTU; Pro is listed at $750 a month for 5,000 MTU with up to 20 live experiences; Growth, from $1,250 a month for 5,000 MTU billed annually, adds unlimited live experiences and governance features. Its plan table centres on experiences, targeting, testing and governance, and lists more than 30 integrations, including Mixpanel and HubSpot. Our reading is that it suits a team that already has a product analytics tool and wants a strong guidance layer on top.

**UserGuiding** publishes one of the lower entry prices in this group: Starter from $249 a month billed yearly for up to 2,000 MAU, Growth from $499 a month billed yearly, and a custom quote above 2,000 MAU. The limits sit in active items: Starter allows 15 active guides but one active checklist, one survey and one resource centre. It suits an early product that needs basic onboarding now and can accept those limits.

Guidance also adds a dependency on your front end. Anchored tooltips and tours find their place in the page through selectors. Appcues' documentation states that renaming a class, removing an element or restructuring the page breaks dependent content silently, and it recommends dedicated attributes such as `data-appcues`. Pendo's help centre similarly advises adding static classes and IDs because dynamic selectors can change with a new version of the application. "No-code" describes who builds the content, not who keeps it working after each release.

Understanding behaviour

These platforms start from analytics and add guidance to it. They suit a team whose first problem is not knowing which accounts succeed, or a team that wants guidance targeted on detailed behaviour.

**Pendo** has a free plan for up to 500 MAU, with analytics, in-app guides and Pendo-branded NPS surveys. Paid plans (Base, Core and Ultimate) are quote-only and priced by MAU and chosen functionality. Core adds session replay; Ultimate adds surveys, journey orchestration and feedback tools, which are paid add-ons on the lower plans. Pendo says pricing is not affected by the number of applications tracked, and that analytics are retroactive from the day it is installed. Its data model includes visitor and account metadata, which matters for account-level questions. It suits a product team that wants analytics and guidance from one vendor and can go through a sales process.

**Amplitude** prices analytics by events. The free plan covers 2 million events a month; Plus starts at $0 for the first 2 million events and scales to 70 million; Growth and Enterprise are custom. According to Amplitude's Guides and Surveys page, guides and surveys are priced by the number you create rather than by users or events, and are an add-on on Plus or bought with Growth and Enterprise. The pricing page's comparison table lists one guide or survey on the free and Plus plans. Account-level analytics ("Accounts") is listed for Growth and Enterprise only. It suits a team where an analyst or product manager already works in event data and wants guidance targeted from the same cohorts.

**PostHog** meters each product separately, with a free allowance that resets monthly: 1 million analytics events, 5,000 session recordings and 1,500 survey responses among others. Beyond the first million, analytics events start at $0.00005 each, identified events add $0.000198 each, and group analytics, its account-level feature, adds $0.000071 per event, with each rate falling at higher volumes. Product tours do not appear among the priced products on the pricing page, so treat in-app guidance there as unconfirmed. It suits a team where engineers will own the instrumentation and want analytics, feature flags, experiments and surveys in one stack, with guidance from elsewhere if needed.

Talking to users in the product

These tools are built around a conversation or a question: support, proactive messages, customer success outreach and research. Each assumes a different team runs it.

**Intercom** is a customer service platform priced per seat: Essential at $29 per seat per month billed annually ($39 monthly), Advanced at $85 ($99), Expert at $132 ($139), plus $0.99 per outcome for its Fin AI agent. All plans include banners and tooltips. Product tours, surveys, in-app messages and checklists belong to the Proactive Support Plus add-on, listed at $99 a month including 500 messages, with further messages charged per unit. It suits a product where the support team is the main voice in the product and proactive messages are an extension of support.

**Gainsight PX** does not publish prices. Gainsight lists product analytics, in-app guides and engagements, an in-app hub and surveys, across web, mobile and desktop, and describes the product as informing roadmap and customer health decisions. Our judgement is that it fits best where customer success owns adoption and the company already uses Gainsight's customer success platform, though we have not verified how deep that connection goes.

**Sprig** is a research tool rather than an engagement tool. It publishes no prices; the page says pricing scales with the research programme, by response volume, capabilities and deployment environments. It suits a product with a research or design team that needs in-product studies and analysis. Most platforms above include basic NPS and microsurveys, which can be enough when the aim is a score rather than a study.

Adoption across enterprise software

Digital adoption platforms (DAPs) guide people through software they must use, including internal systems. Both vendors below sell a separate offering for customer-facing applications, so they will appear on some B2B SaaS shortlists.

**WalkMe** lists two offerings, one for employees and one for customer-facing applications, both on quote only. SAP completed its acquisition of WalkMe on 12 September 2024.

**Whatfix** lists Standard, Premium and Enterprise plans on quote only, each priced as a flat fee plus user licences. For customer-facing applications a licence equals a monthly active user; for employee-facing applications it equals every user with access.

Our judgement is that a DAP earns its place on a SaaS vendor's shortlist when the same organisation also needs adoption support across internal software, or when procurement prefers one enterprise vendor for both. For guiding customers through your own product alone, the tools in the first two groups are built more directly for the job.

What it will cost

The licence is only part of the decision. What matters is which unit you are billed on and how that unit grows as your customer base does.

"Built around" and "usually run by" are our reading of each vendor's pages, not vendor claims. Four points follow from the billing units.

• User-based pricing depends on the definition of a user. Pendo counts unique visitors active in the last 30 days; Appcues counts users who sign in during the month; Chameleon counts identified profiles sent to it. Where the count is what you send, you may be able to limit it to the users you intend to guide. Ask how each vendor counts a user who signs in once a quarter.
• Account-level data is sometimes an extra. Amplitude lists account analytics for Growth and Enterprise only, PostHog charges per event for group analytics, and Mixpanel lists group analytics as an add-on. For a B2B product that needs account-level answers, this is a requirement, so price it from the start.
• Guidance tools cap what is live. Appcues caps published experiences, Chameleon's Pro plan caps live experiences at 20, and UserGuiding caps active checklists and surveys. Count how many experiences you expect to run at once, including those for existing customers.
• The running cost sits outside the licence. Someone must write and retire content, engineers must keep targeted elements stable across releases, and moving vendors means rebuilding content. Appcues and UserGuiding both offer migration support, which suggests switching takes real work.

Checks before you sign

1. Name the value moment. Write down the account-level behaviour that shows a customer is getting what they bought. If you cannot, start with analytics or research, not guidance.
2. Name the weekly owner. Choose the person who will build, review and retire content, and check that the tool's seats, roles and pricing suit them.
3. Test account-level questions in the trial. Ask the tool which accounts reached the value moment this month and which roles within them have not started. If it cannot answer, or answers only with an add-on, include that in the price.
4. Agree targeting with engineering. Decide which elements will carry stable attributes for guidance, and add a check for guidance dependencies to your release process.
5. Price three years of growth. Model your billed unit at today's volume, at double and at the volume in your plan. Ask for renewal terms in writing where prices are not published.
6. Plan for fewer, better experiences. Chameleon's 2025 benchmark report, drawn from its own customers' data, reports that tours beyond five steps lose the attention of more than half of users, and that tours users start themselves get double the engagement of automatically triggered ones. That is one vendor's data, but it points the same way as the rest of this article: guide at the moment of need, briefly.
7. Know when guidance is the wrong fix. If new accounts stall because setup depends on data, roles or decisions the product does not support, a tour will describe the obstacle without removing it. Our SaaS onboarding guide covers the path before first value, and if accounts stall in the work around the product, such as security reviews, data migration or partner tasks, see customer onboarding software for B2B SaaS.

How this list was compiled

We chose platforms that a B2B SaaS team is likely to meet when searching for in-app guidance, product analytics, in-app messaging or surveys, and grouped them by the job each is built around. There is no score or ranking, and the order within each group carries no meaning. Every product fact comes from the vendor's own pages as they appeared on 13 October 2026; where a vendor publishes no price, we say so rather than estimate. No tool was used for this article, and we at Tcules have no commercial relationship with any vendor named.

This decision sits between product design and measurement

An engagement platform adds a layer to your product; it does not replace the product's own path to value. When you cannot yet tell whether accounts are stalling because value is missing, use is blocked or the offer is wrong, a UX Product Audit follows the affected workflow and investigates the cause before you buy a layer to address one of them. Where engagement depends on the underlying workflow model, see B2B SaaS and Workflow Software. Keeping guidance, tracking and interface in step across releases is implementation QA.