In-App Assistants Rule: Sell the Journey Map, Not the Tour Builder
When a client asks for in-app onboarding help, should the agency scope the work around deploying a guidance tool or around the segmentation and iteration that makes the guidance work? Scope in-app assistant engagements around segmentation, journey mapping, and iteration cadence, and treat the guidance tool as the delivery mechanism rather than the deliverable.
By InnovaAI ResearchPublished Updated
“When a client asks for in-app onboarding help, should the agency scope the work around deploying a guidance tool or around the segmentation and iteration that makes the guidance work?”
Scope in-app assistant engagements around segmentation, journey mapping, and iteration cadence, and treat the guidance tool as the delivery mechanism rather than the deliverable.
Agencies quote the build (tour count, tooltip count, checklist count) and hand over a configured workspace, then discover the client's own product manager can clone the setup in a week, leaving no reason to renew the retainer. The tool gets blamed for the churn when the real gap was the absence of segment-level analysis and an iteration loop the client could not run alone.
The category description is explicit that the commoditization risk sits in the tool itself, since clients can self-serve no-code builders like Chameleon, UserGuiding, and Userflow, so the defensible work is the surrounding insight. That framing matches the wider market: 83% of B2C marketing decision makers already work with AI agents, which means tool access is a baseline expectation rather than a differentiator an agency can bill a premium for. The same pattern shows up in adjacent disciplines, where the value has shifted from owning a platform to owning the context and governance around it, as seen in the push for private AI deployments that preserve differentiation and in the formalization of agent scaffolding as a distinct engineering discipline.
- •A client asks for product tours, tooltips, or checklists as a line item on a retainer or post-launch optimization project.
- •The client's product team has already trialed a no-code builder such as UserGuiding or Userflow on a free tier and believes the remaining work is configuration.
- •Feature adoption data exists but nobody has mapped which user segments stall at which step of the journey.
- •The engagement is priced per tour or per tooltip rather than against a retention or activation metric.
- •The client has an in-house product manager who could plausibly self-serve the tool within two quarters.