Appcues vs Fulcrum
Side-by-side trajectory, velocity, and editorial themes.
Appcues drops Embeds — in-product experiences that live inside the UI rather than overlay it.
Appcues is a product-adoption platform whose recent quarter has run two parallel storylines. Captain AI, the in-product assistant, has gone from a chat helper to something that drafts segments, analyzes funnels, diagnoses display problems, and explains performance — adding capability essentially every monthly release. Alongside that, the team has expanded the experience surface itself: an MCP Server that exposes Appcues data to ChatGPT and Claude, and Embeds — a new experience type that lives inside the product UI rather than as an overlay.
Appcues is reframing what an 'in-product experience' tool covers. Embeds break the long-standing overlay-only model that defines the category (Pendo, Userpilot, Chameleon all anchor on overlays). MCP exposes the same data surface to external AI tools, which makes Appcues a source as well as a destination. Captain AI keeps absorbing operator tasks — segmentation, funnel analysis, install diagnostics — turning the product manager's in-tool workflow into more of a conversation than a configuration session.
Expect Captain AI to start fully building things autonomously rather than drafting (the team teased this in the January notes), and for Embeds to gain a bigger pattern library now that the underlying primitive is shipped. The MCP server integration line will likely grow with more bidirectional actions exposed to external AI tools.
Fulcrum tightens its field-first story: lasso selection, offline KML layers, Intune auth.
Fulcrum is shipping weekly across iOS, Android, and web with a consistent theme: more direct manipulation on the map, more offline resilience, and broader enterprise auth. The Lasso Tool is the standout — freehand selection on the map with bulk edit, export, and delete actions. KML/KMZ layers can now be cached for offline use on both mobile platforms, and Intune users can finally authenticate with Microsoft Authenticator. A custom Power BI connector landed in the prior cycle.
The direction is clear: Fulcrum wants the map to be the primary work surface for field teams, not the records list. Expect more map-side bulk operations (assignment, status changes, geofence-based actions) and continued offline parity work. Enterprise auth and BI integrations are also picking up cadence, suggesting a push into larger field-services accounts where SSO and Power BI footprint matter.
Within the next two release cycles expect a saved-lasso/saved-selection primitive (so the freehand selection can drive recurring workflows) and an extension of offline caching to vector tiles or MBTiles. The Power BI connector will likely be joined by a Tableau or Snowflake equivalent.
See more alternatives to Appcues →
See more alternatives to Fulcrum →