The whole product model skill

The Whole Product Model

Pragmatist buyers do not buy products. They buy solutions to problems. The gap between what you ship and what they need is called the "whole product gap," and it is the primary reason technology companies fail to cross the chasm.

This reference provides the complete whole product framework, gap analysis tools, partnership strategies, and planning templates to ensure your offering meets the pragmatist's actual buying criteria.

Table of Contents

1. The Four Layers of the Whole Product
2. Whole Product Gap Analysis Template
3. Common Whole Product Gaps
4. Partnership Strategy for Filling Gaps
5. Industry Examples of Whole Product Evolution
6. Whole Product Planning Canvas
7. Prioritizing Which Gaps to Fill First

---

The Four Layers of the Whole Product

Layer 1: Generic Product

What you ship out of the box. The core technology, the downloadable software, the API, the thing your engineering team built.

Characteristics:

• What appears on your product spec sheet
• What you demo in sales calls
• What your engineers are proud of
• What innovators and early adopters evaluate

Reality check: This is the only layer that matters to innovators. For everyone else, it is necessary but insufficient.

Layer 2: Expected Product

The minimum configuration of products and services necessary for the buyer to achieve their basic purchasing objective.

Includes:

• Core product plus essential configuration
• Basic documentation and getting-started guides
• Standard integrations with common tools
• Minimum viable support (email, knowledge base)
• Basic security and compliance features

Reality check: If you don't deliver the expected product, customers churn within 90 days. This is table stakes.

Layer 3: Augmented Product

The product fleshed out to provide the maximum chance of achieving the buyer's purchasing objective. This is what pragmatists actually evaluate when making a buying decision.

Includes everything in Expected, plus:

• Deep integrations with the buyer's existing stack
• Professional services for implementation and migration
• Training programs and certification
• Industry-specific templates and configurations
• Dedicated support with SLAs
• Best practices documentation and playbooks
• Peer community and user groups
• Partner ecosystem for complementary capabilities

Reality check: This is where the chasm lives. Early adopters buy the generic product. Pragmatists require the augmented product. Most companies fail to bridge this gap.

Layer 4: Potential Product

The product's room for growth as more complementary products come to market and the product evolves.

Includes:

• Platform extensibility and custom development
• Advanced features on the roadmap
• Ecosystem of third-party add-ons
• Future integrations and partnerships
• Innovation pipeline

Reality check: The potential product matters for long-term positioning and valuation, but pragmatists buy based on the augmented product today, not the potential product tomorrow.

Whole Product Gap Analysis Template

Use this template to identify the gaps between what you ship and what your beachhead segment needs.

Step 1: Map the Buyer's Complete Need

Interview 5-10 target customers in your beachhead segment. Ask:

• What does your end-to-end workflow look like today?
• What tools and systems are involved?
• Where are the manual handoffs and pain points?
• What would a complete solution look like?
• What would prevent you from adopting a new solution?
• What would need to be true for you to recommend this to a peer?

Step 2: Complete the Gap Analysis

Category	What Pragmatists Need	What We Ship Today	Gap	Severity (H/M/L)	Fill Strategy
Core functionality
Data integration
Migration/onboarding
Training
Support
Documentation
Security/compliance
Reporting/analytics
Customization
Industry adaptation
Ecosystem/integrations
Professional services

Step 3: Classify Each Gap

For each gap identified, classify the fill strategy:

• Build: Add to your product roadmap (highest control, highest cost)
• Partner: Find a partner to provide the capability (moderate control, moderate cost)
• Recommend: Suggest a third-party tool and document the integration (lowest control, lowest cost)
• Accept: Acknowledge the gap and position around it (only for low-severity gaps)

Common Whole Product Gaps

Integration Gaps

The most frequent gap. Pragmatists live in an existing ecosystem. Your product must work within it, not replace it.

Typical integration requirements:

• CRM (Salesforce, HubSpot, Dynamics)
• ERP (SAP, Oracle, NetSuite)
• Identity provider (Okta, Azure AD, Google Workspace)
• Data warehouse (Snowflake, BigQuery, Redshift)
• Communication (Slack, Teams, email)
• File storage (Google Drive, SharePoint, Dropbox)
• Workflow automation (Zapier, Make, Power Automate)

Pragmatist expectation: Native, maintained integrations -- not "you can use our API to build it yourself."

Training and Enablement Gaps

Pragmatists need their teams to be productive quickly. They don't have time to figure it out.

Minimum training whole product:

• Role-based onboarding guides (admin, end user, manager)
• Video tutorials for common workflows
• In-app guided tours
• Certification program for power users
• Train-the-trainer materials for enterprise rollouts
• Regular webinars on new features and best practices

Support Gaps

Early adopter expectation: Slack channel with the founder. Responses in minutes.

Pragmatist expectation: Tiered support with defined SLAs, escalation paths, dedicated account managers for enterprise, and a searchable knowledge base.

Support Tier	Response Time	Channel	For
Self-service	Instant	Knowledge base, community	All customers
Standard	24 hours	Email, chat	Paid customers
Priority	4 hours	Phone, chat	Enterprise customers
Critical	1 hour	Dedicated line	Business-critical issues

Migration and Onboarding Gaps

Pragmatists are replacing something. The migration from their current solution must be low-risk and well-supported.

Migration whole product:

• Data migration tools and scripts
• Migration planning guide with timelines
• Parallel running support (old and new system)
• Rollback plan if migration fails
• Dedicated migration support team
• Post-migration validation and cleanup

Compliance and Security Gaps

Pragmatist organizations have procurement and security review processes. Missing any of these is a deal-killer:

• SOC 2 Type II certification
• GDPR compliance documentation
• Data processing agreements
• Single sign-on (SSO) support
• Role-based access control (RBAC)
• Audit logging
• Data residency options
• Penetration test results
• Business continuity / disaster recovery documentation
• Insurance certificates (errors and omissions, cyber liability)

Partnership Strategy for Filling Gaps

Types of Whole Product Partners

Partner Type	What They Provide	Example
Technology partners	Integrations, complementary features	CRM, data warehouse, identity providers
Service partners	Implementation, training, customization	System integrators, consultancies
Content partners	Industry expertise, templates, best practices	Industry associations, domain experts
Channel partners	Distribution, trust, existing relationships	VARs, MSPs, consultancies

Partner Selection Criteria

• Do they serve our beachhead segment?
• Are they trusted by pragmatist buyers?
• Is the partnership mutually beneficial (not one-sided)?
• Can we execute a joint go-to-market?
• Do they fill a high-severity gap?
• Is the integration maintainable long-term?

Partnership Engagement Levels

Level	Commitment	Example
Listing	Directory listing, minimal integration	"Works with Salesforce" badge
Integration	Built and maintained API integration	Bi-directional data sync
Co-marketing	Joint content, webinars, case studies	"Better together" campaigns
Co-selling	Joint sales calls, bundled offerings	Combined solution for segment
Embedded	Deep product integration, shared roadmap	White-labeled capabilities

Industry Examples of Whole Product Evolution

Example: Project Management Software (2010s)

Layer	2012 (Generic)	2016 (Expected)	2020 (Augmented)
Core	Task lists, boards	Task lists, boards, timelines	Full work management platform
Integrations	API only	Slack, GitHub	200+ native integrations
Templates	None	Basic templates	Industry-specific templates
Support	Email only	Email + chat	Tiered support with SLAs
Training	None	Help docs	Academy, certification
Compliance	None	Basic security	SOC 2, HIPAA, GDPR
Services	None	Basic onboarding	Professional services team

Example: Marketing Automation (2000s-2010s)

Generic product: Send emails to a list.

Whole product for mid-market B2B pragmatists:

• Email sending with deliverability management
• CRM integration (Salesforce native)
• Lead scoring and routing
• Landing page builder (no developer needed)
• Campaign templates by industry
• ROI reporting tied to revenue
• Implementation services (60-90 day onboarding)
• Dedicated customer success manager
• User community and annual conference
• Agency partner ecosystem for execution
• Compliance with CAN-SPAM, GDPR

The distance between "send emails" and the full list above is the whole product gap. HubSpot and Marketo won their respective segments by closing this gap faster than competitors.

Whole Product Planning Canvas

Use this canvas to plan your whole product for the beachhead segment:

Section 1: Buyer Context

• Target segment: [Your beachhead]
• Primary buyer persona: [Title, role, responsibilities]
• Current solution: [What they use today]
• Primary pain: [The specific problem costing them money/time]
• Switching cost: [What it takes to move from current to you]

Section 2: Whole Product Map

Component	Required?	Current State	Gap	Owner	Timeline
Core product	Yes			Engineering
Integration: [specific]	Yes			Engineering
Integration: [specific]	Yes			Partner
Migration tools	Yes			Engineering
Onboarding program	Yes			Customer Success
Training materials	Yes			Product Marketing
Support infrastructure	Yes			Support
Documentation	Yes			Technical Writing
Compliance: [specific]	Yes			Security
Professional services	Maybe			Services
Industry templates	Maybe			Product

Section 3: Partnership Plan

Gap	Potential Partners	Partnership Level	Status

Section 4: Timeline and Milestones

Milestone	Target Date	Dependencies
Whole product v1 (minimum for first pragmatist sales)
Whole product v2 (competitive with incumbents)
Whole product v3 (market-leading for segment)

Prioritizing Which Gaps to Fill First

Not all gaps are equally important. Use this prioritization framework:

Priority Matrix

	High frequency (most buyers need it)	Low frequency (some buyers need it)
Deal-breaker (won't buy without it)	Priority 1: Fill immediately	Priority 2: Fill within 6 months
Preference (nice to have)	Priority 3: Fill within 12 months	Priority 4: Monitor, fill if needed

Identifying Deal-Breakers

After every lost deal, ask:

• What was the primary reason you chose not to move forward?
• Was there a specific capability or requirement we did not meet?
• What would have changed your decision?

Track these responses. When the same gap appears in 3+ lost deals from your beachhead segment, it is a Priority 1 gap.

The 80% Rule

You do not need to fill every gap before selling to pragmatists. You need to fill the gaps that matter to 80% of your beachhead segment. The remaining 20% are either edge cases or can be handled with workarounds that pragmatists will accept if the core value proposition is strong enough.

The danger of perfectionism: Waiting until the whole product is "perfect" means you never sell to pragmatists. Ship the 80% whole product, win your first 5-10 pragmatist customers, and iterate based on their feedback.