CX Orchestration & Connected CX Automation
Internal Demo & Sales Enablement Machine

Internal workspace for deciding what to lead with now, what to refine into customer-showable demos, and what reusable assets should strengthen 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 what should advance as a customer-showable generic demo and which reusable assets should strengthen future CX Orchestration and Connected CX Automation offerings.

  • Compare items using stage, readiness, reuse leverage, and next action.
  • This workspace stops at demo and sales-enablement readiness.
  • 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 A focus: move concepts into customer-showable generic demos and reusable demo assets.

Lead now
0
Count of Green items with strategic priority = Now
Demo ready
0
Items already customer-showable in generic form
Needs demo design
0
Items that still need workflow-to-demo packaging
High reuse
0
Items with High reuse leverage

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 A — Demo / sales enablement

Key fields: stage_demo, demo_readiness, sales_enablement_readiness, best_for, next_action_demo

Use this view to decide what should become customer-showable generic demos and which items best support current enablement.

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 concept to demo

Use the arrows to move across pipeline stages.
Incubate0
Demo Design0
Demo Ready0
Reusable Pack0
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 demo-stage decisions: what to lead with now, what to refine into customer-showable generic demos, and which reusable packs should be hardened to support future solution development.

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 demo pipeline.

Readiness: how mature the item is for the current workspace.

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.

Demo definition for this workspace

A demo is a customer-showable, generic, business-relevant workflow demonstration that proves the use case and orchestration approach well enough for customer, partner, or sales conversations.

It is not yet a customer-specific implementation.