I see your point, and many of my later "hacks" has been improved since my first ten. But it also depends on who's definition we use. Most of my "hacks" includes coding (i.e. hacking) and are meant to increase growth. Are they considered growth hacks then? Or must something be "hacked" for it to be called growth hacking?
Yes, that may be true, but the others could still contribute to growth. And it would be really hard (and probably not even good) to come up with 100 "true" growth hacks, and perform them one day after another ;)
Agree! I do actually work on more deeper problems. At the moment I spend a lot of time creating integrations, improving the documentation and the getting-started guides. As we do get new signups every day, I want more of them to get started and really using UserApp. But to learn how I can improve all that I need feedback, and things takes time. Meanwhile I wait for feedback and test results I spend my time trying to improve conversion rates on the website and to drive more traffic, etc.
Thanks for your feedback. Not all of them are UI stuff, e.g the survey, the open-source warranty and the email where I asked why users had canceled. And these was the first 10, now I'm at day 36 and all of them are not about just UI. But I see your point, and the problem is mostly to be able to pull off one hack each day, many would have to be simple and easy to do, and therefore lower quality.
Regarding what actually is a growth hack or not, if it has to be new, none of my 35 hacks are a growth hack. Sharing stuff on social media would be social media marketing, blogging would be content marketing and SEO, and more fundamental "hacks" would be either a part of a business plan or just a marketing strategy.
However, my main goal of many of the things I do is to increase growth, both direct and indirect.
I will give this a thought and see how I can plan my upcoming weeks. I have considered about canceling my every-day growth hacks to focus more on larger "hacks", and also finding users and helping them getting started. Let's see what happens :)
Yes, we are working on that :) The user authentication stuff maybe take a few hours/days to get in place for a experiences developer. However, what we want to focus on is everything else around user management. That's why we are building an add-on store for third-party integrations. Some example cases that we could solve:
* If you have users, you might want to sync them to e.g. MailChimp.
* You would probably want to charge them for using your app, so you would need to integrate a payment provider, calculate payments, creating price plans, etc. UserApp already takes care of all that except the payment processing, which will come as add-ons later.
* Social login (OAuth) to support login from Facebook, Twitter etc.
* Send welcome emails, forgot password emails, etc.
* An admin interface t be able to delete, block, search and manage your users, permissions, etc.
And this is not just for mobile apps. It's for every web, or mobile, app that has users to manage.
I really like your advice! Others have actually told me the same and I understand "the concept". But I would like to ask you for some more advice: how can I spend my days only focusing on getting users to use us? We are already emailing every new signup offering them help etc, and some respond with questions, which we help them with. But that usually doesn't take the whole day. I would like to know some activities on how to get more of those. Cold calling?
Otherwise, thank you for your feedback. Appreciate it :)
I hear you. But some are hard to measure and some just takes longer than a few days to show results. I will probably follow up on the earlier rounds, and maybe also update the posts as well with the results. Though for every day there's one more "hack" to follow up on.
Our decisions (including this one) is based on what's best for our company and customers, not any future VCs. And also, this clause is mainly an insurance for our customers during our first "risky" years. Hence the expiration on the clause (October 31, 2015).