Studio or Agent? How to Choose Your Userflow Starting Point

Two Userflow products, two approaches to adoption. Here's how to figure out which one fits your team, your users, and where you need to move the needle first.

Christy Huggins

July 1, 2026

Announcements

Adoption

Activation

I hear this a lot from teams evaluating Userflow:

"We need to guide users better. Where do we start?"

It's the right question. It's also harder to answer than it sounds, because the real answer depends on something more fundamental: where do your users need the most help right now, and when?

That question is exactly what Adoption Studio and Adoption Agent are designed around. These aren't two versions of the same product. They're two approaches to the same goal. You can use one, the other, or both—but which makes sense for you depends on your team, your users, and where you're trying to move the needle first.

Here's how to think through it.

Key Takeaways

Studio and Adoption Agent are two distinct products built for different teams and different adoption strategies. Neither is a stepping stone to the other.
Studio is proactive: you configure the triggers, conditions, and targeting, and it deploys experiences in-app automatically.
Adoption Agent is responsive: a user sends a question, our Agent reads it, selects the right flow from your library, and guides them through it. If no matching flow exists, it answers from your trained docs and knowledge base.
Both products use the same flow library. Build a flow once; the difference is how it reaches users.
Product and marketing teams typically start with Studio. Customer success teams typically start with Adoption Agent.
Most teams end up wanting both. You can start wherever your most pressing problem is and expand from there.

Studio vs. Adoption Agent at a Glance

	Adoption Studio	Adoption Agent
What is it	The proactive product. You configure the triggers, conditions, and targeting—Studio deploys experiences automatically.	The responsive product. A user sends a question, Agent selects the right flow and guides them through it.
When	On your criteria: page, event, attribute, segment, behavior, schedule	On the user's question: inbound chat triggers everything
What You Configure	Everything—segments, triggers, timing, content, A/B tests	Your knowledge sources and flows; Adoption Agent handles the matching
Who it's for	Product and marketing teams looking to trigger onboarding and adoption flows based on specific customer usage or data	Customer success teams, and product teams who want on-demand coverage
Full content suite	Checklists, surveys, NPS, banners, tours, launchers, A/B testing, analytics integrations	Chat, suggested flows, knowledge base trained on your docs
What's included	All the features and functionality you need to to craft flows and proactively drive adoption at specific points in the customer journey. Scale based on how many users you reach.	Everything you need for Adoption Agent to show your users how to reach their goals, not just send them to a help article. Scale based on how many credits you use.
Price	$500/mo ($400 billed annually)	$100/mo ($80/billed annually)

Both products use the same flow library. You build a flow once; what changes is how it reaches users. Studio deploys it proactively, on your criteria. Adoption Agent surfaces it on-demand, in response to a question.

That distinction is the whole ballgame.

Studio + Agent = Your Complete Production Adoption Engine

Most teams end up wanting both. You can start wherever your most pressing problem is and expand from there.

The two products share the same flow library, so whatever you build for one, you've already built for the other. Studio users who add Adoption Agent get proactive coverage where they've designed it, plus responsive coverage everywhere else. Adoption Agent users who add Studio get the first-touch and lifecycle layer they didn't have before. Together, they cover the full adoption surface: guiding users before they ask, and meeting them when they do.

Frequently Asked Questions

What's the difference between Adoption Studio and Adoption Agent?

Studio deploys in-app experiences proactively, based on triggers and conditions you configure. Adoption Agent activates when a user sends a chat: it reads the question, selects the most relevant flow from your library, and guides them through it. Studio is for teams who want to reach users before they ask. Adoption Agent is for teams who want to meet users when they do.

Do I have to choose one or can I use both?

You can buy either product on its own, or both together. Most teams start with the one that solves their most urgent problem and add the second later. Because both products share the same flow library, anything you build for one is automatically available to the other.

Can Adoption Agent guarantee a flow for every question?

No. Adoption Agent surfaces the most relevant flow from your library when one fits the question. When no matching flow exists, it answers from your trained docs, knowledge base, and URLs. The more Flows you've built, the more often users get in-product guidance rather than a text answer.

‍Which product is right for a product team?

Most product teams prefer to use the full Adoption Engine platform, but many start with Adoption Studio. It gives you the targeting, triggers, A/B testing, and full content suite for proactive in-app adoption at scale. That said, if your product has a chat or help widget and your team is fielding a lot of on-demand questions, Adoption Agent can complement Studio or stand alone.

Which product is right for a customer success team?

CS teams typically start with Adoption Agent. It scales your team's ability to handle on-demand questions without adding headcount, and it surfaces in-product flows at the moment a user asks for help rather than sending them to documentation.

Can I start a free trial for either product?

Yes. Both Adoption Studio and Adoption Agent are available to try. Start your free trial here →

Ready to guide your users—before they ask, or when they do? Start your free trial → or see pricing →