User Guide · CRM Demo

The StructuredOps™ CRM Governance Demo

A complete walkthrough of the three-stage governance simulation: Scout (Diagnostic), Architect (Blueprint Design), and Enablement (Governance Monitoring). Understand every control, every verdict, and every handoff — before touching your live CRM.

Current version: v1.0 · Phase 2
Last updated: April 2026
Reading time: ~10 min
Audience: Founders, Sales Ops, CRM Admins
Quick Start

Just want to try it?

Go to structuredopsai.com/crm-demo, select a scenario from the bar at the top, click Run Scout Assessment, and follow the guided mission steps. The entire Scout → Architect → Enablement journey takes under four minutes with no sign-up required.

Open the Demo →

Overview

The CRM Demo is a fully deterministic simulation of the StructuredOps™ governance methodology. It runs entirely in your browser — no API calls, no account required, no latency from an AI model. The "intelligence" you see is a pre-authored Scenario Library: expert narrations written once and stored locally, so the demo costs $0 in API fees regardless of how many people use it simultaneously.

The demo proves a single claim: a CRM environment can only be safely automated after it has been structurally governed. It does this by making you live the three-stage lifecycle in sequence — you cannot reach Architect without a Scout verdict, and you cannot reach Enablement without a signed Blueprint.

The Three-Stage Governance Pipeline

STAGE 01
📡
Scout
The Diagnostic — assess your CRM environment against three governance questions
STOP / GO verdict
STAGE 02
📐
Architect
The Blueprint — design six governance artefacts from your Scout data
Locked until Scout GO
STAGE 03
🛡️
Enablement
The Governance — monitor live agents, trigger scenarios, manage kill-switches
Locked until Blueprint Sign-off
Why the gates matter

The stage locks are not cosmetic. They mirror real StructuredOps™ production logic: an Enablement Agent cannot be deployed without a signed Blueprint, just as a Blueprint cannot be generated without a GO verdict from the Scout. The demo teaches the methodology by enforcing it.

What the Demo Is — and Is Not

✓ What it is
A governed simulation of the three-stage lifecycle, using pre-authored expert narrations. Identical to the production UI and logic flow. Safe for unlimited use at $0 cost.
✗ What it is not
Not a live connection to your HubSpot portal. Not a real AI model call during the demo. Phase 3 production will integrate real HubSpot OAuth and Claude API calls — the demo simulates that behaviour.

Getting Started

The demo is available at structuredopsai.com/crm-demo. No login, no browser extension, and no installation is required. It works in any modern browser — Chrome, Firefox, Safari, Edge — on desktop or tablet. Mobile is supported but the full dashboard experience is optimised for screens 900px wide and above.

First-time walkthrough (4 minutes)

  1. 1
    Choose a scenario
    In the amber scenario bar below the navigation, select one of the three pre-built governance failures: Stale Pipeline Record, Invalid Stage Transition, or Missing Mandatory Document. This pre-fills the Scout form with a matching CRM profile. You can also type your own data if you prefer.
  2. 2
    Run the Scout Assessment
    Click Run Scout Assessment. The engine applies the three StructuredOps™ governance questions and produces a STOP / GO verdict with a Readiness Score out of 10. This takes approximately 5 seconds.
  3. 3
    Proceed to Architect
    If the verdict is GO (score ≥ 7), the Proceed to Architect Agent button appears. Click it. Notice the green connection line light up in the Lifecycle Sidebar — and the handoff pill on the Architect screen confirming your Scout data was transferred automatically.
  4. 4
    Generate Blueprint Artefacts
    Click Generate Blueprint Artefacts. Watch all six governance documents build sequentially (A1 through A6). This takes approximately 5 seconds with a shimmer animation per artefact.
  5. 5
    Sign off the Blueprint
    Tick all three sign-off conditions and click Compute STOP / ENABLE Verdict. An ENABLE verdict unlocks Stage 3 and boots the Enablement Audit Log with a live-looking system startup sequence.
  6. 6
    Trigger a scenario in Enablement
    In Stage 3, click ▶ Run Scenario in the left panel. The Audit Log populates with a pre-authored L4 Narration, Rule Reference, and verdict. Then toggle the Master Kill-Switch — watch all agents suspend and the audit log record a HALTED event in real time.
Tip — Guided Mission Panel The collapsible Guided Mission panel at the top of the content area tracks your progress across all three stages. It shows a checkmark when each mission step is complete. If you close it accidentally, click Show Mission in the sidebar footer.

Interface Tour

The dashboard is composed of five persistent UI zones that remain visible across all three stages.

Top Bar
Displays the StructuredOps™ wordmark, live demo status badge, version number, and a direct link to open the demo in a new tab. The top bar never changes between stages.
Lifecycle Sidebar
Persistent vertical navigation showing all three stages with icons, lock states, and completion indicators. Click any unlocked stage to navigate. Connection lines between stages light up green when a stage is complete.
Guided Mission Panel
A collapsible three-step task panel that tracks your progress. Each step shows the task, a hint, and a checkmark on completion. Collapse it once you no longer need it.
Scenario Bar
An amber bar below the mission panel with three scenario trigger buttons. Selecting a scenario pre-configures the Scout form and the Enablement narration library to match the chosen governance failure.
Stage Content Area
The main scrollable region that changes per stage. Scout shows the assessment form and results. Architect shows the artefact generation and sign-off. Enablement shows the split agent-panel / audit-log view.
Handoff Flash
When a stage transition completes (Scout → Architect, or Architect → Enablement), a green flash animation briefly illuminates the content area to signal that data has been transferred between agents.

Stage 1 — Scout Agent

The Scout Agent applies the three universal StructuredOps™ assessment questions to your CRM environment and produces a Readiness Score from 1–10 with a binary GO or STOP verdict.

Completing the Assessment Form

The form is divided into four sections. The three required fields (marked with an asterisk) are Company name, Pipeline stages, and Deal ownership clarity. All other fields improve scoring accuracy but are optional for the demo.

The Three Assessment Questions

Q1
Ownership Clarity
Is the decision-maker clear? A single named owner must exist per deal stage, pipeline, and routing rule. Shared inboxes, rotating ownership, and undocumented handoffs all reduce this score. Weight: 35%.
Q2
Workflow Explicitness
Is the workflow step-by-step? Entry and exit criteria must be explicit and reproducible — not tribal knowledge. Undocumented stage transitions and rep-discretion advancement both lower this score. Weight: 35%.
Q3
Failure Mode Definition
Is there a defined failure mode? Every workflow must specify what happens when data is missing, malformed, or contradictory. Silent failures and reactive-only escalation paths reduce this score. Weight: 30%.
Using the Scenario Pre-fill If you select a scenario from the amber bar before opening Stage 1, the Scout form auto-populates with a realistic CRM profile matching that scenario. You can edit any field before running the assessment — the scenario pre-fill is a starting point, not a constraint.

Reading Your Results

After the 5-second processing animation, the results panel renders with four components:

  • 01
    Verdict Banner
    A large GO or STOP word with your Readiness Score out of 10. Green indicates readiness score ≥ 7 (GO threshold). Red indicates the CRM environment needs remediation before automation. The banner also shows the next available action.
  • 02
    Sub-Scores (Q1, Q2, Q3)
    Three cards showing individual scores for each governance question, each with an animated progress bar. The weighted composite formula is: Score = (Q1 × 0.35) + (Q2 × 0.35) + (Q3 × 0.30). A score below 7 in any individual question flags a structural gap that the Architect must address.
  • 03
    Red Flags
    A registry of specific structural gaps, each tagged with the affected Workflow Node, the governing question (Q1/Q2/Q3), a severity rating (HIGH or MEDIUM), and a plain-language description. These red flags are automatically loaded into the Architect's work queue when you proceed to Stage 2.
  • 04
    Priority Actions & Safe Nodes
    Three ranked remediation actions to act on before deployment, followed by a list of workflow nodes already cleared as safe to automate — these pre-populate into Artefact A5 in the Architect stage.
Export PDF Report (Professional Tier)

The Export PDF Report button (with the lock icon) opens a preview modal describing the branded, client-ready PDF export available in the Professional tier. In the production product, this generates a full assessment report with executive summary, flag registry, and remediation roadmap suitable for sharing with stakeholders.

Stage 2 — Architect Agent

The Architect Agent takes your Scout GO verdict and generates six governed artefacts — the complete Blueprint for your CRM environment. This Blueprint is the single source of truth that all Stage 3 Enablement Agents read on every startup and every polling cycle.

Stage Lock Stage 2 is locked until Stage 1 returns a verdict. If the Scout returns STOP, you can still enter Architect in Review Mode — but the Generate Artefacts button is disabled until the underlying structural gaps are addressed. In the demo, you can proceed regardless to explore the interface.

The Active Handoff Card

At the top of Stage 2, a green handoff card displays your Scout results with an ↳ HANDOFF FROM SCOUT AGENT pill. This confirms that the following data was transferred automatically — you did not re-enter it:

  • Company name, CRM platform, and industry
  • Individual Q1, Q2, and Q3 sub-scores
  • All Red Flags (pre-loaded into the Architect work queue)
  • Safe-to-automate workflow nodes (pre-loaded into Artefact A5)
  • Pipeline stages (pre-loaded into Artefact A1)

The amber Active Handoff notice below the card itemises exactly what was transferred and into which artefacts.

The Six Blueprint Artefacts

Clicking Generate Blueprint Artefacts starts a sequential generation animation. Each of the six artefacts transitions from PENDINGGENERATINGCOMPLETE with a shimmer effect. Total generation time is approximately 5 seconds in the demo.

A1
Decision-Gate Pipeline Map
Entry and exit criteria, named owners, and gate types (PROCEED / HOLD / STOP) for every pipeline stage. In the production product, this renders as a live Mermaid.js diagram from structured JSON.
A2
Lead Routing Ownership Matrix
A named owner role for every lead category, territory, and deal-value threshold. Fallback owners are defined for every routing rule — eliminating the team-inbox failure mode.
A3
SLA Governance Model
Commitment definitions, breach thresholds, pre-breach actions (triggered at 80% of the window), and escalation owners for every SLA tier. Sourced from your Q3 failure-mode answers.
A4
Approval Authority Document
Autonomous approval limits and escalation tiers by deal value. Defines exactly when a rep can close autonomously versus when Sales Manager or VP approval is required — with hour-based SLAs per tier.
A5
Automation Boundary Document
An explicit allowlist of every action an Enablement Agent is permitted to perform, with a DENY_ALL default posture. Pre-populated with your Scout's safe-to-automate nodes. Anything not on the list is blocked.
A6
Failure Mode Register
A per-action failure scenario library: what the agent does for every failure case (HOLD, ESCALATE, BLOCK), who gets notified, and what message they receive. Sourced from your Q3 Red Flags and clarification answers.

Blueprint Sign-off

After reviewing the artefacts, scroll to the Sign-off panel. You must check all three conditions before the Compute STOP / ENABLE Verdict button activates:

  1. Artefact completeness: confirm A1–A6 accurately reflect your CRM governance requirements.
  2. A5 DENY_ALL posture: acknowledge that Enablement Agents will operate exclusively within A5 permissions.
  3. Immutability acknowledgement: confirm you understand the Blueprint version is immutable post-sign-off. Material changes require a new version and full redeployment.

Clicking the verdict button produces an ENABLE banner with the Blueprint ID, version, and timestamp. The Lifecycle Sidebar immediately shows Stage 3 as unlocked. The Enablement Agent boots automatically when you navigate to Stage 3 — you will see the system startup sequence in the Audit Log.

Blueprint Hash Immutability

In the production product, every Blueprint is assigned a SHA-256 hash at sign-off. All five Enablement Agents verify this hash on every startup and every polling cycle. A CRM schema change after sign-off (stages added, roles renamed, routing rules modified) causes a hash mismatch and triggers an immediate BLUEPRINT_MISMATCH halt across all agents. The demo simulates this with the Simulate CRM Change button visible after sign-off in the Architect prototype.

Stage 3 — Enablement Agent

Stage 3 is the governance monitoring environment. It shows five Enablement Agents in real time, allows you to trigger governance scenarios, manage kill-switches, and read a live Audit Log. In the demo, this stage becomes available only after the Blueprint is signed in Stage 2.

The Split-Panel Layout

Stage 3 uses a two-column layout. The left panel contains the Agent Control Panel with individual and global kill-switch controls, the Scenario Trigger interface, and the Enterprise Tier tease for Multi-Pipeline Mode. The right panel is the scrolling Audit Log.

Kill-Switch Controls

The EA-1 Lead Triage Agent row in the left panel has a small toggle switch — the Master Kill-Switch for that agent. Toggling it to the ON (red) position immediately:

  1. Changes EA-1's status badge from ACTIVE to SUSPENDED.
  2. Aborts any pending EA-1 actions (shown in the Audit Log as a queued event).
  3. Writes a [SYSTEM] Master Kill-Switch ACTIVATED entry to the Audit Log with a timestamp and an L4 narration.
  4. Disables the Trigger Scenario button — no new scenarios can fire while the agent is suspended.

Toggle it back to resume. The Audit Log records the resumption event. The Suspend All and Resume All buttons at the bottom of the left panel apply the same logic to all five agents simultaneously — useful for simulating a system-wide governance halt.

In Production In the live product, a kill-switch suspension immediately halts all pending HubSpot property writes, task creation, and external notifications from the suspended agent. The suspension is logged with the operator's identity, reason code, and timestamp in the immutable audit trail. Resumption requires selecting a resolution type from a governed dropdown.

Reading the Audit Log

The Audit Log on the right auto-scrolls to the latest entry. Each entry contains:

Field Description Example
AUDIT-ID Sequential unique identifier for this audit event AUDIT-0001
AGENT-ID Which Enablement Agent processed the event EA-1
Verdict badge The governance decision for this record ESCALATE HOLD BLOCK
Rule Reference The Blueprint rule that triggered this verdict R-102, R-505
Affected Record The CRM record or workflow node that was evaluated Lead Record #4421
Owner Role The named role assigned responsibility for this event Sales Ops, System
Narration The L2/L3/L4 narration explaining the verdict in plain language See Narration Tiers below

Narration Tiers

Each audit entry that requires human notification includes a tiered narration — the pre-authored expert explanation of the governance verdict:

L2
Rule Reference: States the specific Blueprint rule violated and the immediate action taken. Used for routine HOLD events with a clear single-rule trigger. Most concise narration level.
L3
Contextual: Adds the reason why the rule was triggered, referencing the CRM data condition that caused it. Used for ESCALATE events where context accelerates resolution.
L4
Synthesis: Full contextual analysis including probability of issue recurrence, downstream risk, and a specific recommended action. Used for ESCALATE events routed to senior stakeholders. Highest narration tier — designed to stand alone as a self-contained briefing.

In the demo, narration content is pre-authored in the Scenario Library and rendered locally at $0 API cost. In Phase 3 production, L3 and L4 narrations are generated by the Claude API with the proprietary StructuredOps™ Narration System Prompt stored as a Cloudflare environment variable — never exposed in the client bundle.

Governance Scenarios

The Scenario Library contains three pre-built governance failures, each designed to demonstrate a different enforcement pathway. Select a scenario from the amber bar to pre-fill the Scout form and the Enablement trigger queue.

Scenario CRM Failure Type Scout Verdict EA-1 Verdict Rule Ref Narration Tier
Stale Pipeline Record Deal with 0 activity for 14+ days in "In Progress" STOP 3/10 ESCALATE R-102 L4
Invalid Stage Transition Lead → Closed Won skip, bypassing Discovery and Demo STOP 5/10 BLOCK R-505 L3
Missing Mandatory Document $250k deal missing A2-Alpha discovery artefact GO 7/10 HOLD R-210 L2
Why these three? Each scenario demonstrates a different severity level and verdict type: ESCALATE (highest urgency, routed to a human for review), BLOCK (action prevented by the agent entirely), and HOLD (record paused pending human data completion). Together they cover the full spectrum of governance enforcement the Enablement Agent can apply.

Running a Custom Assessment

You are not limited to the three pre-built scenarios. Deselect all scenarios in the scenario bar and complete the Scout form manually with your own CRM details. The assessment will still run through the Scenario Engine — the verdict and narration will match whichever pre-built profile most closely aligns with your answers. Full live Claude API assessment is available in Phase 3 production (not the demo).

Commercial Features

The demo includes two deliberate commercial overlays — visible locked features that preview Professional and Enterprise tier capabilities. These are informational only; no payment is required and no gateway is triggered.

🔒 Export PDF Report (Professional)
Visible as a locked button in the Scout results panel. Clicking it opens a modal previewing the branded PDF report — executive summary, full flag registry, and remediation roadmap. Available in the Professional tier.
🔒 Multi-Pipeline Mode (Enterprise)
Visible as a greyed-out toggle in the Enablement Agent left panel with an "ENTERPRISE TIER" label. In production, this allows monitoring governance across multiple HubSpot pipelines from a single dashboard. Requires Enterprise tier.
Lead Qualification via Demo

The demo itself serves as a lead qualification mechanism. A prospect who navigates the full Scout → Architect → Enablement flow without assistance has demonstrated they understand the governance methodology. The business email prompt (available when access gating is enabled) converts that journey into a qualified lead automatically — no sales call required. See the implementation roadmap for Cloudflare Access configuration details.

Frequently Asked Questions

Does the demo connect to my HubSpot account?
No. The demo is entirely self-contained in the browser. No HubSpot OAuth is initiated, no CRM data is read, and no external API is called. The Phase 3 production product will introduce real HubSpot integration — the demo simulates that behaviour with pre-authored data.
Is the AI in the demo actually calling Claude?
No. The demo uses a deterministic Scenario Engine — pre-authored JSON objects mapped to governance triggers. The "1.5-second thinking" pause is a simulated latency delay to maintain the feel of a live AI system. No API key is needed and no API costs are incurred during the demo. Phase 3 will introduce real Claude API calls for live narration generation.
Why does Stage 2 lock unless I get a GO verdict?
The lock enforces the StructuredOps™ methodology. A Blueprint cannot be generated from a CRM environment that has not passed the minimum governance threshold — doing so would produce an unreliable artefact set. This mirrors the production behaviour exactly. In the demo, you can still navigate to Architect in Review Mode by clicking the greyed-out stage — the Generate button simply remains disabled.
Can I reset the demo and start again?
Yes. The New Assessment button in the Scout results panel resets Stage 1 entirely. To reset the full three-stage lifecycle, reload the page — all in-memory state is cleared and you return to the initial Scout form.
What is the Readiness Score formula?
Readiness Score = (Q1 × 0.35) + (Q2 × 0.35) + (Q3 × 0.30), rounded to the nearest integer. A score of 7 or above produces a GO verdict. Below 7 produces STOP. The weighting reflects that Ownership Clarity and Workflow Explicitness are equally foundational, while Failure Mode Definition — though slightly lower-weighted — is the most common gap in practice.
How do I share the demo with a specific prospect?
Send them directly to structuredopsai.com/crm-demo. If you need access control (e.g., sharing with a verified prospect without making the demo public), Cloudflare Access Zero Trust can be configured on the /crm-demo route to require a verified email or access code. See the Implementation Roadmap for configuration details.
Why does the audit log show a boot sequence when I reach Stage 3?
This simulates the Enablement Agent startup sequence that runs in production: Blueprint ID loading, hash verification, logic gate activation, and readiness confirmation. The entries mirror real production log output — they demonstrate that the agent verifies its Blueprint before accepting any instructions. This is the "Aha!" moment that shows the Blueprint is not just a document — it's an active governance contract loaded by the agent at runtime.

Glossary

TermDefinition
Blueprint The signed, immutable set of six governance artefacts (A1–A6) that defines how a CRM environment should behave. Generated by the Architect Agent and verified by all Enablement Agents on every cycle.
Blueprint Hash A SHA-256 fingerprint of the Blueprint JSON at sign-off. Any material change to the CRM schema causes the recomputed hash to mismatch — triggering an immediate agent halt.
DENY_ALL The default posture of Artefact A5. No agent action is permitted unless it is explicitly listed on the allowlist. The reverse of a permissions model — everything is blocked unless approved.
Enablement Agent One of five automated governance processes (EA-1 through EA-5) that monitor and enforce Blueprint rules across the CRM. Each agent has a specific trigger, permitted action set (A5), and failure mode register (A6).
Governance Failure A CRM condition that violates a Blueprint rule — triggering a HOLD, ESCALATE, or BLOCK verdict from an Enablement Agent. The three demo scenarios each represent a distinct governance failure type.
Kill-Switch A per-agent toggle (or global control) that immediately suspends an Enablement Agent's ability to process events or write to the CRM. All pending actions are aborted and logged. The agent resumes only on explicit operator instruction.
Narration Tier The depth level of the audit explanation: L2 (Rule Reference — brief), L3 (Contextual — adds reason), L4 (Synthesis — full analysis with recommended action). Higher tiers are used for higher-severity events routed to senior stakeholders.
Readiness Score A composite 1–10 score produced by the Scout Agent: (Q1 × 0.35) + (Q2 × 0.35) + (Q3 × 0.30). GO threshold is 7. Below 7 = STOP.
Scenario Engine The deterministic simulation layer that replaces live API calls in the demo. Pre-authored JSON objects map governance triggers to expert narrations, producing $0 API cost at unlimited scale.
Stage Gate A hard lock between lifecycle stages. Stage 2 requires a Scout GO verdict. Stage 3 requires a Blueprint sign-off. The gates cannot be bypassed — they enforce the methodology structurally.

Last reviewed: April 2026 · StructuredOps™ AI
Open the Demo → ← Back to Guides