Appbot Logo

Feedback Driven Growth: A process for sustainable growth

feedback driven growth illustration

Everyone wants a silver bullet for growth. We all look for that amazing “growth hack” that will instantly drop millions of new users into our products.

The tech press likes to talk about the unicorns who have hundreds of millions of users a year after launching. In reality most tech successful companies don't have hockey stick growth, they have linear growth. They launch to very little fanfare, have very few customers in the early days and constantly think they won't make it.

It's rarely one specific thing you do will create a successful company. It's the sum of hundreds or thousands of small things your team tick off their lists.

DHA from Basecamp shared their amazing year by year growth.

Appbot hasn't been around as long as Basecamp. But we are still proud of our month by month growth. We decided early on to bootstrap and try and make a sustainable growth business. Each month on it's own isn't a lot to get excited about. But month by month it adds up into something sustainable and profitable.

line chart showing appbot's monthly growth

We could easily keep a team of 20 busy, but we decided to grow within our means.


I get people reaching out to me with a very similar question. “I've launched my app and can't get any users, what should I do?”

The truth is, for the vast majority of us, it takes a long time to be successful. It doesn't happen in one Big Bang. You toil away for years seeing small improvements and then one day, years later, you look up and think “Wow, we made it, we are alive”.

My advice to them is always the same. “Delight the few users you have”. To do this you need to be able to work out how to delight them.

The one technique that I've found that works is something I call “Feedback Driven Growth”.

Essentially you are using user feedback to find two critical things:

  1. What parts of your app or service are delighting people.
  2. What pain points users have that you can solve better.

Early in the life of your product it's easy to handle this manually and keep it all in your head. “Hey, that's the fourth person this month that wants that feature”! As you grow and you hire support staff it becomes much harder to stay on top of everything.

Feedback Driven Growth

I'm a big believer in using user feedback as a way to improve your product and hence drive growth. It doesn't mean blindly implementing everything users ask for. It's about discovering recurring pain points and then innovating a solution that will delight.

diagram showing the feedback driven growth loop

When you break it down Feedback Driven Growth is a very simple process. Gather and read, analyse, classify, prioritise and iterate.

Gathering and Reading Feedback

I group feedback in two forms:

  1. Unprompted feedback - this is always the best. App reviews, support tickets and emails are ideal. If the user has taken the time to give feedback unprompted you know it's valuable.
  2. Prompted feedback - Surveys, NPS, interviews and so on. These can be great, but are often misleading because people are compelled to think of answers to your questions.

By default we will ask the first question, get the answer we want and yell out “we are validated!” and move on to building.

Back before commercialising Appbot I built a service that would easily add a support system to your mobile app. I sent out a survey to a bunch of developers I knew. They all loved the idea and couldn't wait to use it. I built it and not one of them tried it out. But they did give me the answer I wanted so I left them alone quicker.

Analyse - Distilling Feedback into Pain Points

Often the feedback is actually a solution the customer has come up with. ���I should be able to click on x to do y”. It may take a bit and back and forward with the customer to get what the real pain point is. Why do they want to do that? What are they trying to solve?

Here's the thought process I go through for each 'pain point':

Classify / Tag

Now you need to actually record it for your backlog.

I like to think of it in a few steps:

We then come up with a way to tag the request. For example a feature request about topics would be FR-Topics-New Feature Name a bug report in our Slack integration would be BR-Integrations-Slack-Bug Name.

This goes into our CRM against the customer where we can report on it and also find the customers to notify when it's done.

Fix / Iterate

Fixing and iterating comes down to your own development process. But choosing what to build or fix next can be a tricky task.

I've written more extensively about this in the past, but we follow a basic principle of scoring based on:

We add these scores together to find our the winner.

drawing showing how appbot scores what to work on

That's It

The process of Feedback Driven Growth has helped Appbot bootstrap to where we are default alive. Hope it helps you!

About The Author


Stuart is Co-founder & Co-CEO of Appbot. You can connect with him on Twitter.

Enjoying the read? You may also like:

Ready to better understand your apps?

Quick setupFree for 14 daysNo credit card required