Record the walkthrough once. Keep the documentation.
Record a walkthrough and turn it into notes on how it works.
- For
- The only template whose subject is your product rather than a user — founders and PMs narrating their own screen for onboarding, sales, or handover.
- Leads with
- Record with screen
- Preset goals
- 5 — the most a project holds, all editable
- Also uses
- The Chrome extension — record the tab you are already in
You are the one presenting, so the ways in start with your own screen and your narration over it.
You already give this walkthrough. To a new hire, to a customer, to whoever inherits the feature. The recording is the easy part; what disappears is everything you explained around it — and that is the part someone needs next week.
The capture routes this project puts in front of you.
All seven capture methods work in every Sense project. This template only decides the order — and for concept demo, that order starts here.
Capture your screen and your voice together, so what you say lands next to what you did.
Record a voice note in the browser — the fastest way to get a thought down right after a session.
Drop in audio, video, or a document you already have and we will transcribe it.
5 preset goals, written for this situation.
A goal is an extraction prompt: it tells the AI what to pull out of every transcript in this project. These ship with the template and are yours to rewrite — a project holds up to five.
What the product does as demonstrated on screen, not merely named — and it notes when something was only talked about rather than shown.
The ordered end-to-end sequence, the branches you mentioned, and the steps you skipped or glossed over.
The vocabulary the demo teaches, in your exact wording. Naming you use inconsistently is surfaced rather than quietly normalised.
The benefit asserted for each part, quantified promises, and comparisons to the old way — recorded as made, without judging them.
The limits you mentioned in passing: "for now", "eventually", "this part is still manual".
One line becomes an action item, without losing the words.
Nothing here is a summary. Each hop keeps a link back to the one before it, so the item at the bottom still opens onto the sentence at the top.
- 01Capture
Someone hits record on the tab they are already in, screen and voice together. A walkthrough is one person narrating their own screen.
app.example.comREC1:08Finish - 02Signal
It lands as a transcript — timestamped, searchable, with the recording attached.
0:03NilsThis is the intake card — everything a team captures lands here first, whatever the source.0:11NilsYou drop a recording in and we transcribe it, pull out the quotes that matter, and group them into findings automatically.0:24NilsExporting all of this to a doc comes later — that part isn't wired up yet. - 03Anchor
Read against this project's 5 goals, the passage that answers one gets lifted out verbatim and tagged. The anchor keeps its offsets into the transcript.
0:03NilsThis is the intake card — everything a team captures lands here first, whatever the source.0:11NilsYou drop a recording in and we transcribe it, pull out the quotes that matter, and group them into findings automatically.0:24NilsExporting all of this to a doc comes later — that part isn't wired up yet.Tagged toCore functionality - 04Insight
Anchors group into a finding. One insight often draws on more than one goal.
Capture to findings runs unattended: drop a recording, get transcript, quotes, and grouped findings
3 anchorsCore functionalityWorkflow steps - 05Action item
The finding becomes a backlog item on the workspace kanban, still linked to the anchor it came from.
Document the capture-to-findings flow for onboardingTodoTraces back to Nils at 0:11
Every walkthrough becomes a signal, and what the product does — plus what you promised and flagged in passing — lands in your backlog.
Action items live on the workspace backlog, not inside a single project — so a fix that came out of a testing session sits next to one that came out of an interview, each carrying its own evidence.
Documentation as a byproduct.
- The throwaway hedge you said out loud — "that part isn't wired up yet" — becomes a real item instead of disappearing with the recording.
- Called a thing three names in twelve minutes? Concepts & terminology surfaces your own inconsistent naming, in your exact wording.
- Talked about a feature without showing it? That gets noted as talked-about, not demonstrated, so the write-up does not overstate the demo.
Record the tab you are walking through
The extension carries the capture for this template. Hit record on the tab you are demoing, narrate over it, and the walkthrough arrives in this project as a signal — with your voice on the same clock as the screen.
- One click from the tab you are already demoing — no separate recorder to set up
- Screen and voice on the same clock, so what you say lands next to what you showed
- Picks the project before you record, so the walkthrough arrives already filed
The Chrome extension and the feedback widget solve the same problem for different audiences. This template ships with the extension; collecting user feedback ships with the widget.
All seven capture methods are available in every project. A template only decides what you see first.
Rewrite, remove, or add to the preset goals at any time. A project holds up to five.
A new workspace is seeded with one project per template. Nothing is locked behind a choice you make on day one.
Every anchor carries its citation offsets into the transcript, so each claim traces back to the words that were said.
Every workspace starts with this project already in it.
Create a workspace and all six projects are seeded for you — this one included, goals and capture order set up. Nothing to configure before your first capture.
Your first run in this project ends on “Record a walkthrough”. The project tour spotlights the recorder, so the first run ends with a walkthrough already captured.