Henrik Berglund, Venture Cup, feb 2013

145
Henrik Berglund Chalmers University of Technology Center for Business Innovation [email protected] www.henrikberglund.com @khberglund Business Models/Customer Development 2022-06-18 1

description

Henrik Berglund, Presentation at Venture Cup, feb 2013. This presentation is based on the Customer Development theory developed by Steve Blank and Bob Dorf (http://www.steveblank.com), and is based on slides developed by Steve Blank and Bob Dorf (http://www.slideshare.net/sblank/).

Transcript of Henrik Berglund, Venture Cup, feb 2013

Page 1: Henrik Berglund, Venture Cup, feb 2013

Henrik BerglundChalmers University of Technology

Center for Business [email protected]

www.henrikberglund.com@khberglund

Business Models/Customer Development

2013-02-15 1

Page 2: Henrik Berglund, Venture Cup, feb 2013

by Steve Blank and Bob Dorf

More info: www.steveblank.comBuy the book: http://www.amazon.com/gp/product/0984999302/

Presentation based on

Page 3: Henrik Berglund, Venture Cup, feb 2013

developed by Steve Blank and Bob Dorf

http://www.slideshare.net/sblank/

Using slides from

Page 4: Henrik Berglund, Venture Cup, feb 2013

Agenda

1. Startups 2. Business Models (briefly)3. Customer Development

Page 5: Henrik Berglund, Venture Cup, feb 2013

Part 1

Startups(What We Used to Believe

What We Now Know)

Page 6: Henrik Berglund, Venture Cup, feb 2013

What We Used to Believe

Page 7: Henrik Berglund, Venture Cup, feb 2013

Startups are a Smaller Version of a Large Company

Page 8: Henrik Berglund, Venture Cup, feb 2013

What We Now Know

Page 9: Henrik Berglund, Venture Cup, feb 2013

Startups ≠ Small companies

Page 10: Henrik Berglund, Venture Cup, feb 2013

Startups Search Companies Execute

Page 11: Henrik Berglund, Venture Cup, feb 2013

What We Used to Believe

Strategy

Page 12: Henrik Berglund, Venture Cup, feb 2013

Start by developing a Business Plan…

Page 13: Henrik Berglund, Venture Cup, feb 2013

…make the financial forecasts…

Page 14: Henrik Berglund, Venture Cup, feb 2013

…then Execute

Page 15: Henrik Berglund, Venture Cup, feb 2013

What We Now Know

Strategy

Page 16: Henrik Berglund, Venture Cup, feb 2013

5-Year Plans

Page 17: Henrik Berglund, Venture Cup, feb 2013

Develop and Execute the Business Plan

Page 18: Henrik Berglund, Venture Cup, feb 2013

Why?

Page 19: Henrik Berglund, Venture Cup, feb 2013

No Business Plan survives first contact with customers

Page 20: Henrik Berglund, Venture Cup, feb 2013

“Everybody has a plan until they get punched in the face” Mike Tyson

Page 21: Henrik Berglund, Venture Cup, feb 2013

Searching for a Business Model comes before

Executing a business plan

Page 22: Henrik Berglund, Venture Cup, feb 2013

Key activities Value proposition

Customer relationships

Customer segments

Cost structure

Key resources

Revenue streams

Channels

Key partners

Business Models

http://www.businessmodelalchemist.com/

Page 23: Henrik Berglund, Venture Cup, feb 2013

Business Model Hypotheses

Search

Strategy

Execution

Operating Plan +Financial Model

Page 24: Henrik Berglund, Venture Cup, feb 2013

What We Used to Believe

Process

Page 25: Henrik Berglund, Venture Cup, feb 2013

We Built Startups by Managing Processes

Product Management+

Waterfall Engineering

Page 26: Henrik Berglund, Venture Cup, feb 2013

Traditional Development Process

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 27: Henrik Berglund, Venture Cup, feb 2013

Traditional Development ProcessHas Two Implicit Assumptions

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Customer Problem: known

Product Features: known

Works well for incremental development projects targeting existing customers.

Page 28: Henrik Berglund, Venture Cup, feb 2013

Tradition – Hire Marketing

- Create Marcom Materials- Create Positioning

- Hire PR Agency- Early Buzz

- Create Demand- Launch Event- “Branding”

Marketing

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 29: Henrik Berglund, Venture Cup, feb 2013

Tradition – Hire Sales

- Create Marcom Materials- Create Positioning

- Hire PR Agency- Early Buzz

- Create Demand- Launch Event- “Branding”

- Build Sales Organization

Marketing

Sales - Hire Sales VP- Hire 1st Sales Staff

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 30: Henrik Berglund, Venture Cup, feb 2013

Tradition – Hire Business Development

- Create Marcom Materials- Create Positioning

- Hire PR Agency- Early Buzz

- Create Demand- Launch Event- “Branding”

- Build Sales Organization

Marketing

Sales - Hire Sales VP- Hire 1st Sales Staff

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

- Hire First Bus Dev - Do deals for FCSBusiness Development

Page 31: Henrik Berglund, Venture Cup, feb 2013

Examples - Recognize these?

Page 32: Henrik Berglund, Venture Cup, feb 2013

What’s wrong with this picture?

• Both Customer Problems and Product Features are hypotheses

• Emphasis on execution rather than learning and discovery

• No relevant milestones for marketing and sales• Often leads to premature scaling and a heavy

spending hit if product launch fails

You do not know if you are wrong until you are out of money/business

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 33: Henrik Berglund, Venture Cup, feb 2013

- Create Marcom Materials- Create Positioning

- Hire PR Agency- Early Buzz

- Create Demand- Launch Event- “Branding”

- Build Sales Organization

Marketing

Sales - Hire Sales VP- Hire 1st Sales Staff

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

- Hire First Bus Dev - Do deals for FCSBusiness Development

Page 34: Henrik Berglund, Venture Cup, feb 2013

What We Now Know

Process

Page 35: Henrik Berglund, Venture Cup, feb 2013

Product and Customer Development

Product Development

Customer Development

CompanyBuilding

CustomerDiscovery

CustomerValidation

Customer Creation

+

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 36: Henrik Berglund, Venture Cup, feb 2013

Problem: unknown Solution: unknown

Product and Customer Development

Page 37: Henrik Berglund, Venture Cup, feb 2013

Business Model Hypotheses

Strategy

Process Customer &Agile Development

Operating Plan +Financial Model

Product Management& Waterfall Development

Search Execution

Page 38: Henrik Berglund, Venture Cup, feb 2013

What We Used to Believe

Organization

Page 39: Henrik Berglund, Venture Cup, feb 2013

Hire and Build a Functional Organization

Page 40: Henrik Berglund, Venture Cup, feb 2013
Page 41: Henrik Berglund, Venture Cup, feb 2013
Page 42: Henrik Berglund, Venture Cup, feb 2013

What We Now Know

Organization

Page 43: Henrik Berglund, Venture Cup, feb 2013

Founders run a Customer Development Team

No sales, marketing and business development

Page 44: Henrik Berglund, Venture Cup, feb 2013

Business Model Hypotheses

OrganizationCustomer

Development Team, Founder-driven

Customer Development,Agile Development

Operating Plan +Financial Model

Product ManagementAgile or Waterfall Development

Functional Organization by Department

Search ExecutionStrategy

Process

Page 45: Henrik Berglund, Venture Cup, feb 2013

Part 2

Business Models

Page 46: Henrik Berglund, Venture Cup, feb 2013

Key activities Value proposition

Customer relationships

Customer segments

Cost structure

Key resources

Revenue streams

Channels

Key partners

Business Model

http://www.businessmodelalchemist.com/

Page 47: Henrik Berglund, Venture Cup, feb 2013

Key activities Value proposition

Customer relationships

Customer segments

Cost structure

Key resources

Revenue streams

Channels

Key partners

Business Model

A framework for making your assumptions explicit

Page 48: Henrik Berglund, Venture Cup, feb 2013

Customer Segments

Who are the customers?Why would they buy?

Page 49: Henrik Berglund, Venture Cup, feb 2013

Customer Segments

Who is the customer?Multi-sided market?Different from user?

http://www.businessmodelalchemist.com/2012/08/achieve-product-market-fit-with-our-brand-new-value-proposition-designer.html

Page 50: Henrik Berglund, Venture Cup, feb 2013

Customer Segments- jobs to be done

What functional jobs is your customer trying get done? (e.g. perform or complete a specific task, solve a specific problem…)

What social jobs is your customer trying to get done? (e.g. trying to look good, gain power or status…)

What emotional jobs is your customer trying get done? (e.g. esthetics, feel good, security…)

“What jobs are the customers you are targeting trying to get done”

Page 51: Henrik Berglund, Venture Cup, feb 2013

Customer Segments- customer pains

What does your customer find too costly? (e.g. takes a lot of time, costs, effort)

What makes your customer feel bad? (e.g. frustrations, annoyances)

How are current solutions under-performing for your customer? (e.g. lack of features, performance, malfunction)

What negative social consequences does your customer encounter or fear? (e.g. loss of face, power, trust, or status)

“What are the costs, negative emotions, bad situations etc. that your customer risks experiencing before, during, and after getting the job done.”

Page 52: Henrik Berglund, Venture Cup, feb 2013

Customer Segments- customer gains

Which savings would make your customer happy? (e.g. in terms of time, money and effort)

What would make your customer’s job or life easier? (e.g. flatter learning curve, more services, lower cost of ownership)

What positive social consequences does your customer desire? (e.g. makes them look good, increase in power, status)

What are customers looking for? (e.g. good design, guarantees, features)

What do customers dream about? (e.g. big achievements, big reliefs)

“What are the benefits your customer expects, desires or would be surprised by.”

Page 53: Henrik Berglund, Venture Cup, feb 2013

Value Propositions

What are you building?For whom?

Page 54: Henrik Berglund, Venture Cup, feb 2013

Value Propositions

What are your products and services?

How do they create value for the customer segments?

Page 55: Henrik Berglund, Venture Cup, feb 2013

Value PropositionsCan your product/service:

• Produce savings?

• Make your customers feel better?

• Put an end to difficulties?

• Wipe out negative social consequences?

Page 56: Henrik Berglund, Venture Cup, feb 2013

Value PropositionsCan your product/service:

• Outperform current solutions?

• Produce outcomes that go beyond their expectations?

• Make your customer’s job or life easier?

• Create positive social consequences?

Page 57: Henrik Berglund, Venture Cup, feb 2013

Product Market FitGetting this right is essential!

Page 58: Henrik Berglund, Venture Cup, feb 2013

Product Market Fit

Getting this right is essential!

Page 59: Henrik Berglund, Venture Cup, feb 2013

Channels

How does your product get to customers?

Page 60: Henrik Berglund, Venture Cup, feb 2013

How Do You Want Your Product to Get to Your Customer?

60

Yourself

Through someone else

Retail

Wholesale

Bundled with other goods or services

üüüüü

Page 61: Henrik Berglund, Venture Cup, feb 2013

Web Channels

61

Page 62: Henrik Berglund, Venture Cup, feb 2013

Physical Channels

62

Page 63: Henrik Berglund, Venture Cup, feb 2013

How Does Your Customer Want to Buy Your Product from your Channel?

63

• Same day

• Delivered and installed

• Downloaded

• Bundled with other products

• As a service

• …

üüüüüü

Page 64: Henrik Berglund, Venture Cup, feb 2013

Customer Relationships

How do you get/keep/grow customers?

Page 65: Henrik Berglund, Venture Cup, feb 2013

Customer Relationships

Page 66: Henrik Berglund, Venture Cup, feb 2013

Revenue Streams

How do you make money?

Page 67: Henrik Berglund, Venture Cup, feb 2013

Key Resources

What are your most important assets?

Page 68: Henrik Berglund, Venture Cup, feb 2013

Key Activities

What activities are most important for the business?

Page 69: Henrik Berglund, Venture Cup, feb 2013

Key Partnerships

Who are your key partners and suppliers?

Page 70: Henrik Berglund, Venture Cup, feb 2013

Cost Structure

What are the costs of operating the business model?

Page 71: Henrik Berglund, Venture Cup, feb 2013

Visualization of the business model

framwork

Key activities Value proposition

Customer relationships

Customer segments

Cost structure

Key resources

Revenue streams

Channels

Key partners

Page 72: Henrik Berglund, Venture Cup, feb 2013
Page 73: Henrik Berglund, Venture Cup, feb 2013

What’s a Company?

Page 74: Henrik Berglund, Venture Cup, feb 2013

What’s a Company?

A business organization, which sells a product or service in exchange for revenue

and profit

Page 75: Henrik Berglund, Venture Cup, feb 2013

How are Companies organized?

Page 76: Henrik Berglund, Venture Cup, feb 2013

How are Companies organized?

Companies are organized around Business Models

Page 77: Henrik Berglund, Venture Cup, feb 2013

How are Companies organized?

Companies are organized around Business Models

Page 78: Henrik Berglund, Venture Cup, feb 2013

What’s a Startup?

Page 79: Henrik Berglund, Venture Cup, feb 2013

What’s a Startup?

A temporary organization designed to search

for a repeatable and scalable business model

Page 80: Henrik Berglund, Venture Cup, feb 2013

What’s a Startup?

A temporary organization designed to search

for a repeatable and scalable business model

Page 81: Henrik Berglund, Venture Cup, feb 2013

What’s a Startup?

A temporary organization designed to search

for a repeatable and scalable business model

Page 82: Henrik Berglund, Venture Cup, feb 2013

Guess Guess

Guess

Guess

Guess

Guess

Guess

GuessGuess

Page 83: Henrik Berglund, Venture Cup, feb 2013

The goal is not to remain a startup

Startup Large Company

The goal of a startup is to become a large company!Failure = failure to transition.

Transition

Page 84: Henrik Berglund, Venture Cup, feb 2013

Part 3

Customer Development

Page 85: Henrik Berglund, Venture Cup, feb 2013

To repeat

Page 86: Henrik Berglund, Venture Cup, feb 2013

More startups fail from a lack of customers than from a failure of

product development…

To repeat

Page 87: Henrik Berglund, Venture Cup, feb 2013

… because they think startups = small companies…

Page 88: Henrik Berglund, Venture Cup, feb 2013

…they focus on executing the plan…

• Both Customer Problems and Product Features are hypotheses

• Emphasis on execution rather than learning and discovery

• No relevant milestones for marketing and sales• Often leads to premature scaling and a heavy

spending hit if product launch fails

You do not know if you are wrong until you are out of money/business

Concept Product Dev. Alpha/Beta Test

Launch/1st Ship

Page 89: Henrik Berglund, Venture Cup, feb 2013

… so they scale on untested assumptions…

Page 90: Henrik Berglund, Venture Cup, feb 2013

… and end up going bust.

“We have been too visionary. We wanted everything to be perfect, and we have not had control of costs"

Ernst Malmsten(BBC News, May 18 2000)

Page 91: Henrik Berglund, Venture Cup, feb 2013

So what to do?

Page 92: Henrik Berglund, Venture Cup, feb 2013
Page 93: Henrik Berglund, Venture Cup, feb 2013

Customer Development: Key Ideas

• Parallel process to Product Development (agile)

• Measurable checkpoints not tied to FCS but to customer insights

• Emphasis on iterative learning and discovery before execution

• Must be done by small team including CEO/project leader

Page 94: Henrik Berglund, Venture Cup, feb 2013

Customer Development Heuristics

• There are no facts inside, so get out of the building!

• Earlyvangelists make your company, and are smarter than you!

• Develop a minimum viable product to maximize fast learning.

Page 95: Henrik Berglund, Venture Cup, feb 2013

•Customer Discovery Articulate and Test your Business Model Hypotheses•Customer Validation Sell your MVP and Validate your MB & Sales Roadmap•Customer Creation Scale via relentless execution and fill the sales pipeline•Company Building (Re)build company’s organization & management

Customer Development: Four Stagessearch

execution

Page 96: Henrik Berglund, Venture Cup, feb 2013

Customer Discovery

• Articulate and test your BM hypotheses(value prop/customers key)

• No selling, just listening• Must be done by founder

Page 97: Henrik Berglund, Venture Cup, feb 2013

building

blockbuildingblock

buildingblock

buildingblock

buildingblock

building

block

buildingblock

buildingblock

building

block

buildingblock

buildingblock

buildingblock

Sketch out your business model!

Page 98: Henrik Berglund, Venture Cup, feb 2013

But,Realize it’s just Hypotheses!

Page 99: Henrik Berglund, Venture Cup, feb 2013

Guess Guess

Guess

Guess

Guess

Guess

Guess

GuessGuess

Page 100: Henrik Berglund, Venture Cup, feb 2013
Page 101: Henrik Berglund, Venture Cup, feb 2013
Page 102: Henrik Berglund, Venture Cup, feb 2013

”Do you have this problem?”1.2.3.

Test Customer Problem Hypotheses

Page 103: Henrik Berglund, Venture Cup, feb 2013

”Do you have this ”Tell me about it, how problem?” do you solve it today?”1. 1.2. 2.3. 3.

Test Customer Problem Hypotheses

Page 104: Henrik Berglund, Venture Cup, feb 2013

”Do you have this ”Tell me about it, how ”Does something like thisproblem?” do you solve it today?” solve your problem?”1. 1. 1.2. 2. 2.3. 3. 3.

Listen carefully to what they say at each step!

Focus on learning - Don’t try to sell them on your idea!

In the process you find out about other BM parts as well: workflow, benefits (to users & others), preferred channels, critical influencers, respected peers etc…

You want to become a domain expert!

Test Customer Problem Hypotheses

Page 105: Henrik Berglund, Venture Cup, feb 2013

Finding people

Introductions (ask everyone you know)

• Provide the exact text that they can copy and paste into a tweet or email (They’re doing you a favor! Make it as easy as possible for them)

• Tell them exactly how you are going to communicate with their contacts (They’re risking a bit of social capital for you. Be very clear that you won’t spam or annoy people)

• Tell them your goals (What do you think you’ll get/learn if they make this intro for you? People want to know that they’re contributing to a bigger picture!)

Page 106: Henrik Berglund, Venture Cup, feb 2013

Finding people

AdWords, Facebook Ads, Promoted Tweets

Summarize your idea and get it in front of people who have expressed an interest in it by having searched for your keywords and clicked your ad – get conversations (and/or test hypotheses using landing pages).

http://www.cindyalvarez.com/best-practices/customer-development-interviews-how-to-finding-people

Page 107: Henrik Berglund, Venture Cup, feb 2013

Finding people

Twitter Search

Look for people who have already discussed a similar product, problem, or solution and address a tweet directly to them:

“@username Would love yr feedback on [product/problem/solution] – shd only take 2mins [URL] thanks!”

Page 108: Henrik Berglund, Venture Cup, feb 2013

Finding people

Google Alerts

Set up Google Alerts for your product/problem/solution – when it finds relevant blog posts or comments, email and ask for feedback:

“I read your [post/comment] about [product/problem/solution]. I’m currently working on a related idea and I think your opinion would be very valuable to me – could you take 2 minutes and check out [URL]? Thank you – I’d be happy to return the favor any time.”

Page 109: Henrik Berglund, Venture Cup, feb 2013

Interview tips

http://www.giffconstable.com/2011/07/12-tips-for-customer-development-interviews-revised/

Page 110: Henrik Berglund, Venture Cup, feb 2013

Much faster to build => get quantitative feedback sooner.

Use a low-fi landing page as substitute for – and introduction to – conversations.

Key to drive traffic through AdWords/Facebook Ads/Promoted Tweets etc.

Build (design test), measure (run test) and analyze (evaluate test)!

Web

Page 111: Henrik Berglund, Venture Cup, feb 2013

http://blog.kissmetrics.com/landing-page-blueprint/

Landing page design

Page 112: Henrik Berglund, Venture Cup, feb 2013
Page 113: Henrik Berglund, Venture Cup, feb 2013

Reality check!

CustDev and ProdDev teams meet and discuss the lessons learned from the field.

”Here is what we thought about customers and their problems, here is what we found out”

BM hypotheses, product specs or both are jointly revised.

Page 114: Henrik Berglund, Venture Cup, feb 2013

Test Solution Hypothesis

1) ”We believe you have this important problem” – listen (check). 2) Demo how your product solves the problem. Focusing on a few key features.

Include workflow story: ”life before our product” and ”life after our product” – listen!

3) ”What would this solution need to have for you to purchase it?” Listen, ask follow up questions.

Page 115: Henrik Berglund, Venture Cup, feb 2013
Page 116: Henrik Berglund, Venture Cup, feb 2013

Dropbox

• 1st solution test: a three minute video made in the founder’s apartment before a complete code was written.– Generated valuable feedback from visionary customers.

• 2nd solution test: another video of the product that was posted on a social network.– Waiting list jumped from 5 000 to 75 000.

• Dropbox’s original intent was to build and ship their product in eight weeks.

• Instead, they gathered feedback and launched a public version 18 months later.

Page 117: Henrik Berglund, Venture Cup, feb 2013
Page 118: Henrik Berglund, Venture Cup, feb 2013

Test Product Hypotheses

After demoing, ask about other things: Positioning – how do they describe the product?Product category (new, existing, resegmented)CompetitorsFeatures needed for first versionPreferred revenue modelPricingAdditional service needsMarketing – how do they find this type of product?Purchasing processWho has a budget?etc.

Page 119: Henrik Berglund, Venture Cup, feb 2013

Build out a high-fidelity web page with “functioning” back-end, based on lessons learned.

“Mechanical Turk”-solution.

Ask for money: first “pre-order” then charging.

Continue to test, measure and analyze!

Web

Page 120: Henrik Berglund, Venture Cup, feb 2013
Page 121: Henrik Berglund, Venture Cup, feb 2013

Reality check!

CustDev and ProdDev teams meet and discuss the lessons learned.

”Here is what we thought about product features and here is what we found out”

BM hypotheses, product specs or both are again jointly revised.

Page 122: Henrik Berglund, Venture Cup, feb 2013

What are your customers top problems?How much will they pay to solve them?

Does your product concept solve them?Do customers agree? How much will they pay for it?

Can you draw a day-in-the-life of a customer?Before & after your product

Can you draw the org charts of users, buyers and channels?

Customer Discovery: Exit Criteria

Page 123: Henrik Berglund, Venture Cup, feb 2013

Customer Validation

• Develop and sell MVP to passionate earlyvangelists• Validate a repeatable sales roadmap• Verify the business model

Page 124: Henrik Berglund, Venture Cup, feb 2013

Based on your insights from Customer Discovery, sell the smallest feature set customers are willing to pay for!

• Purpose 1: Reduce wasted engineering hours (and wasted code)

• Purpose 2: Get something into the hands of earlyvangelists as soon as possible => maximize learning!

Minimal Viable Product

Page 125: Henrik Berglund, Venture Cup, feb 2013

The Apple I, Apple’s first product, was sold as an assembled circuit board and lacked basic features such as a keyboard, monitor and case.

Page 126: Henrik Berglund, Venture Cup, feb 2013

The owner of this unit added a keyboard and a wooden case.http://en.wikipedia.org/wiki/Apple_Inc.

Page 127: Henrik Berglund, Venture Cup, feb 2013
Page 128: Henrik Berglund, Venture Cup, feb 2013

The MVP is not the goal = Requires commitment to iteration!

• “A complex system that works is invariably found to have evolved from a simple system that worked.”

• “A complex system designed from scratch never works and cannot be made to work. You have to start over, beginning with a working simple system.”

Minimal Viable Product

Page 129: Henrik Berglund, Venture Cup, feb 2013

Not helpful

Jackpot!

1. Has a problem

2. Understands he or she has a problem

3. Actively searching for a solution

4. Cobbled together an interim solution

5. Committed and can quickly fund a solution

Types of earlyvangelists

Page 130: Henrik Berglund, Venture Cup, feb 2013

Do you have a proven sales roadmap?Organization chart? Influence map?No staffing until roadmap is proven!

Do you have a set of orders ($’s) of the product validating the roadmap?

Is the business model scalable?LTV > CAC, Cash

Customer Validation: Exit Criteria

Page 131: Henrik Berglund, Venture Cup, feb 2013

If yes – Start executing

Page 132: Henrik Berglund, Venture Cup, feb 2013

If no – Pivot!

• The heart of Customer Development

• Change without crisis (and without firing executives)

“The idea that successful startups change directions but stay grounded in what they've learned”

Page 133: Henrik Berglund, Venture Cup, feb 2013
Page 134: Henrik Berglund, Venture Cup, feb 2013
Page 135: Henrik Berglund, Venture Cup, feb 2013
Page 136: Henrik Berglund, Venture Cup, feb 2013
Page 137: Henrik Berglund, Venture Cup, feb 2013

Pivot

Adapt the Business Model until you can prove it works

Page 138: Henrik Berglund, Venture Cup, feb 2013

search

execution

Page 139: Henrik Berglund, Venture Cup, feb 2013

• Grow customers from few to many

• Comes after proof of sales

• Inject $’s for scale

• This is where you “cross the chasm”

• “Growth Hacking”

Customer Creation

Page 140: Henrik Berglund, Venture Cup, feb 2013

• (Re)build company’s organization & management• Dev.-centric Mission-centric Process-centric

Company Building

Page 141: Henrik Berglund, Venture Cup, feb 2013

•Customer Discovery Articulate and Test your Business Model Hypotheses•Customer Validation Sell your MVP and Validate your BM & Sales Roadmap•Customer Creation Scale via relentless execution and fill the sales pipeline•Company Building (Re)build company’s organization & management

Summary – Customer Development

Page 142: Henrik Berglund, Venture Cup, feb 2013

Don’t do a Boo!Concept Product Dev. Alpha/Beta

TestLaunch/1st Ship

“We have been too visionary. We wanted everything to be perfect, and we have not had control of costs"

Ernst Malmsten(BBC News, May 18 2000)

Page 143: Henrik Berglund, Venture Cup, feb 2013

Henrik BerglundChalmers University of Technology

Center for Business [email protected]

www.henrikberglund.com

@khberglund

Tack!

2013-02-15 143

Page 144: Henrik Berglund, Venture Cup, feb 2013

by Steve Blank and Bob Dorf

More info: www.steveblank.comBuy the book: http://www.amazon.com/gp/product/0984999302/

Presentation based on

Page 145: Henrik Berglund, Venture Cup, feb 2013

developed by Steve Blank and Bob Dorf

http://www.slideshare.net/sblank/

Using slides from