---
id: "concept-product-context-ai-adaptation"
type: "concept"
source_timestamps: ["§ Product"]
tags: ["product-strategy", "b2b-vs-b2c"]
related: ["org-sap", "org-adobe", "prereq-erp-integration", "framework-sap-customer-journey"]
definition: "The necessity of tailoring AI sales and adoption tools to the specific complexity, integration requirements, and buying mechanics of a given product."
sources: ["commercial"]
sourceVaultSlug: "hbr-seg-commercial"
originDay: 5
articleStem: "hbr-foci-64-ai-broaden-customer-base"
sourceUrl: "https://hbr.org/2025/03/how-one-company-used-ai-to-broaden-its-customer-base"
sourceTitle: "How One Company Used AI to Broaden Its Customer Base"
---
# Product Context AI Adaptation

**Product Context AI Adaptation** is the principle that AI deployment must be **heavily customized to the specific nature of the product** and to how customers make purchasing decisions for it.

The authors contrast [[org-adobe|Adobe]] and [[org-sap|SAP]]:
- **Adobe's** cloud products do **not** require complex integration, so it can use a **freemium** model where AI analyzes free-trial usage to improve the product (product-led growth).
- **SAP's** ERP software requires **deep integration** with client business processes (see [[prereq-erp-integration]]), making a freemium model impossible.

Consequently, SAP had to adapt its AI strategy toward **personalized demos, guided tours, and automated business-case generation** (the **"Value One-Pagers"**) rather than product-led growth via free trials. This is why the [[framework-sap-customer-journey|customer journey]] is built around assisted evaluation rather than self-serve trial.

> **Enrichment check:** The contrast in product context and AI strategy is accurate and consistent with how ERP vs. PLG SaaS businesses operate; it aligns with Product-Led Growth literature (e.g., Wes Bush) explaining why complex ERP cannot run freemium. The term "Product Context AI Adaptation" itself is specific to the article.
