# Customer or Partner Representative

Canonical page: https://apiopscycles.com/roles/customer-specialist

Language: en

Entity ID: customer-specialist

Contributes the business customer or partner perspective for the journey, value, and collaboration model.

## Decisions

- State the reusable integration capability hypothesis and intended outcome.
- Identify intended consumers, reuse scope, provider, owner, and optional supporting evidence.
- Record the initial implementation-style hypothesis without treating it as an architecture decision.
- Define critical assumptions, smallest validation experiment, and proceed-or-stop decision.
- Use shared journey, domain, value proposition, and business model canvases to gather technology-agnostic requirements and decide whether the capability should be reusable.
- Integration work often jumps too quickly to a technical pattern. This station keeps the team focused on consumer need, value, domain meaning, ownership, reuse potential, viability, assumptions, and validation before selecting APIs, events, files, streams, data products, direct integration, or hybrids.

## Outputs

- A testable integration capability hypothesis
- Consumers, reuse scope, provider, owner, and supporting evidence clarified
- Critical assumptions, validation step, and proceed-or-stop decision documented
- design-artifact
- documentation
- research
- roadmap
- Documented consumer requirements and onboarding expectations

## Recommended resources

- [Customer Journey Canvas](https://apiopscycles.com/resources/customer-journey-canvas.md)
- [Capability Value Proposition Canvas](https://apiopscycles.com/resources/capability-value-proposition-canvas.md)
- [Capability Business Model Canvas](https://apiopscycles.com/resources/capability-business-model-canvas.md)
- [Capability Validation Canvas](https://apiopscycles.com/resources/capability-hypothesis-canvas.md)
- [Capability Consumer & Producer Commitments Canvas](https://apiopscycles.com/resources/capability-consumer-producer-requirements-canvas.md)

## Participation by cycle and station

- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md) / [Capability Strategy](https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-product-strategy.md): core
- [Capability Productization Cycle](https://apiopscycles.com/cycles/capability-productization-cycle.md) / [Consumer & Producer Commitments](https://apiopscycles.com/cycles/capability-productization-cycle/stations/api-consumer-experience.md): lead
- [API Productization Cycle](https://apiopscycles.com/cycles/api-productization-cycle.md) / [API Product Strategy](https://apiopscycles.com/cycles/api-productization-cycle/stations/api-product-strategy.md): core
- [Integration Productization Cycle](https://apiopscycles.com/cycles/integration-productization-cycle.md) / [Integration Consumer & Provider Commitments](https://apiopscycles.com/cycles/integration-productization-cycle/stations/api-consumer-experience.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Process & Experience Requirements](https://apiopscycles.com/cycles/automation-cycle/stations/api-consumer-experience.md): core
- [Automation Cycle](https://apiopscycles.com/cycles/automation-cycle.md) / [Automation Rollout & Enablement](https://apiopscycles.com/cycles/automation-cycle/stations/api-publishing.md): core