On this article

Before You Build 50 In-App Guides, Build These 5

Don’t build 50 in-app guides. Build the 5 that drive activation, adoption, fewer tickets, clear comms, and fresh feedback.
This is some text inside of a div block.

Before You Build 50 In-App Guides, Build These 5

It’s tempting to treat in-app guides like a checklist: tooltip every feature, tour every screen, celebrate the coverage. The result is a product that nags more than it helps and guides no one reads. The better approach is the opposite, fewer guides, each doing one clear job.

For a B2B SaaS product, five in-app guides consistently earn their place: a first-value walkthrough that drives activation, a new-feature pin that drives adoption, a “stuck” helper that cuts support tickets, an announcement banner that keeps users informed, and an in-context survey that captures feedback while it’s fresh. Each one targets a single audience, a single moment, and a single outcome, and if you can’t name what a guide is supposed to change, you shouldn’t ship it. Here’s what each one is, and the job it does.

1. The first-value walkthrough → activation

A short, multi-step flow that gets a brand-new user to their first meaningful action — not a tour of every menu. The goal isn’t to explain the product; it’s to get the user to the moment they first experience its value. Keep it to the few steps that matter, skip everything else, and let people start doing real work as fast as possible.

Audience: new users. Moment: first session. Job: activation.

2. The new-feature pin → adoption

A tooltip anchored directly to a newly released feature, shown only to the users who’d actually benefit from it. Not a modal that interrupts everyone — a subtle pin on the feature itself, surfaced to the right segment. It turns “we shipped it” into “people are using it,” which is the whole point of shipping it.

Audience: existing users who fit the feature. Moment: when they’re near it. Job: adoption.

3. The “stuck” helper → fewer support tickets

A helper card that appears when someone is visibly struggling on a complex page — not on a timer, but in response to behavior. This is where Amplitude earns its keep: because Guides & Surveys sits on your behavioral data, you can target the users who are actually showing frustration signals (like rage clicks or repeated failed actions) and offer help at the exact moment it’s needed. Catch the struggle in-product and you deflect the support ticket it would have become.

Audience: users who are struggling. Moment: the point of friction. Job: fewer tickets.

4. The announcement banner → comms

A full-width, easy-to-dismiss banner for the things users need to know but don’t need a walkthrough for: releases, scheduled maintenance, pricing or policy changes. It keeps people informed without hijacking their workflow — visible if they want it, gone the moment they dismiss it.

Audience: all (or a segment). Moment: when there’s news. Job: keep users informed without interrupting them.

5. The in-context survey → feedback

One short question asked right after a key moment — finishing onboarding, using a feature for the first time — instead of a quarterly email blast nobody opens. Feedback captured in the moment is sharper and more honest than feedback recalled weeks later, and response rates are far higher when the question is one tap in the flow they’re already in. (We go deeper on this in getting actionable feedback from Amplitude Guides & Surveys.)

Audience: users who just hit a key moment. Moment: right after it. Job: feedback while it’s fresh.

The pattern: one audience, one moment, one outcome

Notice what all five have in common. Each targets one audience, fires at one moment, and is built to change one outcome. That discipline is what separates guides that help from guides that annoy. The failure mode isn’t building too few guides — it’s building dozens with no clear job, each one a small tax on the user’s attention. So before you ship any guide, finish this sentence: “This guide exists to change ___.” If you can’t, don’t ship it.

It’s also why where you build them matters. Because Amplitude Guides & Surveys targets and triggers off real user behavior — events, cohorts, and signals — each of these five can be shown to exactly the right person at exactly the right moment, instead of blasted at everyone on a timer. That targeting is what turns “one audience, one moment, one outcome” from a principle into something you can actually execute.

Start with five, not fifty

The teams that get the most from in-app guides aren’t the ones with the biggest library — they’re the ones whose every guide has a job. Build these five well, measure whether each is doing its job (more activation, more adoption, fewer tickets, better feedback), and only add more when you can name the outcome the next one will change.

Want help setting these up in Amplitude?

Deciding which guides to build is the strategy; wiring them to the right cohorts and behavioral triggers in Amplitude is the execution. Our Analytics Retainer gives you hands-on support to get Guides & Surveys driving activation, adoption, and feedback — not just installed.

Book a call with our team →

Frequently asked questions

What in-app guides should a B2B SaaS product build?
Five that each do one job: a first-value walkthrough (activation), a new-feature pin (adoption), a “stuck” helper triggered by user friction (fewer support tickets), an announcement banner (comms), and an in-context survey (feedback). Each should target one audience, one moment, and one outcome — if a guide has no clear job, it shouldn’t ship.

What’s the difference between a walkthrough, a tooltip, and a banner?
A walkthrough is a short multi-step flow that leads a user to a first action; a tooltip (or pin) is a small prompt anchored to a specific feature for the users who’d benefit; a banner is a full-width, dismissible notice for information users need to know but don’t need guided through, like releases or policy changes.

How do you decide when to show an in-app guide?
Tie it to behavior and moment, not a timer. Show a walkthrough to new users in their first session, a feature pin to relevant users when they’re near the feature, a helper when someone shows signs of struggling, and a survey right after a key moment. Behavioral targeting is what makes guides feel helpful rather than intrusive.

Can Amplitude trigger guides based on user behavior?
Yes. Because Amplitude Guides & Surveys runs on your behavioral data, you can target guides by events, cohorts, and pages — and surface help to users showing specific signals (such as frustration behaviors) rather than showing the same guide to everyone on a schedule.

How many in-app guides should a product have?
Fewer than most teams think. Start with the five that each own a clear outcome, and only add more when you can name the specific job a new guide will do. A small set of purposeful guides outperforms a large library of ones that collectively just add noise.

‍

Related articles

Guide
5min

How to Build a Marketing Performance Dashboard in Amplitude

Build a marketing dashboard in Amplitude that shows which channels drive quality users—not just traffic. Metrics, steps, and mistakes.
Checklist
5min

The Amplitude Account Health Check: 10 Things to Audit Every Quarter

Run this 10-point Amplitude audit each quarter to catch tracking drift, identity issues, and cost creep before they break your reports.
Guide
5min

How to Audit Your Marketing Measurement: The Data-Strength Framework

The data-strength method for auditing marketing measurement: examine the data, interview the people, and find where they diverge.

Get in touch!

Adasight is your go-to partner for growth, specializing in analytics for product, and marketing strategy. We provide companies with top-class frameworks to thrive.

Gregor Spielmann adasight marketing analytics