Whole Product Model
Close the gap between your marketing promise and the buyer's actual experience by delivering the ...
The Whole Product Model, originally conceived by Theodore Levitt and adapted by Moore for high-tech markets, distinguishes four concentric layers of product completeness. The generic product is what ships in the box -- your core technology. The expected product is the minimum configuration the customer needs to achieve any value at all, including necessary integrations, basic setup, and documentation. The augmented product is the configuration that gives the customer the maximum chance of achieving their buying objective. The potential product represents everything the product could eventually become as the market matures and ancillary products are added.
Moore's critical insight is that the gap between the generic product and the whole product varies dramatically across the Technology Adoption Life Cycle. Innovators happily adopt the generic product and fill in the gaps themselves. Visionaries will tolerate a partially complete product if the vision is compelling enough. But pragmatists demand the expected product at minimum and strongly prefer the augmented product. Conservatives will not buy until the product approaches the potential level with full commoditization and ease of use.
This means that for companies crossing the chasm, the whole product gap is the primary engineering and partnership challenge. Your marketing makes promises that your generic product cannot fulfill alone. The gap must be closed through a combination of internal development, strategic partnerships, and service components. Failure to close this gap is the most common reason technology products fail to gain mainstream adoption even when the underlying technology is superior.
- {"title":"Customers Buy Outcomes, Not Technology","description":"The customer's buying decision is based on whether they believe they will achieve their desired outcome, not on the features of your core technology. If the whole product has gaps, the customer correctly perceives risk -- even if your technology is superior to all alternatives."}
- {"title":"The Whole Product Gap Varies by Adoption Segment","description":"Innovators fill gaps themselves and enjoy doing so. Visionaries tolerate gaps if the strategic vision is compelling. Pragmatists demand that gaps be pre-filled. Conservatives demand that gaps not exist at all. As you move right on the adoption curve, the whole product must become progressively more complete."}
- {"title":"Partners Complete the Whole Product","description":"No company can build every component of the whole product alone. Strategic partnerships with complementary technology vendors, service providers, and system integrators are essential. These partners must be recruited, aligned, and motivated to prioritize your beachhead segment."}
- {"title":"The Simplified Whole Product Focuses on the Compelling Reason to Buy","description":"You do not need to fill every conceivable gap -- only the gaps that stand between the customer and their primary buying objective. The simplified whole product model focuses on the minimum set of complementary products, services, and support needed to deliver on the compelling reason to buy."}
- Map the Whole Product for Your Beachhead SegmentStart with the customer's desired outcome in the beachhead segment. Work backwards to identify every component needed to achieve that outcome: your core technology, required integrations, data migration, training, support, customization, and complementary products. Visualize this as concentric circles around your generic product.Pro tipUse a day-in-the-life scenario for your target customer. Walk through every step of their workflow and identify where your generic product is insufficient. Each insufficiency is a whole product gap.
- Classify Gaps by SeverityFor each gap, determine whether it is a showstopper (the customer cannot achieve value without it), a significant friction point (the customer can work around it but with difficulty), or a nice-to-have improvement. Prioritize closing showstopper gaps first.WarningBe honest about showstoppers. Engineers often underestimate the severity of gaps because they know how to work around them. Talk to actual target customers, not just your internal team.
- Decide Build vs. Partner vs. Acquire for Each GapFor each gap, determine the fastest and most reliable way to close it. Building internally gives you control but takes time. Partnering is faster but requires alignment and relationship management. Acquiring a component company is the most expensive but can be the fastest path to a complete solution.Pro tipFor crossing the chasm, speed usually favors partnerships. You need the whole product ready for the beachhead assault, not in two years. Partner for speed, then consider building or acquiring for long-term control.
- Recruit and Align PartnersApproach potential partners with a clear value proposition: by joining your whole product alliance for this specific beachhead, they gain access to a defined set of customers with a specific, funded need. Make the partnership tangible with joint marketing, co-selling agreements, and shared customer success metrics.Pro tipStart with smaller partners who are hungry for market access, not with large platform companies who will not prioritize your niche. A dedicated small partner is worth more than a distracted large one.
- Validate the Whole Product with Beachhead CustomersBefore full-scale launch, validate the complete solution with your first two to three beachhead customers. Ensure that every gap has been addressed and the customer can achieve their desired outcome without heroic workarounds. Iterate on any remaining gaps.WarningDo not confuse 'the customer made it work' with 'the whole product is complete.' Pragmatists will not perform the heroics that early beachhead customers might tolerate.
- Document and Operationalize the Whole ProductCreate a repeatable delivery playbook for the whole product: what gets installed, in what order, by whom, with what training, and with what support. The whole product must be deliverable by your standard sales and services organization, not just by your best engineers.Pro tipAssign a whole product manager who owns the end-to-end customer experience and has authority to coordinate across engineering, partnerships, services, and support.
Aruba Networks sold wireless networking equipment, but the whole product for their beachhead of university campuses required far more than access points: network management software, security integration with campus authentication systems, support for lecture-hall density, and training for campus IT staff. Aruba assembled all these components, including partnerships with campus IT service providers, to deliver a turnkey solution that competing wireless vendors could not match in this niche.
Lithium's core product was a community platform, but the whole product for its beachhead of customer-enabled tech support required integration with existing support ticketing systems, gamification to motivate community contributors, moderation tools, analytics to measure support deflection, and professional services to design the community structure. Lithium worked with each beachhead customer to ensure the entire support ecosystem was functional before measuring results.
Infusionsoft targeted small businesses needing marketing automation, but the whole product required more than software: it needed campaign templates, training programs for non-technical users, a partner ecosystem of marketing consultants who could implement campaigns, and integrations with e-commerce and email platforms. The core technology was only about 20% of what small business owners actually needed to achieve marketing automation results.
Theodore Levitt introduced the whole product concept in his 1983 book The Marketing Imagination, arguing that customers do not buy products -- they buy complete solutions to their problems. What differentiates market leaders is not usually the core product but the surrounding ecosystem of services, support, and integration that makes the core product useful.
Moore recognized that Levitt's model was particularly relevant to technology markets, where the gap between the generic product and the whole product is often enormous and invisible to the engineers who built it. He integrated the whole product concept into his chasm-crossing framework, making it the centerpiece of the 'invasion force' that companies must assemble to win pragmatist customers.