Comments (6)

By brantcooper, September 13, 2010 4:38 pm

I received a comment on the “Art of Customer Development Conversation” post regarding B2B Customer Development conversations and specifically, “how to navigate complicated customers where you’ll ultimately need approval from 3-5 parties while dealing with motivated saboteurs.”

The number one problem with Customer Development in B2B environments is that startups begin the Customer Development process too late.  The revenue plan has been sold to the board, the product is done or near-done, and a marketing launch date has been chosen.  Despite the increasing popularity of the LeanStartup “movement,” this is, IMO, still standard operating procedure for most B2B startups.  So having skipped Customer Discovery entirely, the company founders have neither validated their problem assumptions nor their proposed solution.  The board eagerly awaits first revenue and to that end, will even help hire the first VP of Sales in order to accomplish this momentous milestone of best-laid plans.

Welcome to the maze of complex B2B sales.  Did you think B2B sales was going to be straightforward; based solely on rational, business-savvy calculations?  Based on the bottom-line?  Most everyone recognizes that the B2C sales process requires appealing to consumer’s emotions.  But believe it or not, business buyers, influencers and users are human, too, and thus are not-exempt from emotional decision making.  Ego, hierarchy, competitiveness, fear, grandstanding, sycophantry join budget, market share, revenue, profits, risk, time, resources in the sale.

The “Status Quo Coefficient” represents that which you must overcome above and beyond the pain your product solves, in order to make a sale.

Pre-Launch Customer Development

If you are practicing Customer Development prior to product launch, then Blank’s The Four Steps to the Epiphany goes into great detail about how to discover and validate your understanding of the complex selling environment.  In less detail, but perhaps with more specific tactics, Vlaskovits and my The Entrepreneur’s Guide to Customer Development is a good resource for executing your Customer Discovery plan.

During Customer Discovery, you are not selling, so you are in a better situation to have “learning conversations” with prospective customers.  Your aim is to establish relationships inside businesses who are likely to be early adopters.  This means you must find your champion.  Your champion will help you understand who your saboteurs are and hopefully, how to navigate around them.  As you build your product and validate your vision with the champion, you empower him or her to sell you inside the organization.

Post-Launch Customer Development

These are tricky waters for the reasons described above.  If you have a sales team in the field, let them go.  If you have a VP of Sales unable to take a learning approach, let him or her go.  If you are fortunate to have a board that has bought into learning before (large scale) selling, perhaps you are able to hire a VP of Customer Development or utilize outside resources.

In 2005, Mark Leslie and Charles Holloway wrote a very #custdev-y paper, called the Enterprise Sales Learning Curve (.doc).  Leslie and Hollow describe the same failures of scaling sales and marketing prior to knowing how market and sell that led Blank to establish the Customer Development methodology.  I highly recommend this paper for B2B startup executives and investors.

Leslie and Holloway advocate hiring a “Renaissance” Sales person to practice Customer Discovery:

The “Renaissance” Sales Rep:    During the initiation phase we would like to hire an individual who is able to facilitate broad based learning by the enterprise.  This individual likely has a deep interest in the technology and in bringing together various customer departments with the appropriate representatives of the company.  The individual is extremely resourceful, able to develop his / her own sales model and collateral materials as needed.

Fundamentally, two approaches exist no matter who you bring on board:  1) go back to Discovery or 2) establish a painstaking process for winning your first five deals.  For a peek out how this approach might be developed, I highly recommend you read this comprehensive interview with Sean Murphy.

So what is it exactly, that you need to learn?

1) Validate Customer-Problem-Solution: No matter what stage your company is in, you need to validate that you have the right combination.

2) Do you have the “whole product?”  Or do you need partners, systems integrators, etc.

3) Identify the buyer’s process and corresponding business tactics.

4) Identify all the player’s in the process: user, influencers, economic buyers, decision makers.

5) What messaging and positioning messages resonate?

6) What does the corporate purchasing process look like?

Non product-specific answers you need:

Are you the decision maker?

Do you have budget?

Who also is involved in decision making?

Is this deal subject to other departments’ approval processes?

Are there compliance issues regarding this deal?

Can legal or purchasing nix the deal?

Do you keep a list of approved resellers/systems integrators?

Are there departments who might disapprove of a deal (are you adversely affecting another department’s budget)?

All things considered, what is the “typical” length of the approval process?

What other user groups/departments will benefit from a deal?

Will a successful pilot assuage naysayers?

Will you sign a contract whereby you purchase upon a successful pilot?

************

The method for obtaining this information doesn’t change significantly between pre- and post- product Customer Development:  You must establish deep relationships.  High-powered, “renaissance” sales people do this through “consultative” sales, whereby they learn what core problems the client needs solving and how they can work together to implement product that does the job.  Either way, you must find an internal champion and developing this relationship is typically a painstaking process that takes months to evolve.

The best way to find internal champions is through your network, no further than 1 link away (i.e., friends of friends).  This means reaching out to the friends, family, and colleagues of you and your co-founders, employees, board members, mentor, advisers, etc., for introductions.

As discussed in The Art of Customer Development Conversations, the answers you seek are not often the result of direct questions, but flow from conversations that grow deeper over time as the fit between problem and solution becomes tighter and trust among principals builds.

Comments (7)

By brantcooper, September 2, 2010 9:52 am

By now all Lean Startup and Customer Development practitioners should know that if you’re not getting out of the building, you’re not doing Customer Development. Each of the following, while often a necessary and beneficial activity, does not constitute Customer Development:

• surveys
• automated customer feedback mechanisms (e.g., uservoice, get satisfaction, et. al.)
• embedded product use analytics
• marketing analytics
• feature request mechanisms
• sales calls
• product demo
• usability testing
• focus groups

Each has its place in the Customer Development process, but without live Customer Development Conversations, you are likely compromising your ability to learn your way to Product-Market fit or startup scaling.  What you seek to learn evolves over time, as do the tactics you employ, but every step of the way should be grounded in real time conversations.

Generally speaking:

Pre-Problem-Solution Fit, you concentrate on learning as much as you can about the problem, who are the real customers (user? buyer? boss?), and possible solutions.

Pre-Minimum Viable Product, you concentrate of learning, developing and testing the minimum features and functionality required o solve the problem to a degree the customer will buy.

Pre-Product-Market Fit, you concentrate on learning about funnels, testing messaging and positioning, and likely iterating on product and market segment in search of P-M fit.

The conversation itself is difficult for many. The key to effective conversations is in developing the conversation around your objectives for the discussion.  Establish 3 or 4 “must learns” for each conversation.  Depending on what you’re trying to learn, you can use “open-ended” questions and direct questions.  Use your conversations to calibrate your other tactics.  Are you asking the right questions in your surveys?  Do responses gibe?  Are product demos necessary from the buyer’s perspective?   Are users using the product the way they say they want to?

I thought I’d share some recent experiences my clients have had with customer development conversations to help illustrate conversation tactics.

1. Talk problem first, not solution.

Client: “I can’t stop talking about the solution.  It’s how the conversation starts.”

Clearly, whenever you meet someone for the first time, you need to introduce the space your product is in.  You must provide a context for the conversation.   You need to be able to state what you’re about succinctly, so you can move on to the purpose of the meeting.  Otherwise, you spend the whole time trying to explain what you’re doing.  This is why the elevator pitch is so important.   In a conversation, you don’t necessarily repeat the pitch verbatim, but you use components of it to steer the conversation.  So, for example, if you are testing your problem assumptions, use a classic sales cold call method of “flipping” the conversation from talking about yourself (solution) to the customer (problem):

Hi, I’m Brant Cooper from Market By Numbers, and I teach Founders Customer Development principles to help get their startups off the ground; (intro that provides context)

I often hear from startup CEOs like yourself, (The Flip)

That they have trouble figuring out how to prove their business model and how to prioritize what they should be working on; (problem hypotheses)

Do you experience this at all? (Open ended question)

Follow up questions depend on the answer.  If answer is no, you might say: “That’s great, it sounds like you have things under control. “What are the primary issues you face as CEO?” or “Do you hear other CEOs that talk about these issues?”

2. Except when that doesn’t work.

Client: “I couldn’t get her to describe her pain.  She kept wanting to know how she could help me!”

The contact was a senior person in the exact type of company needed to confirm a key hypothesis.  My solution would help her company’s relationship with its clients, but I couldn’t get her to talk about that.  Instead, she talked about problems her clients had and the opportunities available to solve them.  I asked if she was a sales person and it turns out she was.    I said it sounds like she’s a good sales person, who understands the needs of her clients, and a good contact, but not his customer. I suggested my client ask her to refer him to her company’s product managers who would be more likely to be interested in his ideas.  “More contacts to speak with” should always be a core objective.

If a problem statement doesn’t resonate, either your problem statement is not articulated correctly, is flat out wrong, or you are not talking to the your customer.

3. This is not feature mongering.

Client: “Conversation inevitably turns to features discussion.”

If you are talking about features, see 1. above.  If your contact or customer is talking features, slow it down by by asking why.  Use the same 5-whys approach Eric Ries talks about to discover a problem in your development process to figure out what is driving the feature request.  Continue to ask why the customer wants specific functionality until they are able to tell you the actual problem they’re trying to solve.  This helps you consider a couple of things.  First, is the feature a high priority to the customer?  Second, are you building the right Minimum Viable Product?  Obviously, one data point is not enough to draw conclusions, but it contributes to the analysis.

4. How to test messaging.

Client: “Can’t I just A/B test?”

It’s fine to use split testing to test messaging, but it’s most effective when you’re optimizing your funnel. If you do it too early, you actually don’t know if you are optimizing for the right product and market.  Also, you can find out that one message works better than another, but you can’t learn why.  In a live conversation, not only can you ask why a message doesn’t work, but you can test several iterations in the same conversation.   When testing messages live, I like to use the “pause method.”

5. Ask them.

Client: “Everyone says I need Facebook, Twitter, a blog.  How do I know?”

If there are two things the world doesn’t need more of, they are Internet Marketers and Social Media Gurus. It’s easy to get caught up in the excitement and clearly Internet and social media marketing can be effective.  But their effectiveness depends less on which expert you hire than whether your customer and their buying process intersect with your online tactics.  I spoke with a CEO recently who had two B2B deals in pilot for his new startup.  He had personally orchestrated the sales process through 1-1 relationship building in a carefully honed market segment. Yet his marketing plan called for Internet and social media marketing that didn’t jive with his experience.  He immediately described a shotgun approach to figure out what the right online channels would be.  While it might be the case that online marketing would be successful and even necessary to scale, at that time all evidence pointed to offline methods.  Using the “Flipping the Funnel” idea, I recommended he Ask his existing customers!  Here’s a question you can ask straight out to your contacts:  Do you belong to social networks?  Do influence your buying decisions? What blogs do you read, etc.

I hope you find this helpful.  What issues do you encounter during your Customer Development Conversations?

Comments (4)

By brantcooper, May 26, 2010 12:23 pm

The consultants came out in droves to weigh in on Steve Blank’s recent post, “Consultants Don’t Pivot, Founders Do.” (Myself included.)  Generally, all were in agreement with Blank’s primary point:

Founders get out of the building (physically or virtually) to test their hypotheses against reality. There are times when customers are going to tell you something that you don’t want to hear.  Or you’re going to hear something completely unexpected or orthogonal to what you expected.

As I like to say, those that hold the assumptions need to test the assumptions.   In the comments, several of us pointed out that teaching Customer Development is a viable service for which entrepreneurs can hire outside consultants. Sean Murphy:

We work with teams as they prepare for and then execute the customer discovery and validation steps in B2B markets. We helping them rehearse leaving the BatCave, we often go with them on customer discovery interviews or sale calls, we debrief from prospect meetings to formalize lessons learned and adjust the sales presentation or the target prospect definition or sometimes the feature set.

Clearly, there’s some value being provided here.  In my experience, entrepreneurs have repeatedly sought help with both Customer Development basics, as well as some of its more nuanced components.  Sean Ellis raises a separate issue, agreeing that consultants can provide value, but wondering how the economics work.

I believe the need is there and most consultants have the expertise to fill the need; the problem is that their cost exceeds their value at this stage.

There is no doubt in my mind that this is a challenge, but there’s more that one way to skin a cat, so I’m not sure such a blanket statement is accurate.  (Note that Ellis isn’t suggesting that consultants don’t provide fair value for their compensation, but that the compensation is likely to be too high for the particular stage the business is in.)

This begs the question, what exactly can be outsourced and at what cost?

What Part of Customer Development Can be Outsourced?

It’s worth pointing out that one of the best Customer Development practitioners I know is Cindy Alvarez, who is a Product Manager and not a founder at KISSMetrics. Theoretically, at least, Alvarez could be doing what she does as a consultant, rather than as an employee.  If she had internal assistance (say, a less Senior PM  or a technical marketer), she could potentially have two or to three clients and perhaps make a pretty good living.  And while KISS is likely at or near Product-Market Fit, Cindy has been executing Customer Development for them for quite awhile.

As with employees, the key element to working with consultants is trust.   Further, Founders must process outside information to make decisions.  Is it better, for example, for Founders to pivot based on analytics than Customer Development information provided by a trusted adviser?  If a Founder has a “salesperson mentality,” and cannot stop selling when supposed to be listening, does that doom the company?  Or can a trusted adviser steeped in Customer Development best practices provide better information?

The more I reflect, the more I think blanket statements about what can or cannot be outsourced are dubious at best.  Learning must happen.  How it happens is not particularly relevant.  The key measure is willingness to learn.  If you belong to one of the archetypes of anti-lean, you are not likely to do Customer Development anyway.  If you are willing to learn, you can likely learn from a trusted consultant, too.  I do think the level of understanding potentially suffers, however, so the stage of Customer Development you’re in should influence who the lead CustDev actors should be and what other roles might benefit the process.

In the book, Entrepreneur’s Guide to Customer Development, we break Customer Discovery down into three stages:

• Problem-Solution fit, i.e., validating your core C-P-S (Customer-Problem-Solution) assumptions:  This is the most important stage for Founders to be heavily involved in.  Consultants might help you articulate your assumptions, define market segments, find prospects to talk to, help prepare the presentation and the presenter, and help analyze results.  I have, in fact, also done the interviews for a Founder with both positive and negative results.
• MVP development: Best if Founders are still heavily involved with early adopters, since they likely need to hone in on the core value they’re providing.  I don’t see much value in consultants here, other than help with process,, like coaching Product Managers (and Founders) to not engage in feature mongering.  This phase requires a dedication to minimum viability, and a balance between customer-driven solution and vision.  If the two diverge, a pivot is required and only Founders pivot.
• Proposed Funnel, i.e., learning your sales and marketing roadmap:  Founders need to be engaged relative to their adamancy regarding their sales and marketing assumptions.  Other business model assumptions are typically exposed here, as well.  I believe consultants can play a larger role in this phase, since many founders can use a lot of help thinking through marketing basics.  Consultants might help with defining market segments, proposing funnel hypotheses, and preparing (or conducting) conversations, surveys, etc., to test and validate assumptions.

Clearly I believe a high level of Founder involvement is necessary.  Founders who actually practice Customer Development themselves are arguably in a better position than those that delegate.  But not only are there parts of Customer Discovery that can be effectively delegated, consultants may have a role as well.  The question remains, however, whether (1) consultants can make a living doing this, and (2) whether startups can afford fees that result in (1).

What Model Works for Outsourcing Customer Development?

I know several individuals who practice customer development as consultants.  Clearly, Sean Murphy has found a model that works for him and his clients; Nick O’Connor is another.  I have helped several clients, though finding the right model has been a challenge.  I am passionate about working with early stage companies and have done so for years as a volunteer mentor at San Diego’s CONNECT Springboard program.  Figuring out how to make some money, too, isn’t a bad thing and admittedly, I’ve struggled to find the right model that serves well early stage Founders.

Recently, Patrick Vlaskovits, pointed to me a startup lawyer with a unique business model, Kevin Houchin. Houchin charges a low monthly retainer for a long(ish) range commitment, which allows clients unlimited contact, but not unlimited access.  So I’m trying the same thing. So far, so good!  I haven’t solved my scaling problem, but I get to work with some great entrepreneurs who are willing and able to execute on Customer Development principles.  They are high-energy, have bought into Customer Development and truly value (and benefit from) feedback, pointers and actionable recommendations.  For more information, see here.

In light of this more in-depth conversation regarding outsourcing and leaving aside for a moment, the general evils of consultants, what do you think about outsourcing components of Customer Development?

Comments (7)

By Patrick Vlaskovits, May 14, 2010 2:19 pm

Very recently, the Diaspora project (advertised as “the privacy aware, personally controlled, do-it-all distributed open source social network”) on Kickstarter has caught the attention of the Twitterati, and has blown past its goal of raising $10,000 by June 1st 2010, by having raised $138,961, as of this post.

The way it works is this: people who create projects to be funded by micro-capital on Kickstarter offer differing levels of sponsorship.  The more you pledge, the more you get.  In this case, if you pledge $10, you get a CD (with the source code), a note from the Diaspora team and a bunch of stickers.  If you pledge $2,000, you get the same as well as phone support, hosted service and a computer.

They seem to have done a few things right, either intentionally or unintentionally.  (Most likely a combination of the two.)  They appear to be riding a recent upswell in anti-Facebook sentiment with regards to privacy (or lack thereof) in a select minority of techie folks.  Their video pitch seems to have hit the right chords (moxie, passion, hard-core geekiness), which appears to resonate with many of the same people.  Lastly, I think their dandelion logo/look is, in a word: cool.  (Get it?  Seeds of a diaspora?)

But that is not what this post is about.  This post is about how to raise micro-capital via clever pricing and bundling strategies.

Now, check out this chart I slapped together.  It shows the Number of Backers per Pledge “Bucket”.  One might expect, very reasonably I would add, that the number of backers declines as price increases.  In other words, you observe the classic, negatively sloping Demand Curve you learned about in Econ 101.  As price increases, demand lessens.

But here it doesn’t quite do that, does it?

Now, take a look at the chart below, and see how that translated into revenue.  Shooting from the hip, one might expect, in terms of revenue by pledge bucket, to see a bell-shaped/normal distribution.

But we don’t, do we?

So in this case, the secret of their success is a pricing/bundling strategy that uses t-shirts as social proof of geekiness.  Or another way to look at it is:  the Diaspora team has utilized Kickstarter to sell +$40,000** worth of t-shirts!

My gut tells me that the Diaspora team hit some sort of nerve that has nothing to do with the potential success or failure of their project.  People think the project is cool and sticking it to The Man (i.e. Facebook), whether or not these guys succeed or fail is almost irrelevant.  So, if I think the project is cool and if the project is likely to provide me substantial geek street cred — well then, what better way to demonstrate my geekiness/validate my support for Diaspora then by sporting a Diaspora t-shirt.  And looking at their de facto marketing materials, the t-shirt is likely to look good.

And if I want that t-shirt, I’d better pony up $25 for it — which, incidentally, seems like a fair price for a t-shirt.  And apparently, I am not the only one who thought that way.

Lessons learned:

• If you can harness yourself to a growing/popular social trend, you may benefit in an extraordinary manner.
• You need to think of pledges/sponsorships in terms products, pricing and value.  In other words, WIIFM (What’s In It For Me?).
• People get value from feeling that they have done their part (sticking it to Facebook), even if it doesn’t amount to anything concrete (aside from a t-shirt).  You can and should capitalize on that.
• Don’t forget about reference pricing.  My reference price for a generic “cool” t-shirt is around $20.  Meaning, that is what I would expect to pay in a store for a t-shirt that was adequately “cool”.  The Diaspora t-shirt, in that light, seems like a bargain.

Full Disclosure:  The only reason I noticed this pricing strategy was because I actually pledged $25 because I wanted a t-shirt (and I think about pricing stuff all the time).

For the record, I actually don’t think that a self-hosted peer-to-peer social network will get off the ground in circles other than amongst hard-core geeks.  As someone mentioned on a Quora thread, no one actually wants to host their own social network on a server under their bed.

But I still think these guys are worth backing.  And are cool.

Lastly, I don’t think this sort of hyper-success is easy to replicate, if at all — but that doesn’t mean you shouldn’t think about your pricing/bundling strategy if you are trying to raise micro-capital.

Before I forget, you should check out the pricing page for book Brant and I wrote.  Not only should you check it out, but you should go buy a copy of our book.

——–

Data table here:

**Actually more since anyone pledging at $25 and above gets a t-shirt.

***The actual numbers in this post are already outdated, but conclusions are the same. Will update later.