The activation interview: a guide for B2B SaaS founders

Your analytics can tell you where new users disappear. Forty-two people signed up last month. Eleven created a project. Four came back a second time.

The funnel is precise, colour-coded, and completely silent on the question that matters: why did the other thirty-eight stop?

That gap between signup and value is where many B2B SaaS products lose a large share of new users. Intercom’s free-trial guidance says the “SaaS law of averages” suggests 40-60% of people who sign up for a free trial use the product once and never come back. Its onboarding guide makes the early-risk point even more plainly: the seeds of churn are planted early, often before a customer has used the feature that successful customers rely on.

An activation interview explains that gap. You talk to recent signups — the people who reached value and the people who stalled — and walk through what actually happened in their first days with your product. Not what they think of your onboarding. Not which feature they want next. What happened.

This guide gives you a template you can run this week: who to recruit, what to ask, which questions to avoid, and how to turn the transcripts into a better activation metric. If you have read Maren’s problem discovery interview template, think of this as the sibling piece. Discovery asks whether the problem is real. Activation asks why the thing you already built is not landing quickly enough.

What activation actually means

Activation is the point where a new user first experiences the value they signed up for.

That sounds simple until you try to measure it. Completing signup is not activation. Reading an onboarding tooltip is not activation. In many B2B products, even “created account” or “invited team” may only mean the user has started the setup work required before value is possible.

Lenny Rachitsky and Yuriy Timen define an activation milestone as the earliest onboarding point that shows product value and predicts long-term retention. They also give a useful test: users who hit the milestone should retain at least twice as well as users who do not. If your milestone does not separate future retained users from future lost users, it is probably a vanity checkpoint, not activation.

Their benchmark survey of 500+ products reported an average SaaS activation rate of 36% and median of 30%, compared with 34% and 25% across all product types. Treat those numbers as calibration, not as a target to copy. Activation rate depends heavily on product type, milestone definition, setup burden, buyer intent, and whether the user must coordinate other people before value appears.

The famous Facebook example is still useful because it shows the shape of a good milestone. Chamath Palihapitiya described Facebook’s early growth focus as getting a new user to 7 friends in 10 days. The point was not the number itself. The point was that the metric represented the user reaching the core value of the product.

Your product has its own version: first report shared, first workflow completed, first teammate invited and active, first dataset connected, first issue resolved, first customer message sent, first useful answer generated. You may not know which one matters yet. That is exactly why you run activation interviews.

One more boundary helps. Interviews will not tell you your activation rate. Analytics will not tell you why the rate is low. The chart shows where people stop. The conversation shows what stopping felt like from the inside: what they expected, what they tried, what felt risky, and what they went back to instead.

Who to talk to

Talk to three groups. Keep the first batch small enough that you can read every transcript carefully.

Recently activated users. Recruit people who signed up in the last two to four weeks and reached the moment you currently believe represents value. They ran the report, connected the data source, invited a colleague, published the page, or completed the workflow. You are trying to understand what the click moment actually was and what had to happen before it.

Recently stalled users. Recruit people from the same signup window who stopped before value. Do not start with last year’s dead accounts. Start with last month’s unfinished stories, while the details are still available. As Intercom puts it, brand new users are just trying the product out. A stall is often not a dramatic rejection. It is a busy afternoon where another priority won.

Invited teammates. If your product is collaborative, the first admin is not the whole onboarding journey. Samuel Hulick describes the first user in a B2B product as often being in “homesteader mode”: setting up the space so others can follow. Invited teammates arrive with less context, less motivation, and a different set of questions. Interview both journeys.

The two-to-four-week window matters because memory decays. Nielsen Norman Group warns that interviews rely on reported behaviour, so recall can be faulty and details can go missing. Their practical advice is to ask about specific events rather than general processes. “Walk me through the first time you tried to create a report last Tuesday” will produce better evidence than “How was onboarding?”

For a first pass, aim for five to eight conversations in each group if you can. If your volume is lower, start with what you have. Three stalled users this week are more useful than waiting two months for a clean research sample while the funnel keeps leaking.

Prepare before the interview

Do not arrive with only the account name and a vague goal.

Before each conversation, pull a simple timeline from your product data:

Do not show this timeline to the participant as proof. Use it to ask better questions. If the event log says they paused at the integration screen for two days, do not say, “Why did the integration screen confuse you?” Say, “I noticed there was a gap after you got to setup. What was happening on your side during that time?”

That distinction matters. The first version smuggles in your interpretation. The second invites the story.

The 30-minute activation interview guide

Nielsen Norman Group recommends interview guides with a few concise, open-ended questions followed by prepared probes. The structure below keeps the conversation chronological because activation is a story: before signup, first session, setup work, first value or stall, and what happened next.

Record the interview with permission. Tell the participant you are not there to defend the product or sell them anything. You are trying to understand what the first experience was like from their side.

1. Warm-up: their work context

Start with something easy.

• “Tell me a little about your role. What does a normal week look like?”
• “Where does [problem area] fit into that week?”
• “Before you tried us, how were you handling that?”

The goal is not rapport theatre. It is context. Activation depends on the job the product is being hired to do, and Intercom’s value-based onboarding guidance is clear that first use should be built around the value the user is trying to reach, not around a tour of your screens.

2. The day they signed up

Now reconstruct the trigger.

• “Take me back to the day you signed up. What was going on that day?”
• “What had happened that made the old way no longer good enough?”
• “Where did you first hear about us?”
• “What did you expect the product would help you do?”

This section reveals push and pull. Intercom’s Jobs-to-be-Done onboarding piece, drawing on Bob Moesta’s four forces, describes adoption as a balance between push, pull, inertia, and anxiety. Activation stalls when the push and pull are not strong enough to overcome the effort and risk of switching.

Listen for the gap between expectation and first screen. If marketing promised “weekly reporting in minutes” and the product opened on an API-key setup page, that mismatch belongs in the synthesis.

3. The first session

This is the core of the interview. Go slowly.

• “Walk me through your first session. You had just signed in. What did you do first?”
• “What were you trying to get done in your work, outside the product?”
• “What did you try next?”
• “Where, if anywhere, did you stop or hesitate?”
• “What else was competing for your time that day?”

Keep pulling the conversation back to the specific sequence. Teresa Torres’s story-based interviewing advice is useful here: keep the interview grounded in specific instances of past behaviour. “The setup was confusing” is a summary. “I got to the SSO screen, realised I needed our IT admin, sent a Slack message, and closed the tab” is evidence.

For multi-user products, ask what happened outside the product too:

• “Who else had to be involved before this could work?”
• “Did you need approval, credentials, data, or help from another team?”
• “What did you tell them when you asked?”
• “Did anyone push back?”

Activation is often blocked by work the product cannot see: permissions, internal politics, data access, procurement, legal review, or the fear of inviting a manager into an unfinished workspace.

4. The click, or the stall

For activated users, ask for the first value moment.

• “Tell me about the moment you first thought, ‘This is going to work.’ What exactly were you looking at?”
• “What had to happen before that moment was possible?”
• “Which step nearly lost you?”
• “Did you tell anyone? What did you say?”

For stalled users, ask for the stopping point without making it sound like a failure.

• “Tell me about the last time you opened the product. What were you hoping to get done?”
• “What did you do after you closed it?”
• “Was there anything you were unsure about trying?”
• “What made continuing feel not worth it at that moment?”

That final question matters because drop-off is often rational. Intercom’s four-forces article says new users drop during onboarding when the core value does not feel worth the cost of continuing. Cost can mean time, coordination, technical setup, risk to reputation, anxiety about sending something to customers, or the simple fact that the old workaround was familiar.

5. Wrap with comparison and consequence

End by connecting the first experience back to the user’s real work.

• “What did you go back to using instead?”
• “What, if anything, changed after trying us?”
• “If a colleague asked whether they should try this, what would you tell them?”
• “What would have had to happen in that first session for you to keep going?”

The last question is close to hypothetical, so treat it carefully. Do not turn the answer into a roadmap promise. Use it as a way to surface the missing condition, then look for supporting evidence in the story.

Questions to avoid

The Mom Test’s rules apply cleanly here: talk about their life, ask about specifics in the past, and listen more than you talk. In activation interviews, that means avoiding questions that produce politeness, prediction, or product reviews.

Teresa Torres makes the future-behaviour problem bluntly: when people answer future-looking questions, they often answer as the person they hope to be. That is why your guide keeps asking about yesterday, last week, the first session, and the last thing they tried.

How to turn transcripts into an activation metric

After the first batch, do not jump straight to “we need a better checklist.” Read the transcripts for repeated moments.

Create a simple synthesis table:

Then write candidate activation milestones in plain language:

• “Created first report and shared it with a teammate.”
• “Connected data source and received first useful alert.”
• “Invited at least one colleague who completed their first task.”
• “Published first customer-facing workflow.”

Now let product data challenge the stories. Lenny’s activation-metric process is: brainstorm candidate moments, check their relationship to retention, then run experiments. For a young B2B product with 50-1,000 users, the data may be thin. That is fine. You can still ask whether users who reach the candidate moment retain, expand, invite others, or come back next week at meaningfully higher rates than users who do not.

Be careful with correlation. A milestone can look predictive because only your strongest-fit customers reach it. That does not make it useless, but it means the next question is causal: can you help more of the right users reach that moment, and does retention improve when you do?

Common traps

Treating signup as activation. Signup proves intent. It does not prove value. If your milestone is too early, your activation rate will look healthy while retention quietly disagrees.

Choosing a milestone the team can control but the user does not value. Completing a checklist, watching a video, or filling a profile can be necessary setup. It is not activation unless it connects to the user’s reason for trying the product.

Only interviewing successful users. Activated users tell you what worked. Stalled users tell you where the first experience lost the argument. If one group has to be over-represented, choose the stalled group.

Explaining during the interview. The moment you say, “Oh, that button is actually over here,” you have switched from learning to teaching. Note the issue. Fix the product later. Keep asking.

Ignoring the invited teammate journey. Many B2B products activate at the account level, not the first-user level. If the admin reaches value but invited colleagues do not understand why they are there, activation is still fragile.

Treating interviews as the metric. A strong story can reveal candidate milestones. It cannot prove the activation rate. Pair the conversations with event data before you rebuild the onboarding flow around a hunch.

Where Maren fits

Activation interviews work best when they happen close to signup, while the story is still fresh. That is hard for a founder to maintain manually. The users who stall are exactly the people least likely to book a call, and the first two weeks pass quickly.

This is one of the research jobs Maren is built for. You define the groups, give Maren the guide, and send recent signups a share link. She can talk to activated users, stalled users, and invited teammates while the memory is still specific, ask the same warm follow-ups every time, and bring back the themes without turning the conversation into a sales call.

The point is not to replace your funnel chart. It is to make the chart explainable. Analytics tells you where new users stopped. Activation interviews tell you what they were trying to do, what got in the way, and which first value moment is worth building around.