Data-Driven In-Product Experiences
Diving deeper into
Pulkit Agrawal, co-founder of Chameleon, on software that drives product adoption
if you're going to be effective with in-product experiences, you need to have some good data
Analyzed 5 sources
Reviewing context
The key shift was that in app messaging stopped being generic training content and became a targeting problem. Once teams could see which users were stuck, which features they had touched, and where they dropped off, they could trigger a walkthrough, banner, or upsell at the exact moment it mattered. That is what moved the category from static tours toward product analytics tied directly to action.
-
WalkMe began as software layered on top of tools like Salesforce to train employees on fixed workflows. That model was useful for enablement, but it was mostly one size fits all guidance, not behavior driven personalization inside customer facing products.
-
Pendo and Appcues expanded the category by pairing guidance with usage data. In practice, that means a product team can segment users by behavior, show guides only to the right cohort, and then measure whether those guides changed feature adoption or completion rates.
-
The next step is unbundling. Chameleon argues analytics integrations are now table stakes, so the edge shifts to better orchestration, deeper integrations, and more native feeling experiences. Instead of owning all analytics, newer tools plug into Segment, Mixpanel, or the warehouse and focus on acting on that data inside the product.
This category is heading toward real time personalization. The winning products will look less like popup builders and more like decision layers that read product data, choose the right in app intervention, and make software feel different for a new user, a power user, and an upsell ready account.