CX Orchestration & Connected CX Automation
Internal Commercialization & Product Readiness Machine

Internal workspace for deciding what should move from generic demo into pilot thinking, derivative configuration, named-solution analysis, pricing hypotheses, and future blueprint capture for the Launch and Extend solution families.

Demo / Sales Enablement Commercialization / Product Readiness Field Schema

How to use this workspace

Purpose: Use this workspace to decide which items should move from generic demo into pilot thinking, derivative configuration, packaging, pricing, and future blueprint capture for CX Orchestration and Connected CX Automation.

  • Compare items using stage, readiness, reuse leverage, and next action.
  • This workspace begins after an item is worth commercial attention.
  • Open Help for terminology and interpretation.
  • Open Instructions for the documentation process, source-of-truth model, and update sequence.

Portfolio logic

Green = lead now Blue = package next Orange = reuse everywhere

Lane = portfolio role. Stage and readiness show lifecycle state. Next action shows what should change next.

Workspace B focus: quantify pilot potential, derivative configuration, packaging, pricing, and future reference capture.

Pilot emerging
0
Items with pilot readiness marked Emerging
Strong named-solution candidates
0
Items marked Strong candidate
Package / analyze
0
Items currently in commercialization analysis
Reference gap
0
Items still lacking a customer reference or blueprint

Pipeline controls

Field schema used by this machine

Shared core fields

Identity: label, name, type, vertical

Portfolio role: lane, portfolio role, strategic priority

Structure: named solution family, workflow family, pattern families

Decision signals: reuse leverage, sensitivity, business clarity, incremental effort

Workspace B — Commercialization / product readiness

Key fields: stage_commercial, pilot_readiness, named_solution_readiness, pricing_status, reference_status, next_action_commercial

Use this view to decide what is worth pilot analysis, derivative configuration, pricing work, or named-solution elevation.

Intake and update model

Use the Excel intake template as the initial source of truth. One row = one item.

Recommended sheets: README, Inventory_Master, Lists_Validation, Schema_Guide.

New items should be added through intake first, then promoted or held using stage + readiness + next action.

Pipeline board — from pilot thinking to named-solution analysis

Use the arrows to move across pipeline stages.
Hold0
Incubate0
Package / Analyze0
Derivative Expansion0
Named Solution Review0
Supports Multiple Items0
Tip: click any card to inspect the decision record, reusable pattern links, promotion rule, and next action.

Instructions — using this machine

Standard sequence

1. Intake: record the item in the intake template first.

2. Machine: manage live stage, readiness, priority, and next action here.

3. Controlled artifact: create or revise the Architecture Matrix Seed Artifact when the narrative is mature enough to publish.

4. Technical design / delivery: create GitHub, runbooks, blueprint, LLD, pilot configuration, and implementation records only when the item enters execution work.

Source of truth

Intake template: structured baseline record.

Internal machines: live source of truth for stage, readiness, promotion, and next action.

Architecture Matrix Seed Artifact: controlled narrative snapshot at a specific version.

Technical design / delivery artifacts: source of truth for implementation detail.

What this workspace owns

This workspace owns commercialization-stage decisions: pilot thinking, derivative configuration, named-solution analysis, pricing logic, and future blueprint or reference capture.

What this workspace does not replace

This workspace does not replace the intake template, the Architecture Matrix Seed Artifact, or downstream technical design and delivery records.

Update rule

Update the machine first when stage, readiness, priority, or next action changes. Revise the DOCX artifact only when the controlled narrative or milestone state changes enough to require a new version.

Help — interpreting this machine

Lane meanings

Green: strongest lead demo story now.

Blue: strongest next packaging or commercialization candidate.

Orange: reusable internal accelerator or pattern asset.

Key fields on each card

Stage: where the item sits in the commercialization pipeline.

Readiness: how mature the item is for pilot, packaging, or named-solution work.

Reuse leverage: how strongly the item can power other use cases or offers.

Next action: what the team should do next to advance or hold the item.

Commercialization definition for this workspace

This workspace begins when an item is worth quantifying for pilot adaptation, derivative configuration, packaging, pricing, or future blueprint capture.

It is where you decide what should become a stronger repeatable offer or implementation pattern.