Customer Value Chain Analysis (CVCA)
Customer Value Chain Analysis (CVCA) is a product definition method that maps every party involved with a product and the flows between them: money, products and services, information, and complaints. It is done before requirements are written, and its purpose is to identify which customers are critical to the product's success and what each of them values.
- What it produces
- A one-page diagram of parties and flows, and a short list of critical customers
- When to use it
- Start of product definition, and again when the business model changes
- Time required
- One to two hours for a first draft with a small team
- Origin
- Stanford University, Manufacturing Modeling Laboratory (ME317)
What is Customer Value Chain Analysis?
Most products involve more than one customer. The party that pays is often not the party that uses the product, and neither may be the party that decides whether it can be sold at all. A CVCA makes these parties and their relationships visible on one page.
The diagram has two elements. Parties are drawn as boxes: the company itself, its buyers, end users, payers, channel partners, suppliers and regulators. Flows are drawn as arrows between the boxes, with a symbol showing what moves along each arrow.
The analysis answers three questions:
- Who is involved with this product, beyond the end user?
- What does each party give and receive?
- Which parties must be satisfied for the product to succeed, and what does each of them value?
CVCA was developed by Krista Donaldson at Stanford University's Manufacturing Modeling Laboratory under Professor Kosuke Ishii and Sherri Sheppard, and taught in the graduate course ME317, Design for Manufacturability. The reference description is Donaldson, Ishii and Sheppard, "Customer Value Chain Analysis," Research in Engineering Design 16 (2006).
CVCA notation
- MoneyPayments, funding, reimbursement
- Product or serviceThe physical product, software or service delivered
- InformationData, specifications, diagnoses, approvals, regulation
- ComplaintsFeedback and dissatisfaction, which show where problems surface
Two drawing rules keep the diagram readable. Each party gets one box. Each flow gets its own line, so two parties that exchange both money and a product are connected by two separate arrows, each pointing in the direction of the flow.
How to do a Customer Value Chain Analysis
- Step 01
State the business model. Write down what the product is, who is assumed to buy it, and how the company expects to be paid. These are assumptions the diagram will test.
- Step 02
List the parties. Include everyone who buys, uses, pays for, installs, services, approves or regulates the product. Include the company itself.
- Step 03
Draw the relationships. Place each party in a box and connect the ones that interact.
- Step 04
Label the flows. For each connection, draw one arrow per flow and mark it as money, product or service, information, or complaint.
- Step 05
Identify the critical customers. Follow the money back to its source and the complaints to where they land. Parties that fund the chain, decide the purchase or can block the product are critical, whether or not they ever touch it.
- Step 06
Carry the results forward. Write the value proposition for each critical customer. These become the customer inputs to the Project Priority Matrix, Quality Function Deployment and, later, Failure Mode and Effects Analysis.
CVCA examples
Two examples show why the end user alone is not enough to define a product.
EKG machine
An EKG machine is bought by a hospital, operated by a nurse or technician, applied to a patient, interpreted by a physician and ultimately paid for by an insurer. No single party is "the customer."
- MoneyPayments, funding, reimbursement
- Product or serviceThe physical product, software or service delivered
- InformationData, specifications, diagnoses, approvals, regulation
- ComplaintsFeedback and dissatisfaction, which show where problems surface
| From | To | Flow |
|---|---|---|
| EKG manufacturer | Hospital | EKG machine |
| Hospital | EKG manufacturer | $ |
| Hospital | Nurse / technician | $ (salary) |
| Nurse / technician | Patient | EKG test (service) |
| Nurse / technician | Physician | I (EKG trace) |
| Physician | Patient | I (diagnosis) |
| Patient | Insurer | $ (premiums) |
| Insurer | Hospital | $ (reimbursement) |
| Nurse / technician | Hospital | ! |
| Hospital | EKG manufacturer | ! |
What the map shows: the patient benefits from the machine but neither selects it nor pays the manufacturer. The hospital makes the purchase, the insurer's reimbursement rules shape what the hospital can afford, and the operator's complaints reach the manufacturer only through the hospital. A product definition built around the patient alone would miss the purchase decision, the reimbursement constraint and the operator's daily experience.
Aircraft engine
An airline orders engines from the engine manufacturer, but the engines are delivered to the airframer, which installs them and delivers the finished aircraft to the airline. The regulator oversees all three.
- MoneyPayments, funding, reimbursement
- Product or serviceThe physical product, software or service delivered
- InformationData, specifications, diagnoses, approvals, regulation
- ComplaintsFeedback and dissatisfaction, which show where problems surface
| From | To | Flow |
|---|---|---|
| Airline | Engine manufacturer | $ (engine order) |
| Engine manufacturer | Airframer | Engine |
| Airframer | Airline | Aircraft with engines |
| Airline | Airframer | $ |
| Passengers | Airline | $ (fares) |
| Airline | Passengers | Flight (service) |
| Airline | Pilots | $ (salary) |
| Pilots | Airline | Flying the aircraft (service) |
| Regulator (FAA) | Engine manufacturer | I (certification, oversight) |
| Regulator (FAA) | Airframer | I (certification, oversight) |
| Regulator (FAA) | Airline | I (oversight) |
| Passengers | Airline | ! |
What the map shows: for the engine manufacturer, the money comes from the airline while the product goes to the airframer. The engine has to meet the airline's operating needs, such as fuel burn and maintenance cost, fit the airframer's integration requirements, and pass certification by a regulator that buys nothing. Passengers and pilots never deal with the engine manufacturer, yet their experience drives what the airline asks for.
CVCA for software and AI products
The method was developed for hardware, and it applies without modification to software, services and AI systems. The parties change. For an AI product, the map commonly includes:
- Model providers, whose pricing, terms and model changes flow into the product
- Data sources and data labelers, who supply the information the system depends on
- Cloud and compute providers, often the largest cost flow
- The enterprise buyer, including security, legal and procurement reviewers who can block a purchase
- End users, who may differ from the buyer
- People affected by the system's outputs, who may never use it directly
- Regulators and standards bodies, such as those enforcing the EU AI Act or, in the United States, the FTC
Drawing these parties early shows dependencies and approval paths that a user-only view leaves out.
Common mistakes
- Mapping only the end user. The buyer, payer and approver are often different parties.
- Leaving out regulators and other non-paying parties. A party that exchanges no money can still stop the product.
- Combining flows on one arrow. Separate lines make it clear who pays whom and what is delivered in return.
- Omitting complaints. Complaint flows show where dissatisfaction collects and whether it reaches the company.
- Treating the diagram as the result. The result is the list of critical customers and their value propositions.
- Drawing it once. The map changes when the channel, pricing model or regulation changes.
Where CVCA fits in product definition
CVCA is the first of six structured design methods.
- Customer Value Chain Analysis
- Project Priority Matrix
- Quality Function Deployment
- Function-Structure & Cost-Worth Analysis
- Morphological Analysis & Pugh Selection
- Failure Mode & Effects Analysis
The critical customers identified here become the "who" in Quality Function Deployment, and the flows between parties suggest where failures would be felt in Failure Mode and Effects Analysis.
See all six methods →Frequently asked questions
What is Customer Value Chain Analysis?
Customer Value Chain Analysis (CVCA) is a product definition method that maps every party involved with a product, including buyers, users, payers, partners and regulators, and the flows of money, products, information and complaints between them. It is used early in development to identify which customers are critical and what each one values.
Who developed CVCA?
CVCA was developed by Krista Donaldson at Stanford University's Manufacturing Modeling Laboratory under Professor Kosuke Ishii and Sherri Sheppard, and taught in the graduate course ME317, Design for Manufacturability. The reference paper is Donaldson, Ishii and Sheppard, 'Customer Value Chain Analysis,' Research in Engineering Design, 2006.
How is CVCA different from Porter's value chain?
Porter's value chain describes the activities inside one company that add value, such as operations, logistics and marketing. CVCA looks outside the company: it maps the separate parties around a product and what is exchanged between them.
How is CVCA different from a stakeholder map?
A stakeholder map lists the parties and often ranks them by influence or interest. CVCA also draws the specific flows between parties, one line per flow, so it shows who pays whom, who receives the product, who supplies information and where complaints go.
When should a team do a CVCA?
At the start of product definition, before requirements are written. It is also worth redrawing when the business model, channel or regulatory situation changes.
What comes after CVCA?
The critical customers identified in the CVCA become inputs to the Project Priority Matrix and to Quality Function Deployment, where their needs are translated into measurable requirements. The same map later informs Failure Mode and Effects Analysis.
Reference
Donaldson, K. M., Ishii, K., and Sheppard, S. D. (2006). "Customer Value Chain Analysis." Research in Engineering Design, 16(4), 174–183.
Maintained by Larry Chao, PhD, Sovereign Pivot. Last updated September 2026.
Map the value chain for your product.
Sovereign Pivot works with deep tech and AI-native founders to define the product, starting with the customer value chain.