Demo Plan — White Cap + World of Concrete (End of 2026)

March 23 Rebaseline

Demo narrative must remain synchronized with:

  1. 00-vision-and-success-criteria.md for canonical status.

  2. 03-phase-plan-p0-p5.md for execution gates.

  3. 38-marketing-product-research-sprint.md for approved messaging and objection handling.

Demo narrative direction

  1. Lead with validated workflow value, not speculative capability.

  2. Use a dual-track narrative where appropriate: desktop modernization progress plus web strategy clarity.

  3. Keep a fallback script that avoids blocker-dependent claims.

Note: This plan is a working draft. Some technical details (exact file provenance, build parity, vendor timelines, pricing, and Autodesk product capabilities) may need verification as we inventory the full legacy tree and validate behavior in modern environments.

Outcome goal

By December 2026, have a stable, rehearsed demo that proves:

  • The modernized ConstructiVision installs cleanly

  • Works on modern AutoCAD (target 2026)

  • Produces a complete deliverable package (panel book, reports, outputs)

  • Is credible for partner rollout and show visibility

Demo Readiness Gate (Parity Completion)

Demo readiness depends on the 45-tb11-parity-test-plan M2 parity gate closing successfully (target: May 19–26, 2026). The parity scorecard (≥95% of 76 testable items PASS/PARTIAL) directly determines which workflows can be safely demonstrated:

  • If M2 closes on time: Full live demo with all core workflows. Demo script covers panel creation → output generation → export pipeline.

  • If M2 is delayed: Fallback demo script uses only workflows that passed G1–G3 (menu routing, dialog appearance, field functionality). Avoid demonstrating any workflow that failed G4 (XRecord persistence) or G5 (drawing operations).

  • If M2 does not close by Jun 30: Escalate to recorded-demo-only strategy. No live demo of TB11 source-mode — use PB11 VLX-mode on XP VM as fallback.

The 12 BLOCKED and 4 DEFERRED items from doc 45 should be excluded from the demo script regardless of M2 outcome.

White Cap (partner demo / pilot)

Target (Q4 2026)

  • 1—2 curated workflows with “wow factor”

  • Minimal setup time

  • A pilot agreement structure (even informal) for feedback

What White Cap should see

  • “Before vs after” time savings

  • Output professionalism (panel book package)

  • Reliability: no hacks, no VM, no manual file copying

Pilot success metrics

  • Install time < 30 minutes

  • First output generated < 1 hour from install

  • 80% of pilot users can run without engineer help

World of Concrete readiness (end of 2026)

World of Concrete 2027: January 19—21, 2027 (Education: Jan 18—21)
Demo Freeze: December 15, 2026

The operational intent is:

  • stable, demo-ready product by Dec 15, 2026

  • a repeatable “demo kit” that can travel

Demo kit contents

  • Demo laptop image (clean, documented)

  • Installer + offline license path (if needed)

  • Sample datasets (minimal + standard)

  • Printed one-pagers / QR linking to docs (draft)

  • Recorded fallback demo video (insurance)

Demo script (10 minutes)

  1. Install / activate (or show “already installed”)

  2. Open sample project

  3. Run core workflow commands

  4. Generate outputs (panel book + reports)

  5. Show cloud-ready artifact pipeline preview (if P4 MVP exists)

Demo rehearsal cadence

Starting in Q3:

  • monthly rehearsal In Q4:

  • weekly rehearsal

Every rehearsal produces:

  • issues list

  • time-to-complete metric

  • “demo risk” score

Deliverables

  • demo/script.md

  • demo/datasets/

  • demo/one-pagers/ (draft content)

  • demo/rehearsal-log.md