Softwr

Customer Success · head to head

Appcues vs Arrows

Appcues logo

Appcues

Customer Success

In-app onboarding flows and product announcements built without engineering time

From
On request
Rated
-
Full reviewWebsite
Arrows logo

Arrows

Sales Enablement

AI agents that run a deal playbook and keep quiet pipeline moving, integrated with HubSpot and Salesforce

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Appcues appcues no longer publishes any prices; the pricing page shows tiers and limits but no dollar figures, so what used to be a self-serve purchase now requires a sales call and there is no way to compare cost against alternatives before contact.; Arrows the product has repositioned from HubSpot customer onboarding to AI-driven deal execution, so buyers acting on older recommendations may find the capability they were promised is no longer the focus of the roadmap.
  • They diverge on capability: Appcues covers No-code flow builder, Arrows covers Deal gameplan.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Appcues and Arrows actually diverge.

Attributes where Appcues and Arrows differ
AttributeAppcuesArrows
PlatformsWeb, iOS, AndroidWeb
CategoryCustomer SuccessSales Enablement

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Appcues

  • No-code flow builder
  • Onboarding checklists
  • Segmentation and targeting
  • NPS and in-app surveys
  • Mobile SDK
  • Experience analytics
  • Workflows
  • A/B testing of flows

Only in Arrows

  • Deal gameplan
  • Playbook definition
  • Rep workspace
  • Follow-through automation
  • CRM write-back
  • Research and preparation
  • Stakeholder tracking
  • Shared customer plans

What people use each for

The jobs each tool is most often brought in to do.

Appcues

  • A SaaS company whose trial-to-paid conversion stalls because new users never reach the action that demonstrates valuenot Arrows
  • A product team shipping a significant feature that needs an in-app announcement and walkthrough on launch day, not three sprints laternot Arrows
  • A customer success team wanting to replace repetitive onboarding calls with a self-serve checklist for smaller accountsnot Arrows
  • A team that needs contextual NPS or feedback prompts targeted at users who have actually used the feature in questionnot Arrows

Arrows

  • A HubSpot-centred sales team whose deal records go stale because reps update the CRM only when a manager asksnot Appcues
  • A sales organisation where a consistent playbook exists on paper but nobody applies it below the top five deals in each pipelinenot Appcues
  • A company where deals go quiet for weeks and nobody notices until the close date slips, wanting the follow-up to happen without a rep rememberingnot Appcues
  • A revenue leader onboarding new account executives who need the playbook applied to their pipeline from day one rather than learned over two quartersnot Appcues

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Appcues

  • Appcues no longer publishes any prices; the pricing page shows tiers and limits but no dollar figures, so what used to be a self-serve purchase now requires a sales call and there is no way to compare cost against alternatives before contact.
  • Published experience caps bite well before user limits do: Start allows only 10 live experiences and Grow only 25, so a mature product with tooltips across many features hits the upgrade trigger regardless of how many users it has.
  • Flows are DOM overlays pointed at elements in your live application, so a front-end refactor or a class name change silently breaks a walkthrough, and nobody notices until activation metrics drop.
  • Pricing scales with monthly active users, which means cost rises as the product succeeds, whether or not the additional users ever see an Appcues experience; the bill tracks your growth, not the tool’s contribution.
  • The platform reports on its own influence, so completion and goal metrics attribute activation to the flow without a proper counterfactual; justifying renewal on Appcues’ own numbers is circular unless you run holdout groups yourself.

Arrows

  • The product has repositioned from HubSpot customer onboarding to AI-driven deal execution, so buyers acting on older recommendations may find the capability they were promised is no longer the focus of the roadmap.
  • Pricing is not published and is scoped per engagement, so there is no benchmark, no self-serve entry, and two comparable buyers can be quoted materially different figures for the same product.
  • A scoping session is required before you get a number at all, which lengthens evaluation and makes it impossible to sanity-check budget before committing sales cycle time.
  • It depends on the CRM holding accurate deal and contact data; teams whose HubSpot or Salesforce hygiene is already poor get agents acting confidently on wrong information.
  • It is a small vendor in a category being entered by both CRM incumbents and well-funded agent startups, so betting a core sales workflow on it carries real continuity risk over a multi-year horizon.

Pricing, plan by plan

Appcues

On request
  • Start$undefined/month
    • Up to 3,000 monthly active users
    • 10 published experiences
    • 12 months reporting history
  • Grow$undefined/month
    • From 3,000 monthly active users upward
    • 25 published experiences
    • 24 months reporting history
  • Enterprise$undefined/year
    • Custom monthly active user volumes
    • 100 published experiences
    • 36 months reporting history
  • Spark$undefined/month
    • Programme for teams under 25 people
    • Intended for a first set of in-app experiences
    • Terms quoted on application

Arrows

On request
  • Arrows$undefined/year
    • Deal gameplans and playbook execution
    • Rep workspace
    • Automated follow-through and CRM updates

Which should you pick?

Choose Appcues if

  • You need no-code flow builder.
  • You work on Web, iOS, Android.
  • You also want onboarding checklists.
Appcues review

Choose Arrows if

  • You need deal gameplan.
  • You also want playbook definition.
Arrows review

Questions people ask

Is Appcues or Arrows better?
Neither clearly leads. Appcues starts at On request and Arrows at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Appcues or Arrows?
Appcues starts at On request and Arrows at On request.
Does Appcues or Arrows run on more platforms?
Appcues runs on Web, iOS, Android. Arrows runs on Web.
What is Appcues best used for?
Appcues is most often used for a saas company whose trial-to-paid conversion stalls because new users never reach the action that demonstrates value, a product team shipping a significant feature that needs an in-app announcement and walkthrough on launch day, not three sprints later, a customer success team wanting to replace repetitive onboarding calls with a self-serve checklist for smaller accounts, a team that needs contextual nps or feedback prompts targeted at users who have actually used the feature in question. Of those, a saas company whose trial-to-paid conversion stalls because new users never reach the action that demonstrates value and a product team shipping a significant feature that needs an in-app announcement and walkthrough on launch day, not three sprints later are not what Arrows is typically brought in for.
What can Appcues do that Arrows cannot?
Appcues covers No-code flow builder, Onboarding checklists, Segmentation and targeting, NPS and in-app surveys. Arrows covers Deal gameplan, Playbook definition, Rep workspace, Follow-through automation.

Answered from the vendors’ own pages

Appcues: How much does Appcues cost?

It no longer publishes prices. Start, Grow and Enterprise tiers show monthly active user limits and experience caps but no dollar amounts, and each routes to a call or a trial.

Arrows: Is Arrows still a customer onboarding tool?

It is now positioned around AI-driven deal execution rather than post-sale onboarding. Confirm with the vendor that the onboarding plans you want are still sold as you expect.

Appcues: Do I need a developer to install it?

A developer installs the snippet or SDK once and maps user properties. After that, building flows genuinely requires no engineering time.

Arrows: Do I need HubSpot?

HubSpot is the deepest integration and its historic home, but Salesforce is supported. It is a layer over a CRM, not a CRM replacement.

Appcues: What breaks flows?

Front-end changes. Because experiences are anchored to elements in your live DOM, refactors and renamed selectors break walkthroughs silently.

Arrows: How is it priced?

By scope of work and deal coverage, not per seat. The vendor runs a scoping session before proposing a figure, and nothing is published.

Appcues: What is the Spark programme?

A route for teams under 25 people shipping their first in-app experiences. Terms are quoted on application rather than listed.

Arrows: Does it replace my CRM?

No. It writes back into HubSpot or Salesforce and gives reps a workspace so they spend less time in the CRM interface.

Share

Related pages

More on Appcues

More on Arrows

Keep looking

Other head to heads