Archive for July, 2014
There’s only a few ways to scale user growth, and here’s the list
Scaling growth is hard – there’s only a few ways to do it
When you study the most successful mobile/web products, you start to see a pattern on how they grow. Turns out, there’s not too many ways to reach 100s of millions of users or revenue. Instead, products mostly have one or two major growth channels, which they optimize into perfection. These methods are commonplace and predictable.
Here are the major channels that successful products use to drive traction – think of them as the moonshots.
- Paid acquisition. If your users give you money, then you can buy users directly through ads. Usually companies try to maintain a 3:1 CLV:CAC ratio to keep their margins reasonable after other costs. (eBay, Match, Fab, etc.)
- Virality. If your users love your product, then you can get major “word of mouth” virality driven by a high Net Promoter Score. If you can get your product to spread as a result of users engaging with the product, you can further optimize the viral loops using A/B tests to generate even more virality. People often measure “viral factor” to see how effectively existing users attract new users, and of course, you want your viral factor to exceed 1.0. (Facebook, Instagram, Twitter)
- SEO. If your product creates a ton of unique content, in the form of Q&A, articles, long-form reviews, etc., you might end up with millions of unique pages that can in turn attract hundreds of millions of new users who are searching for content via search engines. (Yelp, Rap Genius, Stack Overflow, etc.)
- Sales. For startups targeting SMBs or the enterprise, you’ll end up fielding a large sales org to handle both inbound and outbound. This is especially true for companies targeting local SMBs, where telesales becomes the only option. Of course, to make this work, you’ll need to generate a multiple in revenue of what you pay them.
- Other. There’s the odd partnership, like Yahoo/Google, that can help make or break a startup – but these are rare and situational. But sometimes it happens!
These channels work and scale, because of two reasons:
- They’re feedback loops. Each of these channels creates exponential growth because when you make money from customers, you can use that money to buy more customers, which give you more money. Or in the virality scenario, a cohort of new users will invite even more users, who then invite even more on top of that.
- They have a high ceiling on saturation. Part of why paid acquisition will always be around is because people like free products, which cause these products to monetize using ads. As long as people will love free products (which they will, forever), there will be advertising to buy. The biggest ad networks reach a billion users or more. Similarly, SEO works because almost everyone uses Google, so as long as you’re dealing with a high-volume base of searches (like music lyrics, or products) then you’ll be able to reach hundreds of millions of users.
It might seem like it’s best to crack one of these channels right away, and then ride then into glory. But that almost never happens, and instead startups have to work towards them – but it takes time. To figure out if your CLV and CAC match up, you need to buy some users, then wait 6 months to see how well they monetize. If you want to see if your product is viral, you need to build your app, then wait to see if you have the retention and frequency to support a strong viral loop. SEO is hard because after the content is built, Google has to index it and you have to build PageRank. This can take months and years.
New products often only have months, or a year, to live, so these strategies are often not a real option.
High-risk, high-reward
Attacking one of these scalable channels is high risk but also high reward. Every startup has to make sure they are able to slot themselves into one of channels in order to scale their business, but in the meantime, how do you show enough traction to not run out of money?
This essay by Paul Graham gives us a clue, as he writes about Startups = Growth:
A good growth rate during YC is 5-7% a week. If you can hit 10% a week you’re doing exceptionally well. If you can only manage 1%, it’s a sign you haven’t yet figured out what you’re doing.
Another way to say this is, growth is measured through a percentage and so early on, small things can drive a high % growth when the base is small. When you’re starting, there’s a whole list of other tools you can use which don’t scale at all but are nevertheless low risk.
Here are some low-risk, unscalable ways to get users:
- Getting your friends+family to use the product
- Emailing/posting among your local community, whether that’s college or an alumni mailing list or whatever
- Guest writing on niche blogs – you often see this with mommy blogs, etc.
- Cold e-mailing potential users and influencers
- Engaging with potential users over Twitter, Reddit, forums, and other communities
- Contests and giveaways, partnering with a blogger/YouTuber or something
- Getting covered in niche press outlets, like the tech press
- … etc., etc.
All of the above require hustle, but are low-risk and fairly high-percentage. And when a contest can generate a few thousand signups, on a small base that’s not bad at all. The other added benefit is that these methods put you in direct/close contact with your users. So in the early phase, when you are still working on product/market fit, this can be an important way to learn if you have the right product.
However, none of these methods scale well, which is OK, if you know when you need to move on. Even getting covered in the mainstream press, like NYT level, maybe only garners a few hundred thousand signups max. Getting featured by Google or Apple is about the same thing. That’s better than nothing, of course, but it’s still far below what you need to get on a rocketship trajectory. For the rocketship, you’d need to perfect one of the 4 main channels I listed earlier.
So ultimately, how do you balance these? Let’s talk about the barbell strategy.
The barbell
To answer the question of how to balance these growth projects, let’s talk about the barbell strategy. The barbell strategy is a way that investors can split their holdings between some high-risk/high-return investments as well as low-risk/low-return conservative investments. Investopedia describes it:
Put your eggs in two baskets. One basket holds extremely safe investments, while the other holds nothing but leverage and speculation.
In the context of these growth channels, the key is to balance a series of progressively more scalable growth projects, while keeping track of the big growth channels that will help you shoot the moon.
Do the methods that don’t scale
During the early days, by all means, sign up friends and family. And get those blog mentions, and do all the content marketing you can handle. That’ll help create a base of engaged users, while you hit product/market fit. At each point, as what works caps out, go after the next marketing channel that can drive incrementally more users. In the early days, perhaps a contest partnership with a niche blog would do, but after a while, maybe you’d hire a small team to author long-term content marketing pieces to circulate.
Invest in moonshots
The other end of the barbell, the high-risk/high-reward projects, should be taken with deliberate projects and analysis. If you need your userbase to generate a lot more unique content for SEO, start fiddling around with features that reward long-form content. And start tracking what % of users write great content. And start making the small changes needed for Google to index your site. After a few months of this, you can start to understand what it would take to create enough pieces of unique content to make an SEO strategy work. You can usually work this kind of thing out on a spreadsheet.
Balancing between the two
It’s important to balance these short-term and long-term efforts. If all you do is work on nonscalable marketing methods, then inevitably the channels will tap out and your growth will slow. When you see the startups that are highly dependent on press hits for their traction, but seem anemic otherwise, this is exactly what’s happening.
The barbell strategy helps products make progress on long-term goals while still creating short-term momentum – you’ll need momentum to attract investor interest, but you’ll need the long-term scalable growth channels to really build your business.
Good luck. And if you have a product that’s working well, has a nice base of traction, and now the only things that can move the needle are scalable methods, don’t hesitate to email me for advice: voodoo at gmail.
Lessons learned adding messaging to a notes app (Guest Post)
[Today we have a guest post from Alex Schiff, who’s a co-founder and CEO of Fetchnotes, which makes simple, smart tools that help people work together and get things done. Fetchnotes graduated from Techstars Boston in November 2012, and is currently a team of 5 in Cambridge, Massachusetts. -Andrew]
Alex Schiff, CEO of Fetchnotes:
Thereâs a big craze in messaging right now, and everyone seems to be trying to integrate some form of it into their product. Having learned that people who shared notes were way more likely to build a habit with Fetchnotes, we definitely caught the bug in our last iteration. It also coincided with a goal to evolve our value proposition beyond just personal organizationâââthereâs just a lot of noise in that space.

A more detailed overview of that product, featured to the left, can be found here. To summarize, we wanted to create an organized feed for the things youâre keeping track of as well as the things other people want you to be keeping track of. Effectively, we built out messaging features (revolving around @-mentions) that allowed you to communicate in a hyper-organized way, on top of what was still at its core a personal notes/to do list app.
We learned a lot about the way people communicate and work together (which is informing a lot of future product plans), but we didnât really budge the core metric we were trying to move: % of monthly active users sharing at least one note per month (below).

The % of users sharing actually went down before returning to pre-launch levels. We had a large influx of users from launch press, but the sharing value proposition still didnât click. As a result, we had an even higher percentage using it as a personal notes app. Not the results we wanted, but we learned a lot in the process.
For anyone out there building social products, I wanted to share some of those lessons.
Be aware of invisible mental walls
Before we launched this iteration, a common complaint we heard was that the places people kept track of information personally tended to be isolated from where other people sent it to them (email, SMS, and other communication channels). This was pretty consistent across both people who used Fetchnotes and people who used other tools, and it was a major influence on the product we designed.

It turns out that while information silos are indeed a pain point, a major reason they exist is because people tend to think of âpersonal stuffâ and âshared stuffâ differently. They donât want them co-mingled in one organizational area. When we started asking people the right questions, we also found âI need to send this to someoneâ is just not the same mental mode as âI need to remember this for myself.â
With good reason, tooâââhere are some problems that you run into when you try to combine the two:
- People have different ways of organizing, prioritizing, categorizing, etc. that conflict with each other. And they are very particular about itâââeverybodyâs a little OCD.
- Where you keep track of personal information is sacred. When other peopleâs stuff start showing up, you feel like itâs not yours anymore. That leads you to not want to put deeply private material there.
- Messaging/communication is inherently noisy and chaotic. Personal organization is about order.
Most often, people bucket Fetchnotes as either social-only or private-only, and generally itâs the latter. So if youâre building a product that has anything to do with shared and personal organization, make sure you give people walls to protect their âpersonal space.â
The concentration of communication channels

We were trying to get people to use Fetchnotes to communicate things that had an element of permanence or action. It was all about adding things to peopleâs listsâââi.e., organizing your communication so it was where the recipient wanted it (featured to the left). What we didnât want was the more conversational fluff, like this:

At that point, we might as well be having a conversation in Google Docs.
By talking to a lot of users and non-users about their habits, we learned that communication channels tend to concentrate around only a handful of categories:
- People. âWhen I want to talk to Hans in Germany, I use WhatsApp. When I talk to my mom, I use SMS.â
- Context. âWhen I want to talk about work stuff, I use Slack. When I want to talk to my friends about going out later, I use Facebook Messenger.â
- Media type. âWhen I want to send my friends photos, I use Snapchat. When I want to communicate via text, I use SMS.â
- Publicity. âWhen I want everyone to see my thoughts, I use Twitter. When I want to send messages privately, I use SMS.â
If someone canât use a product for all of their communication within one of those buckets, you tend not to use it for any of your communication. There are certainly exceptions, but theyâre exactly thatâââexceptions. People need an extremely clear mental model to answer the question, âWhen do I use this app?â
Regardless of what product youâre building (though itâs especially true in messaging), make sure that your users can answer that without having to think.
Make sure your âviral hookâ is organic and frequent

Our users frequently asked for ways to share their notes with non-users, and that underpinned a big part of our growth strategy. That was the thinking behind our address book integration, which actually works quite well when people need it. In fact, about 25% of all notes shared are shared with non-users (via SMS or email).
The problem, as we realized, is that communication is about sending (one-way) information to another person. When I message someone about say, a link I think they should check out, Iâve already checked that link out. I donât need to save that information for myself, so I have no reason to send that information to you via Fetchnotes (since it will just send you a text anyway). People do share with non-users in other ways (like sharing pre-existing notes after the fact), but that behavior isnât frequent enough to make an impact on growth (less than 1%).
So as youâre thinking through your âviral hook,â make sure youâre building it around something that people organically need to do, and need to do often. âNon-user sharingâ around inorganic behavior is just an invite system no one uses. Get granular, map it out from beginning to end, and talk to people about how they accomplish these steps currently. Donât take shortcuts or make assumptions.
Your network-specific identity is probably confusing people
Way too many companies start off thinking, âWe need our own identity!â Pretty much every major social network has one, and theyâre enticing from a brand perspective (i.e., âFollow me @alexschiff on Twitter!â). However, most products donât really need usernames to be front and center. People donât want yet another identity to think about, and it usually ends up causing a lot of design complexity. Product managers tend to believe people will value their usernames, but unless youâre a product that is public in nature people stop caring after five minutes.

Ideally, identity should be something that fades into the background of a social product. Particularly for productivity-oriented tools, no one wants to share with â@alexschiffââââthey want to share with âAlex Schiffâ. Unless your product is public in nature, you might not even need a username at all. Either way, focus on real names, not aliases.
How groups adopt tools
Finally, we noticed a major trend in the way groups adopt toolsâââone that existed across families, businesses, friends, and pretty much anyone we talked to. We identified 3 major personas when a group chooses to use a new product, and one of them is much more important than the others.
The Leader

The leader isnât necessarily the âalphaâ of the group, but theyâre the one who takes the lead in planning and organizing. More importantly, theyâre the one who searches, evaluates and introduces a tool into the groupâââthey want to use something to improve efficiency. They would generally set up Fetchnotes, load in a bunch of information (i.e., a list of prospective apartments youâre sharing with your roommates), and start using it completely. Frankly, theyâre not that pickyâââthey just want it outside of the noise of normal communication channels.
The Engaged Follower
The engaged follower is the person who contributes to the conversation, but defaults to using existing channels like email or text. For example, rather than adding a new apartment listing in Fetchnotes, they would send everyone an email, text, FB message, etc. They vary in reluctance to adopt new technology, but the unifying pattern is that they end up dragging the conversation back into email by not using the chosen tool.
The Passive Follower
These are the people that just go with the flow on how things are planned. They might contribute a little or not at all, but theyâll generally just go wherever the conversation is happening. This is because, for them, the conversation is more for reference than it is actively contributing their own ideas and effort.
Today, collaboration products are built for the leader. In other words, theyâre built with the assumption that everyone in the group is planning on using it. But the secret truth is that theyâre already plenty satisfied with the tools availableâââitâs the lack of adoption by other members that causes problems.
The key to getting group collaboration tools adopted, I believe, is by making it work for the âengaged followers.â The âpassive followersâ will go wherever the conversation goes, and the leaders are generally satisfied with the tools that already existâââbesides the fact that no one will use them.
