1 min lesson
Five questions for each segment
Choose the five-part sequence for one demo segment and explain why each part is needed.
Step 1 of 3
Each segment: problem, workflow, guardrail, metric, control
Each segment should answer five questions in order:
Learn more
Advanced table
The five-part segment structure
- Arc step
- Pain
- What you do
- Name a felt problem
- Example phrasing
- "Onboarding to this service takes a new hire two weeks."
- Arc step
- Workflow
- What you do
- Show Cursor doing the work
- Example phrasing
- "Watch Ask modeA read-only mode for asking questions about a codebase without changing files; the safe way to explore unfamiliar or legacy code. Press Enter for the full definition. map the call graph in 40 seconds."
- Arc step
- Guardrail
- What you do
- Surface the safety mechanism
- Example phrasing
- "The repository allowlist stops the agent from touching the payments module."
- Arc step
- Metric
- What you do
- Tie to a number they care about
- Example phrasing
- "Box reported 75% usage growth in six weeks after a staged rollout. Verify that vendor figure before quoting it."
- Arc step
- Control
- What you do
- Use the buyer's audit term
- Example phrasing
- "You just saw model and repository allowlists. Your security team owns those access controls."
| Arc step | What you do | Example phrasing |
|---|---|---|
| Pain | Name a felt problem | "Onboarding to this service takes a new hire two weeks." |
| Workflow | Show Cursor doing the work | "Watch Ask modeA read-only mode for asking questions about a codebase without changing files; the safe way to explore unfamiliar or legacy code. Press Enter for the full definition. map the call graph in 40 seconds." |
| Guardrail | Surface the safety mechanism | "The repository allowlist stops the agent from touching the payments module." |
| Metric | Tie to a number they care about | "Box reported 75% usage growth in six weeks after a staged rollout. Verify that vendor figure before quoting it." |
| Control | Use the buyer's audit term | "You just saw model and repository allowlists. Your security team owns those access controls." |
Do not stop at "it is safe." Name the mechanism in the buyer's own terms, such as separation of dutiesNo single person can author, approve and deploy the same change. The core control AI autonomy has to respect. Press Enter for the full definition., ITGCIT General Controls. The baseline IT controls auditors check: who can change what, how changes get approved and how systems are run. Press Enter for the full definition. evidence, blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition., allowlist or audit log. Exact language helps the buyer explain the workflow during a risk review.
Do not narrate keystrokes by saying, "Now I click here. Now I type this." Explain intent and control instead. "I'm asking it to plan first so a human reviews the scope before any code is written."
If a segment ends without a named control, pause and add it. A short correction is better than leaving the safety claim vague.
Learn more
Optional practice