Are you sometimes in doubt about what to focus on next for your business? Asking your target group can be a huge benefit, but how do you do it most effectively? This right here is LeanBe a platform helping you to prioritise what to focus on next. Let’s dive in.
So here we have the LeanBe platform with the dashboard, the widgets and so much more. On the dashboard, you can make changelog activities and feature request activities as well. The changelog activities also work like announcements or news. So let’s say you make a big release of your product, or you release some features which has been requested. Then you can go in here in the category you choose, whether it’s an announcement, a new feature or bug fix.
Software reviews each week
Get one new software review in your inbox every week.
What’s coming next?
Do you want to have a say in what review I do next? Then go to my roadmap and vote or suggest a product.
- Features of LeanBe
- LeanBe Pricing
- Alternatives to LeanBe
- Future of LeanBe
- Pros & Cons using LeanBe
- Last thoughts on LeanBe
Features of LeanBe
Let’s just choose announcement. You enter your title and your content, and then you just make it ready to be published. You can also schedule it down here where you choose the date and the exact time. And you can even choose if this announcement should only be available for a certain amount of time. For instance, here I’ve chosen from 26 February until 3 March, and then I can schedule it.
Now I need to fill out a title and some content here. We can also make a custom redirection if you want to redirect to something specific, we can ask for feedback on this specific announcement, whether it’s feedback for feature request or it’s something third, then we can add emojis, but we can also add comments, and then we can enable social sharing as well. For now, I’ll just publish this one, and then I will accept it. So now it’s laying in here as an announcement.
You can see it’s active right now and this has taken us directly into our notifications. So here we have our categories with the bug fix, new features and announcement which you just saw. We can also add new categories if you feel these are not fulfilling, and then you can add the colours for these categories and back to the notifications. We have the scheduled one, the draft and the active ones. And this is the changelog, as you can see up here as well.
Now one thing that we just skipped for a moment is the widget. The widget is your way of adding the announcement and everything that you are building within LeanBe on your website. So here we have a default widget. Let’s go and edit this one, so you can see we have our embed script up here which you need to add on your website. Then you can give it a name, or you can choose what type this widget should be, whether it should be a pop-up or a sidebar.
The launching type again should be a link or a button. A link then you can place it wherever you want on your website. A button, then it’s placed down here to the left where you can see it, and before we move on that I really show you. Then you can also choose the button customisation with the icon here. You can choose what size this button will be.
You can choose the position of the button. You can see that when we choose the bottom right. It has an issue with the chat functionality. What we have seen within LoopedIn is that LoopedIn actually places it on top of the chat functionality. It is just a small thing, but that should definitely be fixed.
Then we can also customise what we want to show in the widget. You can see here right now we’re just showing all categories, but we can also choose if we only want to show certain categories. And the same with the tabs here. Right now it is only showing changelog and feature requests, but I will also add the Roadmap.
The header title: what’s new? Let’s just go up and change it to be bottom left again. What’s new is what we see up here. And then you can see after I added Roadmap, it has now added the menu point. But other than that, we have the changelog with the announcement we have already made and here we can give some feedback, and then we have the feature request which I will come to.
Then again, you can customise it even more with the close icon. You can choose where the close icon should be, the overlay option, even animation and the page scroll, whether it should be enabled or disabled. And you can even collect email addresses down here where they are then just sent to your email. It would be great to have an integration with another email system and this could be solved with the web hooks which are coming up, because then we can build a Zapier integration. But this is the widget.
So let’s just update our changes here. Accept and then you can see that the widget is now ready with the functionality. On the widget we have feature requests. So right now I just went into the widget and this is our page that we have on LeanBe. So here I can request a new feature where I can add the title of the feature, the priority.
The fact that I can set the priority shouldn’t be possible because everyone just wants their feature to be developed with the highest priority. So I think that should be moved. Let’s see if we can move that later on. And then I will add some description to this feature request. I will now submit it.
So now it has been submitted, and it’s already added in here. I would like to be able to filter. So all the feature requests had to go through an approval process where I approved whether this feature request should be there or not, because we can then now start voting on this feature request, and we can add comments as well. And over here we can see all the voters. But this one is basically the same that we have seen within the widget.
We have the roadmap, and we have our change lock with the announcement we already made. Now let’s try and go back to LeanBe. So within LeanBe, if we go to feature request, you can see that we now have the request here. And what is great is that this one is awaiting approval. This means that I need to approve this one before anyone else can see it except for me and whoever made this feature request.
So I will just approve this one. So now it is public, and it is in to do in the roadmap. And the more feature requests that there will be, the more there will be over here as well. We can also make internal notes if there’s something we want to remember. Otherwise, we can also comment on it from here and others who are making comments.
They will also show here. Over here, we changed the status of this specific feature request where it should be visible to the public and whether it should be shown on the roadmap. I would really like to be able to change the priority here, but that is not possible right now. I will then save my changes. And now we also have the status
The statuses as you’ve seen is waiting for approval to do in progress in review and done. And these, I assume, are also the status of the roadmap. But at least this is the status for the feature request. Now moving over to the roadmap, you can see that the feature request we added is now here with the title. It was created on 1 March, and we can then move it around from to do and progress or done.
Now what I really like about this roadmap is that we can set objectives. An objective is a bigger goal that consists of multiple tasks. So let’s say that you have a product where you have an onboarding phase. One objective could be to minimise the onboarding phase to three steps. But in order to do that, you have maybe five tasks you need to go through.
So here you can see that if we add an objective to say minimise onboarding time to ten minutes, for instance, then we can set a colour, I’ll just set it to red, and then we can press create. Now this objective here now consists of tasks. So, if we have this task here, I would like this task to be part of that objective. And in order to do that, then we have to go back to the feature request. I need to edit the post, and then you can see an objective here.
I can then change and set it to minimise onboarding time to ten minutes, press update. And now we have the first task within our minimise onboarding time. So, going back to the road map, you can see here that this task is part of the objective, minimise onboarding time to ten minutes. And that is what I really like about objectives Now, what I’m missing about these objectives is a status bar.
I would love to see this objective. How far are we and maybe even a roadmap for objectives. So we have, of course, the roadmap for our specific tasks here, but we also like to make a visible roadmap on a timely basis, showing all the objectives and when they need to be done, when they need to be started on. Because right now if I have ten tasks under one objective and I can’t even set a deadline on these objectives, it’s a little difficult to feel how far we are on these specific objectives. Now, one thing you can also do is that you can integrate into both Trello and Jira.
So this means that you can integrate your tasks between LeanBe and Trello or Jira. So you don’t have to do double work. You don’t have to go through all these manual processes to update first in Trello, then in Jira and then in LeanBe. If you’re using all of these three software, in this case, every time you do something in LeanBe, it will also be reflected in Jira and Trello. So this will just save you time.
And it’s just a great way to optimise your entire workflow from when a customer or a visitor is asking for a feature until it’s done. Now we do also have tracked users and here right now we only have one user. One thing I can’t get clarified here is when I finish a task in the roadmap, whoever has something related to do with this task, are they notified that this task is now done? Because that is highly relevant for them to know.
So they can start using the feature because they have either asked for it, they have maybe voted for it, or they have commented on it. So that’s just one thing that would be really nice to have. We can also customise the roadmap if you want to add more columns, It could be a column called In Review, and then we can attach it to the status from the feature request and then save. So we have to do it in progress in review and done. So the in review I’ll of course add to before done.
We can always set the settings for the different statuses in our roadmap, but that is how easy it is to just move around and change your roadmap to be exactly how your workflow works best. Now for each project we also have the settings and within the settings you can set a logo, a font, a colour, and even a favicon to really make it yours, so it looks like it’s within your universe. You can also add custom branding, or you can just remove the branding completely. Then we can also change the standalone page set up and as you saw before when we went into the feature request, then we had this page with all the different modules, here I’m talking about the changelog, the roadmap and the feature request.
And again, we can change the primary colour, the secondary colour, even the buttons, how the tabs are looking, how the page grid should be, and so much more. So you can really design this page to fit into your universe, so it looks like it’s part of your design and your website. You can also set it up on a subdomain if you want it to really fit your domain. And then you can add team members as well for your project. So this is really great to see because this means that we can really customise our project to be ours and not to be this generic project where everyone can see that this is from LeanBe.
So that is a great add-on The last thing I just want to show you is role management because as you’ve seen in the higher plans, we can add more team members. But if you want to really change the roles of each of these team members, this is possible. Right now we only have two, we have the admin, and we have the author. The author can manage the widget, can manage the categories and the notifications.
We can, of course, edit to add more of these different permissions. Or we can just create a completely new role, give it a name here and then choose that this is only for the notifications that they can focus on and that is how easy it is to manage all the roles. Then you go back to the team members, and then you add the roles to the team members that you need.
Now to the pricing of LeanBe where you can get started completely free, and you can test out most of the functionality. They do have only one team member and a limited amount of functionality, but it is a great way to start, and you do have enough functionality to get an idea of how LeanBe is working. And then, when you feel that you want to streamline your workflow more, you want integrations.
Then you upgrade to one of the three paid plans where they differ not only in functionality, but they also differ on the amount of team members you get. So do be aware of this.
Alternatives to LeanBe
Now the alternative to LeanBe are UpFeed which I have previously reviewed. UpFeed is a very minimal scale compared to LeanBe because LeanBe have the widgets, they are working on a feedback system, they already have integrations. So the functionality is just a lot more within LeanBe, whereas as we saw with UpFeed more minimal, the design is maybe a little bit better, a little bit easier to use, but the functionality just wins when it comes to LeanBe.
UpFeed is a simple platform to maintain your roadmap and announcements for your target group.
Now the other alternative is LoopedIn and if you have seen my LoopedIn review you know that I’m a big fan of LoopedIn and you can go back and see it. LoopedIn has more functionality than LeanBe. They already have the feedback implemented. They have articles, so you can build an entire knowledge base and so much more. The development speed of LoopedIn has impressed me a lot, so I will definitely recommend you take a look at LoopedIn and compare it to LeanBe to see what is the perfect match for you, because they are two different systems, and they might go in different directions, so just be aware of this as well.
LoopedIn is a more refined platform to manage your roadmap, widgets, feedback and so much more from your customers.
Future of LeanBe
Now LeanBe is not only a platform to help you what to focus on next. It can also help you streamline your entire functionality from when it’s asked until it’s developed and this is done by integrations. But looking into the future of LeanBe they’re focused on building an entire private feedback portal, so you can gather feedback from all of your users and use this feedback again to choose and prioritise what to focus on next. Then they’re working on adding web hooks. This will make it possible to integrate with Zapier for instance, and just make it possible to integrate a lot more to streamline the workflow I just mentioned. They are also working on adding more languages to the platform, so you can target it to your different target groups and then, last but not least, they have a lot of small features they are using to make the platform better to remove all those duplicates to just make it better overall.
Pros & Cons using LeanBe
Now using LeanBe I really like the objectives because it paints the big picture of all the small tasks you’re building and then the fact that we have the integrations that make it possible to streamline our workflow much better. The design is also working well. Now the fact that we don’t have the Zapier integration is a bit of a letdown and then the fact that we don’t have the feedback widget as well.
Last thoughts on LeanBe
LeanBe is perfect for letting your target group guide the direction of your business and just to get a lot of great input. I feel LeanBe has come far already with two essential integrations and with the feedback portal coming up, I want to give them four stars.