Technology marketing

Advice about the marketing of enterprise technology, based on 30+ years of experience, and most particularly upon our flagship Monash Advantage program.

July 9, 2014

Judging opportunities

This is the first of a not-very-organized series of posts on two related subjects:

Most of my posts can be said to touch on those areas, especially the latter one. But in this series I’ll try to be more direct about it.

Useful background may be found in:

For a new company in a new enterprise IT product category, the path to success may be oversimplified as:

Read more

July 2, 2014

Pitfalls for Pollyannas

Q. What’s the primary difference between used car and computer salespeople?
A. A used car salesman KNOWS that he’s lying.

– A joke that was old in 1995

The technology business is difficult, so it’s natural for technology vendors to make mistakes. Many of these fall into two broad categories:

In particular, vendors commonly overestimate their (current and future) competitive positions. This isn’t just for public consumption; often, they fool themselves as well. Popular forms of overestimation include (and these overlap heavily):

The dictum Fake it ’til you make it bears a certain relevance here, all the way down to its Alcoholics Anonymous associations.

Read more

March 14, 2014

Pricing advice: Avoid the looking-glass

From time to time over the past 30+ years, vendors have described to me pricing schemes in the vein:

That sounds like a risk-sharing win-win kind of deal, in which your customer’s costs perfectly mirror the benefits achieved.

The naive form of that argument is wholly ridiculous, however; what customers pay you is only a portion of their total cost of ownership, and in most cases not close to the majority. The plan has more fundamental problems too, and experience shows that it rarely works in practice.

Last May, I summarized and explained my standard pricing advice by:

  • There should be 2 or more simple pricing algorithms, so that …
  • … the price for any given customer is the lowest of those choices.

Generally one pricing algorithm will be suited for most of your customers, while the others will be meant for minority or edge cases. …

Core reasons for that approach include:

  • Simplicity. Your salesman on the account should be able to quickly determine which pricing approach will apply. The prospect should be comfortable that there won’t be hard-to-foresee “gotcha” charges.
  • Fairness and match to use case. For any particular prospect, there probably will be a pricing scheme that fits well.
  • Competitive flexibility. Nothing in this strategy puts much of a floor or ceiling on your pricing. You can do whatever you think is economically best.

Benefit-sharing pricing, by way of contrast, can be simple or fair, but it has great trouble being both at once. So if you propose it, messy negotiations will ensue.

For example, suppose that Tweedledee Inc. mirrors Tweedledum Corp. in all ways but one: Tweedledee uses your best competitor Humptyware, while Tweedledum runs the far inferior Dumptysoft. Thus, if Tweedledee implements your Frabulizer, their rate of rattle-breakage will drop from 2 percent to 1; but if Tweedledum buys it, their rate will drop from 10 percent to the same 1. Should and will Tweedledum really pay you 9 times as much for the same thing as Tweedledee? Not a chance. So if you try to price on the basis of measurable outcomes improvement, you’ll probably just get into a huge price negotiation mess.

I do see one scenario in which I might consider benefit-sharing prices — when you’re in a messy price negotiation anyway, and benefit-sharing could close the gap. For example, if you want $1 million for what you claim will be a $20 million benefit, and the customer offers $750,000 for what they more conservatively estimate as a $10 million outcome, you could let the last $250,000 ride on some agreed-upon metric tracked over time. But even that is a questionable stratagem, in that it amounts to a bet that your salesman’s optimism will actually prove to be correct.

Bottom line: Keep your pricing simple, which it isn’t if it depends upon your customers’ internal operating metrics.

March 3, 2014

Marketing in stealth mode

I consult to ever more stealth-mode companies, so perhaps it’s time to pull together some common themes in my advice to them. Here by “stealth mode” I mean the period when new companies — rightly or wrongly — are unwilling to disclose any technological specifics, for fear that their ideas will be preempted by rival vendors’ engineering teams (unlikely) or just by their marketing departments (a more realistic concern).

To some extent, “stealth-mode marketing” is an oxymoron.* Still, there are two genuine stealth-mode marketing tasks:

Further, I’d divide the second task into two parts — messaging and outreach. Let’s talk a bit about both.

*I am reminded of my late friend Richard “Rick” Neustadt, Jr., whose dream job — notwithstanding his father’s famous book on presidential power — was to be a US Senator. So he needed to punch his military duty ticket, and got a billet doing PR for the Coast Guard. (One of his training classmates was Dan Quayle.) His posting was to a classified base, and so his PR duties consisted essentially of media-mention prevention. But I digress …

Stealth-mode messaging

As I wrote in a collection of marcom tips, the pitch style

“We’re an awesomely well-suited company to do X.”

is advantageous

  • In stealth mode, when you don’t have anything else to say …
  • … but not at first product launch, when you finally do.

For small start-up companies, this message is most easily communicated through highlights of the founders’ awesome resumes, for example:

Our CTO personally stuffed and dyed the yellow elephant for which the Hadoop project is named.

But that still begs a central question – how do you describe what your stealth-mode company is planning to do? I.e. — in the quote above, what is the “X”?

Read more

February 16, 2014

Messaging to multiple audiences

A common question I’m asked may be paraphrased as:

My standard three-part answer is:

Read more

December 29, 2013

The core of strategy

This blog is based on two precepts that also guide my consulting:

Let’s spell that out.

Messaging is the core of strategy

The enterprise software business, in simplest terms, is about the building, marketing and selling of software. Messaging is central to all of those activities! In particular:

If we add another level of complexity, the story changes only a little. Read more

November 3, 2013

Rules for names

A common subject of my consulting is naming, and specifically naming the category of product or technology something goes in. Clients are well aware that no market categorization is ever precise. Still, words must be chosen, collateral must be prepared, and talks must be given to rapturous* audiences. Here are some of my go-to techniques.

*One hopes.

1. My most precise tip starts from a classic naming dilemma:

Increasingly, my advice is to pick a name that’s “half new”, usually in the form of a two-word phrase that overlaps partially with the name of an old product category the new thing sort of resembles.

In some examples from my own work:

2. A principle underlying that tip is that connotation is as important as denotation. The reactions that category names evoke can be as important as their literal meanings, especially since those literal meanings aren’t very precise anyway.

Returning to the examples above:  Read more

August 30, 2013

Fluency

Paul Graham got into a flap by saying that strong accents interfere with founders’ entrepreneurial success. The key section makes it sound like his point is you have to be able to pitch in (fairly) fluent English:

Conversations are more of a problem, as I know from my own experience doing office hours. We talk about a lot of subtle points at office hours.  … And I know I don’t get as deeply into things with the groups that don’t speak English well. I can feel it happening; we just can’t communicate well enough. …

A startup founder is always selling. Not just literally to customers, but to current and potential employees, partners, investors, and the press as well. … And yet a lot of the people you encounter as a founder will initially be indifferent, if not skeptical. They don’t know yet that you’re going to be huge. You’re just one person they’re meeting that day. They’re not going to work to understand you. So you can’t make it be work to understand you.

At least in enterprise IT, however, I’d say that there are four points, not just one. You — and by “you” I mean the CEO, the CTO, and any contributor in sales, marketing or product management — should be able to:

My reasons for saying that start:

You can’t sell effectively without listening. This is one of the basic facts of business, yet shockingly many people forget it. You can’t pitch effectively without understanding how the prospect frames what she hears, and you can’t judge that unless you listen to what she says.

You can’t listen at maximum effectiveness without selling. Of course, that depends greatly on what you’re listening for. But commonly your goal in a conversation is one or more of:

Read more

May 10, 2013

Faith, hope, and clarity

Some principles of enterprise IT messaging.

0. Decision makers are motivated by two emotions above all — fear and greed. In the case of enterprise IT, that equates roughly to saying they want to buy stuff that:

1. For a marketing message to succeed, whatever its goals are, the “confer benefits” part of the story needs to be:

2. The “safe” part needs to be believed too. Rational belief in the safety of doing business with you is good. Blind faith is even better, but usually is enjoyed only by the most established of vendors.

In some cases, that may be the greatest competitive strength they have.

3. To be believed, enterprise IT messaging generally needs to be:

A certain amount of exaggeration is expected, and easily shrugged off. It’s also possible to get away with a certain amount of vagueness, whether in a fear/safety story or when pitching something as new/innovative/exciting. But don’t overdo either.

One common way to overdo your exaggeration — make an obviously false claim of uniqueness.

4. Please note: Deficiencies in the consistency of your messages can undermine credibility and clarity alike.

5. Messaging can become distorted in many ways, both accidental and deliberate. For example: Read more

May 7, 2013

Notes on pricing

Vendor clients often ask me about pricing. Everybody knows that there usually are:

But the whole process has to start with some concept of a single-unit price.

What kind of price? Well, for appliances, you usually should just charge a one-time fee for whatever is in the carton, plus annual maintenance; most alternatives are gimmicks. But for packaged software, there are numerous choices. The easy part is timing:

Tougher is deciding what kind of “unit” you should price by. My standard advice has become: Read more

Next Page →

Feed including blog about strategic marketing and messaging in technology and politics Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.