Value or Viral?

I can’t help but think that the startup world is a bit drunk on the concept of viral distribution. Distribution is a huge problem for startups, so I suppose that I can’t blame them.

First of all, I want to point out that I think viral distribution freakin’ rocks. It’s amazing. It’s awe-inspiring. If you can build virality into your app, do it– and do it early. What I’m focusing on in this post is when a startup is presented with a choice of “viral or value”. Either in the very earliest days when deciding what idea/problem/space to pursue (“We really love this idea, but this OTHER idea has soooo much inherent virality!”), or when making choices about features and initiatives in your startup (“THIS would make our users happy, but THIS would really bring in the new eyeballs!”). While we all like to go on about all of the hats we wear as entrepreneurs, it’s damn hard to be maniacal about making your users happy AND be investing time and energy in distribution.

So, as I watch myself continue to back-burner features at RescueTime that have viral/SEO potential, it occurs to me that it’s probably worth running through my thoughts on WHY. Thus this blog post. You can run through my thoughts with me.

“It’s easier to build a great business on top of an existing viral engine than it is to build virality into an existing business”

This was said to me by a hacker who was working with a team on a “stealth viral business”. At the time, I found myself nodding. You can’t throw a rock in Silicon Valley (or Seattle) without hitting a startup that has tried to staple on a viral loop to their application or service. “I know!” Manager X says. “Let’s add a tell-a-friend bucket to our app. And we need to widgetize it. Oh, and we should probably make a funny video about it! Then we’ll explode!” It turns out that viral loops are HARD.

But, as I think about it, I can name something that’s a LOT harder, and that’s building a product that people really want. In fact, I can fairly readily name off a long list of Facebook Apps and widget companies that have, with fairly minimal effort, built apps that are viral. I can’t as easily name off companies that have created great products that people love over a long weekend of coding. Products are HARD. Virality is, comparatively, much easier.

Another point to illustrate this– Top Facebook Apps are hemmoraging active users (some have lost 30-40% from peak). Presumably, these app creators are alarmed. I can imagine small teams huddled over a table frantically running through how they can make their apps more fun, more useful, more real. Here is an army of smart and well-financed people who are trying to add a great product onto an existing viral loop. I don’t think many of them are having a lot of success.

Virality Isn’t New

It’s important to note that virality isn’t new, especially if you argue that word-of-mouth is the same thing. For the purposes of this post, I’m talking about the type of virality that Andrew Chen (who is one of my absolute favorite bloggers) defines as:

“I tend to think of Viral Marketing that include both systematic and unsystematic ways that your current customers acquire new customers… In some of these cases, the virality has been “built-in” to the system – for example, but chain letters explicitly promise you something in return for sending on a letter, as do Multi-Level Marketing systems like Tupperware. These incentives and systematic design are originated with the intent to propagate a viral process.”

In the standard word-of-mouth model, you have:

1. User tries product.
2. User loves product.
3. User evangelizes product to everyone they know.
4. Some subset of those preached to (greater than 1) tries the product.
5. Rinse, repeat.

Think Google, Apple, Microsoft (in the early days), etc.

In the viral-focused model you have:

1. User tries the product.
2. As part of trying the product, they (sometimes unwittingly) tell everyone they know about the product.
3. Some subset of those victims tries the product.
4. Rinse, repeat.

Think Facebook Apps, chain letters, tupperware parties, Geocities, and Hotmail. Or, let’s roll back to another web investment mini-craze– the SEO/Vertical Search business. Any SEO/user-generated content business is inherently viral. User creates account. Some subset of new users create a page of content. Content gets indexed by search engines. The new page brings in some traffic. Eventually, that user-created page converts a visitors to a content creator. Rinse, repeat.

Paul Graham (“ah, yes– the obligatory PG quote”) talks about the concept of getting upwind of revenue:

“In Patrick O’Brian’s novels, his captains always try to get upwind of their opponents. If you’re upwind, you decide when and if to engage the other ship. Craigslist is effectively upwind of enormous revenues. They’d face some challenges if they wanted to make more, but not the sort you face when you’re tacking upwind, trying to force a crappy product on ambivalent users by spending ten times as much on sales as on development.”

What I THINK he’s also advocating for is the concept of getting “upwind of distribution”.

It seems to me that when you remove the “user loves the product” step, you’re failing to solve the CORE problem that needs to be solved to build a great company. If you can’t create and maintain unique value with your widget or Facebook app, you’re doomed to experience the same fate as chain letters, mood rings, and GeoCities. You might well be able to get in and get out (with millions of dollars in your pocket) before you “jump the shark“. If your startup has a user-generated-content component, you might be able to amass enough SEO-fodder to make a healthy living on advertising, but that has its own challenges.

Hopefully you’ve got some grand capital-efficient plans to get it in front of your target market (WE do– we haven’t even gotten started at this front). But if your wondering why users aren’t coming to your web site, chances are you have a product problem– not a marketing problem.

It’s not what you say… It’s what they hear

Long ago, when I set up this blog I read a few primers on blogging. One of them suggested that you have a picture of yourself on your blog. There were lots of good arguments for doing it, so I dutifully hunted among my photos for a picture of myself. Turns out that I didn’t have too many (I tend to be behind the camera rather than in front of it).

tpic.jpg

I did find one that I liked. It was on a nasty old fishing boat on the Prince William Sound (in Alaska). A friend of mine had bought the boat and invited a few friends for an multi-day cruise. There was no running water. The bathroom was a 5 gallon green bucket (I’ll leave it to your imagination how we “flushed” it). At the end of the trip, I was scruffy as hell, but I’d had an absolute blast tromping around the rugged islands of Alaska. That’s where the pipe picture was taken.

As my blog actually accumulated readers, there came a trickle of negative feedback about the pipe, which has increased to a steady stream. Some people feel like I was trying to look serious. Or academic. Or rich. Or that I was just clowning around. To me, the photo had a ton of meaning. To anyone else, not so much.

For some reason, this made me think of one of my favorite posts on product/UX design. Here’s a quote:

“When I started working on Wufoo, I was definitely a bad designer. I thought I was hot shit and knew all the answers. I saw the user as a wild beast that needed to be tamed. He got in MY way. Use the tool the way I designed it, fool—not the way you think it should work [emphasis added]. Thinking back, I remember being angry all of the time.”

One of the big lessons (which I continue to learn a little bit more every single day) is that it doesn’t matter a damn bit what you’re saying (whether you’re “saying” it to a user with design or saying it with words or pictures on a blog), it matters what’s being heard.

So I’ve pulled the pipe picture in favor of a more recent one. Some people suggested that I keep it as a “schtick”, but I’d rather be known as “that guy who kicks ass with RescueTime” than “that guy with the pipe” (who actually never smokes a pipe).

RescueTime Improves… A little bit, and over and over again!

One of the frustrating things about iterative software development is that you never get to do a heroic launch (a la Steve Jobs). Your software starts off to be barely good enough for someone to endure. The next week it’s better. Rinse, repeat. If you’re good, someday you wake up and you’ve built great software. We’ve got a long road before this day, but we think we’re onto something.

Anyhoo, hat tip to Web Worker Daily!

They posted a note describing some of the cool new features in RescueTime, including the very first version of RescueTime Groups, which seems damn promising. Give it a look!

Does a Business Guy have a Place in Software Startups?

[edit: I should probably have made a stronger point that I am talking about early early early stage startups. 2-5 people, pre-funding. Carry on!]

There is a tremendous amount of venom loosed towards so called “business guys” or “idea guys” (as I’ve called ‘em) in the startup community. They can’t catch a break.

A big part of the reason is that we’ve all had that hellish experience with the MBA. The guy who has his “big idea” and “just needs someone to build it”, presumably why he stands back and waves his hands a lot (and occasionally plays golf in space). You can find CraigsList littered with ads by biz guys, incredulous that hackers aren’t falling all over themselves to execute on their ideas.

It doesn’t take a lot of hunting around to learn that great technology startups aren’t generally built on the shoulders of a great business guy. Here’s a gem of a quote from a gem of an essay:

If you work your way down the Forbes 400 making an x next to the name of each person with an MBA, you’ll learn something important about business school. You don’t even hit an MBA till number 22, Phil Knight, the CEO of Nike. There are only four MBAs in the top 50. What you notice in the Forbes 400 are a lot of people with technical backgrounds. Bill Gates, Steve Jobs, Larry Ellison, Michael Dell, Jeff Bezos, Gordon Moore. The rulers of the technology business tend to come from technology, not business. So if you want to invest two years in something that will help you succeed in business, the evidence suggests you’d do better to learn how to hack than get an MBA.

Take a look at the genesis of your favorite startup and find me the MBA. Find me the program manager. They just aren’t there.

So your startup doesn’t need a business guy. In fact, there seems to be pretty compelling evidence that having a business guy in your software startup has a reverse corrolation with success.

So, take a walk, biz guy. We don’t need you.

Or do we?

It turns out that it’s not so simple as that. Startups are diverse– each startup has different needs. How do you think SalesForce.com would’ve done if it’d been started by a bunch of hackers? How do you think Zappos.com would have fared if it wasn’t started by a zealot for customer service and support? There are plenty of examples of great software startups with a critical founder who wasn’t really a technologist (arguably, Apple is a great example of this). And there’s no denying that for startups that have something that they intend to CHARGE for, a business guy is incredibly valuable– so long as he actually can dive in and do sales largely full-time. Most business guys I know turn there nose up at cold-call style sales– which is really what you need.

So what does every startup absolutely need?

Startups need BUILDERS. People who make stuff. Absolute animals, as Paul Graham puts it. People whose output is positively awe-inspiring.

But startups also need a product genius. Someone who has great instincts about what people want and need.

So what’s to stop a business guy from being a product genius? Not a darn thing. Sure, there are plenty of biz guys who are stupid about products, but it certainly doesn’t take much work to find a hacker who has a truly awful idea for a product.

It’s just not so simple.

But I’ll tell you something that is simple: a hacker or designer’s output is strongly correlative with their sense of ownership. Here are a pile of modifiers that can effect a sense of ownership:

  • The builder *IS* the “idea guy”. It’s his idea. (+50)
  • The builder isn’t the “idea guy”, but has the problem that the product is trying to solve. (+40)
  • The builder isn’t the “idea guy” and doesn’t really have the problem that the product is trying to solve, but can really empathize with the problem. (+30)
  • The builder is a principal author of HOW the solution is built, even if WHAT is being built isn’t entirely his baby. (+20)
  • The builder stands to make truckloads of money if the product takes off. (+20 * the number of truckloads)

In a world where startups are beset with endless challenges and frustration, anything you can do to heap on a feeling of ownership among the people who are actually building stuff is critical.

If there’s any indisputable advantage that startups have over big business, it’s the insane amount of sheer output that a startup can generate. Part of this is just being lean and bureaucracy-free, but a huge part of it is the motivation that comes with a sense of ownership. I think it’s pretty safe to say that the bigger a company gets and the more pure-play “managers” that get hired, the farther away the builders get from this feeling.

For all the startups out there who have a biz guy playing golf in space while a collection of hackers and designers slave away on the idea that they don’t really love…. Well, I don’t think you are necessarily doomed to failure. But I think you’ve taken an uphill road that’s a bit too steep for my tastes.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25  Scroll to top