Startups Stack Exchange Archive

How To Validate A Peer-to-Peer Business Idea

Pretend you just came up with the idea for Airbnb. How would you validate that you had an idea worth pursing.

What I’m trying to get at more generally here (and from my other questions) is how to validate a peer-to-peer business idea.

Answer 427

  1. Focus on Customer Outcomes. These are very specific, measureable outcomes like Minimize cost of an X day stay place to sleep. Note that we are avoiding talking about solutions b/c customers may not be able to visualize your solution (yet). So let's say the Outcome "space" or "area" is : Overnight stay away from your home. We'll then exlore the pain associated with that. I'd focus on each half seperately, starting with the Renter and then looking at the Rentee (landlord or host)

  2. Get a small focus group of customers (maybe 20 in focus groups of 3 to 8) and talk to them about their needs to create a fairly exhaustive list for #1. So you might find Outcomes like:

    a. Minimize cost of "hotel room" with a kitchen. b. Minimize cost of "hotel room" with XYZ

  3. After you have that fairly exhaustive list, find 800 to 2,000 potential users to take survey where they rank how important each outcome is and how well served their current solution(s) are. This is tricky b/c in the Airbnb example, you need to survey both halves: the renters and the rentees.

  4. Look for Opportunities, which are Outcomes that are Important and Undeserved.

Ideas in this answer were shamelessly stolen from What Customers Want by Ulwick.

Answer 408

The activity that you’re after is two things, of which I feel the most important is Customer Development. The other is to build out the Business Model Canvas. Between them, they tell you whether anyone cares about your product or service, who in the organisation you have to reach, why they care about it, and how much they’re prepared to pay to deal with the problem; the business model canvas tells you whether you can build an organisation that will deliver what the customer has told you they want, andwhat the critical factors will probably be.

Customer Development is based on identifying from historical behaviours, whether anyone finds a problem for which you have a solution, important enough to throw money at it. If they do care, who is the person in the organisation that cares - whose KPI, whose salary, whose easy life, are you solving such that they will release budget?

All my problems with startups have come from failing to grasp this stage. Making sure that you know who the customer is, why they’re a customer, and how much the problem you solve, costs them. You can do this before you have a product. You can do this before you build anything. And you can do it on paper, and the phone, for peanuts - other than time invested. It’s what I do, now, and I’m starting on CustDev for my next startup. :)

Answer 423

That is a tricky question.

If its a Me-Too business (copy of an existing model with minor variations in an existing industry and you are looking to take a % of the industry pie) then I would see who was the first to start the field and learn their history, see how much money is in the field, and then read up on how competitors started and or flopped. From that your market data would be around how to transition existing users from that services to yours.

For NexGen business (new product, new market, new scope, solving a problem no one else has started e.g.) then its really the wild west. For that you will need to first take the idea and flesh it into terms for people to understand/comprehend. Then figure out how to build a low cost, low effort MVP or prototype to show people.

If any of this can be summed up by a simple quote

“If I had asked people what they wanted, they would have said faster horses. ― Henry Ford”

I usually lean on getting a prototype first to show. Sometimes the words you use will never really paint the full picture until one uses/sees it in action.

Answer 426

You’re starting with the wrong question. Ideas are plentiful, good and bad, and nobody has a reliable way to distinguish the two.

The classic lean approach is to start with a customer group you would like to serve, and a problem hypothesis. Work as hard as you can to dis-prove that the problem is real. If you can’t, work as hard as you can to prove that nobody will pay you to solve the problem. Do this by talking to people, by claiming you have the answer to the problem, and by seeing how fast you’re sent away with your tail between your legs.

This investment in time and effort has a guaranteed negative return, but it spares you the greater pain of falling in love with your ideas, bringing them to reality, and seeing them rejected.

Now you have a space in which to create an idea: not just any idea, but an idea for a way to solve the problem that you have evidenced, that someone would pay you to fix. But don’t create just one idea, create a hundred and one ideas. Ideas are cheap, implementation is expensive, and execution is infinitely challenging.

When you’ve reached this point, you can start applying taste and judgement to choose which one or two ideas you are ready to take to the next stage - some kind of minimum viable product (which may just be words you speak to the next ten prospective customers).

Airbnb isn’t an idea. It’s a system, a user base, a story, a community, it’s lots of things. Nobody is waiting to pay you for your idea, however awesome.

But if you can take away a painful problem, even clumsily, when nobody else has, we’ll queue round the block to buy that from you.


All content is licensed under CC BY-SA 3.0.