The (in)famous walkthrough.

Where do you draw the line between walkthrough and onboarding? I asked this very question on Twitter. Here are some of the replies I got. 

Image of a tweet asking the question, do you use the terms Walkthrough and Onboarding interchangeably
image of a tweet from Brian Casel, giving his version of what the difference between onboarding and a walkthrough is.
Image of Connor Lindsey on Twitter giving his definition of what onboarding and walkthroughs are.

Even experienced SaaS founders differ in their definition of an in-app walkthrough and customer onboarding. Many of us use these terms interchangeably, and we expect others to know which bit we're referring to. So, let's look at the customer onboarding experience as a whole experience. Or to put it another way, the first few minutes of a new customer journey.

The customer journey.

How do you give your potential new customer the best chance of converting to a paid customer? This is a tough one as it varies from SaaS to SaaS. However, there are common mistakes that I see over and over in my customer onboarding reviews.

  • Forcing your customers through a walkthrough. While you might think you’re doing them a favour, you’re just helping them to hate a little on your app…just a little. It's far better to give them the option to ignore it altogether, pause, come back later, or start looking around immediately.
  • Letting users skip the walkthrough and then having no way of getting back to it. This is important, and it happens all the time. Just because someone doesn’t want to go through your onboarding right now, it doesn’t mean they won’t want to later. Make it easy to get back to the walkthrough later.
  • Abandoning your customers on the dashboard and offering no help… at all! This is way too common, (particularly in newer, smaller apps) yet when we experience it as customers it immediately makes us feel like the app is unfinished or that the founders simply don’t care about our success.
  • Constantly reminding your customer that they are a bad person/user. And how does this happen? We won't let them forget that; “You've only filled 65% of your profile/goals/account details”. This is incredibly frustrating. If the customer thinks there’s no way to complete this data to the satisfaction of your software (and often there isn’t if certain data isn’t relevant to their account), then it becomes incredibly demoralizing...and annoying! Let them dismiss these warning messages if they don’t think it’s relevant or important. Ultimately, you need to ask yourself, is it 100% necessary?
  • Thinking that onboarding just shows people how your app works. Outside of this basic function, it can also be incredibly useful for collecting important data in bite-sized chunks. Forcing new customers to give you all their data as soon as they've signed up can just be too much. Give them time to look around and soak it all in. If something is not vital to their immediate success, give them a break.
  • Custom building the onboarding yourself. Go on, admit it, you’re already planning how to build this out. With so many existing solutions out there you’d be crazy to build something. Put your skills to better use! Here are seven examples to check out: 

User onboarding. Isn’t it the same as a walkthrough?

I know that we’ve just looked at walkthroughs, but I want to talk briefly about onboarding. Why? Because these terms are often used interchangeably, however I would suggest that onboarding is an expanded version of the walkthrough… Here’s why. 

If we think about a typical walkthrough, what is it really doing? Well, it shows new customers around the basic functions of the app. Think of it as a you-can-do-this, you-can-do-that, kind of thing.

  • This is where you build your proposals. 
  • This is where you store your account details.
  • This is what to do if you need help

The walkthrough does as its name suggests. It walks users through the software. 

However, onboarding typically goes beyond this. Over a defined amount of time, it subtly (or not in some cases) pushes the user to a point where they are ready to commit to becoming a paid customer. 

You wouldn’t want to leave a new user to fend for themselves after finishing a guided walkthrough. Not if you want to improve their chances of success and yours. So, you’d nurture them through continued onboarding.

There are plenty of resources that can be incorporated into your onboarding, for example: 

Drip emails. These help new customers (and old ones) get the most out of your software. They can be triggered by an action or the fact that a user fails to take an action. For example, if you know that most new customers (who convert) send a proposal within the first two days, then you’d better do all you can to help new users do the same! Having this knowledge means you can automatically email new users who haven't sent a proposal by the end of day two. Encouraging them to do so will help them reach that "aha" moment.

Onboarding Calls. Few people like doing onboarding calls, but some trial users prefer to be onboarded by a real person. It helps to instil trust and can make the time from trial to paid user quicker. One way to do this is to make the option available during the initial walkthrough, from within a chat widget or even via one of those automated emails you’ll be sending out. 

Ongoing education. Initially, new users want to learn enough about your software to get the job done. But the less time they must spend in your app, the better. So, educating them on how to get the most out of your software can turn them from customers into fans. They’ll be far happier with your software knowing that they can get the job done in half the time. Ongoing education, via a newsletter linked to recent blog posts, or new and updated knowledge base articles can be great. Whatever works for your users.


I hope by now you can see the importance of onboarding new customers and doing it in a way that doesn't overwhelm them. The tricky thing about onboarding is that every user is different, yes you might be using user personas (which is great), but user personas will only get you so far. You will need to test, (live user tests are awesome) iterate and test again. No one gets it right the first time, or the second. Successful onboarding can significantly impact your growth, so getting it right just makes financial sense, right?