Tagged business model

Browsing all posts tagged with business model

The #CustDev Whiteboard

Steve Blank and Alex Osterwalder have combined their respective methodologies, Customer Development and Business Model Generation, into a powerful business model generation and testing framework.  There are several good sources for how these two mesh, including this Jan post on Osterwalder's blog, here and most recently, in Blank's SXSW presentation:

Blank's Customer Development is critical, otherwise speculating what comprises your startup's business model is just another academic exercise.  Arguably, one could easily waste as much time documenting assumptions on your business model canvas as documenting them inside a 40 page business plan.  The canvas exposes your hypotthesis and customer development tests them.  It's a laudable ambition to document and test all of your business model canvas components.

But how much is necessary to get going?

All building blocks are not created equal.  I believe there's a natural progression towards figuring out your business model and many blocks are directly dependent on prior blocks.  Is it worth the time to document 2nd or 3rd tier blocks before establishing the reality of 1st tier?  The answer, of course, depends on you and your business.  It doesn't hurt to go as far as you can at the start, unless the activity inhibits you from getting started, i.e., "getting out of the building."

To use a rather simplistic example, you might presume that your customer is an enterprise-sized business that requires a field sales force and partnerships with highly technical systems integrators.  What if your customer ends up being a medium-sized business that requires SaaS product distribution?  Early customer development might very well point you down the correct path from the outset.  Some business model components flow naturally from validated core hypotheses.

The real dilemma in my mind is, what do you test first? The key to getting started is to nail the validate of the core hypotheses: Customer, Problem, Solution.

Go to the #CustDev White Board

#CustDev whiteboard imageIn our book, The Entrepreneur's Guide to Customer Development, Patrick Vlaskovits and I developed a white board exercise to help think through business model risk in order to determine what to test first.  The key components are:

=> draw the ecosystem around your business as you imagine it, including partners, distributors, customers.

=> determine which are mission critical -- in other words, can you get going without any?  Which are absolutely necessary?

=> state the value proposition for each mission critical participant -- what determines whether or not they join the ecosystem?

=> list the minimum product functionality necessary to get entities to participate.

=> prioritize the risks (technical and market) based on the above.

Ultimately, what you trying to prioritize is: what's the quickest way to fail your business model. The "value path" of testing your business model runs through testing the the core value proposition of each of your mission critical ecosystem entities.  Easiest to test means:  what you can test in the shortest time frame.

If building a landing page and driving traffic to it has the potential of killing your present business model hypotheses, then it's a legitimate "intermediate MVP" and worth testing.  But be careful.  Are you sure you're not testing your ability to drive some amount of traffic or your positioning?  If a 3rd party API doesn't provide the hooks you need to develop a critical piece of technology and therefore your business model fails, maybe that's what you test first.

Documenting the building blocks of your business model = good.  Using the #CustDev White Board exercise in conjunction helps you determine what to document and test first.

How do you determine what to test first?

Lean Start-up: Part II

I have a great opportunity to test out some theories about customer development, process-oriented, and metrics-driven marketing. I thought I’d keep a running blog on our progress.

Week 1 is here.

By now we have completed the following:

  • documented business hypotheses;
  • identified 100+ potential users -- primarily through personal networks;
  • identified partners;
  • created interview process, objectives, and questions;

MRD is now in the hands of Engineering who is preparing wireframes.   Part of our completed assumptions include the features we believe are required to secure memberships, subscriptions, and advertisers.

We have chosen our temporary blogging platform.  I now need to get the "visionary" comfortable blogging.

We have discussed metrics.  We have a couple of phases defined, similar to phases of customer and product development.  Our primary objective at this point is to get more funding.  To do so, we must go as far as we can to prove the business model. It is interesting, that even at this juncture in company development, there is difference in opinion about how to define progress.  Some would like to measure progress by deliverables, which is a classic project management approach.  And there's nothing wrong with that.

But how do deliverables tie to our objectives? If our objective is to earn additional funding, the "deliverable" is not "a functional web site," but rather proof of the business model. So while proof requires a functional web site, what we actually need to achieve with existing funds is much greater.

So, what we are doing now:

  • scheduling interviews with users and partners;
  • developing online survey to gather more detail;
  • finalizing 1st phase of product development;
  • defining 1st phase metrics

Comments welcome.