90-second screen-recorded demo — Engagement Canvas → Preview-as-board

The post-meeting follow-up artifact. Send 30 minutes after the first partner conversation, while the meeting is still fresh.

Audience: the partner you just met with + whoever they choose to forward it to inside their firm.

Output target: ≤90 seconds, ≤30 MB, MP4 720p or 1080p. No music. Founder voice only. Single take preferred — re-shoot rather than splice.

Setup (do once before recording):

• Open Arx Engagement Canvas.html in a clean browser window. Hide bookmarks bar, browser extensions, dev tools. Use a dark-mode browser theme so the in-product chrome looks clean.
• The page seeds with the Cisco-shape default (5 functions, 19,900 agents, ~$1.92B annualized recovery on the balanced scenario). Confirm this on screen before recording.
• Open Arx Board View.html?mode=projection&engagement=northstar in a second tab — verify the projection-watermark banner displays. Close the tab; the recording will navigate to it from the Canvas.
• Audio: external mic, no environmental noise. Record audio first, sync to screen capture if your tool supports it.

---

Beat sheet (5 beats × ~18s)

0:00 – 0:15 — Open: name the problem

On screen: Engagement Canvas, fully loaded with seeded Cisco-shape data. Cursor visible.

Say: *"This is what we'd put in front of [Customer]'s exec team if you and I co-delivered the engagement we talked about. It's not a slide — it's the working model. Watch what happens when I plug in actuals."*

Don't: narrate the UI. The viewer can see it. The voice is the partner's value-add framing.

---

0:15 – 0:30 — The Canvas, demonstrated

On screen: Cursor moves to the Sales tile. Drag the headcount slider — change from 1,500 to 2,000, then back. The right rail's recovery + agents + cost numbers recompute live. Audience sees this happen.

Say: *"Each function tile has the customer's actual headcount, the agent-to-human ratio you're proposing, and the function-specific productivity multiplier. Move a slider — the cost, productivity, connector requirements, and compliance overlays all recompute. This is the customer's number, not a [Firm] template."*

Click: the "Aggressive" scenario toggle on the right rail. The recovery number jumps from $1.92B to ~$2.4B. Click back to "Balanced."

Say: *"Three preset scenarios. Customer's CFO can see the conservative-aggressive band, not just a single point estimate."*

---

0:30 – 0:50 — The board view

On screen: Cursor moves to the right rail's "Preview as board →" button. Click it. The Board View opens with the warn-banded PROJECTION watermark across the top.

Say: *"This is the moment that matters. Click 'Preview as board' — and you're in the customer's CEO seat in their next board meeting, six months in. Cost recovered. Productivity gain. Audit defensibility. Open risk register. Plan-versus-actual against your modeled cohorts."*

Pause briefly while the page renders. Let the audience read the cards. Don't talk over the visuals.

Say: *"Every card has a one-sentence narration the CEO can read aloud. The numbers come from the engagement plan I just modeled. The watermark up top tells everyone in the room this is a projection — when you sign the contract, the engagement becomes active in ARX and these numbers get replaced with live operating data, refreshed every minute."*

---

0:50 – 1:10 — The defensibility hook

On screen: Scroll down to the Audit Defensibility card and the footer line. Hover briefly over block_28402_e1f3...a921.

Say: *"This is what your customer's CISO needs to see. Auditor verifies the chain integrity directly from the customer's own S3 bucket. They never call ARX. We give them a CLI; they walk the Merkle proofs themselves. Seventy-eight of one hundred thirteen SOC 2 controls auto-mapped to the line of code that produced the evidence, hash-pinned to the ARX release. This is the part that turns a pilot into a procurement."*

---

1:10 – 1:30 — Close: the partner ask

On screen: Stay on the Board View. Don't navigate away. Slow zoom out (or stay still — depends on your recording tool).

Say: *"That's roughly seventy-five seconds of what would be a thirty-minute working session in [Customer]'s boardroom. The Engagement Canvas, the Board View, the audit chain, the Cedar policy library — all real, all demonstrable. If you can put one named [Customer] prospect in front of us in the next two weeks, we'll co-deliver the working session and you'll close that engagement this quarter, not next. The brief is in your inbox; the calendar invite goes out today."*

End on: the Board View visible, watermark visible. Don't fade. Don't outro music.

---

Total time: ~1:30 (90 seconds)

The five beats above add to ~85 seconds of spoken content with ~5 seconds of natural pauses between beats. If the recording exceeds 100 seconds, drop one of these:

• The slider demonstration in beat 2 (the partner can intuit it from the static shot)
• The aggressive-scenario toggle in beat 2 (mention only verbally)
• The footer line walkthrough in beat 4 (let the audit-chain pill speak for itself)

---

What not to include in the recording

• No mention of "AIUC-1 Type II readiness assessment." Save for the technical follow-up. The 90-second demo is a sales artifact, not a compliance artifact.
• No model output / generated text. Don't show a chat with ChatGPT or Claude. The Engagement Canvas is the hero; LLM chat is not the demo.
• No mention of competitors by name. Don't say "unlike Microsoft Defender" or "unlike LangSmith." The brief already does that. The demo is positive.
• No mention of pricing. That's the second meeting.
• No engineer-speak. Don't say "Cedar PDP" or "JWT-SVID" or "Merkle root." Say "policy decision" / "agent identity" / "audit chain."
• No founder bio. The demo is the product, not Mershard.

---

What goes in the email when you send it

Subject: *ARX × [Firm] — 90-second walkthrough of what we discussed*

Body (3–4 lines max):

> *[Partner name],* > > *Promised follow-up from this morning. Ninety seconds — what the [Customer] working session would actually look like with the Engagement Canvas + Board View on screen.* > > *If your team wants to see it driven by their own numbers, I can spin up a sandboxed engagement for [Customer] inside 24 hours. Calendar invite for the deeper session is attached for next week's Mon/Wed/Fri windows we discussed.* > > *— Mershard*

Attachments: the .mp4 (or a private Loom / Vimeo unlisted link if file size is an issue).

---

Recording tools that work

• macOS: QuickTime screen recording + Audacity for audio cleanup. Free.
• Loom: fastest if you don't need a downloadable file. Watermark removed on paid plan.
• OBS Studio: higher quality, steeper learning curve. Use the Window Capture source pinned to the browser window so you don't catch desktop chrome.
• Riverside / Descript: if you want to retake individual sentences without re-recording the whole thing. Useful if your delivery isn't first-take clean.

Whatever tool you use, do not add captions, lower thirds, intro animations, or zoom transitions. The demo's credibility comes from the production looking unproduced. A senior partner watching a polished marketing video knows it's marketing; a senior partner watching a clean screen recording with a steady founder voice perceives it as a product, which is what we're selling.

---

Re-record triggers

Re-record if any of these happen:

• Voice tremor or audible breath / sigh
• Browser shows a tooltip, modal, or extension popup
• Slider drag overshoots and you correct visibly (re-shoot — looks unrehearsed in a bad way)
• Total runtime > 100 seconds
• The recovery number on the Engagement Canvas doesn't match the seeded $1.92B (means the localStorage state got polluted; clear and reload)

If two takes fail, take a 10-minute break and come back. The 90-second-clean-take quality bar is real; do not ship a 90-second-with-one-stumble demo to a senior partner.