Appcues vs Lightdash
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.
Lightdash chips away at the SQL barrier with NL-to-formula table calcs and metric-tree visualization.
The release cadence is high and the work spans three areas: lowering the technical barrier (spreadsheet-style formulas in table calculations, plain references to grand totals), enriching what a chart and dashboard can express (color palettes at every scope, row/column limits, rich-text table cells), and self-serve operability (default user spaces, expiring preview projects, dashboard-version rollbacks that include chart configs). The Canvas now hosts persistent metric trees, hinting at a heavier semantic-layer story.
Lightdash is positioning between a dbt-native semantic layer (where SQL-fluent analysts live) and a self-serve BI tool (where business users live). The intent-driven formula editor and reference-total functions chip away at the SQL prerequisite for table calculations, while Saved Trees push the metric model into something visually editable. Underneath, the platform is doing the unglamorous self-serve work — personal spaces, palette hierarchies, preview hygiene — that BI products need to survive in larger orgs.
Expect the formula editor to grow into broader AI-assisted authoring (filters, joins, custom dimensions) and Saved Trees to evolve into a more general semantic-layer view that consumes from dbt and produces governance artifacts. Color and palette work suggests embedded/customer-facing BI ambitions next.
See more alternatives to Appcues →
See more alternatives to Lightdash →