what should your next release contain? ask the crm

33
SalesLogistix ©2011 What’s In the Next Release? Ask The CRM Intro Beyond Features CRM Data for Features Usage Data

Upload: svpma

Post on 06-May-2015

116 views

Category:

Documents


2 download

DESCRIPTION

What should your next release contain? Ask the CRM by David Taber at SVPMA Monthly Event March 2011

TRANSCRIPT

Page 1: What should your next release contain? Ask the CRM

SalesLogistix

©2011

What’s In the Next Release? Ask The CRM

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 2: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Ask The CRM – Agenda

• The Product Management Challenge

• Feature Futures

• Customer Usage

• What’s Getting in the Way?

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 3: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Today’s Haiku

The Big Marketing

Problems are not Marketing

Problems: Look Elsewhere

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 4: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Who is David Taber?

• 25 years in Information Technology

• Virtually all experience in Software Finance, Telecom, Manufacturing, & Defense industries

• MBA, BA from University of California Lecturer, UC Berkeley graduate school of business

• Now a CRM Management consultant Startups through $5B firms in six countries

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 5: What should your next release contain? Ask the CRM

SalesLogistix

©2011

The Newtonian Model of Product Development

• Product design is an inbound process• Product Marketing influences engineers

Engages prospective buyers

Makes mid-course corrections

Tweaks messages to fit product reality

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 6: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Problems with the Newtonian Model

• Engineers design for themselves

“Stupid customers”

• Sales overly focused on the last lost deal

• Marketers write requirements tomes

Nobody follows most of the Great Ideas

• Customers don’t know what they need

Often follow ideas put in their heads by your competitor

Suffering from future shock (undigested shifts)

They don’t care the way you do…

• Defendable, objective data?????

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 7: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Infinite Loop / Simultaneous Equation

Needs

Features

Market Size

Value Prop& Messaging

PressStory

ChannelPitch

CustomerResponse

Segments

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 8: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Resolving the Infinite Loop

Target Market

Target UserProduct Features

Value Proposition

BusinessThesis

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 9: What should your next release contain? Ask the CRM

SalesLogistix

©2011

What’s a CRM?

• Customer Relationship Management =

Sales Force Automation

Call Center Automation?

Customer Support?

ContactsAccounts

Sales Cycles

Forecasts

Call History

Leads

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 10: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Where does a CRM Fit?

CRM

Accounting

Distribution

Licensing &Fulfillment

Bug Tracking

Call Center

Customer Support

Marketing Automation

Web Site

Web Analytics

Surveying

eCommerce

Customer Portal

Partner Portal

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 11: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Watch Out!

• If you’re a small company

The CRM hasn’t been integrated with anything else

There isn’t a good way to correlate the data

Probably…it’s an Access/MySQL party!

• If you’re a BIG company

There will be multiple CRMs, ERPs, CCAs, etc.

The integrations will be fragmentary, partitioned

Probably…it’s off to the Data Warehouse!

• Either way: get good at data reduction & analysis!

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 12: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Booby Traps

• Politically-gamed Sales input

• Blurred semantics

• Self-selection bias

• Narrow populations

• Social networks Insta-mobs

“The Wisdom of Crowds” does not apply to most internet communities

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 13: What should your next release contain? Ask the CRM

SalesLogistix

©2011

CRM Data You Can Often Ignore

• Lead Source

• Purchase intention scores/qualifiers

• Competitors

• Win/Loss Reasons

• Contact Roles (political map)

• Customer Configurations

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 14: What should your next release contain? Ask the CRM

SalesLogistix

©2011

CRM Hidden Gems for Feature Input

• Customer Service

Cases & RMAs

CS auto-surveys

Professional Services RFI/RFP/SOW/commentary

• Sales

Pre-Sales engineer commentary

Approval forms (e.g., loaners, POCs, etc.)

• Email threads

• Forum / Discussion Board threads

• Marketing automation cookie crumbs

• Assets / License Mgt / Fulfillment

• “Ideas” and feature votes

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 15: What should your next release contain? Ask the CRM

SalesLogistix

©2011

The CRM Maturity Model™

• All “meaningful” calls/contacts in the system

• Every sale and renewal is in the system

• Every sale has product line items

• # of Internal Systems Integrated (e.g., email)

• # of External Systems Integrated (e.g., Marketo)

• “All” bookings forecasts based only on CRM data

• A Deduping Tool/Service is in use

• Reps and SEs see CRM as their key info resource

• Customer support logs Cases in system

• ProSvcs puts every project in the system

½

½

½

3

1

A good score is 8 or above

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 16: What should your next release contain? Ask the CRM

SalesLogistix

©2011

“But Dave…”

• Why doesn’t all this just get done in a data warehouse?

In some organizations, that’s exactly where all this data

should be living

But the data isn’t likely to be properly organized,

summarized, or meaningful for your purposes

So get a budget of $XX,000 and wait in line

• If you don’t have a data warehouse yet

Get a budget of $XXX,000 and wait in line

In the immortal words of Dr. Phil…

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 17: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Nirvana

• Link the CRM system to the product

• Collect extracts from real usage data

• Eliminate survey (and surveyor) biases

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 18: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Customer-Centered Product Design

• Develop and engage users as early and often as possible Wikis and forums and portals and blogs: community input

• Customer interaction should be part of the UI Anonymous “call home” usage stats

Auto-update driven announcements and invitations to portal, voting, etc.

Explicit “conversation” via IM

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 19: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Customer Engagement in “Enterprise Software”

• “Call home” model Appliances

• Update + Security notices

Emails inviting follow-up

Customer self service portal = opportunity!

• Support and Consulting are your best touch points Get these groups actively using your SFA / CRM system

Integrate marketing survey questions into their normal way of

doing business

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 20: What should your next release contain? Ask the CRM

SalesLogistix

©2011

SaaS = Warp Drive for User Interaction

• Who needs user surveys?

• You know the names and emails of every single user

• You can measure everything that current and prospective users do, at every session

• You know how every “demo” and “POC” is going in real time

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 21: What should your next release contain? Ask the CRM

SalesLogistix

©2011

What if it’s not a “feature deficit?”

• Is it product quality / reliability?

• Is it the message?

• Are we going after the right verticals?

• Is it the sales team?

• Are we targeting the right customers?

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 22: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Before you design your product,

design your customer.

– Somebody Brilliant™

Intro Beyond FeaturesCRM Data for Features Usage Data

™ SalesLogistix Corporation, all lefts reservedGraphics courtesy PC Week

Page 23: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Remember our Haiku?

• Your “product problem” may not really be a product problem

Positioning (messaging)

Pricing (including pricing model)

Place (channel)

Performance (including quality and reliability)

• First, look at OOBE

You can never make a product too easy to use

• Then, look at EOP

You can never make a product too easy to buy

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 24: What should your next release contain? Ask the CRM

SalesLogistix

©2011

The Classic B2B Pipeline …

Source: Research work from Sirius Decisions and DOTnet Consulting

600

200

40

12

4-6

33%

20%

33%

30% - 50%

Qualified Leads

ID Requirements

AppointmentsValue

Demonstration

Scope&Proposal

New Customer

25,000

3000

12%Target Market

Responses

20%

Demand Discovery

Marketing

Demand Development

Sales

Demand RefinementTelemarketing/Inside Sales

“Names” or “Attendees”or “Audience”

“Leads”

“Qualified Leads”

“Contacts”

“References”

“Opportunities”

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 25: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Analyzing Conversion Failures

• Use CRM data to develop a model for the real pipeline

Conversion percentages

Time in stage

Separate by product, vertical, and channel

• Examine CRM data for diagnostics about the failures

Forget about Sales’ win/loss reasons

Look for correlations, serial patterns

Survey customers immediately upon failure

Make sure the surveyor isn’t biasing the answers

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 26: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Sometimes it’s the simplest stuff…

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 27: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Make it Really Easy for Customers to Connect the Dots

• Remove customer speed-bumps

Unnecessary steps

Things that could be automated, streamlined

Anything that engenders purchase delay

• Change the rules!

Contractual complexity

Weird / paranoid business rules

• Make purchasing pleasant

Conversations, not adversarial negotiations

Be that much easier than your competitor

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 28: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Your Take-Aways

• The way to win in product planning is to have solid, objective data

• The most defensible, attractive data is from real customers Existing customers are more profitable than new ones

(But you can never ignore new customer wins)

The CRM system can be your private gold mine

• The problem: integration and validity of data Get good at statistical methods and analysis

• In this case, the sizzle is the steak Customers begging for new features should trump everything else

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 29: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Thank You!

[email protected]/download/archives.htm

650-326-2626

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 30: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Product Features

Focus on this LAST

Develop Iteratively

Think Agile Development / eXtreme Programming

Talk with prospects, but don’t take them literally

Do not focus on feature lists / competitive parity

If you chase the bad guys on their own terms,

you will always be behind

Do not focus on the “how”

Better to focus on the “what”

Even better to focus on the “who, when…”

Best to focus on the “why”

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 31: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Product Features

Instead, develop a coherent thesis

The core: your theory about what the customer

values most

• “Our product is best in the world at doing X for users who

need to do Y inside customer Z.”

Use your thesis to keep scope focused

Do a few things exquisitely well

Version 1.0 will inevitably be incomplete, but it

must not be fragmentary

Does enough of the job to show value

It can never be too easy to use

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 32: What should your next release contain? Ask the CRM

SalesLogistix

©2011

Look Beyond Product Features

Product boundary Will the customer think of your 5 line-items as one product?

Will they think of your one product as 3 things bundled?

Will customers need other stuff to make your product usable?

Product boundary determines the scope of competitors & substitutes

Pricing and licensing Pricing (and licensing) model

Price points

Discounts, bundles, and allowances

Packaging and OOBE How is the product delivered and installed?

What is the initial user experience?

Intro Beyond FeaturesCRM Data for Features Usage Data

Page 33: What should your next release contain? Ask the CRM

SalesLogistix

©2011

The Best MRD…

• Write a 2-page press release for the product before the team begins

What’s the opening gambit?

Who gets quoted and what do they say?

Who is the channel selling to?

What are the visible benefits, and for whom?

What’s the pricing, packaging, and distribution?

• And have a Wiki for a dynamic view of the product details

Intro Beyond FeaturesCRM Data for Features Usage Data