Monday, May 27, 2024
HomeCommentaryA Product Marketing Case Study: Rypple

A Product Marketing Case Study: Rypple

I had an interesting chat with a startup and I wanted to share their story because I think that it’s one that product marketers and product managers could learn a lot from.

The founders of this company were founders of a successful company called Workbrain.  Workbrain provided solutions for workforce management and grew to close to $100 million in annual revenues before being acquired in 2006 by Infor.

When thinking about their next venture they went back to the human capital management space looking for unmet needs.  They hit on the issue of performance reviews and how much people hate giving and receiving them.  One reason this is true is because the end users (employees and managers) have different goals than the folks that own the process and buy the tools (Human Resources). HR’s goals of determining pay increases, identifying top/bottom performers, promotion planning, etc, don’t line up with an employee’s wish to get some timely feedback or management’s desire to give it when it’s needed.

So the idea for their new company, Rypple was born.  Rypple allows users to is a tool get feedback from managers, peers or anyone else whose opinion they trust.  This feedback can be about anything from a person’s performance, to opinions on an meeting or input from a team on working together.  It’s easy to use – just put in your question, choose whom you want to ask it to and away you go.  Rypple is as remarkable for what it doesn’t do as it is for what it does do.  It doesn’t constrain people to a set of pre-defined questions, nor does it determine who should give you feedback or when you receive it.  Feedback is completely anonymous, so people can feel to call it like they see it. By leaving the tool so open, the Rypple folks left room for users to use the product in ways they couldn’t have imagined, such as using it to survey customers or to take an anonymous vote on something.

Sounds great right?  Wait a minute! Did you say free?  Where’s the money!?  HR owns the budget for tools related to performance reviews and frankly, they’re the ones that got us into this mess in the first place.  They aren’t going to want to rip out what they’ve spent years building up.  Plus some of these use cases aren’t looking so much like HR’s domain anymore, are they?

Rypple’s approach takes a page from the open source handbook.  The tool is web-based so there is nothing to install and it’s free.  Users can simply start using the tool today, regardless of any corporate policies or HR processes (MySQL pops up in companies in much the same way). Managers or HR folks that start seeing the benefits of using the solution, then want to formalize its use inside the company.  That means they need support and a security, which Rypple sells to them for a small per user, per month fee.  Notice that Rypple didn’t have to displace or disrupt anything to get to this money.  As Dan Debow, the co-CEO put it to me “Our competition isn’t performance review systems, it’s pizza.  If you have budget for a monthly team pizza lunch, you can buy our solution.”

Does this all translate into hundreds of millions of dollars in revenue?  Time will tell but so far it seems to be working. After launching just a few months ago, Rypple has thousands of users at hundreds of companies.  And so far they haven’t had to “sell” anyone.

So what can product marketers at startups learn from this example?  A LOT.  Here’s my take:

  1. Start with a business problem – Notice how I didn’t mention technology once.  The Rypple founders focused on identifying a business problem first, then started thinking about how best to solve it.
  2. Do what you know – It wouldn’t make sense to go from human capital management to building satellites.  Your knowledge of an existing market counts for a lot in discovering unmet needs.
  3. Personas matter a LOT and not always just the buyer’s persona – I’ve successfully sold B2B software where the end user’s opinion of the solutions didn’t matter to my sale whatsoever.  One of the key decisions Rypple made was to focus on the unmet needs of the USERS and then figure out a way to have either the users or the HR folks buy.  Focusing only on the HR buyer would have resulted in a “me too” product in a crowded space.
  4. Don’t be afraid of simplicity – The simplicity of the solution left the door wide open for users to be very creative.  Focusing too heavily on performance reviews in the initial version of the product would have discouraged users from trying to use it for other things
  5. An innovative business model can matter as much as an innovative product –  Targeting end-users instead of HR buyers was a stroke of genius.   This isn’t an HR solution – it’s a tool for making employees, managers and teams better at their jobs.  As a manager I would give up my team lunch money to buy that and after a few months, I’d be asking why it wasn’t coming out of HR’s budget (if HR didn’t ask the question first).
  6. “Viral” applies to products as much as it does to marketing tactics – One of the beautiful things about Rypple is that every user brings on more users with each request for feedback.  The product itself is inherently built to spread and in effect, sell itself by getting itself into users hands through other users.

Subscribe to this blog or follow me on Twitter or Friendfeed



  1. This is a great story April.
    The last company I worked for implemented a big system to meet this need, including cascading goals from the top right down. I liked the idea of it, but it was a bear for the HR Director to get employee buy-in – and it sure seemed like that needed to be a success factor. Sounds like the emphasis on user personas is stronger here.
    Tom @tomwgibson

  2. Thanks for the comment. Like I said in the post, I’ve marketed and sold a lot of software where what the end users thought was irrelevant. The product I sold at Siebel for example was not exactly popular with the sales forces that had to use it but it did everything Sales Management wanted it to and that’s what got us the deal.
    I don’t think an approach of just focusing on the end user will work in every case but in this one, the results are pretty interesting.

  3. Great post April.
    I really like point #4 around simplicity. Don’t pigeon hole your product by going too deep and specific initially. Get your product out and let the users define it, change it, improve it, love it.
    Tons of best wishes for Rypple success

  4. Great story April and lots of that rings really true.
    For example: “Do What You Know” – could write a book on that and the number of technology companies I’ve come across who think that they could apply their technology to any problem in the world. But the truth is that an organisation can only do what it has the capability to do. That includes understanding the needs, understanding the market, understanding the workflows, without that they are just dreaming.
    They just get so hooked up on how cool their technology is (see: ) that they can’t see the real world and bend their world-model to fit their technology application. How many of us, for example, have seen a B2B technology company successfully launch a consumer product?

  5. Thanks for the comment. Simplicity is so much harder than it looks. It’s very difficult to fight off the urge to design in everything you can possibly think of that might make your product more appealing to customers. The downside the folks don’t often think about is that each decision to add something closes the door on a set of other things that might have been possible.

  6. Market insight counts for a lot, particularly when you are getting started and you don’t have a lot of customers and users to work with.
    I used to think there was a wide gulf between B2B and B2C, but I am changing my mind on this (will follow up on that in a later post).

  7. Hi April
    I like your idea to find innovation by starting with the business problem. In your Rypple story, the real business problem seems to me much larger than just sending around feedback on demand. So, the question is, how to come to a complete view.
    Conventional: Study and specify for years
    New: Choose an approach like your pt 4 (crowdsourcing/ Wikipedia).
    Intermediate step: Involve experts (or lead users), and find the business problem, which the personas **really** have (taking as given, what they tell you about the problems, they think they have).
    Example: You did not strive the point, how the business model works with companies that do not allow hosted tools for critical data (data security).

  8. I stumbled upon at Mesh. A unique tool for 360 degree feedback. The power of getting safe (because it’s anonymous) feedback cannot be understated. I’ve been using it and recommending it to others, who are also finding success with it. In fact April, you should post a Rypple (there, I’m the first to turn Rypple into a noun) on your blog on Rypple.
    BTW, excellent blog/description of Rypple.

  9. Nice case points April. I would add that that they are remaining user centered by getting Rypple in people’s hands and watching closely. I’ve already see several new features come out. Adapt and evolve, don’t over plan!

  10. How honoured am I to have worked with both April and Daniel at two amazingly successful start-ups AND am now a customer of Rypple AND an HR leader… but don’t hold that last point against me Daniel. 🙂

    We love your blogs at Kobo. My 4th start up now. Please keep them coming.


Please enter your comment!
Please enter your name here

Most Popular

Recent Comments

Ashawndra Edwards on Choosing a New Vertical Market
marcelene28 on Startup Marketing Podcast
Name: Johanna on How to Name Your Startup
Samuel Riksfjord on A Value Proposition Worksheet
Vivian Dilberd on Startup Marketing 101
Krissie Thornton on A Value Proposition Worksheet
Krissie Thornton on A Value Proposition Worksheet