Recent Posts
- A great SVPMA talk: “How To Get That Next PM Job”
- Market Facts, Judgment, Fallibility and Ownership
- New (old) role, new (old) site, new (old) city
- Review: “Adapting Configuration Management for Agile Teams”
- Site Licenses and Other Real-World Intrusions
Topical Index »
Search
Subscribe
“Goldilocks” Packaging
Established companies in established markets generally have some standard ways to package and price their new offerings. Product extensions are benchmarked against the existing product line or the other guy’s features and prices. This leaves product managers focusing on “faster, cheaper, better, more.”
In a brand-new market, though, there are fewer guideposts. Close competitors may not exist. Even before final products are ready, you need to define initial packaging and pricing for your fledgling sales force and prospects. Otherwise, the sales team will invent it haphazardly, one visit at a time. Here’s a starter approach that I’ve called “Goldilocks” packaging.
Borrowing lightly from the fairy tale, we want to construct three pricing packages with increasing feature sets. We hope that prospects will think of them as “too small, too big, and j-u-s-t right!” Why three? Huge consumer products companies that measure buying behavior tell us that we like to have three options (whether for hamburger meals or SUV models or external hard drives). When faced with more than three choices, we get confused and may postpone a purchase. With fewer, we don’t notice that each package has any features.
Even more important, we want to sell on features as well as size. Our customers don’t know how much they need (in obscure product metrics like “virus scans per hour” or “GB of trading data”), so we want to offer functional reasons to trade up. The goal of “Goldilocks” packaging is to create three distinct versions that appeal to different buying audiences. Of course, it’s critical to know which of your features are the “must have” items at each level, so that your hungry sales force will have a way to upsell customers into bigger packages.
How About an Example?
Imagine that you’ve founded a start-up targeting the latest generation gap in office communications: Instant Messaging (IM) and its conversational shortcuts. Corporations are being forced to keep audit logs of IM chat — and forty-something IT directors are struggling to understand their twenty-somethings’ crazy IM abbreviations. Here’s a market ripe for innovation. This is a completely new niche, so prospects can’t size their need. (“How do I know how many MB/sec these crazy Instant Message kids use?”) So, we’d prefer to scale our packages by features as well as capacity. Assuming that our brilliant developers can work miracles overnight, here are a few cool reasons for upsell:
| Package | Features | Price |
| Entry |
- Logs 2 simultaneous IM conversations - 10 MB storage - Browser-based archive search |
$2,000 per appliance |
| Department |
- Logs up to 20 simultaneous IM conversations - 100 MB storage - Can display traditional English equivalent ("k otp g2g" also shown as "OK, on the phone, got to go.") |
$6,000 per appliance |
| Enterprise |
- Logs up to 200 simultaneous IM - 20 GB optical storage - Fault-tolerant, dual-processor - High-efficiency cache for emoticons - Email-to-IM bridging. Sets up a translated conversation between Instant Messaging and email users. (Boss sends "strategic downsizing" email and code geek receives a "chek out MnsterBord" instant message) |
$40,000 per cluster |
