SaaS copilot demo script (60–90s)
Film this for README proof and founder demos. Users feel remembered when session 2 answers without re-asking session 1.
Video status: not published yet. Until it is, this file and docs/DEMOS.md are the source of truth.
Story
A SaaS founder added AI chat to their product. Users kept repeating preferences every session. MemoryNode fixes that: prove recall in Playground, ship with SDK/API.
Shot list
| # | Duration | Visual | Narration |
|---|---|---|---|
| 1 | 5s | README or console Home | "Memory and context for AI products." |
| 2 | 10s | Sign in → Open Playground | "Prove it with a SaaS copilot in five minutes. No API key needed." |
| 3 | 15s | Playground — Save | "User prefers weekly email digests and dark mode UI." |
| 4 | 20s | Playground — Ask | "How should the dashboard feel for this user?" |
| 5 | 20s | Build context → Context ready panel | "Different question. Same user. Prompt-ready context — inject into your LLM." |
| 6 | 10s | Code snippet: remember + contextFor with ownerId | "Ship with SDK/API. Same owner_id as your app's user ID." |
Playground does not show an LLM reply. For a full copilot UX with OpenAI reply, use the SaaS copilot starter.
Do not
- Search the exact same text you just saved on turn 1
- Lead with embeddings, architecture diagrams, or MCP tool lists
- Show Playground as a chat app with model replies
Do
- Show the Context ready panel and recalled preferences
- Use stable
owner_id/default-userin Playground - Keep the story on continuity, not infrastructure
Local replay
export MEMORYNODE_API_KEY="mn_live_..."
node examples/sdk-quickstart/index.mjs
# Full UI: cd starters/saas-copilot-nextjs && pnpm dev (requires OPENAI_API_KEY)
Sync checklist
- README walkthrough links stay accurate
-
docs/DEMOS.mdwalkthrough table matches this script - Console Playground copy matches save → context flow