# W/ ISV Academy — The Compliant Product Claim

**Room:** ROOM-07 · **Portfolio stage:** Later  
**Audience:** Independent software vendors, SaaS product teams, implementation partners, sales engineering, and customer success

> A product claim is not a customer responsibility model.

## Consequential question

Can product and customer teams derive the same bounded PCI responsibility statement from one deployment?

## Fictional scenario

A fictional ISV markets a PCI-compliant payment module deployed into customer cloud accounts with optional support, webhooks, identity integration, and managed updates.

**Pressure:** Sales, product, implementation, and the customer each mean something different by ‘handled by the platform.’

## Five working artifacts

- [ ] Claim decomposition record
- [ ] Deployment-pattern matrix
- [ ] Product/customer responsibility model
- [ ] Evidence handoff contract
- [ ] Change-notification covenant

# Four practice moves

## 1. Decompose

**Prompt:** Separate product capability, hosted service, deployment, configuration, assurance, and customer outcome claims.

**Output:** Claim stack

## 2. Instantiate

**Prompt:** Apply the claim to an exact service, mode, region, feature set, and customer deployment.

**Output:** Deployment profile

## 3. Assign

**Prompt:** Map provider, ISV, implementer, and customer activities with evidence and retained duties.

**Output:** Responsibility model

## 4. Handoff

**Prompt:** Specify what the customer receives, must configure, must prove, and must revisit after change.

**Output:** Customer assurance packet

## Bounded decision output

One deployment-specific customer responsibility statement that survives product, implementation, and customer review.

## Pilot format

One product team and one customer implementation team independently derive the statement from the fictional deployment and compare omissions.

## Stop rule

Stop if the room becomes product certification, vendor endorsement, a customer compliance result, or marketing-copy optimization.

## Reviewed reading route

- WACK-CONTENT-0124
- WACK-CONTENT-0099
- WACK-CONTENT-0128
- WACK-CONTENT-0158
- WACK-CONTENT-0100

## Program boundary

W/ Practice Rooms is practitioner-developed commissioning material. It is not PCI SSC guidance, not an assessment, not a compliance result, not an accredited curriculum, not professional certification, and not legal, financial, healthcare, public-sector, employment, or product-validation advice. Every room uses fictional facts and requires its named pilot before expansion.