Trade Demo Command Center

Before the demo

The Demo Command Center is the sales talk track for Trade — a tight, buyer-facing companion to the operator golden paths. Use it to walk a buyer through four core paths without overclaiming SFTP, regulator filing, or ERP integration.

Read the Launch Readiness Center first to confirm which modules you may exercise live, which are beta, which are pilot, and which must stay closed.

Demo rules

• Start with core LIVE paths first — clean transaction, denied-party match, evidence — before touching beta or pilot modules.
• Mention beta and pilot labels plainly. Buyers respect honesty more than polish.
• Keep SFTP off unless explicitly staged. The product is fail-closed there for a reason.
• Use Help articles as proof, not promises — open the article in a tab while you demo.
• If asked about ERP integrations, say CSV and manual intake are live and deeper connector work is scoped per deployment.

Demo path 1 — Clean transaction (LIVE)

Purpose — show the normal intake, screening, and certification workflow on a complete, no-hold row.

Talk track — Trade helps the team see transaction risk quickly, move clean work forward, and keep a defensible record.

Proof point — every disposition produces a screening reference, an audit row, and a regenerable evidence pack on demand.

• Click — Dashboard then Transactions, pick a clean row, review disposition and audit, then optionally jump to Evidence.
• Recovery — if the chosen row has any banner, swap rows; do not improvise an explanation on a clean demo.
• Follow-up — /help/transactions for the full workspace guide.

Demo path 2 — Possible denied-party match (LIVE)

Purpose — show a held transaction and the human adjudication workflow with audit rationale.

Talk track — when something needs human review, Trade makes the queue, the rationale, and the audit trail visible to the right people.

Proof point — holds are visible, adjudications are role-gated, and every decision writes an append-only audit row scoped to the organization.

• Click — Dashboard then Approvals, open a held item, walk claim and decision, point to the audit row.
• Recovery — if no held row exists in the demo dataset, walk the empty state and link to Help; do not invent a hit.
• Follow-up — /help/approvals for the full adjudication workflow.

Demo path 3 — License required (BETA)

Purpose — show license awareness, drawdown context, and the BETA posture honestly.

Talk track — Licensing is beta but already shows the workflow direction: connect license records, conditions, drawdowns, and transaction context, without overpromising regulator automation.

Proof point — operators see remaining capacity and conditions per license, link transactions explicitly, and never silently overdraw.

• Click — Licenses then a specific license, point to conditions and balance, then a license-required transaction.
• Recovery — anchor on JSON packet today, Empowered Official uploads at DECCS or SNAP-R; never promise dates for direct filing.
• Follow-up — /help/licenses for the headers, lines, and drawdown workflow.

Demo path 4 — Evidence request (LIVE)

Purpose — show the strongest product value: proof on demand for a chosen transaction.

Talk track — Trade is built to answer three questions: what did we screen, what did we decide, and what proof do we have? Evidence packs make that answerable in seconds.

Proof point — evidence packs assemble from live workflow data; they reflect what was actually stored, including any intentional fail-closed gaps.

• Click — Evidence, pick a transaction with stored workflow data, generate or regenerate the pack, walk the contents.
• Recovery — if the pack shows gaps, frame intentional fail-closed transparency as the point, not a defect.
• Follow-up — /help/evidence for pack generation and audit-trail anchoring.

Demo data readiness

Demo data readiness is not product state. It is a pre-call checklist. If the sample data is missing, do not improvise the claim — fall back to Help articles and walk the workflow honestly.

• Clean transaction sample (LIVE) — needs one transaction with complete classification, complete party data, no holds, screening complete, certifiable disposition, and audit rows. Ready when you can open Transactions and explain why the row is clear without banners. If missing, walk the list and the Help article; do not pretend a held or incomplete row is clean.
• Held / possible denied-party sample (LIVE) — needs one transaction in review or hold state, a visible screening or policy reason, an adjudication path, and tied audit rows. Ready when you can open Approvals and explain why human review is required. If missing, walk the empty state and the Approvals article; do not invent a hit.
• License-required sample (BETA) — needs one active license with conditions or remaining balance, plus one linked or license-required transaction with drawdown context. Ready when you can open Licenses and show why licensing matters. If missing, frame Licensing as BETA and open the Licenses article; do not claim GA.
• Evidence-ready sample (LIVE) — needs one transaction with stored workflow data, a screening result, a recorded decision, a generable or reviewable evidence pack, and audit rows. Ready when you can show proof assembled from stored workflow data. If the pack shows gaps, frame fail-closed transparency as the point; do not invent missing evidence.

What we will not claim

If a buyer pushes on any of these, route to the Launch Readiness Center and the Capabilities not available yet article rather than improvising a date.

• No production-ready SFTP transport.
• No live ERP integration; no direct SAP, Oracle, or NetSuite sync.
• No direct regulator filing; no automated BIS or DDTC submission.
• No outbound CDD SFTP support; outbound SFTP for CDD is a stub.
• No PDF license application packets — Trade emits JSON.
• No invented evidence — packs reflect what was stored, including gaps.